Deadline for PBCore 2.0 change requests looms
July 25th if the official deadline for input on the next major revision of PBCore. A release of PBCore 2.0 in November, 2010 is expected to represent a major leap forward, based on lots of change requests and research among the user community, plus where projects like the American Archive need to go. This is our chance to make sure it’s going in the most useful direction, and solving the right problems.
You can see the full list of submitted change requests, and add your own, here:
By July 25th please!
Translation Advice
The PBCore Module for Drupal is now being used by several public access stations. Next month I’m helping the Open Channel in Växjö Sweden implement Open Media there. I’ve read karavan’s post about PBCore en Español, but that seemed to focus on translating the names of the schema elements. I’m going to need to translate the genres, ratings, and languages themselves.
We’re still relying on phpMyAdmin to enable genres, languages, and rating. We’ve focus our effort on improving the UI producers see as they add videos. Most stations have taken advantage of the options to customize elements and create hierarchy. By adding some javascript to the Open Media Show module, only genre elements in the selectlist with a parent term that has a customized description matching the Theme. Most stations have 10-12 Themes used for programming the cable channel. Under each of those Themes, 5 or 6 genres are enabled. In the UI, the producer must select Art of Community Interest in on select list before the next select list is activated and filtered.
Art
- Anthology
- Collectibles
- Dance
- Literature
- Performance
- Photography
- Visual Art
Community Interest
- Activism & Advocacy
- Event
- Gay/Lesbian/LGBTQ
- Minority Interest
- Promotional Announcement
- Public Serve Announcement
This makes enabling a large number of genres more user friendly.
Art
- Anthology
- Collectibles
- Dance
- Literature
- Performance
- Photography
- Visual Art
Community Interest
- Activism & Advocacy
- Event
- Gay/Lesbian/LGBTQ
- Minority Interest
- Promotional Announcement
- Public Serve Announcement
Now I think the way to do this is to use the custom description field that’s already part or the module to present users with the Swedish, but store the official English term in the database. So if Öppna Kanalen used the same hierarchy as channelAustin, producers submitting content would see something like…
Konst
- Anthology
- Collectibles
- Dans
- Litteratur
- Performance
- Fotografering
- Visual Art
Gemenskapens intresse
- Aktivism & Advocacy
- Event
- Homosexuella / HBTQ
- Minoritetens andel
- Marknadsförings Meddelande
- Offentliga Servera Meddelande
Any content tagged as Gay/Lesbian/LGBTQ or Homosexuella / HBTQ would be stored as “Gay/lesbian” in the database. That way if a show tagged Homosexuella / HBTQ was moved to channelAustin, it would show us as Gay/Lesbian/LGBTQ. The original English PBCore term could be a hash tag or some other unique identifier while we’re sharing between stations. When pushing content to an archive where I don’t control the way tags are displayed like Archive.org, I would push both the official PBCore term as well as the station’s customize equivalent.
Does this make sense?
Comments:
Write a comment: