-
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
Add TST as valid value for “Single Nucleus Buffer" #307
Comments
@elv-sb can tackle this during this sprint! Thanks! |
Hi @aclayton555 @elv-sb @adamjtaylor ! Our collaborator is asking for an estimated timeline for when this will be available in DCA. Will this update be included in the next data model release (end of the month, I presume)? |
@clarisse-lau asked that we escalate during our CRDC call so I have implemented and will push through |
Thanks @adamjtaylor ! |
@clarisse-lau this should now be live in production. 🚀 |
Have notified the user. Thank you! |
Information
Proposed change:
Add
TST
as option for required attributeSingle Nucleus Buffer
Current valid values are : NIB, 10x, Omni
Dicussion link:
Email from Allison Frangieh (DFCI) Oct 3, 2023:
We are working on submitting the ScATAC-seqLevel1 spreadsheet on the DCA for our snRNAseq TNP data. We’re having trouble with one column:
“Single Nucleus Buffer”- this is a required field and “unknown” or “not applicable” (in any variation) is not accepted. The valid values are 10x, NIB, or Omni, but none are applicable to the protocol we used (i.e. TST buffer from Slyper et al. paper). I think we are unable to submit until this error is resolved.
How important is this feature?
When will use cases depending on this become relevant?
Implementation checklist
HTAN.model.csv
editied and pushedHTAN.model.jsonld
validated and created by Github actionmain
ncihtan/HTAN-data-curator
(if required)The text was updated successfully, but these errors were encountered: