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!

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!

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

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

11. PCDM diagram Portland Common Data Model

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. Snippet of new data model spreadsheet, highlight the tiers and then the other uri’s (add a bibframe one?)

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

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

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

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

19. Links Our GitHub acct: https://github.com/ucsdlib/https://github.com/ucsdlib/ Hydra Metadata Working group: https://wiki.duraspace.org/display/hydra/Hydra+Metadata+Working+Gr oup https://wiki.duraspace.org/display/hydra/Hydra+Metadata+Working+Gr oup Revised (in process) data model: http://bit.ly/ucsd_dams_4_2_modelhttp://bit.ly/ucsd_dams_4_2_model Our current data model: http://bit.ly/ucsd_dams_4_modelhttp://bit.ly/ucsd_dams_4_model Portland Common Data Model: https://wiki.duraspace.org/pages/viewpage.action?pageId=69011689 https://wiki.duraspace.org/pages/viewpage.action?pageId=69011689 More about our changing approach to rights: http://bit.ly/rightspreshttp://bit.ly/rightspres