IG Data Fabric : PID Centric Configuration Building

You are here

25 May 2016 2409 reads

Meeting title Data Fabric Configuration Building : PID-Centric

Please give a short introduction describing the activities and the scope of the group

Numerous data experts see PIDs as central for proper data management and access.   At a Plenary 7 Data Fabric session, an inductive approach was used to attack data fabric composition; where component composition starts small and builds up from component size (n=1). Our approach is PID Centric Data Management and Access as it builds upon existing reference software of the Persistent Identifier Types and Data Type Registry RDA recommendations.

This activity has been explored since Plenary 7, with a proposal to host a session at Plenary 8 where experts discuss a strategy for arriving at consensus for one or more data models for minimal metadata associated with PIDs.  It pushes just beyond where the PIT WG stopped.  The PIT WG defined a number of PID minimal metadata attribute types and an API for global ID agnostic PID handling but stopped at that point.   Some large projects took the next step independently and have a data model for minimal metadata and these will be invited and drawn upon to inform the discussions.     One positive outcome of the effort would be for the RDA community as a whole to endorse an existing approach.    Another but different positive outcome would be profile based, with profiles for minimal metadata developed by individual communities of users.  

Why undertake this? Our group will push further to come up with agreed upon models Minimal metadata associated with a PID allows for rapid and lightweight accept/reject decisions to be made about the suitability of an object.  PIDs resolve extremely quickly, so the minimal PID metadata could be used to make decisions about routing an object for instance.   But the PID record should also contain the pointer to the full metadata description so that richer decisions can be made.   Pointers to the metadata embedded with the PID also ensure that the metadata record is not decoupled from the data record – it is bound forever through the metadata record of the PID.     To enable this kind of functionality,  the information in the PID record needs to have type information with it, and the definition of the type both registered and described in way that both humans and machines can interpret the typed data. The PID thus serves, in essence, as a map or a guide to both locating a given data object, aka digital object, as well as interpreting and potentially reusing the object.

Please provide additional links to informative material related to your group i.e. group page, Case statement, working documents etc


Please list the meeting objectives

  • Inform attendees about existing approaches to PID minimal metadata
  • a workplan over the next 9 months for arriving at one or more data model profiles for minimal metadata associated with PIDs 

Meeting agenda

  • Co-chairs give overview of problem and goals
  • One or two short presentations from projects that have defined minimal metadata for PIDs
  • Framed discussion about next steps

A report will be written and published via the DFIG site.

Audience: Please specify who is your target audience and how they should prepare for the meeting

All members of DFIG and those interested in the topics are welcome. DFIG is an open forum to also always look for dedicated activities.  Target audience should be familiar with DTR and PIT WG outputs 

Group chair serving as contact person

Beth Plale*, Larry Lannom, Tobias Weigel, Peter Wittenburg

* contact