1 / 19

UC San Diego Library: Where we are with Linked Data

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

JasminFlorian
Download Presentation

UC San Diego Library: Where we are with Linked Data

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. 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!

  3. DAMS Technical Infrastructure

  4. 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!

  5. 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!

  6. 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!

  7. 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

  8. PCDM diagram Portland Common Data Model

  9. 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

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

  11. 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

  12. 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

  13. 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

  14. 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.

  15. 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

More Related