Skip to content

PBCore-AV-Metadata/pbucore

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Assignments

  1. cpb-aacip-15-79v15vkq_pbcore.xml - Drew
  2. cpb-aacip-500-6m335r61_pbcore.xml -- Adam
  3. cpb-aacip-500-6h4csj1p_pbcore.xml -- Julie

Helpful Hints

  1. Jean-pierre's original stylesheet expects <pbcoreCollection> as the root element, so make sure your xml file has that going on.

Converting

There is a provided ruby script to convert individual XML files. To do this, you'll need ruby as well as the bunder gem. With the ruby, gem and git executables installed:

git clone https://github.com/WGBH/pbucore
cd pbucore
gem install bundler
bundle install
ruby lib/converter.rb ~/my-pbcore.xml > ~/my-rdf.xml

Workflow for mapping PBCore elements to EBUCore RDF-XML.

This is for members of WGBH/MLA Github team. If you are not a member of that group, then you can still submit issues and make comments, but you won't be able to push branches. You do not have to be an employee of WGBH to be a member of the WGBH/MLA Github team. If you would like to become a member, contact an existing member.

UPDATE: There is now a detailed document in the wiki for contributing to this project through the Github web interface. Please refer to that if you do not plan to use git from the command line. Otherwise, the steps below are still applicable.

  1. Identify a pbcore node you intend to work on. E.g. <pbcoreAudienceLevel>.
  2. Create a GitHub issue, name it appropriately. E.g. "Figure out mapping of pbcoreAudienceLevel".
  3. Create a branch for the issue, preferably named in a way that briefly states intention. E.g. handle-pbcoreAudienceLevel-nodes.
  4. Use the comments to work out a solution with other collaborators as needed. Notify specific users by "mentioning" them with @ symbol.
  5. Make your proposed changes. Changes should typically included:
  6. Changes to the stylesheet, pbcore-2-ebucore.xsl
  7. A sample PBCore xml file for testing the translation. The file should follow the convention: * "pbcoreAudienceLevel.pbcore.xml", if the node you are addressing is <pbcoreAudienceLevel>. * it should live in the spec/fixtures directory.
  8. The sample output in EBUCore RDF-XML that resulted from running the translation. The file should follow the convention: * "pbcoreAudienceLevel.rdf.xml" * it should also live in spec/fixtures.
  9. Push your branch to Github.
  10. Submit a pull request for your branch. Good job!

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published