Versions Compared

Key

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

Important notes

  1.  At

...

  1. 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. 

...

  1. 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.

...

  1. A dataset can be split in two or more  entries or merged with an already existing entry in the Catalogue

...

  1. 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 the information document:

Information_contract-tag_Temporary-dataset-name_Optional-tag_latest_v11.doc

Old versions:


ActionExpected action:
The Provider adds the information document to the JIRA ticket and asks the CDA to start the integration. 


...