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

Registering subjects of which samples are taken #143

Open
jjkoehorst opened this issue Feb 7, 2020 · 0 comments
Open

Registering subjects of which samples are taken #143

jjkoehorst opened this issue Feb 7, 2020 · 0 comments
Labels

Comments

@jjkoehorst
Copy link

@jjkoehorst jjkoehorst commented Feb 7, 2020

When for example sampling 120 chickens each with its own unique identifier and additional information it could become a bit confusing on where to register what in the SEEK platform.

For example you can register the organism chicken as a global entity but each individual chicken currently has to be registered as a sample. Of these chickens (which are samples) actual samples are taken and registered in the platform as samples of samples.

Ideally it would be nice to have a level between Organism and Sample which would then create the following:

Chicken (Organism) > Chicken1 (Observation Unit) > Sample 1
Chicken (Organism) > Chicken1 (Observation Unit) > Sample 2
Chicken (Organism) > Chicken2 (Observation Unit) > Sample 1

I mentioned Observation Unit as I encountered this in the MIAPPE standard which describes it as followed:

Observation units are objects that are subject to instances of observation and measurement.
An observation unit comprises one or more plants, and/or their environment.
There can be pure environment observation units with no plants. Synonym: Experimental unit.

Not sure if there are better solutions but from a user perspective I think its rather confusing to have samples which are actually animals, bioreactors or other kinds of entities.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.