Closed cansavvy closed 4 years ago
This is a part of the protocol but it was temporarily not working. According to @wvauclain it was temporarily not working:
the reason why it didn't show up is probably because I am running the management command right now to populate that field
This'll be fixed as soon as the management command finishes running that is populating this field on the backend.
Summary
It appears a dataset might have an alternate accession id on its dataset page but it isn't searchable:
But that this wouldn't show up on the search:
A user might search for this dataset using a GEO id and then think we don't have it even though we do and you can find it using the SRA ID. In this example:
SRP149884
comes up butGSE115397
says "no results".This is the example dataset I'm referring to: https://www.refine.bio/experiments/SRP149884/non-inflammatory-tumor-microenvironment-of-diffuse-intrinsic-pontine-glioma-dipg
I have no idea if this has been discussed previously or how difficult it is to implement but I think it would help users out a lot (and prevent people from leaving the site because they think we don't have a dataset we actually do have)>