<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:atom="http://www.w3.org/2005/Atom"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:npr="http://www.npr.org/rss/" 
    xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" 
    xml:lang='en-US'
    xmlns:content="http://purl.org/rss/1.0/modules/content/">
  
  <channel>
    <title>RSS Feed for PBCore Resources</title>
    <description>PBCore Resources articles, projects, and other stuff that might be useful or possible interesting.</description>
    <link>http://www.pbcoreresources.org/</link>
    <language>en-us</language>
    <copyright>Copyright 2013 PBCore Resources</copyright>
    <dc:date>2011-11-14T19:11:48+00:00</dc:date>
    <atom:link href="http://www.pbcoreresources.org/rss/" rel="self" type="application/rss+xml" />
    <admin:generatorAgent rdf:resource="http://www.pmachine.com/" />


    <item>
      <title>PBCore Cataloging Workshop at AMIA Conference</title>
      <link>http://www.pbcoreresources.org/article/pbcore_cataloging_workshop_at_amia_conference/</link>
      <guid>http://www.pbcoreresources.org/article/pbcore_cataloging_workshop_at_amia_conference/#When:19:11:48Z</guid>
      <description>An event for the ages:

PBCore Cataloging Workshop

A day of cataloging exercises and case studies
Wednesday, November 16th, 9 a.m. to 5 p.m. 
At the Association of Moving Image Archivists Annual Conference, Austin, Texas

Find out if PBCore is a good data structure for your audiovisual assets.&amp;nbsp; With PBCore experts, dig into the PBCore 2.0 schema and meet a range of tools; learn mandatory, suggested, and recommended elements, picklists and relationships; and explore workflows for handling intellectual content and instantiations. Gain a solid grasp of why and how PBCore is useful for handling analog and digital audiovisual objects.

The workshop will be held at The Harry Ransom Center, The University of Texas at Austin
www.hrc.utexas.edu/visit/#directions</description>
      <category>rss</category>
      <dc:date>2011-11-14T19:11:48+00:00</dc:date>
    </item>

    <item>
      <title>PBCore in RDF</title>
      <link>http://www.pbcoreresources.org/article/pbcore_in_rdf/</link>
      <guid>http://www.pbcoreresources.org/article/pbcore_in_rdf/#When:17:06:36Z</guid>
      <description>I guess I know just enough about RDF to be dangerous. It may be that I am not plugging the namespace information in correctly, but all my attempts to wrap a PBCore XML record in RDF have failed validation in the W3C validation tool (http://www.w3.org/RDF/Validator/).&amp;nbsp; I would really love and adore an example of a valid PBCore record in RDF.</description>
      <category>rss</category>
      <dc:date>2011-10-06T17:06:36+00:00</dc:date>
    </item>

    <item>
      <title>PBCore 1.3 to 2.0 translator ready for review</title>
      <link>http://www.pbcoreresources.org/article/pbcore_1.3_to_2.0_translator_ready_for_review/</link>
      <guid>http://www.pbcoreresources.org/article/pbcore_1.3_to_2.0_translator_ready_for_review/#When:14:42:42Z</guid>
      <description>Dave Rice, with support of the Dance Heritage Coalition&#8217;s Secure Media Network managed by Bay Area Video Coalition, has created a PBCore 1.3 to 2.0 XSL translator tool.&amp;nbsp; For valid input PBCore 1.3 records, the tool generates a valid 2.0 records as the output.

This process revealed some difficult mapping challenges that have yet to be fully resolved.&amp;nbsp; The main issue is the move away from elements like genreAuthorityUsed to the @source attribute.&amp;nbsp; At first glance, it makes sense that genreAuthorityUsed would become pbcoreGenre source=&#8220;authority&#8221; in PBCore 2.0.&amp;nbsp; But wait, there was an @source attribute for genreAuthorityUsed!&amp;nbsp; So if the value of genreAuthorityUsed is now 2.0 pbcoreGenre source=&#8220;authority&#8221;, what happens to 1.3 genreAuthorityUsed source=&#8220;name&#8221;? It&#8217;s lost!&amp;nbsp; 

Given that the definition of @source in PBCore 2.0 is &#8220;Attribute source provides the name of the authority used to declare data value of the element,&#8221; for this and a few other elements, it appears to be impossible to create a sematically lossless mapping.

We have posted the translator to github for public review.&amp;nbsp; You will see in the header comments of the XSL a number of issues that have come up in the mapping, including the genreAuthorityUsed problem.&amp;nbsp; Issues have been identified for mapping 1.3 titleType, descriptionType, and subjectAuthorityUsed.

You can find the translator here:&amp;nbsp; https://github.com/avpreserve/random&#45;pbcore&#45;metadata&#45;translators/blob/master/13_to_Pbcore2.xsl

We would love to get feedback on this from the PBCore community!</description>
      <category>rss</category>
      <dc:date>2011-05-31T14:42:42+00:00</dc:date>
    </item>

    <item>
      <title>PBCore.org site refresh a welcome sight</title>
      <link>http://www.pbcoreresources.org/article/pbcore.org_site_refresh_a_welcome_sight/</link>
      <guid>http://www.pbcoreresources.org/article/pbcore.org_site_refresh_a_welcome_sight/#When:20:15:26Z</guid>
      <description>If you haven&#8217;t been to http://pbcore.org lately you&#8217;re in for a good surprise. The site has been completely rebuilt, and contains up&#45;to&#45;date documentation, news, case studies, and most importantly, the complete PBCore 2.0 schema. There, I buried the lead: PBCore 2.0 has been officially released!</description>
      <category>rss</category>
      <dc:date>2011-02-20T20:15:26+00:00</dc:date>
    </item>

    <item>
      <title>Sneak preview of PBCore 2.0</title>
      <link>http://www.pbcoreresources.org/article/sneak_preview_of_pbcore_2.0/</link>
      <guid>http://www.pbcoreresources.org/article/sneak_preview_of_pbcore_2.0/#When:02:42:06Z</guid>
      <description>If I’ve learned one thing about the PBCore user community, it’s that we’re not satisfied with the current state of PBCore. We’ve used it enough to discover its strengths in describing AV assets and creating shareable metadata, but we keep running into its gaps and flaws. We’ve been pushing for a change process, and have argued for specific changes. Common threads have emerged right here on this site:


A need for PBCore to support multi&#45;part instantiations, e.g. when you have one complete work comprised of several reels or tapes or files.

A need to express rights information related to a specific Instantiation, instead of only the entire asset. For example, you might want to allow users to download an mpeg4 version of a film for personal use, but not grant the same kind of access to the actual film!

Speaking of rights, formatting of the pbcoreRightsSummary element disallows inclusion of metadata from existing standards such as ORDL or Creative Commons, which seems odd to say the least. If you already have structured rights data, why not simply reuse it?

A need to show relationships between Instantiations, like when you digitize a film to 10&#45;bit uncompressed digital video, then encode an mpeg4 file from the 10&#45;bit uncompressed file, it seems important to show that in the PBCore record.

With pbcoreContributor, you can say that Harrison Ford is an Actor, but you can’t say what role he plays in the film.

There’s no way to uniquely identify a person, subject term, location, or other value that might have an actual URI.

The lack of attributes of any kind! Everything is elements and sub&#45;elements, which seems inefficient and makes parsing more difficult.

The lack of a valid way to identify clip information within an asset, for example where in the timeline a particular subject is discussed or a specific person appears.

The lack of any way to bundle multiple PBCore XML records together in a feed or collection, so you could export/import large groups of records between systems or use PBCore in RESTful web applications.


Well good news folks! PBCore 2.0 is on the way, and it solves all these issues.</description>
      <category>rss</category>
      <dc:date>2011-01-13T02:42:06+00:00</dc:date>
    </item>

    <item>
      <title>PBCore sessions at the 2010 AMIA Conference</title>
      <link>http://www.pbcoreresources.org/article/pbcore_sessions_at_the_2010_amia_conference/</link>
      <guid>http://www.pbcoreresources.org/article/pbcore_sessions_at_the_2010_amia_conference/#When:17:13:46Z</guid>
      <description>The 2010 AMIA Conference is next week. (How&#8217;d it get to be November already?!) For those PBCore denizens attending, please note two sessions that will be of particular interest, both on Thursday, November 4th:

8:30am &#45; 10:00am
Moving to a Digital Asset Management Environment: A Case Study on Fresh Air
Chair: Dave Rice &#45; AudioVisual Preservation Solutions
Speakers: Daniel Pisarski &#45; TelVue Corporation, and Julian Herzfeld &#45; WHYY
Since 1975 WHYY&#8217;s production, Fresh Air, has generated thousands of 1/4&#8221; analog reels, DAT tapes, CDs, and digital files as well as even more Microsoft Word and Excel documents reflecting a disconnected set of rights, inventory, descriptive, and technical information. This panel looks at all aspects of an initiative to assemble Fresh Air&#8217;s metadata collections under PBCore while bringing digital media and metadata into a production&#45;oriented digital asset management system

11:00am &#45; 12:00pm
Coming Attraction: PBCore 2.0
Chair: Courtney Michael &#45; WGBH Media Library &amp;amp; Archives
Chris Beer &#45; WGBH Interactive
Speakers: Courtney Michael &#45; WGBH Educational Foundation
Jack Brighton &#45; University of Illinois
Katrina Dixon &#45; Northeast Historic Film
Kara Van Malssen &#45; Broadway Video Digital Media
There are a number of metadata standards being used by the library and archival community. However few are adequate, and easy for describing media collections. PBCore is a metadata standard that was developed specifically to describe media. Many in the moving image archival community have begun to utilize the standard. After 2 years of a development hiatus, a new initiative has launched to continue development of the standard to bring it to PBCore 2.0. This session will give an overview of PBCore &#45; why it is a good standard to use for media collections and the work to date to bring it to PBCore 2.0. It will demo and tour the new redesigned PBCore.org website highlighting changes, navigation, and the community input features. And finally there will be several use cases showing practical use of PBCore in real archive projects. The end will be a roundtable discussion to get more feedback from the AMIA/IASA community and take questions.

&amp;nbsp;</description>
      <category>rss</category>
      <dc:date>2010-10-29T17:13:46+00:00</dc:date>
    </item>

    <item>
      <title>Metadata as media</title>
      <link>http://www.pbcoreresources.org/article/metadata_as_media/</link>
      <guid>http://www.pbcoreresources.org/article/metadata_as_media/#When:23:03:56Z</guid>
      <description>(As always, I speak only for myself as a media producer and archivist.)

I attended the panel discussion on PBCore at the recent Open Video Conference, and was struck by something that should have been obvious.&amp;nbsp; Those of us pushing development of PBCore have failed to clarify one basic thing: What is PBCore for? I’ve been to workshops and sessions on PBCore over the past six years and have been on metadata panels at the AMIA Conference, the PBS Tech Conference, NETA, and iMA. We often focused on explaining the PBCore elements and why they are useful for cataloging media assets. But at the OVC, the question was raised “Why do we need PBCore to catalog our stuff if we already have a good media database?” The question reveals a conflation of two distinct things: having a media database, and being able to easily interoperate with other databases.</description>
      <category>rss</category>
      <dc:date>2010-10-17T23:03:56+00:00</dc:date>
    </item>

    <item>
      <title>PBCore 2.0 session at the Open Video Conference, October 1, NYC</title>
      <link>http://www.pbcoreresources.org/article/pbcore_2.0_session_at_the_open_video_conference_october_1_nyc/</link>
      <guid>http://www.pbcoreresources.org/article/pbcore_2.0_session_at_the_open_video_conference_october_1_nyc/#When:00:41:28Z</guid>
      <description>For those attending the Open Video Conference this weekend in New York, don&#8217;t miss the panel on PBCore 2.0. A stellar lineup will talk about the process of developing 2.0, and hopefully share some details about where it&#8217;s going.

Here are the panel specifics, copied from the OVC schedule:

Summary: An Introduction to PBCore 2.0: Metadata for Public Broadcasters &#45; (4:30 PM &#45; 5:30 PM)

Description: PBCore has served the Public Media community as a metadata schema for describing media since 2005. With a new round of funding from the Corporation for Public Broadcasting, WGBH Boston is working on PBCore 2.0 – an updated version which will increase its flexibility as a schema and therefore its applicability to diverse user scenarios. In addition, a new web site with updated documentation is set to launch next month (November, 2010). Come learn about PBCore: how it is evolving, how it is applied, and how it can benefit your workflow and interoperability as a video content producer or consumer.

Presenters:
Chair: Nan Rubin — PBCore Project
Linda Tadic — Audiovisual Archive Network
David Rice — Audiovisual Preservation Solutions
Chris Beer — WGBH Interactive</description>
      <category>rss</category>
      <dc:date>2010-10-01T00:41:28+00:00</dc:date>
    </item>

    <item>
      <title>Making PBCore End User Friendly</title>
      <link>http://www.pbcoreresources.org/article/making_pbcore_end_user_friendly/</link>
      <guid>http://www.pbcoreresources.org/article/making_pbcore_end_user_friendly/#When:17:40:27Z</guid>
      <description>Two screencast were recently added to Blip.tv that show how the Open Media Project&#8217;s Drupal modules make PBCore easier for end users.&amp;nbsp; Craig Sinclair from Amherst Community Media created a screencast that shows how to configure the PBCore module for Drupal to display customized elements in a hierarchy to users.&amp;nbsp; I added another screencast that shows how to add PBCore to any content type with CCK and how to use some simple javascript to limit the number of options show to users.&amp;nbsp; 

Sites using the current beta of the module can now export a node as XML as well as dump of their site specific configurations making it easier to compare how organizations are implementing PBCore in practice.

The PBCore module for Drupal is still rough around the edges, but the structure is now there for anyone with even basic PHP skills to contribute.&amp;nbsp;</description>
      <category>rss</category>
      <dc:date>2010-08-09T17:40:27+00:00</dc:date>
    </item>

    <item>
      <title>Deadline for PBCore 2.0 change requests looms</title>
      <link>http://www.pbcoreresources.org/article/deadline_for_pbcore_2.0_change_requests_looms/</link>
      <guid>http://www.pbcoreresources.org/article/deadline_for_pbcore_2.0_change_requests_looms/#When:20:58:24Z</guid>
      <description>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&#8217;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:

http://pbcore.org/2.0/?p=476&amp;amp;utm_source=rss&amp;amp;utm_medium=rss&amp;amp;utm_campaign=change&#45;requests&#45;so&#45;far&#45;submit&#45;yours

By July 25th please!</description>
      <category>rss</category>
      <dc:date>2010-07-22T20:58:24+00:00</dc:date>
    </item>


</channel>
</rss>