Mapping Tools

The goal of this folder is to highlight mapping tools, i.e., concrete implementations of reusable tools that can be used to predict, review, curate, or reason over semantic mappings.

The goal of this folder isn’t to highlight mapping formats like SSSOM, JSKOS, etc. nor software that simply implements object models and I/O for the formats.

Name Description
SSSOM Curator Lexical prediction of semantic mappings and curation interface
Semantic Mapping Reasoner and Assembler (SeMRA) Reasoning-based prediction of semantic mappings

Contributing

You should make a new markdown file in this folder named by the tool. Make the name lowercase with dashes instead of spaces.

Please include the following:

  1. The full name and acronym (if appropriate) for the software
  2. A high-level description of what the tool does and why
  3. A link to its source code, freely available container, or freely available executable
  4. Links to documentation and training materials
    • When documentation does not exist, the Section Metadata WG Onto should try and prepare them
    • Documentation that shows concrete examples, especially cross-disciplinary ones, like https://cthoyt.com/2025/10/07/bridging-culture-and-chemistry.html, are helpful
    • Presenting a live demo for the Section Metadata WG Onto that gets recorded and uploaded to YouTube is also desirable
  5. Links to publications about or using the tool

Importantly, the markdown file for each tool should explicit say how the tool supports linking, harmonizing, and mapping terminologies used throughout the NFDI, and how this promotes interoperability (in the context of harmonizing our used terminologies) within NFDI.

Recommendations if You’re Developing a Mapping Tool

GitHub Epic: https://github.com/nfdi-de/section-metadata-wg-onto/issues/64

  1. Try and avoid being project specific or domain specific, i.e., don’t add NFDI in the name or “bio”- in the name, to avoid alienating people from other communities or domains