-
Notifications
You must be signed in to change notification settings - Fork 7
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
Keeney - Update ARGOS DB url to semantic url #405
Comments
Semantic search URL appears to work ( |
Raja, this is currently where the task is standing. 'https://data.argosdb.org/?query=GCF_002386325.1' does work and when you pass in any "GCF_####" at the end, it will populate the correct search page. But, when you get to the search page after inputting the semantic URL, it returns the URL back to 'https://data.argosdb.org/results/76b04819c7ff104c002e77f7f28a82d1'. Did you want the search page URL to also be semantic? |
Robel - Raja is asking that the search URL also be semantic. Thank you. |
@rykahsay - Raja is asking that the search URL also be semantic. Thank you. |
@rykahsay I just double check and the URL is still not semantic. |
@kee007ney so this was one of them. I believe it sort of became semantic? I think he made it so if you are on the page you searched for, the URL is semantic but any other URL is not. We can check. I just think Raja thought it was too messy of a URL and not useful |
Ask Raja do we want it to be more semantic or just searchable in the URL? @rajamazumder |
The search page on ARGOS DB for a specific organism needs to be updating with a semantic URL, preferably the GCF#### at the end. I think we discussed that it needs to have a sub page created. The query and information we want is below.
The example organism we are working with is: https://www.ncbi.nlm.nih.gov/datasets/genome/GCF_002386325.1/
Document of what we need updated from Raja: https://docs.google.com/document/d/1hVe29qZzxSIOwEw7Eg1tsI9jdbi47s9xNsV_j_-5JzE/edit
Example search page for this organism: https://data.argosdb.org/results/ac57b7476620ede1068c3c91bbba7aac
The text was updated successfully, but these errors were encountered: