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

Unifying Subject-Sample mapping files for HDD data #56

Open
nboukharov opened this issue Jan 9, 2017 · 0 comments
Open

Unifying Subject-Sample mapping files for HDD data #56

nboukharov opened this issue Jan 9, 2017 · 0 comments
Assignees

Comments

@nboukharov
Copy link

Subject-Sample mapping files for Expression, Metabolomics, MIRNA_QPCR, MIRNA_SEQ, Protein, RBM and RNASeq Data have slight differences that create unnecessary issues for curators. We would like to have one format for all HDD data maping files, the same as is used for Expression data: STUDY_ID, SITE_ID, SUBJECT_ID, SAMPLE_ID, PLATFORM, TISSUETYPE, ATTR1, ATTR2, CATEGORY_CD, SOURCE_CD
The only mandatory fields should be STUDY_ID, SUBJECT_ID, SAMPLE_ID PLATFORM and CATEGORY_CD. Other columns should be allowed to be null. If a specific loading procedure requires one of the optional columns to have a value, a default value should be inserted (e.g. "Unknown" for TISSUETYPE, "STD" for CATEGORY_CD). Unified mapping file loading procedure should be back compatible and flexible. Both ATTR1 and ATTRIBUTE_1, STUDY_ID and TRIAL_NAME should be acceptable for respective columns. All "tokens" (SITE_ID, PLATFORM, TISSUETYPE, ATTR1, ATTR2) should be allowed to be used in the CATEGORY_CD in any order (don't have to have values in ATTR1 to use ATTR2)

@mirasrael mirasrael assigned mirasrael and baroleg and unassigned mirasrael Jan 10, 2017
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

3 participants