Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (17)
Semelhante a VRA_2015_CatalogingRoundup_Seneff
Semelhante a VRA_2015_CatalogingRoundup_Seneff (20)
VRA_2015_CatalogingRoundup_Seneff
- 1. Using The Getty Vocabularies As Linked Open Data In A Cataloging Tool For An Academic Teaching Collection: Case Study At The University Of Denver Heather Seneff, MA, MLS Director of the Visual Media Center School of Art and Art History University of Denver Fernando Reyes, MS Senior Systems Developer University Libraries University of Denver Sheila Yeh, MLS, MSE Library Digital Infrastructure and Technology Coordinator University Libraries University of Denver © Seneff, H., Yeh, S., Reyes, F. VRA 2015, Session 4: Cataloging Round-up March 12, 2015
- 2. Sir Tim Berners-Lee The Semantic Web (Web 3.0) = web of linked data
- 3. Semantic Web: URIs = Uniform Resource Identifiers
- 4. Semantic Web: URIs = Uniform Resource Identifiers RDF = Resource Description Frameworks SPARQL = SPARQL Protocol and RDF Query Language
- 5. Semantic Web: URIs = Uniform Resource Identifiers RDF = Resource Description Frameworks SPARQL = SPARQL Protocol and RDF Query Language Ontologies and vocabularies OWL = Web Ontology Language
- 6. Semantic Web: URIs = Uniform Resource Identifiers RDF = Resource Description Frameworks SPARQL = SPARQL Protocol and RDF Query Language Ontologies and vocabularies OWL = Web Ontology Language LOD = Linked Open Data
- 7. Semantic Web: URIs = Uniform Resource Identifiers RDF = Resource Description Frameworks SPARQL = SPARQL Protocol and RDF Query Language Ontologies and vocabularies OWL = Web Ontology Language LOD = Linked Open Data
- 8. Subject Object RDF Triples After Yang & Lee: Organizing Bibliographic Data with RDA, p. 8,
- 9. Subject Object URIs URIs URIs or text RDF Triples After Yang & Lee: Organizing Bibliographic Data with RDA, p. 8,
- 10. Subject Object URIs URIs URIs or text Shakespeare Is author of Othello RDF Triples After Yang & Lee: Organizing Bibliographic Data with RDA, p. 8,
- 12. CC-BY-SA license: Linking Open Data cloud diagram 2014, by Max Schmachtenberg, Christian Bizer, Anja Jentzsch and Richard Cyganiak. http://lod-cloud.net/
- 14. http://dp.la/
- 18. user-friendly design qualified Dublin Core metadata schema accommodate fields from the first generation cataloging tool export metadata into CourseMedia
- 19. user-friendly design qualified Dublin Core metadata schema accommodate fields from the first generation cataloging tool export metadata into CourseMedia metrics for production ability to review and edit new records integrated authority control
- 20. user-friendly design qualified Dublin Core metadata schema accommodate fields from the first generation cataloging tool export metadata into CourseMedia metrics for production ability to review and edit new records integrated authority control ULAN and Library of Congress names authority for the “creator” and “repository” (DC: coverage: spatial) fields AAT and Library of Congress subject headings for the “style/period” (DC: coverage: temporal) and “subjects” fields.
- 27. Screenshot from Fernando Reyes
- 47. BIBLIOGRAPHY Breitman, Karen Koogan, Marco Antonio Casanova, and Walter Truszkowski. Semantic Web Concepts, Technologies and Applications. New York; London: Springer, 2007. Hendler, James, Jeanne Holm, Chris Musialek, and George Thomas. “US Government Linked Open Data: Semantic. Data. Gov.” IEEE Intelligent Systems 27, no. 3 (2012): 0025–0031. Hooland, Seth van. Linked Data for Libraries: How to Clean, Link and Publish Your Metadata. Chicago, IL: Neal-Schuman, 2014. Johnson, L., S. Adams Becker, V. Estrada, and A. Freeman. NMC Horizon Report: 2014 Library Edition. Austin, Texas: The New Media Consortium, 2014. Manifesto for Agile Software Development. “Manifesto for Agile Software Development.” Accessed January 23, 2015. http://www.agilemanifesto.org/principles.html. Mitchell, Erik T. “Building Blocks of Linked Open Data in Libraries.” Library Technology Reports: Library Linked Data: Research and adoption 49, no. 5 (July 2013): 11–25. Mitchell, Erik T. “Three Case Studies in Linked Open Data.” Library Technology Reports: Library Linked Data: Research and adoption 49, no. 5 (July 2013): 26–43. Park, Jung-ran, and Lynne C. Howarth, eds. Library and Information Science, Volume 7 : New Directions in Information Organization. Bradford, GBR: Emerald Insight, 2013. Park, Ziyoung, and Heejung Kim. “Organizing and Sharing Information Using Linked Data.” In Library and Information Science, Volume 7 : New Directions in Information Organization. Bradford, GBR: Emerald Insight, 2013. Yang, Sharon Q., and Yan Yi Lee. “Organizing Bibliographic Data with RDA: How Far Have We Stridden Toward the Semantic Web?” In Library and Information Science, Volume 7 : New Directions in Information Organization. Bradford, GBR: Emerald Insight, 2013. Presentation screenshots by H. Seneff unless otherwise noted
Notas do Editor
- Linked Open Data is an exciting component of the Semantic Web that has special implications in the realm of art and cultural objects. In the Semantic Web, objects and concepts are seen in context through the use of structured, defined data. This improves searches and services on the Internet and exposes cultural objects in a new way. The Getty Research Institute has made the Art and Architecture Thesaurus (AAT) available as LOD, with plans to do the same for its Union List of Artist Names (ULAN) in 2015. These vocabularies are traditional mainstays of cataloging cultural objects. This case study addresses some of the practical applications of LOD in the cataloging environment during the 2013 development of a cataloging tool at the University of Denver. This study will also discuss principles of agile software development, which contributed to a successful collaboration.
- The Semantic Web (Web 3.0) is the newest evolution of the Internet. In the Semantic Web, natural language is structured so it is machine-readable. Logical connections can be made between “things.” Sir Tim Berners-Lee (who is considered the inventor of the Internet and is now Director of the World Wide Web Consortium or W3C) envisions the Semantic Web to be a “web of linked data” rather than a “web of hypertext” as it is now. In his 2009 TED talk The Next Web of open, linked data, he explained that the Semantic Web can unlock enormous potential on the Internet. The content is there on the web, but the data about the content needs to be explored, added to, and structured.
- The Semantic Web relies on three important components: Uniform Resource Identifiers, which are unique strings of characters identifying a resource—an entity or “thing.”
- RDF triples-- subject, predicate, and object—are the syntax that describes the “thing.” RDF information is expressed in a graph format using SPARQL (SPARQL Protocol and RDF Query Language) which is the W3C standard query language for the Semantic Web
- Ontologies and vocabularies which define the properties and relationships of the “thing” and how it is described. These ontologies and vocabularies are created by “subject domains” or specific disciplines using W3C standards in RDF schema language or in Web Ontology Language (OWL), and are shared on the Semantic Web.
- Those that are freely accessible and shared without licensing on the Internet are called Linked Open Data or LOD.
- These are the “pillars” of the Semantic Web--URIs, RDF, and standardized ontologies.
- At the basic level, information is organized in a RDF triple with a subject, predicate, and object.
- The subjects and predicates consist of Unique Resource Identifiers while the objects can be URIs or text content.
- Such as this example: Shakespeare. is author of. Othello. These sets of RDF triples then link to other triples…
- …giving further meaning to the information…
- …and spreading out into a web of meaningful content. Examples of projects using LOD include Europeana and the Digital Public Library of America (DPLA).
- Europeana is often cited as an example of the power and usefulness of Linked Open Data. Their goal is to connect and “publish data from Europe’s cultural heritage and scientific communities.” 1500 institutions have contributed over two hundred million records to the Europeana Digital Library, and all the metadata is shared under a Creative Commons CCO 1.0 agreement. The Europeana Foundation exposes its content as Linked Open Data through its professional portal.
- The Digital Public Library of America is a similar project and uses the Europeana Data Model to aggregate the resources of a growing number of partners. Their “metadata model is based on RDF and uses Dublin Core as a central descriptive metadata standard.” In addition to an RDF-based data model, the DPLA also uses JavaScript Object Notation for Linked Data (JSON-LD) serialization. A majority of contributing partners to both Europeana and the DPLA are cultural institutions—museums, archives, libraries--which usually have a wealth of metadata and description about their holdings AND they also benefit by having a number of established vocabularies structured specifically for the types of objects they describe. For example…
- …the Getty Research Institute vocabularies are long established standards for cataloging cultural objects. The Getty Research Institute began working to expose their vocabularies as Linked Open Data, and in February 2014, the Art and Architecture Thesaurus (AAT) was the first vocabulary to be released as Linked Open Data.
- In 2013, I took an online class (a MOOC) from Coursera about Metadata and the professor, Jeffrey Pomerantz, discussed Linked Open Data a bit--enough to intrigue me about LOD, and for me to realize how useful it would be in cataloging cultural objects in my own work as the Director of the Visual Media Center at the University of Denver.
- The University of Denver uses a learning object media management software called CourseMedia which was developed in house in 2003 by DU’s Office of Teaching and Learning. It is a web-based, password-protected media management system for images, video, and audio files to support teaching. The primary software technologies used are Adobe ColdFusion, Flash, and MySQL database. Image files are added to CourseMedia by the Visual Media Center in the School of Art and Art History (video and audio files are added by the library). I have four graduate students and one half-time staff member cataloging art and cultural objects. I train the students and edit each record before it is ingested into CourseMedia. OTL had also developed the cataloging system used in the VMC in 2003, which was becoming outdated. When the opportunity to develop an updated cataloging tool arose in 2013, it was reasonable for me to collaborate with DU’s Library instead of OTL, which was concentrating more on the user end of CourseMedia rather than cataloging. I began meeting with Library’s Digital Infrastructure and Technology Coordinator, Sheila Yeh, and the Library’s Senior Systems Analyst Fernando Reyes to plan for this software.
- I envisioned user-friendly software based on a qualified Dublin Core metadata schema that would accommodate fields from the first generation cataloging tool and export metadata into CourseMedia
- I also wanted metrics for production assessment and a process for me to review and edit new records. And I wanted integrated authority control for certain fields:
- the ULAN and Library of Congress Names authority for the “creator” and “repository” fields, and the AAT and Library of Congress subject headings for the “style/period” and “subjects” fields. Sheila and Fernando decided to apply an “agile software development” approach to the planning.
- This approach focused on defining the features of the system and what it could and could not do, and on prioritizing the development, allowing for features that could be added later. Using this approach, the development efforts welcomed reasonable changes and focused on a modular design for simplicity, sustainability, and reusability. The three of us also met frequently in face-to-face meetings as the development progressed and as the software was ready for testing. The collaboration went well and communication remained open and positive throughout the project. Here is a teaser look at the finished product (from the cataloger’s view) before I talk more about Fernando’s role in programming behind the scenes:
- This is the cataloger’s view of Art History Metadata Management system (MMS). It uses JavaScript, PHP and MySQL which were chosen because of Fernando’s expertise and the fact that they are currently part of the general curriculum of Computer Science education. This helps with the sustainability of the project, since MMS does not rely on the specific skillset of one individual or a particular team. MMS also uses Solr search server and a Fedora-based digital repository. Solr is an open source search platform produced by the Apache Software Foundation used in indexing metadata and providing a fast discovery layer. Fedora offers an accessible application programming interface (API) to manage XML metadata, in this case the qualified Dublin Core, in a flexible way. The LOC names and subjects were integrated into MMS by API and the AAT and ULAN were purchased from the Getty in their pre-LOD form for integration as local data stores.
- After MMS was in use for about 6 months, the Getty made the AAT accessible through API as linked open data. Fernando and Sheila and I jumped at the chance to utilize the Linked Open Data AAT when it was made available by Getty. MMS’s local JavaScript Web service was modified to search the AAT (in addition to the LCSH and LCN) using SPARQL query language in a uniform manner.
- Fernando found that the Getty Institute facilitates the use of its LOD very professionally with things like sample queries guidelines.
- There is also a forum for users to ask technical questions of all kinds. This is the SemanticWeb forum accessed through the Getty’s implementation instructions. For example, Fernando initially encountered ambiguous headers from the dataset returned from the AAT Web services, but was able to quickly gain insights on the problem from reading posts from the forum. The forum is also helpful when LOD changes the way their Web Services return data, helping the programmers accommodate the changes to service. Now the next screenshots are from Fernando to reveal coding--
- This is an example of a JSON (JavaScript Object Notation) search response….
- …where you can see what a search for “pipes” in the AAT exposes—with the specific term “calumets” within the structured data.
- This screenshot shows the metadata class returned from the AAT’s vocabulary service in MMS.
- This shows the AAT’s response in LOD code. Now we’ll look at MMS again from the cataloger’s perspective…
- So here we’re back at the cataloger’s view of MMS, where you can…
- …choose authorities ….
- …from a pulldown menu on the right (Alora is the acronym for the first generation cataloging tool developed in 2003—we had to keep two vocabulary lists from that tool to support some of the older records in the system).
- So for example we can use the AAT to search for a term…
- …like “pipes” for which we retrieve a number of results. We want to be sure to differentiate between pipes in the context of plumbing, musical instrument pipes, or the kind of pipes that are Native American ritual objects (as opposed to the kind of pipes that are associated with a different sort of ritual in Colorado….). We can select a more specific term, like “calumets”….
- …and access the AAT for more information on the term by clicking the associated URL (or URI)….
- …which takes you to the LOD version of the term. From here you can see the RDF triples associated with the term….
- ….on the left hand side tabs…
- … revealed in columns of Subject, predicate, object --and on the right hand…
- …side the links to the AAT website and the hierarchy to which the term belongs.
- Here’s the familiar page for a term in the AAT –this one for calumets, the term for the specific type of pipe we are cataloging.
- Then from inside MMS, we can click the AAT term of choice…
- …and the appropriate field is populated! No re-typing necessary. You can see here that the subjects field is repeatable, too, with the plus sign above the field. We can use the LOC Subject Heading authority for the same field….
- ….and for the style\period field above as well.
- Here’s an example of a completed record in MMS.
- You can see multiple subjects used. The software has proved to be user friendly for the graduate students I train and direct, and it encourages good cataloging habits. The integrated vocabularies help me mentor the students about the importance of metadata -- AND the authoritative terms improve the searches in CourseMedia.
- It’s now been over a year since MMS has been used as our cataloging system in the VMC. You can see the metrics displayed within MMS here. I believe using integrated vocabularies has improved our productivity, our efficiency, and our accuracy in cataloging new records and correcting old ones. MMS was a successful collaboration, and an exciting introduction to the power and usefulness of Linked Open Data.