Information on resource 'GAVO RegTAP Service (Paris Mirror)'

Services defined within this resource descriptor

• A Resolver for IVOA Identifers (IVOID)

  A service for easy access to VOResource information by IVOID (“resolve IVOA identifiers”) – simply append the IVOID to the base URL of this service. There is actually a shortcut for this service on the mein GAVO server: Just prepend https://dc.g-vo.org/I/ to an IVOID to get its VOResource rendered.

• GAVO DC searchable registry PMH interface

  The OAI-PMH endpoint of the GAVO searchable registry. This service gives access to the full content of the VO registry using the Open Archive Initiative's protocol for metadata harvesting. Advanced queries are possible using ADQL in the rr schema at http://dc.g-vo.org/tap.

  For the DC's publishing registry, see http://dc.g-vo.org/oai.xml.

• Harvest Trigger Service

  Operators of publishing registries can use this service to request a re-harvest of their registry by pasting in their registry's IVOID below. If you paste in the magic value ivo://ivoa.net/rofr, we will also fetch new registries from the RofR.

  You usually want to use this when you want to see the effect of some change in your registry on, say, TOPCAT. Note that you cannot start a full re-harvest of a registry from this interface. Contact the operators if you think you need that.

• RegTAP examples

  This service has the examples from the RegTAP spec in the form of a DALI examples document.

• VOResource Landing Page Generator

  A service that turns VOResource into HTML in a way that is supposed to work as a DataCite-style landing page, explaining non-VO experts what access options there may be. Use it by prepending http://dc.g-vo.org/LP to any ivoid and feeding that to your web browser.

Tables defined within this resource descriptor

• rr.alt_identifier – queryable through TAP and ADQL

  An alternate identifier associated with this record. This can be a resiource identifier like a DOI (in URI form, e.g., doi:10.1016/j.epsl.2011.11.037).

• rr.authorities – queryable through TAP and ADQL

  A mapping between the registries and the authorities they claim to manage.

• rr.capability – queryable through TAP and ADQL

  Pieces of behaviour of a resource.

• rr.g_num_stat – queryable through TAP and ADQL

  An experimental table containing advanced statistics for numeric table columns. This is only available for very few tables at this point.

  Note that the values reported here may be estimates based on a subeset of the table rows.

• rr.imported

  Administrative table: the files ingested together with the processing date. Due to incremental harvesting, multiple files may/will exist for a single resource.

• rr.interface – queryable through TAP and ADQL

  Information on access modes of a capability.

• rr.intf_param – queryable through TAP and ADQL

  Input parameters for services.

• rr.oairecs

  Pre-rendered XML fragments for building OAI-PMH documents.

• rr.registries – queryable through TAP and ADQL

  Administrative table: publishing registries we harvest, together with the dates of last full and incremental harvests.

• rr.relationship – queryable through TAP and ADQL

  Relationships between resources (like mirroring, derivation, serving a data collection).

• rr.res_date – queryable through TAP and ADQL

  A date associated with an event in the life cycle of the resource. This could be creation or update. The role column can be used to clarify.

• rr.res_detail – queryable through TAP and ADQL

  XPath-value pairs for members of resource or capability and their derivations that are less used and/or from VOResource extensions. The pairs refer to a resource if cap_index is NULL, to the referenced capability otherwise.

• rr.res_role – queryable through TAP and ADQL

  Entities (persons or organizations) operating on resources: creators, contacts, publishers, contributors.

• rr.res_schema – queryable through TAP and ADQL

  Sets of tables related to resources.

• rr.res_subject – queryable through TAP and ADQL

  Topics, object types, or other descriptive keywords about the resource.

• rr.res_table – queryable through TAP and ADQL

  (Relational) tables that are part of schemata or resources.

• rr.resource – queryable through TAP and ADQL

  The resources (like services, data collections, organizations) present in this registry.

• rr.stc_spatial – queryable through TAP and ADQL

  The spatial coverage of resources. This table associates footprints (ADQL geometries) with ivoids. The footprints are intended for resource discovery; a reasonable expectation for the resolution thus is something like a degree.

• rr.stc_spectral – queryable through TAP and ADQL

  The spectral coverage of resources, given as one or more intervals. The total coverage is (a subset of) the union of all intervals given for a resource. The spectral values are given as messenger energy.

• rr.stc_temporal – queryable through TAP and ADQL

  The temporal coverage of resources, given as one or more intervals. The total coverage is (a subset of) the union of all intervals given for a resource. All times are understood as MJD for TDB at the solar system barycenter.

• rr.subject_uat – queryable through TAP and ADQL

  res_subject mapped to the UAT. This is based on a manual mapping of keywords found in 2020, where subjects not mappable were dropped. This is a non-standard, local extension. Don't base your procedures on it, we will tear it down once there is sufficient takeup of the UAT in the VO.

• rr.table_column – queryable through TAP and ADQL

  Metadata on columns of a resource's tables.

• rr.tap_table – queryable through TAP and ADQL

  TAP-queriable tables.

• rr.validation – queryable through TAP and ADQL

  Validation levels for resources and capabilities.

[Manage RD]