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

Inclusion of new injection routes #37

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

laurenechan
Copy link
Collaborator

including three more specific injection routes requested as a part of ECTO manuscript edits, completes #35

including three more specific injection routes requested as a part of ECTO manuscript edits
Copy link
Collaborator

@matentzn matentzn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should be editing

https://github.com/CTDbase/exposure-ontology/blob/master/src/ontology/exo-edit.obo

you are editing the release file :) Sorry about that.

I do not do content review, but structurally it looks ok otherwise. I wonder whether a more unambiguous naming scheme would be better, like subcutaneous injection route, as subcutaneous sounds like a characteristic to me.

@laurenechan
Copy link
Collaborator Author

Whoops! I will shift those changes over to the obo file. @diatomsRcool any preference for the term labels? Happy to adjust if that more specific label is preferred.

removing from the release file, will re-add to edit file
adding injection routes back into the edit file
Copy link
Collaborator

@matentzn matentzn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can do:

git checkout master -- exo.owl

when in the top level of ecto with terminal to undo all changes to exo.owl.

updating diff
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 this pull request may close these issues.

2 participants