CCO - Applying CCO - The Ten Key Principles Video Transcript Slide 1. Welcome to the second in our series about CCO: Cataloging Cultural Objects Applying CCO; The Ten Key Principles Slide 2. Principle #1 Establish the logical focus of each Work Record, whether it is a single item, a work made up of several parts, or a physical group or collection of works. Clearly distinguish between Work Records and Image Records. Slide 3. Cataloging is always about choices Determining what the work is, and the relationships between collection, work, and image records requires thought and planning depending on the scope of a given collection or project, what complexity and depth of cataloging your users require, the expertise of your catalogers and best practices that promote access. Slide 4. So, What is the Work? Here we have an example of a stereoscope card, dated 1900, from a special collection, which depicts the Taj Mahal. On the right we have a modern digital image of the Taj Mahal. Slide 5. How do we determine the Relationships? We could create a collection record for the entire collection, and link a work record for the card to the collection, with an image of the card linked to that. If we have a full record for the actual Taj Mahal complex, we can link the card's work record to that as well. The modern digital image would also be linked to the work record for the Taj. Slide 6. Imagine however that the scope of the cataloging is primarily about the stereocard collection; the Taj Mahal may not have a full work record, but can still be linked to the card as a controlled subject, or by a CONA record ID. Slide 7. Here we see on the left, the Taj Mahal as a Library of Congress Subject Heading with a record ID and on the right the complete CONA record from the Getty. CONA stands for the Cultural Objects Name Authority thesaurus. This also was a record ID. Slide 8. Principle #2 Include all the required CCO elements. Slide 9. What do we mean by CCO “elements”? Remember CCO is not a structural element set. The print and online versions of CCO simply use the idea of ‘elements’ as a way to organize the publication, to facilitate looking up information about titles, or creators, etc. The elements were given generic names that can be understood when used with standards like VRA Core and CDWA. Slide 10. What constitutes a “minimum record”? CCO makes recommendations (including the need for both work and image records) Most structural standards also make recommendations (Title is usually required) These recommendations should be considered, along with your user's needs when you formulate and document your local practice for training and consistency Slide 11. CCO Recommended Elements  Work Record: Work type, Title, Creator display, Role, Creation Date, Subject, Current Location, Measurements, Materials and Techniques  Image Record: View Description, View Type, View Subject, View Date CCO assumes and recommends that there is a database structure which links related records and controlled vocabulary terms; CCO is also to be used in conjunction with a structural standard Slide 12. Here is a comparison of the generic "elements" or topics in CCO contrasted with the actual element names in VRA Core 4. They don't match exactly in name, but they do match functionally in terms of formatting. Slide 13. The VRA Core subelements of the element "agent" are formatted here according to CCO rules. The subelements include the name in natural order, the nationality, life dates and role. The location is formatted using controlled terms from the Thesaurus of Geographic Names. In using VRA Core 4 there is also a controlled list of location types which includes site, repository, exhibition and discovery. There are 14 possible types. In CCO and VRA Core practice the repository ID number for the object is included at the end of the location display. Slide 14. We are going to skip over some of the principles for now, to be covered in our third video, Structuring and Storing Data Slide 15. Principle #9 Be consistent regarding capitalization, punctuation, and syntax. Avoid abbreviations, but when necessary, use standard codes and lists for abbreviations (for example, the ISO abbreviations for countries or languages). CCO does recommend using "ca period" for circa Slide 16 Principle #10 For English-language information systems and users, use English-language data values whenever possible. In VRA Core practice, you would usually use English as the "preferred" title with non-English variants as "alternate" titles