Some comments about the Data Collections specification

14 Mar 2017

Dear all,
First of all, sorry for the noise exactly before a call. This is for
sure *not* to be included/discussed today.
Despite that in the last time I could not attend the regular conferences
I've been following carefully the evolution of the discussion and
working in parallel on an implementation of the Data Collections
specification, which we plan to deploy at GEOFON (seismological data
center). I commented this to Tobias when we met a couple of months ago,
but the work was still not finished. He suggested me to contact you with
some suggestions.
Namely, I wanted to send you a couple of comments about the
specification that I think that could improve it.
* It could be important to provide support for the creation of more than
one collection at a time. Probably, sending an array with the
collections and returning an array with the results.
* Idem for members.
* A "download" method for a collection/member in order to get the
bitstreams and not only the metadata (for us this is the most important
functionality). For instance, I implemented /collections/{ID}/download
and /collections/{ID}/members/{ID}/download
* A "version" method to check compatibility with different versions of
this specification (this will evolve for sure in the future). It could
be enough to return a normal version number (e.g. 1.0)
I'm sending you this because I think it could improve the work if you
plan to submit it as it was mentioned on some mails during the last days.
Javier Quinteros
Tel.: +49 (0)331/288-1931
Fax: +49 (0)331/288-1277
Email: ***@***.***
Helmholtz-Zentrum Potsdam
Deutsches GeoForschungsZentrum GFZ
Stiftung des öff. Rechts Land Brandenburg
Telegrafenberg, 14473 Potsdam

  • Bridget Almas's picture

    Author: Bridget Almas

    Date: 14 Mar, 2017

    Thank you for this. These are great suggestions and all well worth
    I wanted to raise the question of supporting crud operations on multiple
    items (collections or members) at a time in today's call as it came up
    during Frederik's implementation work too.
    Download is a very interesting operation.
    And I agree that supporting versioning of the spec itself is a good idea.

submit a comment