So You Need to Handle Authority Control in a Music Catalog
Most music librarians and catalogers hit a wall somewhere between AACR2 and RDA, especially when names get complicated. Ruth W. Tucker wrote about this space because it wasn't getting enough attention from mainstream cataloging guides. Her work focused on how to actually apply authority control when your records are full of composers with identical names, folk song collectors who went by pen names, or ethnomusicological field recordings where the original artist information was barely documented to begin with. Authority control in music libraries isn't the same as general authority control. The core problem is that music names are messier. A performer might also be a composer. A composer might use multiple name variants across different editions. Ethnomusicology collections add transliteration headaches that most general catalogs simply don't deal with. Tucker's approach was practical—she observed what actually happened in music libraries and wrote down the fixes rather than just restating Library of Congress Policy Statements.
Authority Control In Music Libraries Ruth W Tucker
Here's how to actually do the work without losing your mind. The first step is deciding which authority source you're using. For most music catalogers in the US, that's the Library of Congress Name Authority File (LCNAF) and the Union List of Artist Names (ULAN) for cross-referencing. If you're working with non-Western classical or folk traditions, you'll also need the Library of Congress Subject Headings for music and whatever transliteration standard your institution has adopted—ALA-LC is the default in the US. Don't skip the transliteration piece. I once spent three days tracking down a Bulgarian folk singer because someone had cataloged the name under a French transliteration variant while the LC authority file had it under the modern standard. The record surfaced only when I stopped searching the personal name and started searching the title field. When you're checking a new musician's name against existing authority records, you pull the name in its canonical form and search LCNAF first. If there's no match, you construct a possible heading and check cross-references in music-specific vocabularies. The trick Tucker kept emphasizing was that you need to check the context—not just the name string. Two people named "Tang Hai" could be completely different individuals: one a guzheng performer and one a contemporary composer. The authority record should include a scope note distinguishing them, and if it doesn't, you file it under the most specific heading you can justify and add a date or specialty qualifier.
Creating a new authority record for a music figure requires a different set of considerations than a standard authority record. You need to document the primary access point, variant names, works titles, and a biographical or scope note. For living performers, the biographical note is often thin—sometimes all you have is a discography page and a festival program. I learned to work with that by pulling together at least three independent sources before filing a new authority. My rule was simple: if I couldn't confirm the name with two sources other than the catalog record itself, I flagged it as uncertain rather than hard-filing it. Bad authority records spread faster than good ones. The hardest part of authority control in music is dealing with collaborative or group names. A band breaks up, reforms under a slightly different name, and suddenly you have five records for the same core musicians with no connecting authority link. The workaround I used was to create a group name authority record with cross-references to all known variants and to include a scope note linking the entities by personnel rather than by name. Personnel-based linking is ugly in a MARC record but it keeps the catalog functional. People searching for the guitarist will find the later incarnation of the band even if the name changed. Another area where Tucker's guidance proved useful was handling composers with non-Latin scripts. If your library doesn't have a dedicated music cataloger who reads the script in question, you rely on LC transliteration. That introduces errors at every step—different editions of a score might use different transliteration conventions, and the composer's own website might latinize their name in a way that doesn't match the authority record. My practical fix was to treat the LC authority form as the primary access point but to index the variant forms heavily so that searches in any reasonable spelling surface the correct heading. This means spending more time on the 4XX fields in your MARC records than most people do, but it pays off in retrieval.
Get the Full Details
One counter-intuitive thing about authority control that beginners miss: having fewer authority decisions is sometimes better than having more. Every new authority record you create is a commitment. If you create an overly specific heading for a minor composer, you're going to end up with scattered authority files that don't connect anything. It's often better to group related entries under a broader heading with a scope note than to create multiple narrow ones. I watched a colleague fragment a series of regional folk music archives into separate authority records for each town's musical tradition when a single regional heading would have done the job and connected the materials usefully. The other thing nobody talks about is the maintenance burden. Authority control isn't a one-time setup. The LC updates its authority file regularly, and old headings get revised, merged, or retired. If your library doesn't have a schedule for reconciling your local authority file with current LC data, you're building drift into your catalog. I set a quarterly reconciliation task that took about two hours per quarter for a medium-sized music collection. The alternative is what I saw at a university library where the music catalog hadn't been reconciled in seven years, and half the new acquisitions were ending up under headings that pointed nowhere. If you're working in a smaller institution without a dedicated music cataloger, the most practical approach is to lean heavily on existing authority files rather than creating new ones. Check LCNAF first, check VIAF second, and only create a local authority record when nothing else fits. Local authority records that duplicate existing ones cause merge conflicts during system updates. This is the advice Tucker was really driving at—authority control works when it's consistent, not when it's extensive for its own sake.
The tools available today make this easier than it was when Tucker was writing. OCLC's Connexion and WorldShare handle some of the authority linking automatically, and the MARC 21 format has proper fields for this work. But the tool still needs someone who understands why the authority record matters and what happens when it's wrong. A bad authority record doesn't just break one catalog search—it breaks every search that depends on it. That's the part the software won't tell you. I should mention one scenario where authority control in music really breaks down and what to do about it. Traditional and folk music often has no single identifiable creator. A song exists in dozens of variants across regions and generations. There is no authentic author to establish an authority heading for. In these cases, the standard approach is to file the work under title with a uniform title, and to link variants through subject headings rather than name authorities. I used this method for a collection of Appalachian ballads where each recording had a different singer claiming a different origin story. Treating the song rather than the singer as the primary authority saved us from making false attributions that would have required undoing later. If you want to read Tucker's actual work, her publications on music library authority control appeared primarily in library science journals and music library association publications. The specific papers aren't always easy to find through general search engines. Your best route is through the Music Library Association bibliography or the Academic Library databases that index journal literature from the late 1990s through the 2010s. The concepts are also reflected in later RDA guidance and LC policy updates, so even if you can't locate every paper, the practical advice made it into the standards that most music libraries now follow.
The bottom line is that authority control in a music catalog is mostly about making consistent decisions and documenting them well. You will encounter edge cases that no guide covers. The workaround in those situations is usually to pick the most defensible heading, link all variants, and add a note explaining why you chose it. Future catalogers will thank you for that note. Past catalogers definitely needed it.
