Ticket #255 (closed defect: worksforme)
entity tokens should be stable
|Reported by:||robert@…||Owned by:||business@…|
The studyToken, sampleToken and assayToken can be changed by the user. This results in errors when a (e.g.) sample is renamed. A module that has data for that sample, doesn't know the sample is renamed, but only knows that one sample is removed, and another one is added. That way, the module doesn't know what to do with the data connected to it.
GSCF has samples A1, A2 and A3. A module has data for all 3 samples. Now, the user renames sample A2 to A4 (for some reason). The module now sees that the study has samples A1, A3 and A4. He will conclude that A2 has been removed and A4 has been added.
This can be avoided by creating stable tokens that will never change. This could be the id of an entity, but might also be another value, as long as it is stable for the lifetime of the object.
Even when this situation won't happen often, it is still important to avoid the problem anyway.
- Owner changed from work@… to robert@…
- Status changed from new to assigned
- Owner changed from robert@… to business@…
- Cc m.s.vanvliet@… added
comment:11 Changed 5 years ago by business@…
- Status changed from assigned to closed
- Resolution set to worksforme