@@ -79,7 +79,6 @@ The following metadata can be repeated and could follow a controlled vocabulary.
7979
8080- Author: name or ORCID
8181- Organization: name or URL
82- - Editor: name or URL
8382- Journal: name or URL
8483- Datacenter that provides the result: name or URL
8584- Contact: email
@@ -115,7 +114,6 @@ For queries on evolving dataset, the version or the date must complete the infor
115114| version | Dataset version (or release date) | |
116115| service_protocol| Protcol access with version | |
117116| request| Request url | |
118- | request_post| (POST Request) POST arguments ** new** | |
119117| request_date| Query execution date | |
120118| contact| email or URL contact | |
121119| landing_page| Dataset landing page | |
@@ -133,12 +131,11 @@ Dataset-origin completes the "Query information" -
133131| Publication-id| Dataset identifier that can be used for citation | yes |
134132| Curation-level| Controled vocabulary | |
135133| Resource-version| Dataset version od last release | |
136- | Rights| Licence URI | |
137- | Rights-type| Licence type (eg: CC-by, CC-0, private, public) | |
138- | Copyrights| Copyright text | |
134+ | Rights_URI| Licence URI | |
135+ | Rights| Licence type (eg: CC-by, CC-0, private, public) or copyrights| |
139136| Creator| Dataset Author(s) or group | |
140137| Publication-ref| Identifier of the original resource that can be an article or the origin Data Center|
141- | Editor| editor name| |
138+ | Journal or Editor| journal or editor name| |
142139| Relation_type | controled vocabulary (VOResource: relationshipType ? ) to specify relation to related resource ** new** |
143140| related_resource | Original resource ** new** |
144141| Publication-date| Date of the original publication | |
@@ -152,33 +149,6 @@ eg: bibcode:...,
152149Serialisation example: < ; info> ; tag makes the jobs. see <a href =' tests/J_AJ_161_36_table8.xml ' >SCS example</a >
153150
154151
155- - Complex output involving ** several tables** (eg: TAP query, ObsCore result)
156-
157- Dataset-origin depends on each table used for the output. Datamodels like Last-step -Provenance or DatasetDM allows to gather the metadata.
158-
159- DatasetDM Example:
160-
161- | meta-data| Description| Mandatory |
162- | --- | :-: | :-: |
163- | dataset: productType |||
164- | dataset: productSubType | controled vocabulary||
165- | dataset: DataID .datasetDID| dataset ivoid| yes|
166- | dataset: DataID .title| dataset title||
167- | dataset: DataID .creationType| type of resource ||
168- | dataset: DataID .date| Publication date of original dataset/article||
169- | dataset: Party .name| (first)Author | |
170- | dataset: Curation .publisherDID| data-center identifier (ivoid)| yes|
171- | dataset: Curation .rights| rights text| |
172- | dataset: Curation .releaseDate| Data-center publication date| yes|
173- | party.Organisation.email| Data-center contact||
174- | dataset: Curation .doi| Dataset DOI| |
175- | dataset: Curation .bibcode| Dataset bibcode||
176-
177- Serialisation example: DatasetDM serialisation. see <a href =' tests/tap.xml ' >TAP example</a >
178-
179- (see also: <a href =' https://wiki.ivoa.net/twiki/pub/IVOA/InterOpOct2022DM/IVOA-DMTAP-VizieR.pdf ' >datasetDM in TAP (ivoa-talk)</a >
180-
181-
182152
183153# About
184154This document describes simple means to declare basic provenance
0 commit comments