uc san diego library: where we are with linked data arwen hutt

UC San Diego Library: Where we are with Linked Data Arwen Hutt

What we’ve done so far:• RDF triplestore• Designed and implemented a local data model and

ontology (using MODS/METS for inspiration and MADS for authorities) and converted our legacy data • Converted strings to things (sort of) - names, titles,

subjects are all represented by (local) URI’s• BIBFRAME monitoring group – lots of LD discussion!

DAMS Technical Infrastructure

What we’ve done so far:• RDF triplestore• Designed and implemented a local data model and ontology (using MODS/METS for inspiration and MADS for authorities) and converted our legacy data • Converted strings to things (sort of) - names, titles,

subjects are all represented by (local) URI’s• BIBFRAME monitoring group – lots of LD discussion!

What we’ve done so far:• RDF triplestore• Designed and implemented a local data model and

ontology (using MODS/METS for inspiration and MADS for authorities) and converted our legacy data • Converted strings to things (sort of) - names, titles, subjects are all represented by (local) URI’s• BIBFRAME monitoring group – lots of LD discussion!

What we’ve done so far:• RDF triplestore• Designed and implemented a local data model and

ontology (using MODS/METS for inspiration and MADS for authorities) and converted our legacy data • Converted strings to things (sort of) - names, titles,

subjects are all represented by (local) URI’s• BIBFRAME monitoring group – lots of LD discussion!

What we’re working on now:• Contributing to the community development of Fedora 4 and

Hydra• Revised, tiered, community data model

• Portland Common Data Model• DPLA Metadata Application Profile• UCSD needed Classes and Predicates

• When possible, using properties from community schemas (DC, DPLA, Schema.org, etc.)

• Simplify• SKOS/DC instead of MADS • Improved RDF encoding • Simplify some metadata

• New approach to rights and access metadata, including using existing URI’s (Creative Commons, Europeana) instead of text

• PCDM diagram

Portland Common Data Model

What we’re working on now:• Contributing to the community development of Fedora 4 and Hydra• Revised, tiered, community data model

• Portland Common Data Model• DPLA Metadata Application Profile• UCSD needed Classes and Predicates

• When possible, using properties from community schemas (DC, DPLA, Schema.org, etc.) • Simplify

• SKOS/DC instead of MADS • Improved RDF encoding • Simplify some metadata

• New approach to rights and access metadata, including using existing URI’s (Creative Commons, Europeana) instead of text

• Snippet of new data model spreadsheet, highlight the tiers and then the other uri’s (add a bibframe one?)

What we’re working on now:• Contributing to the community development of Fedora 4 and Hydra• Revised, tiered, community data model

• Portland Common Data Model• DPLA Metadata Application Profile• UCSD needed Classes and Predicates

• When possible, using properties from community schemas (DC, DPLA, Schema.org, etc.) • Streamline

• SKOS/DC instead of MADS • Improved RDF encoding • Simplify some metadata

• New approach to rights and access metadata, including using existing URI’s (Creative Commons, Europeana) instead of text

What we’re working on now:• Contributing to the community development of Fedora 4 and Hydra• Revised, tiered, community data model

• Portland Common Data Model• DPLA Metadata Application Profile• UCSD needed Classes and Predicates

• When possible, using properties from community schemas (DC, DPLA, Schema.org, etc.)

• Simplify• SKOS/DC instead of MADS • Improved RDF encoding • Simplify some metadata

• New approach to rights and access metadata, including using existing URI’s (Creative Commons, Europeana) instead of text

What we’re working on now:• Contributing to the community development of Fedora 4 and Hydra• Revised, tiered, community data model

• Portland Common Data Model• DPLA Metadata Application Profile• UCSD needed Classes and Predicates

• When possible, using properties from community schemas (DC, DPLA, Schema.org, etc.)

• Simplify• SKOS/DC instead of MADS • Improved RDF encoding • Simplify some metadata

• New approach to rights and access metadata, including using existing (community) URI’s (Creative Commons, Europeana) instead of text

We’re also investigating:

• Adding URI’s to MARC records• Enhancing identity

management• Connecting the dots, entity

resolution (“strings” to things) and reconciliation (things to things)• Using LD for improved user

experience - search expansion, enhanced browse, etc.

Links

• Our GitHub acct: https://github.com/ucsdlib/ • Hydra Metadata Working group: https://

wiki.duraspace.org/display/hydra/Hydra+Metadata+Working+Group • Revised (in process) data model: http://

bit.ly/ucsd_dams_4_2_model• Our current data model: http://bit.ly/ucsd_dams_4_model• Portland Common Data Model: https://

wiki.duraspace.org/pages/viewpage.action?pageId=69011689 • More about our changing approach to rights: http://

bit.ly/rightspres