News
By pbcore on February 1, 2011
PBCore may be used in more than one way to express relations between assets such as programs within a series, chapters within an episode, stories within a program and limitless other combinations.
The simplest approach is to put higher, container-level data next to lower, derivative-level data within the main asset (at the level of element pbcoreDescriptionDocument), using attributes to clarify which is which. For example, to express programs within a series:
<pbcoreDescriptionDocument>
<!-- section removed for clarity -->
<pbcoreTitle titleType="Series" source="PBCore Controlled Vocabulary" version="2.0">Sample Series Title</pbcoreTitle>
<pbcoreTitle titleType="Program" source="PBCore Controlled Vocabulary" version="2.0">Sample Program Title</pbcoreTitle>
<!-- section removed for clarity -->
</pbcoreDescriptionDocument>
Another, more extensive approach to express such relations is to put higher, container-level data within the main asset (at the level of element pbcoreDescriptionDocument) and put lower, derivative-level data within its sub-element structure “pbcorePart.” For example:
<pbcoreDescriptionDocument>
<!-- section removed for clarity -->
<pbcoreIdentifier source="WGBH">NATPRO_NOVA</pbcoreIdentifier>
<pbcoreTitle titleType="Series" source="PBCore Controlled Vocabulary" version="2.0">NOVA</pbcoreTitle>
<!-- section removed for clarity -->
<pbcorePart>
<!-- section removed for clarity -->
<pbcoreIdentifier source="WGBH" annotation="this relates to other data about the NOVA series">NATPRO_NOVA</pbcoreIdentifier>
<pbcoreIdentifier source="WGBH" ref="http://www.pbs.org/wgbh/pages/NOVA/programs/" annotation="this identifies this program in the series">NOLA78334</pbcoreIdentifier>
<pbcoreTitle titleType="Program" source="WGBH" version="2011" annotation="this is the 2011/02/01 broadcast title">TU9</pbcoreTitle>
<!-- section removed for clarity -->
</pbcoreDescriptionDocument>
Posted in How To, Training | Tagged pbcoreIdentifier, pbcorePart, titleType |
By pbcore on February 1, 2011
How we use PBCore
We use some PBCore elements, drawing from those in existence at the time we designed our database, some eight years ago. Once the system was launched that essentially froze our element structure. We haven’t had technical support to make major changes. PBCore itself has been in flux and it hasn’t been practical to alter our database to reflect the frequent revisions, or go back retrospectively and edit records. We’ve made some minor changes, primarily in controlled vocabulary with PBCore updates, but overall once our system was in place, that was it. We were early adopters and the way we use the elements reflects this.
Why we use PBCore
The advantage of PBCore is that it adds media and technical metadata particular to broadcasting, a standard that doesn’t exist with another schema. We were looking at standards to incorporate into the design of our in-house database. PBCore was in the developmental stages at that time, and was one of the standards we reviewed. In fact, MPR was part of an early group that made suggestions about element structure (some of which were adopted) and did initial PBCore testing. We incorporated as much as we could that seemed practical at that time. Some elements we chose were later supplanted with local variation (e.g. rights).
Contact
Josh Kubasta
Archive Manager
Minnesota Public Radio
archive@mpr.org
Posted in Case Studies |
By marciabrooks on September 20, 2010
Here is the final PBCore 2.0 changes document, which builds on the iterative work to define the PBCore requirements that’s been shared in previous postings here. With the PBCore 1.3 requirements addressing American Archive’s needs, version 2.0 addresses additional requirements for American Archive and includes changes culled from the recent public change request process.
Final PBCore 2.0 Change Request Report (XLS)
The same information is sorted and organized in several different layouts:
- The 1st sheet are the changes for the schema, which consolidates similar requests that can be viewed in different layouts on the 2nd and 3rd sheets
- The 2nd sheet represents the change requests by requestor
- The 3rd sheet shows the change requests by type
This is the roadmap that will be used to develop 2.0. Stay tuned here for further developments and join the conversation!
Posted in Change Request, News | Tagged Change Request, homepage, pbcore2.0 |
By courtney_michael on August 17, 2010
Attached is an Excel sheet aggregating the change requests gathered for PBCore 2.0 development. The three sheets represent three different modes of gathering requests (online, in conversation, etc.)
PBCore_2.0_Changes_100726.xls
We had a lot of repeat requests which is encouraging and has help us focus in on a few key changes needed for PBCore 2.0:
- Collections – how to bundle or wrap multiple PBCore records into a collection or feed
-
- Episodes/Chapters/Segmentation – how to use PBCore to represent complex records
- Multiple Carriers – how to express one work across multiple carriers (e.g. one program that spans three tapes)
- People and affiliations – how to increase PBCore’s capacity to store structured “people” data
- Controlled vocabularies – many are outdated and need review. Also support linked data protocols by allowing references to UIDs or URLs.
- Rights – how to make use of PBCore’s extension capabilities to express more complex rights metadata
Many of these issues point to the fact that PBCore 1.2 and 1.3 have not been fully documented on this site and new examples are needed.
We hope to remedy this and include 2.0 documentation as we continue to re-vamp the site this fall. If you have any comments or suggestions on how to address the issues outlined here or in the spreadsheet, please pass them along! Comment on this post or email pbcoreinfo@wgbh.org.
Posted in Change Request, Controlled Vocabularies, News, Redesign | Tagged Change Request, homepage, News, pbcore2.0 |
By pbcore on August 2, 2010
Progress on PBCore!
Here’s the version 1.3 XSD and documentation, which is an interim release to focus primarily on supporting upcoming American Archive projects.
PBCore v1.3:
Many thanks to those who submitted change requests for version 2.0. We’ll keep you posted as work continues to finalize the 2.0 requirements and pbcore.org redesign.
Posted in News, XSD | Tagged americanarchive, homepage, News, pbcore1.3, XSD |
By pbcore on July 6, 2010
As previously posted, CPB has hired WGBH, Digital Dawn and AVPS to further the development of PBCore. As an interim step towards PBCore 2.0, and to accomodate PBCore’s use in CPB’s American Archive Project, we are working on version 1.3, due out at the end of July.
Attached to this post you’ll find a document that we’re working from as we consider changes to PBCore. It’s a grid which includes Digital Dawn’s requirements for changes to PBCore in the first column, and WGBH’s plan to address the changes in either 1.3 or 2.0 in the remaining columns. We’ve also incorporated comments from Dave Rice at AVPS – thanks Dave!
Many of the changes have to do with documentation and best practice examples… more so than schema changes. If you have an example best practice or suggestions for documentation clarity please pass them on to the WGBH team by commenting here on the PBCore blog or via our contact form! In addition, keep your change requests for 2.0 coming! We’ll be posting more about requests received so far in the coming days – requests submitted by July 25th will be considered for PBCore 2.0 (due to be published in early November).
PBCoreRequirementsGrid (PDF)
Posted in News | Tagged homepage, News, pbcore1.3 |
By pbcore on April 9, 2010
CPB has funded the development of PBCore version 2.0 to be released in the fall, 2010.
We are formally collecting user feedback and requests for changes to PBCore through June 30th, 2010July 25th. Requests submitted after that time may be considered at a future date.
Please submit a separate form for each request and keep in mind that more complete forms will be given more consideration.
Questions? Email the PBCore 2.0 Team.
Thank you!
Posted in Change Request, News | Tagged Change Request, homepage, News, pbcore2.0 |