Research Data Collections WG


Group details

Secretariat Liaison:
Case Statement: 
WGs Maintaining deliverables (maintenance group)

Several communities have expressed interest in leveraging aggregations of objects with particular focus on building such aggregations through PIDs and possibly providing identifiers for aggregation objects. There is however no unified cross-community approach to building and managing such collections and no common model for understanding them. The PID Information Types WG has defined a core model and the central interface for accessing object state information and provided a small number of example types, which were consequently registered in the Type Registry WG prototype. With these tools available to describe essential object information, collections can be described so to be able to deal with more than a single object at once.

Building collections within diverse domains and then sharing or expanding them across disciplines should enable common tools for end-users and e-infrastructure providers. Individual disciplinary communities can directly benefit if such tools are made widely available, and cross-community data sharing can benefit from increased unification between collection models and implementations. PID providers may benefit from marketing additional services on collections.

The group has assembled a full recommendation, which is endorsed by RDA. The recommendation is available here:

Group navigation menu:

Recent Activity

22 Feb 2018

Research Data Collections in one slide

Dear all,
looking through past presentations, I did not find a good option that
displays very concisely in one slide what our group has achieved and
what the specification is all about. Based on our P10 outputs
presentation I've drafted a single slide, see attached. Comments welcome
- I want to put this on our entry page or link to it from our
recommendation page if possible.
Best, Tobias
Dr. Tobias Weigel
Abteilung Datenmanagement

02 Feb 2018

Data Collections WG breakout session at P11 in Berlin approved!

Dear all,
great news: our application for a breakout session at P11 in Berlin has been approved - see below for more information about the allocated time slot, as well as the preliminary agenda (included in the session application at the bottom of this message).
Best regards,
- Show quoted text -From: Timea Biro <***@***.***>
Sent: Thursday, February 1, 2018 22:57
To: Margareta Hellström
Subject: Re: Fwd: Form submission from: 11th Plenary Group Session Application Form - WG Research Data Collections

29 Aug 2017

Minutes from today's collection VC

Next meeting: F2F at P10
- Actual API spec is final and released after last minor changes
(renames, documentation)
- Most things we discussed during the call on the recommendations
document are already inserted/added on Github in the issues
- The P10 main session will be based on an extended version of the slide
set used for the outputs plenary presentation
- Output presentation notes:
-- Javier and possibly other adopters/implementors should send 1 slide
to Tobias

31 Jul 2017

summary of recent API changes

Hi all
I think we can consider the Collections API swagger spec frozen now.
I've tagged it as Release Candidate 1.0 (rc1.0.0)
As promised, here is a summary of recent changes (these are changes made
since P9):
You can see the details of these in the commit log:
Model Changes:
- a "*description*" property was added to the *MemberItem* object
- a "*dateUpdated*" property was added to

27 Jul 2017

Notes from collection WG call July 25

Next call: August 29 (recommendation review call)
Call on August 8 is cancelled.
Notes on recommendation/spec work in progress:
* If you have worked on an issue and want someone to review it, please
assign it to Tobias using GitHub - he will play the editor for it
o Bridget will be the editor for Tobias' issues
* Bridget: revised permissions section; worked on introduction and 2.1
- argued for why we did the capabilities stuff
o also: post to Fedora list
o will add a section on this

21 Jul 2017

looking for stakeholders for a Fedora implementation of the RDA Collections API

Dear list members,
We are approaching the close of our 18 month Research Data Alliance
working group effort to develop a general purpose API for working with
research data collections [1]. This work stemmed from a needed
expressed by several communities across disciplines to leverage
aggregations of objects with particular focus on building such
aggregations through PIDs and providing identifiers for aggregation
objects. Up until now there has been no unified, machine-actionable