search

RDA-DMP-Common / RDA-DMP-Common-Standard

Official outputs from the RDA DMP Common Standards WG
The Unlicense
62 stars 34 forks source link

How to add funder template specific extensions needs be worked out #30

Open hmpf opened 4 years ago

hmpf commented 4 years ago

In order to move a plan from one dmp tool to another without losing data, there must be a place to put the data that is not supported by this standard or by the receiving tool.

I suggest the array "extensions" under "dmp", 0..n. Per entry, a nested datastructure with a fixed set of fields with info about the source system, and then a (json) data-block that is left as is, not vaiidated. It must be possible for validators to know which bits should be skipped over! If there is such a thing already, it is not easy to find documentation about it.

The goal is: export from tool A to tool B, then export back from tool B to tool A, and the two plans looking identical in tool A for the human user. (Tool B might leave stuff in it's own extension of course.)

briri commented 4 years ago

Agreed @hmpf. This is related to an older ticket I created #27.

We are currently using the following to convey DMPRoadmap specific information. Note we're using the singular extension to follow the pattern used for other arrays in the schema:

      "dmp": {
        "extension": [
          {
            "dmptool": {
              "template": {
                "id": 946,
                "title": "Environmental Resilience Institute Data Management Plan"
              }
            }
          }
        ]
      }