There is no such content in this group
Posts
05
July
2016
Diagram on collections and PIT
Hello Frederik, I've had a look at your diagram; two comments: - As already noted, the object should not be part of the PID record, but it should be pointed to. This may simply be described by replacing "Object" in the top box with "Object pointer" or similar. - You list a "PIT" entry in the technical metadata section along "size" as another example. I would see this as a special (and very useful) interpretation of a PIT: This PIT describes the object as a whole. During the PIT WG, we interpreted a PIT more widely, and particularly0 | Add new comment
05
July
2016
Definitions, mapping function discussion
Hello Ulrich, I have gone through your revised definitions and I think they are an improvement over what I originally wrote. I agree that your point about the rather indirect recursion is right; to build collections of collections is a core feature and should not be obfuscated in the definitions. I've made some small changes to the document (uploaded to the shared folder and attached). I got a bit confused around the collection metadata and membership metadata. I've now further clarified that the latter is part of the former.1 | Add new comment
30
June
2016
DataShare link
Dear all, The link to our DataShare folder disappeared, so here it is again: https://datashare.rzg.mpg.de/index.php/s/W878ggdygLmxzXD Sorry for that. Tom -- Dr. Thomas Zastrow Max Planck Computing and Data Facility (MPCDF) Gießenbachstr. 2, D-85748 Garching bei München, Germany Tel +49-89-3299-1457 http://www.mpcdf.de0 | Add new comment
28
June
2016
Updated specification document
Dear all, As promised, I updated our specifications document so that it contains now the "collections" graphic from Tobias in version 3 and the definitions from Ulrichs mail. The up-to-date version of the document is: CollectionsSpecifications-20160628.odt -> https://datashare.rzg.mpg.de/index.php/s/YWUxkSd7zqplCDM Best, Tom -- Dr. Thomas Zastrow Max Planck Computing and Data Facility (MPCDF)0 | Add new comment
28
June
2016
Minutes From Call 2016-06-28 - Next Meeting on July 26
Action Items and notice for next meeting:0 | Add new comment
28
June
2016
Meeting today?
Dear all, My calendar tells me that we will have a video meeting in the afternoon? Tom -- Dr. Thomas Zastrow Max Planck Computing and Data Facility (MPCDF) Gießenbachstr. 2, D-85748 Garching bei München, Germany Tel +49-89-3299-1457 http://www.mpcdf.de3 | Add new comment
15
June
2016
Minutes from call 2016-06-15 - next meeting on June 28
!!! Next meeting: June 28, 15:00 CEST / 09:00 EDT !!! Minutes from call 2016-06-15: Attending: Thomas, Frederik, Bridget, Javier, Maggie, Ulrich, Tobias Most of the call was used discussion the new definitions Tobias sent over the list and the corresponding diagram uploaded to the workspace. On the diagrams/definitions: * Frederik suggests we could think of the combination of +collection_state as the PID Record , allowing us to think about a collection record as a pid record in the PIT API terms3 | Add new comment
13
June
2016
Meeting & Agenda
Dear all, Just a quick reminder that tomorrow is the second Tuesday of the month and we will have an online meeting at 3pm CEST / 9am EDT / 6 am PDT. Our preliminary agenda is: 1. Feedback to Tobias’ definitions for Collections, State, Capabilities and Metadata 2. Discussion on interfacing with PIT API and DTR 3. Preparation for Dimitris’ Use Case presentation on 07/26 (if he can join the meeting) Hope to see you tomorrow, Frederik=0 | Add new comment
13
June
2016
Further definitions for collections
Dear all, I've taken another shot at extending the definitions - in view of the discussion about collection metadata and capabilities. Let me know what you think - I want to use these to extend the current definitions in the draft doc later on. Every individual *collection* is a 2-tuple of an identifier and collection state. --> The identifier is part of a collection to allow users to define multiple collections that are identical with regards to their membership and general behaviour (operations, metadata etc.).0 | Add new comment
06
June
2016
Metadata for collections
Dear all, Another point: which metadata we want to add to a collection? Some possibilities: a) The easiest case: a collection has only its own identifier, no more other metadata. Disadvantages would be that a potential user needs already to know about the collection. Displaying / exploring through a bunch of collections would be difficult. b) We leave that topic to other APIs like the PIT API or DTR. c) The collection API itself is able to store / handle metadata about the collection(s).3 | Add new comment