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

Build artifact #5

Closed
4 tasks
maniarathi opened this issue Jan 23, 2020 · 4 comments
Closed
4 tasks

Build artifact #5

maniarathi opened this issue Jan 23, 2020 · 4 comments
Assignees
@parthshahva

Comments

@maniarathi
Copy link
Contributor

maniarathi commented Jan 23, 2020 •
edited by parthshahva
Loading

  • Move ledger files to artifact bucket
  • Automated build of artifact matching jsonschema
    • artifact builder script packaged in docker
    • aws infra to run artifact builder docker image
@maniarathi maniarathi changed the title [Spike] Figure out what the structure of the flattened MD looks like in the artifact [Spike] Determine flattened metadata required for data browser Jan 23, 2020
@brianraymor brianraymor changed the title [Spike] Determine flattened metadata required for data browser Determine flattened metadata required for data browser Jan 30, 2020
@brianraymor
Copy link

Per the discussion at the DCP/2 Leads meeting on Jan 30, we will be more precise in how we refer to flattened metadata:

  • Software readable metadata for files such as project.tsv or files.tsv consumed in the browser
  • Metadata downloadable blob for the full metadata download file

@brianraymor brianraymor changed the title Determine flattened metadata required for data browser Determine software readable metadata Jan 30, 2020
@brianraymor brianraymor changed the title Determine software readable metadata Document software readable metadata Jan 30, 2020
@brianraymor brianraymor changed the title Document software readable metadata Build software readable metadata Jan 30, 2020
@maniarathi
Copy link
Contributor Author

@ambrosejcarr Is this still relevant? The latter part of the ticket (metadata for the browser) is handled by extraction from the artifact. How about the metadata downloadable blob?

@parthshahva parthshahva self-assigned this Feb 20, 2020
@parthshahva parthshahva changed the title Build software readable metadata Build software readable metadata in artifact Feb 20, 2020
@parthshahva
Copy link
Contributor

@maniarathi this ticket has nothing to do with the browser. This is part of the automation of artifact building. I've updated the ticket and assigned myself

@parthshahva parthshahva changed the title Build software readable metadata in artifact Build artifact Feb 20, 2020
@maniarathi
Copy link
Contributor Author

Closing this ticket as part of a cleanup of this repo's open issues given that a new roadmap will soon be deployed.

pablo-gar added a commit that referenced this issue Sep 1, 2022
@pablo-gar
# This is a combination of 11 commits.
6b4c97f 
# This is the 1st commit message:

Add high level tissue dimension to integrated corpus

# This is the commit message #2:

fix bug

# This is the commit message #3:

Change tissue layout

# This is the commit message #4:

Add to summary cubes

# This is the commit message #5:

fix bug

# This is the commit message #6:

Modify placeholder function

# This is the commit message #7:

Fix bug

# This is the commit message #8:

Fix bug

# This is the commit message #9:

Add extra dimension to validation

# This is the commit message #10:

Update query, update unitest

# This is the commit message #11:

Refractor query builder
@tihuan tihuan mentioned this issue Jan 2, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@parthshahva parthshahva

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@brianraymor @maniarathi @parthshahva