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

Extension of data model - References and Substrates #27

Open
gfeuerriegel opened this issue Nov 16, 2023 · 2 comments · Fixed by #29
Open

Extension of data model - References and Substrates #27

gfeuerriegel opened this issue Nov 16, 2023 · 2 comments · Fixed by #29
Assignees

Comments

@gfeuerriegel
Copy link

I think we should add information on publications and substrates of each enzyme to the data model. I suggest adding a table for publications with columns like "doi", "author" and "year" and connecting the table via a junction table (eg. "id", "protein_id", "publication_id") to the ProteinInfo table. The same goes for a substrate table and a junction table. Personally I only need the name and abbreviation of each substrate so far.

@haeussma haeussma self-assigned this Nov 23, 2023
@haeussma
Copy link
Member

Do you think we should add a property called substrate to the ProteinInfo object? Where is the information of an enzyme's substrate coming from? The information might either come from publication or from a not published experiment?

@gfeuerriegel
Copy link
Author

I think that would be an option but how would this property look like? Does it return a list of substrates in the case of promiscuous enzymes? In my case, I especially need the substrates because I am working with different plastics of course, but so far do not include other non-plastic substrates.
So far, this information on substrates came from publications only, as non published data is not included in the database.

@haeussma haeussma linked a pull request Nov 27, 2023 that will close this issue
@haeussma haeussma added this to the Ontology data model refactor milestone Apr 20, 2024
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

Successfully merging a pull request may close this issue.

2 participants