Opened 4 years ago
Last modified 4 years ago
#1209 closed task
Add support for storing TMA specimen — at Initial Version
| Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
|---|---|---|---|
| Priority: | major | Milestone: | Reggie v4.25 |
| Component: | net.sf.basedb.reggie | Keywords: | |
| Cc: |
Description
TMA are sometimes created by external projects. We want to track some information about this so that we at least can say for which patients a TMA exists and were to find it.
We need to define a few things to be able to store TMA specimen.
A new SAMPLE subtype: TMASpecimen.
- It should be a child item of
Case. - The name should be auto-generated as:
<case>.tma,<case>.tma2 - The external/release id should be auto-generated as:
T<NNNNNN>
Annotations:
TMABlock: Name of the TMA block on which the sample is located.TMABlockPos: Position on the block. In some coordinate system that at least can be understood by the person responsible for the external project.PAD: The PAD that was used as source for the TMA. Typically it should match a PAD of a specimen/no-specimen, but it may also be different.ExternalProject: Name of the external project that created the TMA.- More ???
An import wizard for importing TMA data should also be created. It should be able to read from an text or Excel file. It will need a way to identify the case. The simplest solution would be to have the name of the case in the file. But it would also be possible to find the correct case by personal number and laterality or maybe by PAD on specimen.
Once a parent case has been found a TMASpecimen can be created and named automatically. Most annotations are taken from columns in the file. The ExternalProject annotation should be the same for all, so this can be an input parameter in the import wizard.
