Skip to content

Replace Meta_kg with new schema #573

Open

Description

@cbizon

Tagging @EvanDietzMorris to fix my errors :)

meta_kg is part of the trapi spec and so the ingest pipeline is creating that artifact.

However, in the ingest refactoring, a different schema file has been created, and is what retriever is serving and being used by shepherd. It sounds as though we've had a sort of a defacto change from metakg to schema.

Should TRAPI be brought into line with these updates?

Activity

  1. colleenXu commented on Sep 10, 2026

    @colleenXu
    Contributor

    Partially addressed by #574

  2. EvanDietzMorris commented on Sep 10, 2026

    @EvanDietzMorris

    After discussing some with @tokebe, meta_kg is not as obsolete as I thought - Retriever still generates TRAPI meta kgs from the new schema format. It's not clear to me how/if they are used though.

  3. tokebe commented on Sep 10, 2026

    @tokebe
    Contributor

    The schemas are used directly to generate the MetaKG, but the schemas themselves are only provided on an endpoint for dev/debugging purposes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions