-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any combination of sssom metadata elements should be usable as URI parameters #27
Comments
(PS: all pages (search results, mappings, etc) in oxo should have a URI pointing to it) |
Only question is how do we get to this page? Is it like a special case wherein if a user types something on the browser with the correct URL and parameters, it redirects to this? |
Can you meet with @udp and have him explain it? It's critical we get this right! |
@matentzn Is this the same as the "entity" page? https://github.com/EBISPOT/oxo2/issues/36 In the old OxO, this is the way they call the API, in the new OxO with SSSOM, this will need to change the SSSOM API (again and again!) |
All these choices to have a sharable URL depend entirely on the SSSOM API. |
This here is more about the mappings, i.e. the search results for a given search + facets subsetting. The #36 is more about a page about a single entity, like "HPO:123". But the main message is: all pages, regardless of where they are should depend on SSSOM API and have all query parameter part of the sharable URL. |
Ok, need to rebuild the entire SSSOM API for this. |
Lol, please dont.. There must be some misunderstanding somewhere, most likely in my requests! |
Yes, your request is not that simple. |
In the old OXO you could do
https://www.ebi.ac.uk/spot/oxo/mappings?fromId=DOID:162&toId=SNOMEDCT:269513004
We need to be able to do the same, with any sssom element valid, ie
https://www.ebi.ac.uk/spot/oxos/mappings?subject_id=DOID:162&object_id=SNOMEDCT:269513004
https://www.ebi.ac.uk/spot/oxos/mappings?subject_id=DOID:162&object_id=SNOMEDCT:269513004&mapping_source=obo:mondo
The text was updated successfully, but these errors were encountered: