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

profile_table IMPORTANT #94

Open
petermr opened this issue Aug 7, 2019 · 0 comments
Open

profile_table IMPORTANT #94

petermr opened this issue Aug 7, 2019 · 0 comments
Assignees

Comments

@petermr
Copy link
Collaborator

petermr commented Aug 7, 2019

The PROFILE table is central to V1.0 it links to everything. It is critical that the keys in the new tables are linked correctly to PROFILE.

PROFILE contains the individual experiments that were done. It will contain PROFILE_DATA (a list of COMPOUND-PERCENT pairs) . Profile data should be a separate table .

DO WE HAVE A PROFILE TABLE?? It would have about 5000 records . (PROFILE_DATA will have about 142,000 records). The PROFILE table will have (see poster)

  • foreign key to LOCATION (Ambarish)
  • foreign key to PLANT (Shruthi)
  • foreign key to PLANTPART (who is doing this table?)
  • freeform date-time
  • freeform conditions OR link to CONDITIONS_TABLE
  • foreign key to BIBLIOGRAPHY
  • freeform experimental conditions
  • LINK to PROFILE_DATA (the compounds will be in this table)

It is CRITICAL this is solved before Shruthi goes.

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

5 participants