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

Heading that names 'multiple tables' in data management episodes leads to confusion #44

Closed
aromanowski opened this issue Jul 20, 2021 · 2 comments
Closed

Heading that names 'multiple tables' in data management episodes leads to confusion #44

aromanowski opened this issue Jul 20, 2021 · 2 comments
Labels
help wanted Looking for Contributors

Comments

@aromanowski
Copy link
Contributor

During the hackathon, together with @egountouna and @ggrimes we found the heading "Anticipate the need to use multiple tables, and use a unique identifier for every record" a little bit confusing. We should consider rephrasing this bit. The paragraph talks about using unique ids to link multiple tables (in a database kind of style).
@ewallace ewallace added the help wanted Looking for Contributors label Jun 10, 2023
@ewallace
Copy link
Collaborator

I think the text works, but it could be clarified and simplified. Leaving here with a "help wanted" label for now, hoping that someone will have a brainwave as to how to clarify the section.

ameynert pushed a commit that referenced this issue Jun 12, 2023
Clarified use of multiple tables
2703836 
- Record different data types in individual tables as appropriate (e.g. sample metadata may be kept separately from sequencing experiment metadata)
- Use unique identifiers for every record in a table, allowing linkages between tables (e.g. sample identifiers are recorded in the sequencing experiment metadata)

Addresses #44
@ameynert
Copy link
Collaborator

Updated to:

  • Record different data types in individual tables as appropriate (e.g. sample metadata may be kept separately from sequencing experiment metadata)
  • Use unique identifiers for every record in a table, allowing linkages between tables (e.g. sample identifiers are recorded in the sequencing experiment metadata)

In #109

ewallace added a commit that referenced this issue Jun 12, 2023
@ewallace
Response to Lex Nederbragt review (#109)
157988c 
* Summary and clarifications in 02-data_management.md

* Clarifications in 04-collaboration.md

* Simplify recap in 08-what_next.md

* changelog explanation and minor edits to 06-track_changes.md

* Clarify 05-project_organization.md

* Links, clarifications, in 05-project_organization.md

* Attribution to GEP paper in 02-data_management.md

* Attribute GEP paper in 03-software.md

* Attribute GEP paper in 04-collaboration.md

* Attribute GEP paper in 06-track_changes.md

* Attribute GEP paper in 07-manuscripts.md

* Add links in 03-software.md

* More links in 03-software.md

* Intro discussion notes in instructor guide

* Added links to resources on file naming

Addresses #42

* Clarified use of multiple tables

- Record different data types in individual tables as appropriate (e.g. sample metadata may be kept separately from sequencing experiment metadata)
- Use unique identifiers for every record in a table, allowing linkages between tables (e.g. sample identifiers are recorded in the sequencing experiment metadata)

Addresses #44

* Modifications to pseudocode exercise

Simplified exercise by giving learners the function and asking them to call the function with different parameters, then use the function within a for loop.

* Link fix for Azure

* Section heading change for multiple tables

* Expanded glossary

---------

Co-authored-by: ameynert <[email protected]>
zkamvar pushed a commit that referenced this issue Aug 31, 2023
@ewallace
Response to Lex Nederbragt review (#109)
a93ceb2 
* Summary and clarifications in 02-data_management.md

* Clarifications in 04-collaboration.md

* Simplify recap in 08-what_next.md

* changelog explanation and minor edits to 06-track_changes.md

* Clarify 05-project_organization.md

* Links, clarifications, in 05-project_organization.md

* Attribution to GEP paper in 02-data_management.md

* Attribute GEP paper in 03-software.md

* Attribute GEP paper in 04-collaboration.md

* Attribute GEP paper in 06-track_changes.md

* Attribute GEP paper in 07-manuscripts.md

* Add links in 03-software.md

* More links in 03-software.md

* Intro discussion notes in instructor guide

* Added links to resources on file naming

Addresses #42

* Clarified use of multiple tables

- Record different data types in individual tables as appropriate (e.g. sample metadata may be kept separately from sequencing experiment metadata)
- Use unique identifiers for every record in a table, allowing linkages between tables (e.g. sample identifiers are recorded in the sequencing experiment metadata)

Addresses #44

* Modifications to pseudocode exercise

Simplified exercise by giving learners the function and asking them to call the function with different parameters, then use the function within a for loop.

* Link fix for Azure

* Section heading change for multiple tables

* Expanded glossary

---------

Co-authored-by: ameynert <[email protected]>
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Looking for Contributors
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ewallace @aromanowski @ameynert