why we dumped lod for api

20
Why we dumped LOD for API But we are still keeping our metadata LOD- friendly JENNIFER CWIOK IRIS LEE FEBRUARY 15, 2017

Upload: iris-lee

Post on 03-Mar-2017

24 views

Category:

Data & Analytics


0 download

TRANSCRIPT

Page 1: Why We Dumped LOD for API

Why we dumped LOD for API

But we are still keeping our metadata LOD-friendly

JENNIFER CWIOK • IRIS LEE • FEBRUARY 15, 2017

Page 2: Why We Dumped LOD for API

American Museum of Natural HistoryDigital Project ManagerConsultingDigital Asset ManagementWebsite deployment, design and managementDigital Archives

<👀/>

Iris LeeMETADATA MAVEN

Past ExperienceMarvel EntertainmentDigital Archivist/Information Architect

The Granger CollectionMetadata Librarian

Fairchild/Condé NastLibrarian

Lazard FrèresPeriodicals Librarian

University of Georgia LibrariesSerials Cataloger

American Museum of Natural HistoryMetadata AnalystGraphic DesignMaking things pretty since 1999

Past ExperienceAmerican Museum of Natural HistoryProject Archivist

Whitney Museum of American ArtDigital Project CoordinatorPreservation Specialist

University of California, Riverside. California Museum of PhotographyFellow (Camera equipment collection)

Page 3: Why We Dumped LOD for API

Library databases

Page 4: Why We Dumped LOD for API

Library databases

www.wherenow?

Page 5: Why We Dumped LOD for API

Library databases

www.wherenow?

AMNH Science collections

Page 6: Why We Dumped LOD for API

Research gathered in the field

����

��Expeditionary Fieldwork

Library Archives

Page 7: Why We Dumped LOD for API

Research gathered in the field

��

��

���

���

��Expeditionary Fieldwork

Herpetology

Invertebrate Zoology

Ornithology

Page 8: Why We Dumped LOD for API

Link back to provenance

��

��

���

���

��Expeditionary Fieldwork

Herpetology

Invertebrate Zoology

Ornithology

Library Archives

Page 9: Why We Dumped LOD for API

circa 2015

Page 10: Why We Dumped LOD for API

@xlink:hrefcpfRelation/relationEntryoccupationEntryplaceEntryplaceRole*sourceEntry

@xlink:arcrolevocab.org locally defined

Page 11: Why We Dumped LOD for API

• Screenshot of xeac?

xEAC (pronounced zeek)

Page 12: Why We Dumped LOD for API

Linked Open Data!

RDF Triplestore

xEAC

Page 13: Why We Dumped LOD for API

Ummm…. linked open data??

SPARQL-hownow?

Page 14: Why We Dumped LOD for API

Library Applications

Page 15: Why We Dumped LOD for API

Taxonomy as a Service

AMNH Science collections

Peopleamnhp_1

Departmentsamnhc_3

Expeditionsamnhc_2

��

Permanent Hallsamnhc_4

��

Temporary Exhibitionsamnhc_5

Page 16: Why We Dumped LOD for API

��

Library Applications

Page 17: Why We Dumped LOD for API
Page 18: Why We Dumped LOD for API

Hack the Universe

2014Hack the Dinos

2015Hack the Stacks

2016

Page 19: Why We Dumped LOD for API

• Existing Applications API-ready

• Instant ROI – No development needed

• Easier to integrate with other departments using API

• Learning curve high• Would have to RDF all

resources• Infrastructure to have

SPARQL endpoints risky• Would need to develop

additional programming to use data (eg, visualizations)

Page 20: Why We Dumped LOD for API

Thanks!

http://library.amnh.orghttp://images.library.amnh.org/digital/

http://images.library.amnh.org/hiddencollections/https://github.com/amnh/HackTheStacks/wiki

<👀/>

Iris LeeMETADATA MAVEN

[email protected]@supercwiok

[email protected]@collidingIris