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.

Sign up for GitHub

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

Jump to bottom

Evaluate and respond to proposed metadata schema changes #2821

Closed
theathorn opened this issue Feb 22, 2021 · 3 comments
Closed

Evaluate and respond to proposed metadata schema changes #2821

theathorn opened this issue Feb 22, 2021 · 3 comments
Assignees
@hannes-ucsc
Labels
doc [subject] Internal and external documentation no demo [process] Not to be demonstrated at the end of the sprint no pr [process] Resolution (usually hotfix) commited directly to branch orange [process] Done by the Azul team task [type] Resolution requires engineering action other than code changes

Comments

@theathorn
Copy link

theathorn commented Feb 22, 2021 •
edited
Loading

Evolving the schema

..with particular emphasis on the section "Key changes to the schema that we want to prioritise" / "Minor changes intended for first iteration".

..and [Evolving HCA Metadata Schema for Contributor-Generated

@github-actions github-actions bot added the orange [process] Done by the Azul team label Feb 22, 2021
@melainalegaspi
Copy link

@hannes-ucsc :"Focus on schema changes, not update mechanism."

@melainalegaspi melainalegaspi added doc [subject] Internal and external documentation task [type] Resolution requires engineering action other than code changes labels Feb 24, 2021
@melainalegaspi
Copy link

@hannes-ucsc to link to the merged PRs and close this ticket.

@hannes-ucsc
Copy link
Member

Spec: HumanCellAtlas/dcp2#9
Schema: HumanCellAtlas/metadata-schema#1371
Test data: HumanCellAtlas/schema-test-data#8

@hannes-ucsc hannes-ucsc added no demo [process] Not to be demonstrated at the end of the sprint no pr [process] Resolution (usually hotfix) commited directly to branch labels May 21, 2021
@hannes-ucsc hannes-ucsc mentioned this issue May 21, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hannes-ucsc hannes-ucsc

Labels
doc [subject] Internal and external documentation no demo [process] Not to be demonstrated at the end of the sprint no pr [process] Resolution (usually hotfix) commited directly to branch orange [process] Done by the Azul team task [type] Resolution requires engineering action other than code changes
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hannes-ucsc @theathorn @melainalegaspi