Like the Swagger interface, but better for actual work. Some useful features:
- An advanced mode that lets you compare results across different NodeNorm instances
- A bulk mode (avoids needing to use the CLI without much extra resources) -- you enter a list of identifiers, and get back a downloadable table (CSV, TSV, JSON) with the cliques (suggested by @sandrine-muller-research)
- Might be useful to support input filtering -- e.g. rather than entering "NCBIGene:1234", the UI would let you choose NCBI Gene as you could enter just a bunch of NCBI Gene identifiers?
- Might be useful to support output filtering -- i.e. we would return the normalized identifier, its label, but optionally also a particular identifier -- e.g. if you're trying to convert NCBIGene to ENSEMBL, we could return just the ENSEMBL IDs in a separate column (note that this would need to support multiple values, because some prefixes appear multiple times in the same clique)
- Might be useful to (optionally) also query Node Annotator and provide the annotations for the query
- A longstanding wish of mine is to provide a single interface for both NameRes and NodeNorm (i.e. we always do a NameRes query, but we also do a quick NodeNorm query to see if someone has entered an identifier instead) -- maybe this is how we build it?
Other tools with similar search/lookup interfaces:
This is currently in development at TranslatorSRI/babel-explorer#4 but we might want a simpler/prettier interface for general users, while hiding the query options for developers.
Like the Swagger interface, but better for actual work. Some useful features:
Other tools with similar search/lookup interfaces:
This is currently in development at TranslatorSRI/babel-explorer#4 but we might want a simpler/prettier interface for general users, while hiding the query options for developers.