Versions Compared

Old Version 8

changes.mady.by.user Eduardo Damasio da Costa

Saved on

compared with

New Version 9

changes.mady.by.user Eduardo Damasio da Costa

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Note 1:  At the very start of the integration  only the information described in fist step below needs  to be  provided in a complete and accurate way. However, if information described in step 2  can be provided as well that would be useful. 
Note 2: This is an iterative process. When the integration process progresses we expect to alter titles, abstracts, variable names, and even address convention,  if the CDS cannot manage the structure of the dataset.
Note 3: A dataset can be split in two or more  entries or merged with an already existing entry in the Catalogue
Note 4: The last word concerning the contents and the format of the final entry (entries) in the Catalogue is made by the CDS Editorial Board.

Information to be provided: 
(Please us the latest version of  document in the next column to provide that information)

First step of the Integration: data

Please provide:

  • Contract tag or reference
  • Temporary name (title) for the ensemble of data expected to be seen in the Catalogue
  • Location of the manifest file (usually a url address)
  • Name conventions for paths, filenames and variable names
  • version management

Second step of the integration:  documentation

Please provide:

  • overview
  • picture
  • explanation for the variables
  • licence
  • filenames of PUGS etc


Latest version of te information document

Where:

Latest version:

Information_contract-tag_Temporary-dataset-name_Optional-tag_latest_

v10

v11.doc

 



Old versions:

Information_contract-tag_Temporary-dataset-name_Optional-tag_latest_v10.doc 
Information_contract-tag_Temporary-dataset-name_Optional-tag_latest_v9.doc 
Information_contract-tag_Temporary-dataset-name_Optional-tag_latest_v8.doc 
Information_contract-tag_ECV-or-SIS-name_Optional-tag_latest_v7.doc Information_contract-tag_ECV-or-SIS-name_Optional-tag_latest_v4.docx

To be used at the opening of the integration process

Information to be provided

Integration of data:

  • Contract tag or reference
  • Temporary name (title) for the ensemble of data expected to be seen in the Catalogue
  • Location of the manifest file (usually a url address)
  • Name conventions for paths, filenames and variable names
  • version management

Integration of documentation:

  • overview
  • picture
  • explanation for the variables
  • licence
  • filenames of PUGS etc

Integration of documentation is the second step of the integration and should be done after integration of the data

...



Action:
Provider adds the information document to the JIRA ticket and asks the CDA to start the integration. 


History:

2021-02-15: Version 10: Better description of manifest and address conventions

2021-01-05: Version 10: Ask for more information on versioning on the abstract 

2020-07-21: Version 09. asking for info on version of the dataset and policy to manage wrong/deprecated data. 

2019-10-30: Version 08. Minor revisions.

2019-10-10: Version 07. Complete review of version 4.

2019-03-07: Version 04. 

...