EPIC: mapping tools, creation, validation, documentation, and publishing

[StroemPhi]

This task was defined in our WG charter as: "Suggest recommendations on mapping tools, mapping creation, mapping validation, mapping documentation, and mapping publishing."

As an epic task, this issue serves primarily as a hub to link to the more specific subtasks associated with this epic. Hence, please use one of the following issue templates to start (propose) a discussion around a more specific mapping related topic:

• mapping creation issue template

  • This template should be used to discuss specific aspects of how mappings are to be created within NFDI, in terms of which tools, frameworks, standards, and workflows are to be used. Closing such an issue should result in a consensus of our WG which should be documented here.

• mapping documentation issue template

  • This template should be used to discuss specific aspects of how mappings are to be documented within NFDI, in terms of which metadata needs to be provided to document the provenance of a mapping. Closing such an issue should result in a consensus of our WG which should be documented here.

• mapping validation issue template

  • This template should be used to discuss specific aspects of how mappings are to be validated within NFDI. Closing such an issue should result in a consensus of our WG which should be documented here.

• mapping publishing issue template

  • This template should be used to discuss specific aspects of how mappings are to be published within NFDI. Closing such an issue should result in a consensus of our WG which should be documented here.

• mapping tool issue template

  • This template should be used to discuss specific tools, frameworks and standards that can be used in the creation and curation of mappings. Closing such an issue should result in a consensus of our WG which should be documented here.

The only things that should be discussed in the comment section of this issue are about this epic itself, like does it make sense to have so many issue templates, or is the overlap between mapping creation/validation/documentation/publishing/tools too big to maintain such a differentiation.

To keep this discussion space rather "clean", @StroemPhi would hide all comments that have been resolved by somehow being incorporated either here in the description or in some other suitable place/issue, like the README of this epic.