Hello -
After much agonizing, the TV media librarian and I decided to use a modified version of the BBC genre terms for our cataloging efforts (
http://www.bbc.co.uk/programmes/genres). We thought the PBCore list too long, unorganized, and flat, and included too many terms we'd probably never use. The LC genre/form list was similarly long and flat.
We decided to make our Genre field a hierarchical pick list - rather than linking it to a controlled vocabulary on the web. We wanted to be able to limit the terms to what we'd actually envision using, and to organize them hierarchically in our system, to make it easier for both data entry and resource discovery. We thought the BBC list, already formed, best matched our particular collection.
In terms of linking subject authorities, for the record, we are still in the process of designing our system, so nothing I say is tested/foolproof. In our test system, I have certain PBCore fields linked to TGM, others linked to LCSH, and others linked to GeoNames/Geocodes. While I would like our data to be searchable as linked open data, I'm not sure if linking to LCSH exclusively accomplishes this (LCSH is part of the linked open data cloud), or, if we need to have the DBpedia URI also (or exclusively) in our record. DBpedia is at the heart of the linked open data network - everything links to it in some way.
Ideally, I'd like to have our subject and entity fields linked to DBpedia. In addition, I'd like certain information from the DBpedia record to auto-populate specific fields of information in our local authority record (specifically for people and organizations) - but this gets complicated on many levels, and I do question whether or not, this is a good idea. For starters, it needs to be programmed - secondly, I worry that the information may not be truly authoritative, and this needs to be expressed in the data, and perhaps, refreshed periodically.
Fun fun - thoughts are welcome on this.
Allison
Archivist, Wisconsin Public Radio