Opened 8 years ago
Closed 8 years ago
#2058 closed enhancement (fixed)
Item overview is not working when going from extract to derived bioassay
Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
---|---|---|---|
Priority: | major | Milestone: | BASE 3.11 |
Component: | core | Version: | |
Keywords: | Cc: |
Description
It is possible to create an item hierarchy that goes directly from extract to derived bioassay without a physical bioassay in-between.
The item overview functionality has problem with this though since it has not considered this case. It only supports going from extract to physical bioassay or raw bioassay.
It should be relatively easy to implement the missing link.
Change History (7)
comment:1 by , 8 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 8 years ago
comment:3 by , 8 years ago
(In [7301]) References #2058: Item overview is not working when going from extract to derived bioassay
This should fix the first part of the problem so that forward-loading links from extract to derived bioassays are considered.
This will load derived bioassays that has no parent derived bioassays and are linked directly to the extract. Note that there is no need to check other parents items here since if they are included in the overview tree the derived bioassay would have been included on that level instead.
comment:4 by , 8 years ago
comment:5 by , 8 years ago
(In [7303]) References #2058: Item overview is not working when going from extract to derived bioassay
The second fix did not work since it was going up and down among the extracts causing derived bioassays for other libraries in the pool to be loaded when they should not be loaded.
This fix changes the code so that only parent extracts from the root node are considered when loading the derived and raw bioassays.
comment:6 by , 8 years ago
(In [7304]) References #2058: Item overview is not working when going from extract to derived bioassay
The node cache must be disabled for now. There is a problem when, for example, when two or more libraries belonging to the same pool are in the same overview. If nodes are cached, contents below (or above) the pool will always follow the same path which is only correct for the first path opened:
Lib1 -> Pool1 -> ... -> Merged1 Lib2 -> Pool1 -> ... -> Merged1
comment:7 by , 8 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Hmm... it was a lot more complicated than what I first believed...
There might be an intermediary extract (eg. a pool) that is holding the link.
So when looking for derived bioassays to load, we simply can't look att first extract we find upstreams (which is the pooled library) since the back-link may go to any extract in the upstreams chain. We need to load all related extract that we can find, and then we can load the correct derived bioassay.
Note that this seems to be implemented already, but only if we start high enough up in the item chain (eg. at the Library level or higher). If we start at the pooled library level, no derived (or raw) bioassays are loaded in the overview.