Question: harvesting managed vs. all resource records

[KevinBenson]

As you say on your wiki page Ray, you can discover who the curator is by the
Registry type of who is managing that authority id, so I am not quite sure
what the "harvestFrom" gains you.  Now we do need to talk about the notion
again of <ownedAuthority> but that is later (this deals with full-full
harvesting only so we don't keep harvesting every registry around).  An
authorityid should be managed by only one Registry type so I am not quite
sure if harvestFrom will get you anything.  Now it could possibly make sense
to make the curator/contact/e-mail element a required element, just a
thought?

xs:date to my knowledge is okay with time values and in fact astrogrid does
it with a "time" with a "Z" ending and xerces seems to be okay with it.  So
I think date should be okay, we probably should make sure status and updated
are required attributes; possibly created as well.

Yes I like the idea that we should make search interface query only "active"
resources.  We need to get CDS to put in a status attribute though
originally I had registries only doing active ones for a brief time of a day
or two, but realized CDS currently does not have that attribute.

Also I am now coming around on OAI sets, originally I was not to keen on
them, and thought you could just do everything with ListRecords, but I do
see where using a set to get everything the first time could be very good
and is probably not to hard to implement plus adding oai_managed set would
be just as easy.  I do think ListRecords need to only be managed Resources
each time though.

Cheers,
Kevin



-----Original Message-----
From: owner-registry at eso.org [mailto:owner-registry at eso.org]On Behalf Of
Ray Plante
Sent: 04 April 2005 17:21
To: registry at ivoa.net
Subject: Re: Question: harvesting managed vs. all resource records


Hi Aurelien,

Thanks for your comments!

On Mon, 4 Apr 2005, Aurelien Stebe wrote:
> I don't understand why we would need to know where a resource is coming
> from ?

I take it from your referenence to managed resources below that you get
the understand the need for harvesting only resources records managed by
the harvestee.  (For others, see short explanation at
http://www.ivoa.net/twiki/bin/view/IVOA/HarvestAll.)

In general, we need to know which registry a resource record originates
from so that we can trace back and correct problems with individual
records.  For example, if a record is not compliant in its encoding (a
responsibility of the publishing registry), we can contact the curator of
that registry and let him/her know.  Tracking down encoding and content
problems is something we're in the thick of here in the NVO.

> Except for cases when a resource is updated twice the same day.
> For this, the "updated" attribute could be made a "datetime" instead of
> "date",
> or we could force all registry to support the "datetime" granularity for
> the OAI interface.

In practice, I would worry about clock skews when comparing dates too
finely, but perhaps the "xs:date" type imposes arbitrarily too coarse a
granularity.

OAI requires the use of UTC in all its times (I actually haven't check to
see if we comply with this).  If full seconds granularity is given, it
enforces (through the schema) that the special UTC designator (a trailing
Z) be used.  If we change the VOResource updated attribute type to all
finer granularity, we should probably impose this same restriction.

cheers,
Ray