New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ability to describe sequence and numbering #78
Comments
Good idea except that PBS does NOT number their segments within programs. They don't even always give them separate titles. And the segments share a program number. So the multiple use of titles is actually a good thing. Otherwise we would be artificially assigning numbers to segments that would mean nothing except to the institution assigning it. There are unique PBS package numbers that could be helpful? Leah |
I haven’t caught up with recent threads but just noticed Leah’s comment. Actually we do number segments for screening purposes at PBS. Most programs have only one, but we create separate segments for series like the NewsHour, Charlie Rose, and Tavis Smiley, for which the topics vary considerably from segment to segment. That’s why I added issue number 68. On Sep 2, 2014, at 11:35 AM, lelayz notifications@github.com wrote:
|
What about the magazine shows: Nova ScienceNow and Frontline? I don't see segment numbers in the PBS descriptions or databases, but if they exist that would be a great help! Just let me know where to find them. Leah |
Is this also related to issue #63? Could an "otherNumber" element/container (separate from pbcoreIdentifier) be useful to house such additional numbers associated with the asset? We could recommend a @type vocab (DistributionNumber | AlternateNumber | SequenceNumber...)- or leave it to the local institution to decide the type value. I would also recommend a note element for added information for the otherNumber. Having an OtherNumber container would be useful for a lot of purposes - not just to house sequence numbers. And, it would serve as a central location to house all additional numbers associated with an asset, and keep us from extending PBcore in an unwieldy way. |
Most of those get single segments. We create multiple segments for the nightly and weekly news programs to support FCC public file reporting. Stations need to provide quarterly lists of programs they have aired covering issues of potential interest to their local communities. If segment one is about the Obama Administration’s plan for the economy, for example, and segment two is about climate change, I would code segment one as “Economy” and "National Politics/Government" and segment two as “Environment.” Segment numbers are provided to stations via our Program Offer Data Service feeds. I don’t know how they get translated in ProTrack. Glenn On Sep 2, 2014, at 11:47 AM, lelayz notifications@github.com wrote:
|
Thanks, Glenn! Now I need to get the productions to refer to them that way! Leah |
Here for reference are two examples from my own experiments in creating PBS program records in RDF: http://dreampublic.net/pbs/rdf/1.2/programs/M/L/MLNH009511.xml features a general length and specific lengths for individual segments. http://dreampublic.net/pbs/rdf/1.2/programs/A/B/ABML000103.xml features a generic length for the single segment. [Note that these links may change. I'm sorting out inconsistent behavior between "dreampublic.net" and "www.dreampublic.net".] The precise length of the entire program is stored in the records for individual packages (i.e., instantiations), which I haven't covered here, so in that respect I think the PBS Broadview model matches PBCore. |
Intellectual content items are often season descriptions, episodes or parts of some other type of sequential arrangement. Currently, there is not simple way to express this in pbcore. It seems as though you could do this using titles, e.g.
But this seems inelegant and prone to confusion and inconsistent use. In order to enable a more simply way to express this information, it might be worth considering a sequence or numbering element. EIDR achieves this by using a structure like:
The text was updated successfully, but these errors were encountered: