+ Follow

Code4Lib 2013 - All THE Metadatas Re-Revisited

by Matthew Critchlow on Feb 15, 2013

400 views

Last year Declan Fleming presented ALL TEH METADATAS and reviewed our UC San Diego Library Digital Asset Management system and RDF data model. You may be shocked to hear that all that metadata wasn't quite enough to handle increasingly complex digital library and research data in an elegant way. Our ad-hoc, 8-year-old data model has also been added to in inconsistent ways and our librarians and developers have not always been perfectly in sync in understanding how the data model has evolved over time.

In this presentation we'll review our process of locking a team of librarians and developers in a room to figure out a new data model, from domain definition through building and testing an OWL ontology. We¹ll also cover the challenges we ran into, including the review of existing controlled vocabularies and ontologies, or lack thereof, and the decisions made to cover the gaps. Finally, we'll discuss how we engaged the digital library community for feedback and what we have to do next. We all know that Things Fall Apart, this is our attempt at Doing Better This Time.

Accessibility

View text version

Upload Details

Uploaded via SlideShare as Microsoft PowerPoint

Usage Rights

File a copyright complaint

4 Embeds 118

http://lanyrd.com	87
http://cynng.wordpress.com	29
http://www.linkedin.com	1
http://localhost	1

Statistics

Likes: 0
Downloads: 2
Comments: 0
Embed Views: 118
Views on SlideShare: 282
Total Views: 400

Code4Lib 2013 - All THE Metadatas Re-Revisited Presentation Transcript

ALL TEH METADATAS Re-revisited 2013 code{4}lib Meeting February 13, 2013 Esmé Cowles Matthew Critchlow Bradley Westbrook

Overview Overview• Needs assessment and proposed solution • Needs Assessment • Data• Data modeling Model Process • Implementation• Tool implementation

Overview• Needs assessment and proposed solution• Needs Assessment Data modeling Brad Westbrook• Tool implementation

Need One: More consistent data

Need Two: Maintain syntax of hierarchical subjects

Need Three: Improve support for complex objects

Improve support for complex objects-2

Need Four: Align more strongly with DL community• Make sure UCSD RDF is public facing – Use vocabularies in the public – Make UCSD vocabularies public• Develop technology stack – Utilize contributions from non-UCSD sources – Contribute to non-UCSD endeavors

Data Model Process Matt Critchlow

Project OverviewResearch Data Curation Pilot Deadline: June, 2013Timeline: July 16, 2012 – Oct 29, 2012Deliverables• Abstract Data Model• OWL/RDF Ontology• Data Model Extension GuidelinesTeamMetadata Analyst: Arwen Hutt, Bradley WestbrookIT: Esmé Cowles, Matt Critchlow, Longshou Situ

User StoriesAs an administrative unit manager, I want to indicate anyexternal versions or descriptions of an object that may be ofprobable importance to a userAs a user, I want to know what collection(s) an object belongs toAs a DAMS manager, I want to know what administrative unit anobject belongs to

Abstract Model – High Level RelatedCollection Collection Unit Resource RelatedComponent Component Object Object Resource File Component Component File File

Abstract Model DAMS Event Related Resource DAMS Provenance Provenance Language Collection Collection Resource Collection Part Collection Title Subject Name Relationship Date Note Object Unit Name Carto- Source FileVocabulary Object graphics Relationship Component CaptureVocabulary Entry Role Rights Role Component Copyright License Statute Other RightsDAMS Data Model RightsEntity-Relationship Diagram - 2013-02-07 Action class linking class inheritance Restriction Permission

Data Dictionary Title (title 1-m) Copyright (copyright 1) Language (language 1-m) Administrative Unit (unit 1)Relationship (relationship 0-m)

Ontology

Thing 1, Thing 2

Thing 1, Thing 2<dams:Title> Shared Entites <dams:Date>"Adm. Nimitz Joins <dams:type> "creation"Red Tape Cutters" <mads:Topic> "1940" "Midway, Battle of, 1942" <owl:sameAs> <lcsh:sh85085053> dams:date dams:subject dams:title <mads:Topic> dams: "Commercial art--United subject States" <owl:sameAs> <lcsh:sh85028914><dams:Object> <dams:Object>bb1809708v bb16050824 dams: <mads:PersonalName> dams: dams:relationship dams:relationship name "Geisel, Theodor Seuss, name 1904-1991" <owl:sameAs> <lcnaf:n91084846> <dams:Role> "creator" dams:<dams:Relationship> dams: <dams:Relationship> role role <owl:sameAs> <marcrel:cre>

Implementation Esmé Cowles

DAMS Repository• New version of our lightweight repository – Metadata in triplestore – Files on disk or cloud storage• Explicit structural metadata• Native REST API• Fedora REST API (partial)

DAMS Manager• Separate Java webapp• Ingest, batch operations• Uses DAMS Repository REST API• Functionality moved into the repository – Characterization (JHove) – Fixity checking – Derivatives (ImageMagick)

DAMS Public Access System• Old frontend is unsustainable• New frontend in Hydra – Backed by DAMS Repo, not Fedora• Hydra platform and community

Timeline• Started 2 months ago• Code sprint in January with cbeer and jcoyne• March: Beta release with research data• Spring: Migrating existing content• Summer: Production release

One More Thing• We’ve talked about DAMS for years...• Now we have code to share http://github.com/ucsdlib/ @escowles @mattcritchlow bdwestbrook@ucsd.edu