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

[Spike]: Make major design decisions for spreadsheet regeneration #530

Open
justincc opened this issue Sep 3, 2019 · 0 comments
Open

[Spike]: Make major design decisions for spreadsheet regeneration #530

justincc opened this issue Sep 3, 2019 · 0 comments
Labels
t-shirt large A task that can't have a numeric estimate but is assessed as big

Comments

@justincc
Copy link
Contributor

justincc commented Sep 3, 2019

See Ingest Additions and Analysis AUDR HLD 2019Q3.

These are major decisions such as:

a) Do we use data from the datastore or ingest to populate these regenerated spreadsheets?
b) Is it okay to generate a spreadsheet which contains all the data for a project or will this be too much? Does this need the user to be able to select what to populate?

Arathi has been working on spreadsheet regeneration so they can test new schema changes immediately on end to end test. Need to coordinate with them.

@justincc justincc added the t-shirt large A task that can't have a numeric estimate but is assessed as big label Sep 3, 2019
@rdgoite rdgoite assigned rdgoite and unassigned rdgoite Sep 26, 2019
@aaclan-ebi aaclan-ebi self-assigned this Oct 10, 2019
@justincc justincc added this to the Q4 2019 Milestone 2 milestone Oct 10, 2019
@aaclan-ebi aaclan-ebi removed their assignment Nov 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t-shirt large A task that can't have a numeric estimate but is assessed as big
Projects
None yet
Development

No branches or pull requests

3 participants