ESAVO Full Harvestable Registry

[KevinBenson]

Very nice Aurelien, looks good.

I will put it as one of the registries to be harvested at Astrogrid on
Monday.  Sorry for being late on the next Interface Spec document, I should
have it ready by Monday afternoon for review.

Yes the Resource namespace after "metadata"  being the Registry Interface is
fine for Astrogrid registries, we tend to xsl what is below the "metadata"
element to what is needed by our registries.  We might want to put that
issue back on the list of discussions though.  Originally we had it as
"Registry Interface" namespace as well, but early on registries kept having
trouble harvesting us, so eventually decided to make things easier and xsl
to where it is now vr:Resource.

Let me know what problems your having with any Astrogrid Registries, I
suspect it might be because we currently don't support sets.  So a
ListRecords call is by default ivo_managed and does not support the "set"
parameter to it.  I hope to support sets soon, but suspect another good 2
weeks till it is on the production servers.

Here are the known OAI urls to Astrogrid registries:
http://galahad.star.le.ac.uk:8080/galahad-registry/OAIHandlerv0_10   //our
main full+publishing leicester registry
http://msslxv.mssl.ucl.ac.uk:8080/astrogrid-registry/OAIHandlerv0_10
//publishing registry
http://astrogrid.ast.cam.ac.uk/CASU-registry/OAIHandlerv0_10 //publishing
registry --currently down at the moment
http://hydra.star.le.ac.uk:8080/astrogrid-registry/OAIHandlerv0_10 //a
full+publishign leicester registry that will disappear in the coming months.
//finally there is another full registry at Cambridge but it does not really
manage anything so nothing to harvest from that one.


cheers,
Kevin

-----Original Message-----
From: owner-registry at eso.org [mailto:owner-registry at eso.org]On Behalf Of
Aurelien Stebe
Sent: 22 July 2005 15:31
To: registry at ivoa.net
Cc: Pedro Osuna; Christophe ARVISET
Subject: ESAVO Full Harvestable Registry


Hi all,

The ESAVO Registry is now ready and installed on a public server.
We would like the Registry WG to test it and make comments
before doing a public release at the end of this summer.

http://esavo.esa.int/registry/

This is a full harvestable registry supporting VOResource v0.10 +
OpenSkyNode 0.1
Here is the OAI HTTP interface : http://esavo.esa.int/registry/oai.jsp
the Search Web Service interface :
http://esavo.esa.int/registry/services/RegistrySearch
and the Harvest Web Service interface :
http://esavo.esa.int/registry/services/RegistryHarvest

You should note that it is supporting the Sets and returning all resources
if no set is specified, so make sure to harvest using set=ivo_managed.
It does not support resumption tokens yet and use a date only granularity.

The database was populated using a dump of the NVO registry,
then we successfully harvested HEASARC, JVO, NCSA and CDS.
We are having some problems with the other registries.

Two other comments, most of the registries seem to use the VOResource
namespace on the "Resource"
element when returning records in OAI, while we return it using the
Registry Interface namespace as for the
Search interface. I'd be happy to change our OAI response, I just want
to know what should be the right way to do this.
Also, most resources are missing the updated or created attributes
(sometimes both) which forced us to default
those date entries to the current date. Created might not be very
important, but updated could be usefull to have.

Awaiting for your comments ...

Cheers,
Aurelien STEBE