Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Portland Common Data Model (PCDM): Creating and Sharing Complex Digital Objects

1,132 views

Published on

Interoperability has long been a goal of digital repositories, as demonstrated by efforts ranging from OAI-PMH, to attempts to create common APIs such as IIIF, to community based metadata standards such as Dublin Core. As repositories have matured and the desire to work more collaboratively and reuse source code has grown, the need for a common understanding of how digital objects are conceived and represented is essential. The Portland Common Data Model (PCDM) is an effort to create a shared, linked data-based model for representing complex digital objects. Starting in the Hydra community but quickly expanding to include contributors from Islandora, Fedora, the Digital Public Library of America, and other repository-related service communities, PCDM is the result of over sixty practitioners’ contributions to a shared model for structuring digital objects. The process was holistic and rooted in concrete use-cases. An initial in-person meeting in Portland, Oregon in fall 2014 resulted in the release of the first draft of the data model for which it is named. With this shared model, we intend to further the goal of interoperability across repositories and related technologies. This presentation will review the origins of PCDM, provide a general technical overview, update on current status, and forecast future work.

Published in: Education
  • Be the first to comment

Portland Common Data Model (PCDM): Creating and Sharing Complex Digital Objects

  1. 1. Portland Common Data Model (PCDM): Creating and Sharing Complex Digital Objects Karen Estlund, Penn State University Declan Fleming, University of California, San Diego Mark A. Matienzo, Digital Public Library of America Jon Stroop, Princeton University Library
  2. 2. Agenda Purpose and History Technical Details Current Work Future Q & A
  3. 3. Why a common data model? ● Common language and concepts for: ○ simple to complex object structure ○ rights assertions and access control ○ technical metadata ● Allows for shared objects and coding efforts rather than reinventing for every instance ● Aggregates many minds, projects, and products around difficult concepts ● RDF approach allows for extensibility for the future and local customization
  4. 4. PCDM History ● Hydra implements basic RDF 4/2012 ● UCSD complex object data modeling work published 10/2012 ● Oregon RDF work - linked open data and vocabularies registry 2013 ● Stanford RDF meeting 10/2013 ● Hydra Connect 2014 ● Use cases on Github - open process 2014 - (more than developers) ● Portland meeting 11/2014 ● Portland Code4Lib PCDM Meeting 2/2015 ○ concepts like “works,” “resource,” FRBR removed from the model ○ embraced it as an abstract object model not bibliographic
  5. 5. PCDM - More history ● Whiteboard modeling exercises 2015 ● OR 2015 ○ Open solicitation of input ○ refined ordering - still in progress but a working approach exists ● Still evolving ● “Portland” - where we met ● “Common Data Model” ○ Because it’s not just Hydra ■ Islandora, Europeana have same data needs ○ History of the naming ■ avoiding baggage ■ neutral model
  6. 6. Technical Details - Karen Things ● Collection ● Object ● File Relationships ● Has Member ● Has File ● Aggregates ● Has Related File https://github.com/duraspace/pcdm/
  7. 7. PCDM Domain Model
  8. 8. Example: Acerca del chocolate. Mandeville Special Collections Library, UCSD
  9. 9. ...and what can we say about different types of things What Can go Where?
  10. 10. Access Control - pcdm:Collection, pcdm:Object, and pcdm:File Group A can VIEW Group A can VIEW
  11. 11. Descriptive Metadata - pcdm:Collection and pcdm:Object Acerca del chocolate : Manuscript on chocolate ca. 1730 https://libraries.ucsd.edu/ark:/20775/bb3482101x Mandeville Special Collections Library, University of California, San Diego, La Jolla, 92093-0175 Catholic Church--Mexico--History--18th century Cocoa--Therapeutic use--Early works to 1800
  12. 12. Technical Metadata and Bitstream: pcdm:File 2013-11-29T13:56:46-04:00 image/tiff20775-bb3482101x-1-1-3.jpg Intermediate File 527 KB d3b07384d113edec49eaa6238ad5ff00 0000E32F 90990902
  13. 13. PCDM
  14. 14. hasFile Acerca del chocolate
  15. 15. More than one Object hasFile hasFile Acerca del chocolate Inscription Book Plate hasMemberhasMember
  16. 16. More with Objects! hasFile hasMember hasFile aggregates Acerca del chocolate Inscription
  17. 17. Ordering Inscription Book Plate Acerca del chocolate hasMember ore:Proxy ore:Proxy hasFile hasFile proxyIn last proxyIn first nextprevious proxyFor proxyFor
  18. 18. Related Files hasFile hasRelatedFile describes describedBy Inscription
  19. 19. Collections hasMember 18th Century Catholic Church Medicinal Texts Acerca del chocolate
  20. 20. More Collections hasMember Acerca del chocolate hasMember Holograph ManuscriptshasMember Catholic Church Health & Hygiene Texts The Catholic Church in California
  21. 21. Reference Diagram from Use Case Exercise https://wiki.duraspace.org/display/FF/PCDM+Mappings+-+Reference+Diagrams+for+Comment
  22. 22. Sufia CurationConcerns Hydra::Works Hydra::PCDM AF PCDM in Hydra
  23. 23. AF Work with Fedora in a way that feels like Ruby on Rails PCDM in Hydra
  24. 24. Hydra::PCDM Build models based on PCDM objects and relationshipsAF PCDM in Hydra
  25. 25. Hydra::Works This also allows for shared code around:: ● Characterization (JHOVE, DROID, etc.) ● Make Derivatives ● Virus Checking ● Text Extraction Hydra::PCDM AF PCDM in Hydra ● Work Objects ● FileSet Objects ● Group FileSets to create Works
  26. 26. hasFile hasFile Acerca del chocolate (Object) “Page 1” (Object) hasMember (Master File) (Thumbnail)
  27. 27. ● Custom Models ● Routing for CRUD ● File Auditing / Versioning ● Single-Use links ● Upload File Sets ● Access Controls ● Leases and Embargoes ● Proxy Deposit ● User Dashboard & Profiles ● Featured Works & Researchers ● Contact Form ● Activity Streams ● Upload via Cloud Providers Sufia CurationConcerns Hydra::Works Hydra::PCDM AF PCDM in Hydra
  28. 28. PCDM in Islandora https://github.com/duraspace/pcdm/wiki/Diagrams#islandora
  29. 29. The Future of PCDM ● Within Hydra, Islandora, and Fedora communities ● Interoperability across other communities ● Governance, engagement, and maintenance
  30. 30. The future of PCDM: Within Hydra/Islandora/Fedora communities ● Hydra in a Box ● Use and development of PCDM recommendations & extensions ○ Rights metadata ○ Technical metadata ■ File format genre ontology ■ File use vocabulary
  31. 31. The future of PCDM: Interoperability across communities ● Alignment with/mappings to additional community models ○ International Image Interoperability Framework ○ Europeana Data Model ○ DPLA Metadata Application Profile ○ RightsStatements.org ● Expansion into W3C standards development processes ○ Linked Data Platform ○ WebAccessControl
  32. 32. The future of PCDM: Engagement, governance, and maintenance ● Community engagement beyond the Hydra, Islandora, and Fedora 4 communities ● Determining best venues for sustained community engagement ● Vocabulary management infrastructure ● Identifying the best long-term home for PCDM
  33. 33. How to learn more and get involved ● Visit the PCDM Wiki: https://github. com/duraspace/pcdm/wiki ● Join the PCDM Google Group: https://groups.google. com/d/forum/pcdm ● Participate in working groups: ○ Hydra Metadata Interest Group ○ Islandora Metadata Interest Group ● Questions for attendees ○ Where should we go next? ○ What do your communities need? ○ How we can get you more involved? ○ What won’t work for you?
  34. 34. Thank you! Karen Estlund Penn State University Declan Fleming University of California, San Diego Mark A. Matienzo Digital Public Library of America Jon Stroop Princeton University Library

×