Product versions and other additions for DOI process

[smithara]

To mint DOIs there are some essential metadata to be provided:

1. URL for landing page
2. title of dataset
3. author list
4. version number
5. date of publication

To mint a DOI for a given product, this catalogue should therefore contain, for each collection:

1. URL: link to handbook page
2. title of dataset (DONE: definition, but should be reviewed)
3. author list (do we default to "Swarm Team" for L1B?)
4. hierarchy like {version number: {year, details}}

To decide:

• Do we mint a DOI for every product in the handbook? What about externally provided data like CHAMP MAG, which already has a DOI?
• Author list is different per-collection:
  • this will take some time to collect and decide
  • For which ones do we simply use "Swarm Team", all of L1B?
  • and do we define "Swarm Team" somewhere?
  • Do we add "Swarm Team" to all collections in addition to named authors?

[smithara]

Versions

Version hierarchy might be implemented in the schema under the changelog field. For example:

Change:

                "changelog": {
                    "type": "string",
                    "contentMediaType": "text/html"
                },

to:

        "changelog": {
          "version": {
            "year": {
              "type": "string"
            },
            "details": {
              "type": "text/html"
            }
          }
        },

• Should the name "changelog" be changed?
• Consider how will the contents be displayed in the handbook. Make it easy to construct a section with subtitles (for each version)
• Use a full date instead of "year"?
• The DOI minting will just require, "year" and "version"
• The version is a four-digit number with two parts (AABB). AA is the baseline (significant change: mint a DOI). BB is a file counter (not significant: don't mint a new DOI). We don't need to detail changes in BB so should we list "versions" here as, for example, 06xx? since the changelog entry remains valid for all values of xx. This has consequence also for the DOI (should the citation say 06xx rather than 0601 ?)

Author list

Add a field like:

        "authors": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },

misc

Add URLs: both "DOI" and "handbook page". In fact.. DOI should be associated with the version inside "changelog".

mapping to other schemas

Check how compatible these changes will be with SPASE