-
Notifications
You must be signed in to change notification settings - Fork 80
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
Add INSTRUMENT_MODEL as a constraint for EBI submission #1483
Comments
I think the best solution is to add the proper values based on the pre-processing pipeline. We currently support 2 values: Illumina and 454. From list here: ftp://ftp.sra.ebi.ac.uk/meta/xsd/sra_1_5/SRA.common.xsd. What do you think? |
That is confusing, I thought that such information was in the PLATFORM column. |
You need both values. See how we add platform and then hardcode the INSTRUMENT_MODEL. However, we should be adding, if LS454 = type454Model. I guess the idea of hardcoding it is that if we add platform you can "guess" the instrument model. |
Makes sense - we should probably grab EBI nomenclature and just create a dictionary that given the PLATFORM we set up the instrument_model if it is not provided in the prep template (if a user provides it - we just provide such information). |
That's the dream ... |
I will send list
|
@ackermag Thanks but I think this is it: ( * ) We support -- Note that 'UNKNOWN' is supported by Qiita but not is not in EBI's list, what about deleting it? |
That is the list of PLATFORMS not instrument models which is as follows: Controlled vocabulary for LS454 INSTRUMENT_MODEL: 454 GS 454 GS 20454 GS FLX 454 GS FLX+ 454 GS FLX Titanium 454 GS Junior unspecified |
I am also concerned about this platform: On Thu, Oct 1, 2015 at 10:20 AM, Gail Ackermann gail.ackermann50@gmail.com
|
@ackermag, thanks! This means that we either add this to the required field to the templates or we continue sending unspecified ... and yes that will require some code changes. |
Closed by #1484 |
@antgonza from your recent email it looks like this column is required, so we should update the documentation and the constants for EBI so the system checks for this column.
The text was updated successfully, but these errors were encountered: