Sciteam Operations - Telecon 20071114 - Registry Curation Info

Present: NAW, EGS, SD, AMSR, JAT, DKW Time: 16.00-17.00

Background on Registry Info

• see Deploy.DeployedDatasets

Looking through pages for the UK datacenters linked from Deploy.DeployedDatasets.

'Further info' should not point to the DSA page as is the case now. The DSA page could be in the registry entry, but somewhere else.

What is currently generating the current 'Further info' entry during installation? The tech info should be there but in a different location. Also make sure that there is some introductory text, eg containing a reference to a paper describing the dataset. Embed other links in the descriptive text (in addition to main link in Further info). Description of columns needs to be there.

We need to have the waveband info in the registry entry.

Focus on the datasets first, then we will do the application description.

ACTION AMSR: find out how changes to the registry entries are made.

Guide to Registry entries - we need to make it easier for people to register their datasets and understand what the different entries mean. Also: NVO have a guide to filling in registry (ACTION: Find it.). See also Guy's guidance notes: http://ag02.ast.cam.ac.uk:8080/gtr-test-registry/resourceHelp.jsp

ACTION: Find out from Kona about registration for DSA (currently several entries in the registry) - how will this change?

Cambridge

Deploy.RegistryInformationAtIoA

EGS: it would be good for Cambridge to have just one registry rather than 3.

Manchester

Deploy.RegistryInformationAtJBCA

AMSR: Merlin Imager provides images but is registered as a cea application generating data on the fly. This is basically a pipeline. How is such a service described in the registry and found?

Leicester

Deploy.RegistryInformationAtLU

JAT: Single resource entry for the whole of the LEDAS multi-mission archive including multiple (100s of) tables. Available at mssl test registry, will shortly be made available via default AG registry. Good news is all tables are active, ADQL queries are enabled and full column descriptions are given and UCD information is populated. But single resource entry makes it difficult to associate describe/find individual tables which are within the LEDAS resource, e.g. 2XMM, from VOExplorer. Possible memory issues with VOExplorer? It needs to be clear when a resource is a mirror of another archive.

Edinburgh

Deploy.RegistryInformationAtROE

DKW: Registry entries at Edinburgh seem pretty ok. 2MASS appears to be registered twice. Prune out duplicate entries. Add references eg to papers in the description.

MSSL

Deploy.RegistryInformationAtMSSL

SD: MSSL entries in pretty good shape. Dataset of solar images includes several different instruments in 1 DSA (different tables). Good for doing joins but difficult to describe in the registry entry - eg which one is the reference URL?

RAL

Deploy.RegistryInformationAtRAL

SD: Here getting the services actually working is the priority. The metadata is not the main problem

Next Steps

Once we have sorted out the UK datasets, we need to identify the key resources from abroad and assess their registry entries. If necessary contact the data providers re their registry entries.

ACTION NAW - find document on datacenter compliance to IVOA standards, and email it to science team.

JAT: Questionnaire for DCA census will be sent out shortly.

General issue is also how to publish small holdings.

Discuss this further at science team meeting in Cambridge on 27th November.