Add Kit item
|Reported by:||Nicklas Nordborg||Owned by:||Nicklas Nordborg|
Description (last modified by )
A Kit is an item that should represent a kit/collection of reagents and other stuff used in the lab to do something.
To begin with we intend to keep the Kit item as simple as possible. For example we do not add special data structures for keeping track of individual items in a kit (use annotations for that).
A kit should have:
- Name and description (implement the
- Registration date (implement the
- Access is controlled via regular project/user/group sharing (implement the
- A subtype so we can filter kits to be used at a specific step in the lab process (implement the
inactiveflag that indicates if the kit can still be used or not.
expirationDatefor storing the recommended last date the kit should be used.
Selecting inactive kits or using kits after the expiration date should not be forbidden in the core API. It should be used by applications to make sensible default selections.
Kits are linked from:
- Biomaterial events (samples, extracts, physical bioassays)
- Bioplate events
- Derived bioassays (since the first derived bioassay typically represents the sequencing of a flow cell)
Besides the usual list/view/edit pages in the web client we need to implement and update some other things:
- A batch item importer for kits
- The annotation importer should support kits
- Add kits to the "Item overview" and some new validation rules:
- Check the expiration date against the creation date of items that has used the kit
- Add kits to "Item subtypes"
- Inherit annotations from kits