Opened 16 years ago
Closed 16 years ago
#1190 closed task (fixed)
API and interface for creating biomaterial lists
Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
---|---|---|---|
Priority: | major | Milestone: | BASE 2.10 |
Component: | core | Version: | |
Keywords: | Cc: |
Description
This depends on #1175.
In the web interface it should be possible to create biomaterial lists. It should be somewhat similar to how reporter lists can be created. Eg. in any list containing reporter information it is possible to create a list from the reporters that are "selected", "in the current page" or "all matching". We have to go one step further with biomaterial lists, with options for:
- all children (one step down, type doesn't matter)
- all children of same type (any number of steps down)
- all children of next type (any number of steps down until we reach the next type)
The next type of a biomaterial follows the regular order: Biosource -> Sample -> Extract -> Labeled extract
Due to pooling, etc. there may be any number of steps on each level (except biosource) before the next type is reached.
Note! It may make sense to select more than one option.
The functionality of this should go into the core (utils?).
Change History (4)
comment:1 by , 16 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 16 years ago
comment:3 by , 16 years ago
(In [4723]) References #1190: API and interface for creating biomaterial lists
All functionality should now be in place. It turned out that the one-step-down restriction wasn't neccesary since it was possible to link multiple steps together. In other words, it is now possible to generate a list with all labeled extracts that descend from the selected biosources. It also possible to move in the other direction, eg. from labeled extract to biosource.
comment:4 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
(In [4712]) References #1190: API and interface for creating biomaterial lists
Parts of the basic functionality is in place. Needs to be polished up a bit with more error handling.