Open tursynay opened 3 years ago
Per the KGE Session during winter relay, opening a ticket for an action item that was captured at the meeting. Chunlei offered to look over the KGE Smart API Registry entry yaml file.
@deepakunni3 and @RichardBruskiewich, is this the one?
Hi @tursynay, superficially... yes, that will be the file of interest, but having said that, the current file is the initial iteration which will require another iteration (and likely, revision). That said, I may revisit this component of the KGE Archive in a relatively short while.
We've implemented both a Translator Registry entry publication mechanism (with a templated SmartAPI entry parameterized with KGE metadata, capture by the web form) and the "content metadata" is somewhat TRAPI 1.0 compliant and generated.
What we need to do here now are:
As of July 27th, 2021, we are not yet posting Translator Smart API Registry entries. This should be changed soon.
As of Sept 2021, not yet posting to Translator Smart API Registry but code exists. We may need to review how OBO Registry standards may be reflected in our metadata (request from Chris Mungall ...). Keep this issue open for now.
As of Sept 2021, we need to update the Translator Registry template to align with the latest applicable KGE archive API endpoints.
We should also figure out how to start publishing entries to the Translator Registry.
As of January 2022, the old Translator SmartAPI Registry GitHub repo at NCATS-Tangerine seems somewhat deprecated. We need to contact the SmartAPI team (Chunlei?) to sort out the "best practices" programmatic method for publishing new KGX dataset entries to the Translator SmartAPI Registry.
Per the KGE Session during winter relay, opening a ticket for an action item that was captured at the meeting. Chunlei offered to look over the KGE Smart API Registry entry yaml file.
@deepakunni3 and @RichardBruskiewich, is this the one?