Recent Activity: Research Data Collections WG

12 Apr 2016

Mailing List Digest

Gary

  1. Reagan mentioning types of collections: Digital Collection, Data series, Sensor-based data series, Data set: discrete set, Data stream
  2. PIDs are not substrate
  3. need ontology/concepts/mereology
  4. PID != collection/resource
  5. PIDs important for RDA
  6. identifiers are usually digital identifiers in RDA context
  7. identifiers are bitstrings that can uniquely identify a resource
  8. identifiers are a property of the resource

continue reading

12 Apr 2016

Re: [rda-datafabric-ig] Re: [rda-datafabric-ig][rda-collection-wg] Re: [rda-datafabri...

Jacob,
We are essentially on the same page - maybe a different paragraph.
We agree here "saying something like 'collection == PID' (i.e., a
collection is a PID) is *weird *because the object and the identifier are *not
*the same kinds of things and don't possess the same properties and so are
fundamentally, formally not identical to one another. "
>My point is that identifiers really aren't any different than names,
labels, or what ever you call them.
They are, I would say, of the same KIND. But there are differences in

12 Apr 2016

Re: [rda-datafabric-ig][rda-collection-wg] Re: [rda-datafabric-ig][rda-collection-wg] Re: [rda-datafabric-ig][rda-collection-wg] Some thoughts on "Data Aggregations" terminology & concepts

I have been extremely integrated by the conversation so far regarding data
aggregations. I do have a few questions regarding the data though. I
might have missed this part of the conversation so please bear with me.
How is data licensed/policed? For example, some data might have
restrictions (hippa, fisma, etc). I know it seems like a small issue and
might now fall with in the scope of this conversation, but I would like to
see a field specifically for data policy(ies)/licenses.

12 Apr 2016

Re: [rda-datafabric-ig][rda-collection-wg] Re: [rda-datafabric-ig][rda-collection-wg] Re: [rda-datafabri...

Gary,
Of course, and it is our intent. We have already begun, as Ulrich and
Thomas mentioned, by working through the definitions directly within the
RDA instance of the DFT tool so that our work is visible to all as we go.
Best
Bridget

12 Apr 2016

Re: [rda-datafabric-ig][rda-collection-wg] Re: [rda-datafabric-ig][rda-collection-wg] Re: [rda-datafabri...

Bridget et al,
It would seem that the Research Data Collections WG is the proper place for
this conversation and work advance and that you have already assembled some
of the major resources for this.
At some point you may have candidate concepts with definitions to provide
to DFT and others.
Is that OK with the WG to proceed on this?
Gary Berg-Cross, Ph.D.
***@***.***
​​

12 Apr 2016

Re: [rda-datafabric-ig][rda-collection-wg] Some thoughts on "Data Aggregations" terminology & concepts

Dear Keith, all,
dear, I had to truncate the subject line, because it got to long during
our debate for the RDA list server. I think this is a really strong
reminder to get settled;-)
Dear Keith, all,
dear, I had to truncate the subject line, because it got to long during
our debate for the RDA list server. I think this is a really strong
reminder to get settled;-)
Am 12.04.2016 um 12:41 schrieb ***@***.***:
>
> Ulrich –
>
>
>

12 Apr 2016

Re: [rda-datafabric-ig][rda-collection-wg] Re: [rda-datafabric-ig][rda-collection-wg] Re: [rda-datafabric-ig][rda-collection-wg] Some thoughts on "Data Aggregations" terminology & concepts

Hi Gary, all,
I agree with Thomas: this now tends to become a more and more
philosophical debate - I like this, and we should continue this perhaps
with a beer in Denver. But to shorten the decisions process here let me
assume that an undoubted goal is to setup the foundations to build
automated processes on collections and try to bring it down to a simple
question:
Do we want to be able to prove the correctness of processes on
collections or not. If this is case, we need a mathematical solid

11 Apr 2016

Re: [rda-datafabric-ig][rda-collection-wg] Re: [rda-datafabric-ig][rda-collection-wg] Some thoughts on "Data Aggregations" terminology & concepts

Dear Jeremy, all
here, as far as I can see from a first look, the definition is relying
on the binary predicate /isGatheredInto/(/x/,/y/), which I couldn't find
to be defined at the given location anymore. So one probably cannot use
this as a definition here, without defining how this predicate function
works in all cases.
But the other way around: if one uses my reductionist definition, the
function /isGatheredInto/(/x/,/y/) is almost trivially to define,
because one just looks, whether PID y is contained in the set of PIDs in

11 Apr 2016

Re: [rda-datafabric-ig][rda-collection-wg] Some thoughts on "Data Aggregations" terminology & concepts

Hello Ulrich,
thank you for the examples - I particularly like the power collection
idea as it could solve very aesthetically some of the issues we get into
once we talk about collections that grow over time but yet should be
somewhat statically referable. I think this also has a new twist on the
API: A rule-based collection might need its own dedicated querying and
creation mechanisms (or at least different parameter sets). When
thinking in terms of collection models, I mostly worked along lines of

11 Apr 2016

Re: [rda-datafabric-ig][rda-collection-wg] Some thoughts on "Data Aggregations" terminology & concepts

Hi Tobias, Gary and others,
in principle each function, that generates (new) collections, could be
used. For example from a given collection one could build a new
collection by requiring restrictions like for example time constraints
on the generation of the DOs it contains. Or one can build a kind of
power collection, the collection of all sub collections.
Particularly interesting generation rules come with the possibity of
following the links given in the collection, either by the PIDs in the

29 Mar 2016

Re: [rda-collection-wg] GoToMeeting info for today's call - call notes

Dear all,
here are the main items from our call today - thanks again to all
participating, I think we are well prepared for the next steps.
Timeslot for regular meetings: Last Tuesday of the month at EDT 09:00 /
UTC 13:00 / CEST 15:00 via GoToMeeting for 1 hour. Next meeting on April
26, then until P8 at: 05/31, 06/28, 07/26, 08/30.
Everyone has different preferences and strengths on what to work on -
for the time being, we have:
- Definitions and mathematical foundations (Ulrich, Tom, Frederik, ...)

29 Mar 2016

Use Case Templates

Per the query in our just-ended teleconference, here are links to a sample of Use Case templates from across RDA groups. I think any of these would be fine for use in submitting new use cases to the Research Data Collections group, and welcome suggestions for others.  

The Metadata Directory WG provides a template at template https://rd-alliance.org/use-case-template.html-0 and example usage at  https://rd-alliance.org/use-case-example.html .

21 Mar 2016

Re: [rda-collection-wg] [rda-collection-wg] Collection requirements, streaming -...

Hi Thomas,
you make a couple good points, here’s my take on them:
Hi Thomas,
you make a couple good points, here’s my take on them:
> Am 21.03.2016 um 10:32 schrieb ThomasZastrow
<***@***.***>:
>
> Dear all,
>
> I had this discussion - about immutable/mutable objects a PID is pointing to - already a few times in the past ... and depending who is attending the discussion and which current use cases are in consideration the answers (*if* there are answers) are subject of change.

18 Mar 2016

Re: [rda-collection-wg] Collection requirements, streaming - group call suggestion Mar 29

Hi Frederik,
I've looked at your diagrams [1]; yes, these go in the direction of the
two models I described earlier. I'm missing the "parent item" (the
actual collection) in A. This could be your "Stream n+1" object; there
may be a point about thinking whether that collection is conceptually
defined as the aggregation of all parent relations or as the aggregation
of all object. Also, should one of the objects in A be "stream n"?
Can you also upload the sources you used to create the bitmaps (what did

16 Mar 2016

Collection requirements, streaming

Dear all, Frederik,
attached is a new version of the draft requirements document with
updates from during and after the Tokyo plenary session. Not complete in
any sense, but a good start :-) There are still several things to think
about and discuss.
One item I find very interesting is Frederik's notion of a "stream view"
of collections (one possible model in the speak of our case statement).
So far, I understand this as putting a PID on a life broadcast video:
The collection grows over time, but only at the head, is strictly

Pages