Skip to content

🌐 Add Your Data to the MSE Knowledge Graph (MSE KG)

The MSE Knowledge Graph (MSE KG) improves data visibility and serves as an indexing and discovery layer for materials science and engineering resources. It helps people find, connect, and reuse data more easily.

Adding more data benefits us all. Depending on your data type and how your data is currently stored, choose the scenario below that best matches your case.


πŸš€ Choose Your Contribution Scenario

Your situation Recommended scenario
I have a spreadsheet or other tabular data Scenario 1 or Scenario 4
I already have RDF Scenario 2
I run my own SPARQL endpoint Scenario 3
I want to add FDOs Scenario 5

Click a scenario to jump directly to the instructions.


πŸ“š Supported Data Types

The MSE KG currently supports the following resource types:

πŸ™οΈ City
πŸ”¬ Materials
πŸ›οΈ Organization
πŸ‘€ People
πŸ—ƒοΈ Datasets
πŸ’» Software
🌐 Data Portals
πŸ”­ Instruments
πŸ—οΈ Large-scale Facilities
🏷️ Metadata
πŸ“ Ontologies
πŸŽ“ Educational Resources
πŸ“œ Patents
πŸ“¦ FDOs
βš™οΈ Workflows
πŸ”§ Services
🌍 International Collaborations
πŸ“… Events
πŸ“„ Publications
πŸ› οΈ Tools (NFDI resources)
πŸ”© OMS Tools
πŸ§ͺ MatWerk-TA
πŸ”— MatWerk-IUC
πŸ“‹ MatWerk-PP
πŸ“ DFG Preface
ℹ️ DFG General Information

🧭 Contribution Scenarios

Scenario 1: Unstructured Data (e.g., spreadsheet not represented with ontology)

You have unstructured data such as a spreadsheet, but you do not want β€” or do not currently have the time β€” to model it using an ontology.

This is still a valid way to contribute to the MSE KG ecosystem.

⚠️ Please note: We cannot structure the data for you.

What to do

  1. Upload your spreadsheet to Zenodo:
    NFDI MatWerk Community on Zenodo
  2. Provide ROR IDs for organizations and ORCID IDs for people, where applicable.
  3. Your data can then be automatically harvested and added to the MSE KG.

⬆ Back to scenario selection


Scenario 2: RDF Data Already Represented with Ontology

You already have RDF data and it is properly represented using an ontology. This allows direct integration into the MSE KG.

What to do

  1. Upload your repository to Zenodo:
    NFDI MatWerk Community on Zenodo
  2. Ensure that the RDF files are included in the repository.
  3. Your RDF will be integrated into the MSE KG in a separate named graph.

⬆ Back to scenario selection


Scenario 3: RDF Data in a Triple Store (Graph Database)

You already maintain your own triple store and provide a SPARQL endpoint. In this case, we can connect your graph to the MSE KG so users can query it more seamlessly.

What to do

  1. Add your SPARQL endpoint to the integration sheet:
    SPARQL Endpoint Integration Sheet
  2. Your endpoint can then be automatically integrated into the MSE KG.
  3. Optionally, open a GitHub issue to discuss:
  4. mappings
  5. schema alignment
  6. federated SPARQL queries

Submit GitHub Issue

⬆ Back to scenario selection


Scenario 4: Data Type Already Supported in MSE KG (e.g., Person, Software)

You want to contribute data about entities that are already supported in the MSE KG, such as people, software, or organizations.

What to do

  1. Use the data collection spreadsheet template based on the MatWerk ontology:
    Data Collection Spreadsheet
  2. Fill in your data according to the provided format.
  3. To check whether your data is already available in the knowledge graph, use this spreadsheet:
    Availability Check Spreadsheet

ℹ️ This spreadsheet is connected to a Apache-Airflow workflow and is therefore read-only, which prevents accidental edits from interfering with synchronization.

⬆ Back to scenario selection


Scenario 5: FAIR Digital Objects (FDOs)

You want to add your FAIR Digital Objects (FDOs) to the MSE KG.
We provide a simple, semi-automated process so your registered FDOs can be harvested and integrated directly into the graph.

What to do

  1. Add your FDO metadata to the integration spreadsheet:
    FAIR Digital Object Integration Sheet
  2. For each entry, include:
  3. FDO identifier
  4. type
  5. related dataset or publication
  6. persistent URL
  7. Your FDOs will then be automatically harvested and integrated into the MSE KG via the FAIR Digital Object Harvester pipeline.
  8. Optionally, open a GitHub issue if you would like to discuss:
  9. custom FDO mappings
  10. schema alignment
  11. FDO–dataset linking strategies

Submit GitHub Issue

⬆ Back to scenario selection


❓ Not Sure Where Your Data Fits?

No problem β€” we can help.