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

SO Numbers are not required parameters #6

Open
3 of 8 tasks
shamseen opened this issue Jul 7, 2017 · 0 comments
Open
3 of 8 tasks

SO Numbers are not required parameters #6

shamseen opened this issue Jul 7, 2017 · 0 comments
Assignees
Labels

Comments

@shamseen
Copy link
Collaborator

shamseen commented Jul 7, 2017

To create a valid SBOL Document for SBOL 2.0, there needs to be a Sequence Ontology number attached.

Currently, users can leave it blank when adding a new part via Eugene.

  • Require SO numbers as a parameter (allow for duplicates)
  • blanks will map to Engineered Foreign Region: SO_0000805
  • If it's common (e.g. Promoter), can take in English text, not numbers.
  • Non-blank, non-common term: assume it's a number and add to URI namespace (no validation).
  • Mapping unit tests
  • Display a warning about default values and duplicates
  • Display warning about known part names (e.g. Promoter, Origin_of_Replication, etc).
  • Warning unit tests

image
image

@shamseen shamseen self-assigned this Jul 7, 2017
@shamseen shamseen added this to the Support SBOL v2.0 milestone Jul 26, 2017
@shamseen shamseen changed the title Eugene Part/PartType CRUD SO Numbers are not required parameters Jul 26, 2017
@shamseen shamseen added the bug label Jul 26, 2017
shamseen added a commit that referenced this issue Jul 26, 2017
shamseen added a commit that referenced this issue Jul 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant