How to add a knowledge graph

Choose one of the following ways to contribute a new Knowledge Graph to the catalog, which is hosted and maintained in the GitHub repository m1ci/lod-next-gen.

If you are unsure which option to choose, use the GitHub Issue form (Option 1). It guides you through the required metadata and provides feedback directly on your submission.

Recommended

Option 1: KG Metadata via GitHub Issue Form

Use the guided form if you want a simpler way to submit a new knowledge graph to the KG catalog.

KG Submission Form

Option 2: KG Metadata via YAML

Use this option if you are comfortable editing YAML and working with Git. It gives your more flexibility in providing the metadata.

View YAML steps

Option 1: KG Metadata via GitHub Issue Form

Open the New KG Submission form.
Fill in the requested Knowledge Graph details and submit the issue.
An automated workflow validates the submission and reports any problems as a comment on the issue.
Correct any reported problems in the issue and save it so validation can run again.
When validation succeeds, the KG metadata is automatically prepared and a pull request is created for review.
The catalog administrator reviews and approves the KG.

You do not need to create a pull request yourself. If action is required after submission, the catalog administrator will provide instructions in the issue comments or by email.

Option 2: KG Metadata via YAML

Follow these steps if you are contributing directly to m1ci/lod-next-gen.

1. Clone the repository

Start by cloning the catalog repository locally from m1ci/lod-next-gen.

git clone git@github.com:m1ci/lod-next-gen.git

2. Create a KG folder

Inside the knowledge-graphs directory, create a folder for your KG. Use the KG name as the folder name.

cd knowledge-graphs
mkdir my-kg
cd my-kg

3. Add metadata

Create a metadata.yaml file in that folder and fill in the required fields.

touch metadata.yaml

The template below shows the expected structure. Update every field marked with UPDATE and leave the fixed fields as they are.

databus-account: knowledge-graph-catalog # Leave as is. Don't update.
id: my-kg # UPDATE: set unique id of your KG. Check for already used ids at https://databus.dbpedia.org/knowledge-graph-catalog
title: My First KG # UPDATE: set the title of the KG
abstract: This is the coolest KG. # UPDATE: Provide short description of the KG (e.g. 2 sentences)
description: 'This is the coolest KG.' # UPDATE: Provide extended description of the KG. You can either use free text or markdown syntax.
moss-publish: true # UPDATE: set to true when publishing the KG for the first or when introduced updates to the general metadata of the KG.
databus-publish: true # UPDATE: set to true when publishing the KG for the first time  or when introduced updates to the KG artifacts or versions.
license: http://purl.oclc.org/NET/rdflicense/cc-by3.0 # UPDATE: Provide the general license for the KG
homepage: https://example.org/ # UPDATE: home page for the KG, if exist.
domains:
- Cross-domain # UPDATE: the main domain reflecting the content of the KG. Choose from the 8 defined domains below.

# Cross-domain
# Geography & Environment
# Government & Public Sector
# Life Sciences & Health
# Economy, Industry & Infrastructure
# Publications, Education & Research
# Media, Culture & Entertainment
# Linguistics, Social & Digital Knowledge Systems
# ...for more about domains see https://github.com/m1ci/lod-next-gen/blob/main/README.md

keywords: # UPDATE: provide 3-8 keywords describing your KG
- cross-domain
- geography
- intro
sparql: # Provide SPARQL endpoint details, if endpoint is available
- name: main
  url: http://example.org/sparql
maintainers: # UPDATE: add contact info of the KG maintainer
- name: Chuck Norris
  contact: Chuck.Norris@gmail.com
  github: chuck # username on github
artifacts: # UPDATE: provide list of artifacts associated with your KG. 
# Typically an artifact corresponds to a partition of your KG (if your KG is provided in multiple partitions)
- artifact: first-artifact # UPDATE: provide id for your artifact 
  title: First Artifact # UPDATE: provide title for the artifact
  abstract: My first artifact. # UPDATE: provide short description of the artifact (e.g. 2 sentences)
  description: My first artifact. #UPDATE: provide extended description of the artifact
  versions:
  - version: 2026.07.10
    title: First Artifact # UPDATE: provide title for the version
    abstract: My first artifact # UPDATE: provide short description of the version (e.g. 2 sentences)
    description: My first artifact # UPDATE: provide extended description of the version
    license: http://purl.oclc.org/NET/rdflicense/cc-by3.0 # UPDATE: URL identifying the license
    distributions: # here list all files assciated with the artifact and the version
    - file: https://downloads.dbpedia.org/repo/dbpedia/mappings/instance-types/2020.06.01/instance-types_lang%3Dar_specific.ttl.bz2 # UPDATE: provide valid download URL
      format: ttl # UPDATE: provide the format of the file, e.g. nt or ttl
      compression: bz2 # UPDATE: if the file is compressed, e.g. bz2, indicate that info
      status: pending # INFO: pending means that the catalog will be updated (then it will be set to active). Later, if you make any changes and want to propagate them to the catalog, set the flag to pending.

4. Commit and push

After editing metadata.yaml, commit and push the changes.

git add -A
git commit -m "adding new KG"
git push

5. Open a pull request and wait for publication

Open a pull request with your changes and wait for validation and review. If everything goes well, your KG should appear soon in the DBpedia KG Catalog and on the Databus.

What happens next?

After the metadata is approved, the Knowledge Graph is added to the catalog and becomes available through the DBpedia KG Catalog and Databus. Publication may take some time after approval.