[Observation] relation to Dataset

[CresitelloDittmar, Mark]

Doug,

You're right.. I didn't word that right.
In the model, multiple datasets may have the same obs_id.
I was trying to go the other way.. and I may still have this wrong, but it
says (pg 16)

"The form of the obs_id string is up to the data provider so long as it
uniquely identifies an observation within the archive."

which I'm taking to mean that a dataset may be associated with only 1
observation.  That's what was referring to.

Mark




On Thu, Nov 21, 2013 at 6:31 PM, Douglas Tody <dtody at nrao.edu> wrote:

> On Thu, 21 Nov 2013, CresitelloDittmar, Mark wrote:
>
>
>> I don't think that a Dataset should have a bi-directional relation to the
>> full Observation(s) as I noted at the head of this thread, but should
>>   a) have an association back to components of the Observation (
>> ObsConfig, Proposal ) which become part of the Dataset 'provenance'.
>>       (which is what I think Arnold was saying in the other thread).
>>   b) have metadata identifying the relevant Observation(s) comprising
>> Dataset (DataID.ObservationID), as Francois notes.
>>       but this gets tricky because ObsCore expects a singular (well
>> unique) obs_id for each Dataset.
>>
>
> I was with you up to here.  Obs_ID does *not* have to be unique for each
> dataset - the pubDID is what has to be unique.  Multiple datasets may
> share the same obs_id; this is an essential feature of ObsCore.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ivoa.net/pipermail/dm/attachments/20131121/e5bb700d/attachment.html>