We’ve reached the stage where we’re thinking about encoding our database. From a happy place (spiritually speaking) where eighteenth century London-based publishers churned out English collections of Scottish tunes in St Paul’s Church Yard, casually pirating one another’s work as only a newly-copyright-conscious culture could do, Karen now finds herself reading online manuals about MEI, FRBR and RDA.
Karen Finds Her Inner Geek
As it happens, she has already encountered the general principles, if not the practice, of FRBR and RDA, so she decided to start by diving into the Music Encoding Initiative. All was going well, making a reasonable amount of sense and generating some handwritten note-taking, when she decided to investigate printing out the MEI Guidelines so that she could use highlighter pen and generally make them her own. At 745 pages, generously illustrated with chunks of XML coding, this now seems a bit excessive. A marked-up pdf in Dropbox will be greener! Musicologist met Music Librarian – and both were delighted – when it became apparent that Chapter 22 is devoted to encoding paratext. Paratext (prefaces, dedications, indices etc) aren’t music, so it’s recommended to use the MEI FRBR module which accomodates text (in the strict term) as opposed to music.
And there are still the joys of FRBR (Functional Requirements of Bibliographic Records) and RDA (Resource Description and Access) ahead of us! Dear Fiddlers, these databases don’t just happen by magic, you know. We’re so lucky to have Zoltan guiding us through the technicalities!
(Karen the musicologist can’t help but wonder what the publishers Wright, Walsh and Thompson would have made of all this ….)