NCATSTranslator / TranslatorPM

Activities related to the overall project management for Translator
0 stars 8 forks source link

ARAX - Verify Server Info for Expander Agent #52

Open sstemann opened 3 years ago

sstemann commented 3 years ago

Can you please verify what we have for your teams= ARAX on: https://github.com/NCATSTranslator/TranslatorPM/blob/main/Translator%20Server%20Info.md

Assigning to @edeutsch based on SmartAPI registered by info, please redirect as needed.

edeutsch commented 3 years ago

Thanks, @sstemann this looks pretty good to me. Maybe one trivial quibble is our tool is called "ARAX" instead of "ARAX Agent".

Otherwise seems right.

thanks! Eric

sstemann commented 3 years ago

thanks @edeutsch i made the update! some Agent teams have agents and providers, consistency is hard.

sstemann commented 3 years ago

@edeutsch Early in the development, one of NCATS priority for ARA teams was: No ETL - Currently, several ARAs propose/require a local, internal knowledge graph. The responsibility for the upkeep and evolution of that knowledge graph should be transferred to a Tr-KP (possibly an entirely new KP). (it was in this deck - Has KG2 been shared as a KP or KGE? Can it be registered with SmartAPI? Please redirect as needed.

sstemann commented 3 years ago

@edeutsch just checking if ARAX KG2 is available as a KP? KGX?

edeutsch commented 3 years ago

Hi Sarah, apologies from dropping the response on this. Our TRAPI 1.0 interface to KG2.5.1 is nearly complete, and will be rolled out very soon, next week I hope, and will then be registered in SmartAPI. We have put an export of KG2.x available as dumps in S3 at: https://rtx-kg2-public.s3-us-west-2.amazonaws.com/kg2-tsvs.tar.gz and https://rtx-kg2-public.s3-us-west-2.amazonaws.com/kg2-simplified.json.gz for Unsecret Agent and anyone else interested. Our current JSON format has a minor bug in which the edges are not currently equipped with unique ids, but the graph is otherwise biolink compliant; we will provide a JSON export with edge IDs (on a regular basis) as a part of depositing KG2 in the Translator KGE Archive (an initiative being led by the SRI and in which our team is participating). Once it is up and running, we will be ready to supply KG2 in the expected format.

sstemann commented 3 years ago

Thanks for all of the details!

edeutsch commented 3 years ago

Our RTX KG2 TRAPI interface is now registered in SmartAPI: https://smart-api.info/registry?q=RTX