WNET/Thirteen releases its implementation of a PBCore Cataloging ToolWNET/Thirteen hereby releases the software of its PBCore Repository Project under the GPLv3 license (http://www.gnu.org/licenses/gpl-3.0.txt). The PBCore Record Repository is an online database tool built on Ruby on Rails, Sphinx search, and MYSQL that was created at WNET/Thirteen to facilitate the import, export, search, creation and modification of PBCore records according to the PBCore 1.2.1 standard (http://www.pbcore.org/PBCore/PBCoreXMLSchema.html). For testing and evaluation a public installed version of the application can be found at http://pbcore.vermicel.li (for administrative testing log in as username=admin and password=secret). This work employs PBCore. The PBCore (Public Broadcasting Metadata Dictionary) was created by the public broadcasting community in the United States of America for use by public broadcasters and others. Initial development funding for PBCore was provided by the Corporation for Public Broadcasting. The PBCore is built on the foundation of the Dublin Core (ISO 15836), an international standard for resource discovery (http://dublincore.org), and has been reviewed by the Dublin Core Metadata Initiative Usage Board. Copyright: 2005, Corporation for Public Broadcasting. Further technical documentation can be found here http://git.mlcastle.net/?p=pbcore.git;a=blob;f=doc/README_FOR_APP;hb=HEAD and a current snapshot of the source code here http://git.mlcastle.net/?p=pbcore.git;a=snapshot;h=HEAD;sf=tgz. This tool is under development and feedback is appreciated. David Rice Digital Media Archivist WNET/Thirteen
PBCore Genre Picklist from Hell
Let's be honest: The controlled vocabularies for pbcoreGenre suggested at pbcore.org lack relevance in many cases. I mean, "boat"? The main genre list suggested, "PBCore + Tribune Media Services Genre Categories (TiVo)," is mostly very good as far as it goes. But it doesn't go far enough.
And here's the problem: Because it's on the official PBCore website, it looks to many people like the Official PBCore Genre List. I've spoken with several PBCore users (speak up if you wish) who wanted to use certain genre terms not on the list, but didn't think it would be valid. It is valid, as long as you also declare the genreAuthorityUsed to identify the genre list.
This really matters when you want to exchange stuff between systems that speak PBCore, and you want that stuff to show up in the right places. By using a controlled vocabulary that is common to the systems exchanging the stuff, things work as intended. If I call something "boat" and you're expecting "marine," things fall apart. If I use "Horse" as in the suggested picklist, and your system wants to call it "Equestrian," we have a problem.
So what would move this forward? I'll suggest something: People should compile a genre list for a given PBCore user community (yes these really exist), and document it clearly for that community. Code it into applications (in drop-down lists for example) so everyone selects terms from the same genre list. Name that list, and you've got a valid new PBCore genreAuthorityUsed.