Audacity
Gnome Wave Cleaner
icecast.org

and many more software links at Wikipedia: List of Linux audio software

Systematic discography / by Lewis Foreman
Leddy hasn’t

Brian Rust’s guide to discography / by Brian Rust
Leddy hasn’t

Cataloger’s judgment / by Jay Weitz
Leddy hasn’t

Music librarianship at the turn of the century
MLA technical reports no. 27
Leddy hasn’t

Bibliographic relationships in music catalogs / by Sherry L. Vellucci
Leddy hasn’t

Cataloging phono recordings / by Jay E. Daily
Leddy hasn’t

Music librarianship : a practical guide / by E.T. Bryant
Leddy has – ML111 .B83 1985

At any rate, there’s not a lot in Bryant yet that I feel want specifically to make notes on. He has a separate chapter on recordings, which is my area of interest, and so doesn’t discuss them in detail in the chapters I’ve skimmed. He makes the case, I think convincingly, that music materials are different from normal monographs and serials, presenting their own set of challenges. And although Bryant’s book is getting a little old (the second edition I’m reading was 1985; the first, 1959), I find myself anticipating FRBR.

For the most part, library cataloguing practices are based on use. That’s to say that historically we have developed our catalogues based on direct experience, describing actual items in hand. You might say this is a bottom-up approach, building rich bibliographic resources one concrete entry at a time.

FRBR recognizes that, thanks to the historic development of our catalogues, we have learned and can apply a fairly sophisticated conceptual framework to the bibliographic universe. Sophisticated, but also relatively simple. From OCLC:

FRBR conceptualizes three groups of entities:

• Group 1 consists of the products of intellectual or artistic endeavor (e.g., publications).
• Group 2 comprises those entities responsible for intellectual or artistic content (a person or corporate body).
• Group 3 includes the entities that serve as subjects of intellectual or artistic endeavor (concept, object, event, and place).

The internal subdivision of Group One entities is important as well. FRBR specifies that intellectual or artistic products include the following types of entities:

• the work, a distinct intellectual or artistic creation
• the expression, the intellectual or artistic realization of a work
• the manifestation, the physical embodiment of an expression of a work
• the item, a single exemplar of a manifestation.

FRBR also specifies particular relationships between classes of Group One entities:

• a work is realized through one or more expressions
• — each of which is embodied in one or more manifestations
• — — each of which is exemplified by one or more items.

It’s at the end here, with the work – expression – manifestation – item relationships, that things get a little weird. In part, this is because for most “group one entities” the distinction between expression and manifestation is unclear. Shakespeare is often used as an example. Let’s do it bottom-up: we have in our library a number of items called “A Midsummer Night’s Dream” for whom an entity named “Shakespeare” is responsible. These items represent various editions by various publishers, and we would say that these editions are equivalent to manifestations. Now here’s where it gets tricky: if the edition is a manifestation, what would be considered an expression? Well, in this case, all these various print editions are most likely to be considered manifestations of a single expression, which might be called “Midsummer Night’s Dream as a play”. Seems redundant, I agree, but of course I chose this play for a reason: “Midsummer Night’s Dream” is also an opera, and this opera (based on the play) can be considered a different expression of the same work. So to reiterate from the top, down: Midsummer Night’s Dream is a work that has (at least) two expressions, “play” and “opera”. The expression “play” finds its embodiment in numerous manifestations in the various editions compiled and published over the years, and each of these manifestations is exemplified by any number of copies, or items.

Now it seems to me music materials lend themselves quite nicely to FRBR. Adaptations and alternate arrangements are common, and Bryant spends considerable energy discussing the challenges of cataloguing them. FRBR seems an elegant and simple solution, where each adaptation is viewed as an expression.

But the other thing that makes music materials fit nicely with FRBR is the work (pardon the pun) that has been done establishing authoritatively the identity of the works of the major composers. Take, for example, the works of Bach by BWV number, or Mozart by Koechel (or Köchel; you see how quickly things get tricky with music description). It’s almost as though the FRBR notion of “work” was borrowed from music.

Now if only there were a universal authority database for musical works. Then, when, cataloguing a music item, you could simply point to the work and get on with your day. For now, I guess we have the {deep breath} Indexes to the established titles, variant titles, obsolete uniform titles, and work numbers in the Library of Congress Name-Authority File for the works of Bach, Beethoven, Brahms, Haydn, Mozart, Schubert, Tchaikovsky, Telemann.

Integrating this into PHP is still a bit of a challenge for me after, what, a day-and-a-half of trying? Things to remember:

• Five basic steps to querying
1. Open the database connection
2. Select the database (it seems to me these first two have been combined in PHP’s mysqli functions, but I’m using a slightly older text)
3. Run the query
4. Fetch the query results into an array
5. Format and print the results
• Steps one through three require error handling
• The array that’s created in step three is an associative array in which the field name given in the query corresponds to the data returned. The array is processed one row at a time. There’s no need to include the table name, because the array corresponds to the query structure, rather than the table structure. This is easy to visualize if you think of the table that is displayed when a query is run from the mysql command prompt.

So it’s fairly simple to generate a flat html table from data that exist across multiple database tables. I’d like to figure out how to generate not-so-flat data; for example, suppose (just suppose) I had a database in which a number of books are stored in one table, and their chapters are stored in another. I’d like an output that would list the book, then the contents, for each book. The simple approach described above won’t do it. Maybe in another day-and-a-half this too will seem simple, but right now I just can’t quite figure it out.

Williams, Hugh E. and David Lane. Web Database Applications with PHP and MySQL. Sebastapol, CA: O’Reilly, 2004.

]]> http://www.pzed.ca/words/2008/01/30/mysql-and-php/feed/ 0 http://www.pzed.ca/words/2008/01/25/a-quick-note/ http://www.pzed.ca/words/2008/01/25/a-quick-note/#comments Fri, 25 Jan 2008 14:28:44 +0000 pzed http://www.pzed.ca/words/archives/2008/a-quick-note/ -> means “is being passed to.”

I’m sure I whipped right past this yesterday, but it makes sense to me now. The books I’m working through are both read to go to MySQL, but I don’t think I am. For most of the last two days I haven’t had access to the internet, so I put aside my music library reading to focus on the basics of PHP. These are, of course, related, and I soon have to get back the the music stuff. I want to keep at the PHP, though. It’s straightforward enough, but there are some conceptual aspects that I’m struggling with a bit, and I think another day’s immersion will do the trick.

• the usefulness of reusing code should be obvious to everyone!
• require() and include() call code from a file
• the main difference is that if something goes wrong, require() will return a fatal error, include() will only give a warning
• data need not be passed to the include because it is inserted in the code and executed as if present all along (I think)
• it’s a good idea to store include files outside the document tree, making them invisible to internet interlopers

functions

• “A function is a self-contained module of code that prescribes a calling interface, performs some task, and optionally returns a result”
• a library of user-defined functions can be stored in an include file
• data must be passed to a function using a parameter (see “scope”, below)
• user-defined functions must be declared, e.g.

  function say_hi()
  {
  echo 'hi';
  }

• function names can only contain letters, digits, underscores; cannot begin with a digit; and cannot be the same as an existing function name

scope

• scope controls where a variable is visible and useful
• variables declared inside a function are in scope from the declaration until the function’s end brace; this is function scope, the variables are local variables
• variables declared outside functions are in scope from the declaration to the end of the file, but not inside functions; this is global scope, the variables are global variables
• if a require() or include() statement is used within a function, function scope applies; if not, global
• the keyword global can be used to give a variable defined within a function global scope
• to allow functions to operate on global variables, use a pass by reference; the function receives a reference to the original variable, and any modifications performed on the reference are also performed on the original
• a pass by reference is created by prefixing an ampersand to the variable name in the function’s parameter list
• the return keyword can be used to stop a function, usually in response to some condition; return can also be used to return a value
• it is possible to call a function recursively, but this seems dangerous and doesn’t appear to have many benefits

Welling, Luke and Laura Thomson. PHP and MySQL Web Development. 2nd ed. Indianapolis: Sam’s, 2003.

Welling, Luke and Laura Thomson. PHP and MySQL Web Development. 2nd ed. Indianapolis: Sam’s, 2003.

1. built-in superglobal variables are visible everywhere within a script
2. global variables declared in a script are visible throughout the script, but not inside functions
3. variables used inside functions are local to the function
4. variables used inside functions that are declared as global refer to the global variables of the same name

I think this last should read “variables that are declared as global inside functions refer to the global variables of the same name”.

Welling, Luke and Laura Thomson. PHP and MySQL Web Development. 2nd ed. Indianapolis: Sam’s, 2003.

• three-tier architectures: client(browser) ↔ web server ↔ database server
• database applications are stateful, http is stateless
• the browser is a thin client, but it is possible to pass some of the work to the browser; e.g. JavaScript can be used to validate data before sending to the web server

I have a tendency to skim discussion of strings, variables, math, increments, expressions, operators. . . . Can’t I just look that stuff up? But I may need to think about character encoding and data entry. On to the object-oriented stuff:

• an object is a container in which data and functions can be bound
• a class is an object (?) that can be used to create many similar objects (it doesn’t help that the book I’m using keeps using the term package to describe the example of a class that is used†)
• a method is a function that belongs to a class (or package); a method can be called on an object that has been created by the class
• each specific object created by the class is an instance

† – It reads like this: An object is created by a package. A method (or member function) is called on an object. A method is provided by a package. The package in question is a class (aren’t all packages – should I just forget they ever said “package”?). An object created by a class is an instance. Now I get an example that shows me how to create a user-defined class that counts. There’s nothing like learning by doing. Back to class:

• variables defined within a class are member variables; functions, member functions.
• “The class definition defines how data and functionality are actually bound together—member variables and functions take their meaning from the class of which they’re a part.”
• class definitions can be placed in include files, the benefits of which aren’t listed in my text, but I imagine must include:
1. efficiency: the class needn’t be written out every time it’s needed, saving time and bandwidth
2. uniformity: by having only one copy of a class that could be used by multiple programmes, we ensure that the class always functions in the same way
3. security: the class remains on the server, and I’m guessing this might make things a little more secure in some way. Or not. I just can’t finish a list after only two items.
• a constructor is a method that is called when an object is created, and can be used to set up the initial state of the new object
• a destructor is a method that is called when an object is destroyed
• destructor functions are useful for housekeeping tasks like closing the connection to a DBMS or saving user preferences to a file

PHP also has private members variables, but it’s very rare that these ever become law.

I think I’ll save inheritance for tomorrow.

Williams, Hugh E. and David Lane. Web Database Applications with PHP and MySQL. Sebastapol, CA: O’Reilly, 2004.