CCO - Structuring and Storing Data with CCO Video Transcript Slide 1. Welcome to the third in our video series about CCO: Structuring and Storing Data Slide 2. The Ten key principles, continued Slide 3. Principle #3 Follow the CCO rules. Make and enforce additional local rules to allow information to be retrieved, repurposed, and exchanged effectively Slide 4. Discovery and retrieval is enhanced by the use of both index (that is, a data value in a single field) and display data in delivery systems. This example shows the parsed value "India" in a Browse page versus the complete location display in an item page. Slide 5. A very common activity is repurposing data, for loading into delivery systems, for display or for publication. This also includes mapping, which in essence is translating from one structural standard for use in another. Repurposing can be automated, when data is reliably standardized. This efficiency is a major reason for, and result of, adhering to standards. We use planning documents like data dictionaries to record our local practice. Slide 6. Here is a sample of a data dictionary. The goal here was to take VRA Core 4 display values and map them consistently into a Dublin Core field structure, for use in Omeka. Note that Dublin Core does not support linked image and work records. This particular solution is one way of reconciling that problem in a way that can be supported locally and consistently. Slide 7. Structural standards today typically have transmission schemas which have been created for them so that the data can be rendered in XML (Extensible Markup language) or RDF (Resource Description Framework). These standards include VRA Core 4, EAD, LIDO, MODS and METS among others. Slide 8. Principle #4 Use controlled vocabularies, such as the Getty vocabularies and the Library of Congress authorities. Slide 9. The use of controlled vocabularies which offer record ID numbers (known as "ref-ID") is even more important now. Linked Open Data can be achieved by creating URI links to these ID numbers and serving them out to the internet. As a minimum to begin creating LOD data, you must store the ref-ID and the vocabulary name (for instance, ULAN, TGN or LCNAF). Slide 10. Principle #5 Create local authorities that are populated with terminology from standard published controlled vocabularies as well as with local terms and names. Structure local authorities as thesauri whenever possible. Record and document decisions (and sources) about local authorities. Slide 11. What do we mean by "Local" Authorities? As mentioned, to use Linked Open Data, the ref-id from the controlled term must be stored in your database locally You will sometimes not find a given term in authorities; there are mechanisms for you to submit terms (and source information) to Library of Congress, and the Getty etc. This helps everyone. However, if the term is truly local, there is also a means to create and publish LOD links which point to your institution Slide 12. Principle #6 Use established metadata structural standards, such as VRA Core 4, Dublin Core, CDWA (LIDO) A structural standard will be a guide in setting up database fields and tables Compare a CCO record to a VRA Core 4 record in the following slide.... Slide 13. On the left is a sample from an online CCO cataloging example, on the right is the same work, seen in an online VRA Core 4 example. This shows the display values expressed within the formal elements of the structural standard. Slide 14. Principle #7 Understand that cataloging, classification, indexing, and display are different but related functions This impacts cataloging vs. retrieval issues (See CCO pages 32-33) Slide 15. Principle #8 Be consistent in establishing relationships between works and images, between a group or collection and works, among works, and among images. ....and plan for growth, and adding relationships over time Slide 16. As an example, how would you treat part/whole relationships like chapels within a cathedral? Does the chapel have a different date, different creators? What about sculpture and paintings within the cathedral? How do you balance the workflow of the images you have "at hand" now but still have the ability to add more images ( and relationships and complexity ) over time? Do the database and delivery systems tools you use give you the needed structure and flexibility to do this? Slide 17. Stay tuned for the fourth video in our series, Incorporating CCO in your workflow