Replace fairsharing collections with DOIs

[bedroesb]

This will close #1796

[github-actions]

Before approving and merging a pull request (PR), the editors must check that

• The page layout in the preview looks correct.
• The new page is linked in the appropriate sidebar menu, in the same branch of the PR.
• The contributors' names are listed in the CONTRIBUTORS file, in the same branch of the PR. Advice to have at least one contributor per page having its contact information in this CONTRIBUTORS file.
• All relevant metadata fields in a specific page are correctly filled in (see the page metadata and the Editorial board guide). Some critical ones are listed below.
  • unique page_id (List of page IDs)
  • contributors
  • editors
  • related_pages (Related pages)
  • training
  • search_exclude must be deleted
  • description
  • affiliations (only used for Tool assembly pages)
  • coordinators(only used in national pages + they must be listed as contributors as well)
  • resources
• Make sure that listed tools or resources are tagged in the text with the correct snippet + that its metadata is described in the tool_and_resource_list.yml file.
• Check if relevant recipes on FAIR Cookbook can be linked to the RDMkit page that is being added/changed (Linking from RDMkit to FAIR Cookbook).
• The content conforms to RDMkit's scope, style and templates.
• There are no copyright issues related to the content of the page.
• The contributors implemented the requested changes.
• When a new page is added, a news item is added to the news.yml file, in the same branch of the PR.
• The contributors are acknowledged for their efforts and informed about the publication of their content.
• The PR is linked to related issues and can be merged into the main branch with no conflicts.

Please refer to the complete editor's checklist for details.

[github-actions]

Before approving and merging a pull request (PR), the editors must check that

• The page layout in the preview looks correct.
• The new page is linked in the appropriate sidebar menu, in the same branch of the PR.
• The contributors' names are listed in the CONTRIBUTORS file, in the same branch of the PR. Advice to have at least one contributor per page having its contact information in this CONTRIBUTORS file.
• All relevant metadata fields in a specific page are correctly filled in (see the page metadata and the Editorial board guide). Some critical ones are listed below.
  • unique page_id (List of page IDs)
  • contributors
  • editors
  • related_pages (Related pages)
  • training
  • search_exclude must be deleted
  • description
  • affiliations (only used for Tool assembly pages)
  • coordinators(only used in national pages + they must be listed as contributors as well)
  • resources
• Make sure that listed tools or resources are tagged in the text with the correct snippet + that its metadata is described in the tool_and_resource_list.yml file.
• Check if relevant recipes on FAIR Cookbook can be linked to the RDMkit page that is being added/changed (Linking from RDMkit to FAIR Cookbook).
• The content conforms to RDMkit's scope, style and templates.
• There are no copyright issues related to the content of the page.
• The contributors implemented the requested changes.
• When a new page is added, a news item is added to the news.yml file, in the same branch of the PR.
• The contributors are acknowledged for their efforts and informed about the publication of their content.
• The PR is linked to related issues and can be merged into the main branch with no conflicts.

Please refer to the complete editor's checklist for details.

[bedroesb]

@korbinib Could you have a look at the GitHub Action creating the Checklists in PRs, they seem to also be added when I do a new commit. I can make an issue.

[bianchini88]

@bedroesb @korbinib this one will possibly help #1857 (see e.g. here for reference)