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
"GAF" download button on search annotation pages no longer works #293
Comments
For "1" there, it reports as
in bbop.widget.display.button_templates.field_download . |
This may all be mooted by #104 if things work on that side of the fence. |
Nope, not mooted, but a slightly more heartening error:
|
…now; TODO: correct selection of items; #293
The selection error only occurs with the annotation downloads. I'm guessing this is due to annotation IDs being stored like:
but called like:
Is it storing as tabs, or as literal |
Both of these work in the ontology_class download, so unlikely to be something with the parens or quotes:
|
Well, using luke, the solr index itself has it as tabs, with:
So maybe there is a way to figure out how to get these IDs to match (http request into Solr and document id in Solr), but this is such a nasty way to generate IDs I feel like we should just give up here and generate less nasty IDs for annotation documents from the get-go. @hdietze, do you have any opinion here? While having the IDs "mean" something has been nice, I think I'm good without this in particular (encoding tabs? ugh). Either hashing, UUID, or incremental. Given that we do this in the nasty loader and we already have no self-respect there, another nice unique ID could be:
Simple unique ID, that could still give some interesting info if things went south. |
* deal with problematic tabs, by converting the GAF line to hex @kltm * related to issue geneontology/amigo#293
Have finally gotten around to testing. After a refresh of the index (with more sensible IDs), it is working again as expected. |
There seems to be two issues with the GAF download button on /seach/annotations.
As reported by @elserj.
The text was updated successfully, but these errors were encountered: