We will concentrate on PBCore, the metadata standard established in 2005 specifically for audiovisual media assets and rapidly gaining a community of practice; and its use in conjunction with DACS (Describing Archives: A Content Standard) to help support findability--and more efficient management of your analog and digital audiovisual holdings. Workshop will include demonstrations of PBCore’s value in describing intellectual content, rights, and technical metadata; discussion of “More Product, Less Process” decisionmaking for under-resourced AV collections; explore implementation of DACS/EAD and PBCore through an open-source collection management system.

So there are a lot of av archives out there that are un tapped, uncataloged, inaccessible – and this is just PUBLIC broadcasting.

So this morning we’ll do an exercise where we inventory a piece of media – we’ll create a very basic PBCore catalog record for the media using these 9-10 “elements.” Later on this afternoon, we’ll have more time with PBCore and we can dive into the full potential of the XML schema and see how detailed we can get with our moving image catalog records.

Embraced by archives as well as public broadcasting

PBCore 2.0 is made up of 4 content classes, 15 containers, and 82 elements. PBCore 2.0 makes use of 30 XML attributes. Attributes are used to further qualify or describe the elements and their values. Within a PBCore XML Document, the order of the elements is determined by the XSD.

Classes are for your mental model, groupings of elements. Containers could be said to be an artifact of earlier pbcore

Minimal set for american archiveOpen oxygen – add xsd, etc.

Always start with a DescriptionDocument. If you are creating or gathering a collection of records you can next insert Collection Now describe your record, then your instance (your item) and then your track. The trick is that PBCore 2.0 allows great flexibility with what some would see as levels of hierarchy. You can contain them within each other and you can repeat them – like this:

The trick is that PBCore 2.0 allows great flexibility with what some would see as levels of hierarchy. You can contain them within each other and you can repeat them – like this: