Skip to content
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

More consistent platform values to match GEO if possible #176

Closed
Tracked by #179
anngvu opened this issue Jul 12, 2022 · 1 comment
Closed
Tracked by #179

More consistent platform values to match GEO if possible #176

anngvu opened this issue Jul 12, 2022 · 1 comment
Assignees

Comments

@anngvu
Copy link
Collaborator

anngvu commented Jul 12, 2022

Also fulfills this issue dug up from the internal annals -- NFINT-86:

For all values under the attribute/key , align spacing and ensure all values start with the instrumentation company name – e.g., Illumina Next Seq 550 (not Next Seq 550). Do this for both all files, and in the NF schema.

Mainly came up again as something that might help eliminate an additional mapping step for GEO vals.

@anngvu anngvu changed the title More consistent platform values More consistent platform values to match GEO if possible Jul 13, 2022
anngvu added a commit that referenced this issue Jul 15, 2022
* Revise 'extended' templates per issue #175

* Add CUT&RUN per issue #177

* Update platforms as much as possible per issue #176

* Build jsonld

* Add M3 MPNST cell line

* Build jsonld

Co-authored-by: nf-osi[bot] <nf-osi@sagebionetworks.org>
@allaway
Copy link
Contributor

allaway commented Jul 22, 2022

resolved in #179

@allaway allaway closed this as completed Jul 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants