You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.
Activity
colleenXu commentedon Sep 10, 2026
Partially addressed by #574
EvanDietzMorris commentedon Sep 10, 2026
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.
tokebe commentedon Sep 10, 2026
The schemas are used directly to generate the MetaKG, but the schemas themselves are only provided on an endpoint for dev/debugging purposes.