task #5244
closed
[DISCUSS] How should specimens be created and edited?
Added by Patrick Plitzner over 8 years ago.
Updated almost 3 years ago.
Description
What happens when clicking @New->Specimen@? => does not exist anymore, but see open issues
How/where are specimens associated with taxa (Individuals Association/Type Designation/Determination)? => for Campanula/Additivity it was decide to do the association primarily on Individual Associations , all other associations should be handled manually by the user
how is the specimen type handled? Should it be editable after creation? for now we remove the possibility to switch between fieldUnit and derivedUnit, currently also switching between MediaXXX and DerivedUnits or DnaSample and DerivedUnits should not be possible but this will be solved with #9455
How should derivatives be labeled? Including empty specimen. => partly handled with #9678 and others, fully handled with #9679
...
- Status changed from New to Closed
- Resolution set to fixed
- % Done set to 100
This is fixed with the implementation of the unified derivative editor
- Status changed from Closed to Feedback
- Resolution deleted (
fixed)
- % Done changed from 100 to 0
- Status changed from Feedback to Resolved
- Assignee changed from p.plitzner - to Andreas Müller
- Target version changed from Unassigned CDM tickets to Release 4.0
Check if all the issues are fully handled or if we need further tickets/discussion.
- Description updated (diff)
- Target version changed from Release 4.0 to Release 5.21
- Target version changed from Release 5.21 to Release 5.22
- Private changed from Yes to No
- Target version changed from Release 5.22 to Release 5.25
Open issues:
- Calling "New" in specimen list editor first opens single line dialogue and then opens full dialogue. First step should be skipped.
- It is possible to choose "FieldUnit" as type for a derived unit. This throws an exception and therefore should not be possible to choose from
- Description updated (diff)
Andreas Müller wrote:
Open issues:
- Calling "New" in specimen list editor first opens single line dialogue and then opens full dialogue. First step should be skipped.
- It is possible to choose "FieldUnit" as type for a derived unit. This throws an exception and therefore should not be possible to choose from
What kind of exception did you get? I could create a new field unit.
Katja Luther wrote:
Andreas Müller wrote:
Open issues:
- Calling "New" in specimen list editor first opens single line dialogue and then opens full dialogue. First step should be skipped.
- It is possible to choose "FieldUnit" as type for a derived unit. This throws an exception and therefore should not be possible to choose from
What kind of exception did you get? I could create a new field unit.
What I did was
- create new derived unit (with any or no data)
- change "Spec./Obs. Type" to Field Unit
- Description updated (diff)
- Description updated (diff)
- Description updated (diff)
The other way round for field units the type should not be changeable at all as generally switching a field unit to a derived unit and vice versa should not be possible.
- Description updated (diff)
- Status changed from Resolved to Feedback
- Assignee changed from Andreas Müller to Katja Luther
- % Done changed from 0 to 40
This ticket is fixed except for the open issue on limitation when setting the type. Can you please fix these minor issues and give the ticket back to me with status resolved once it is done?
- Status changed from Feedback to Resolved
- Assignee changed from Katja Luther to Andreas Müller
- % Done changed from 40 to 0
I removed the field unit from the combo box if it is anything else than a field unit and removed the combo box if it is a field unit.
Katja Luther wrote:
I removed the field unit from the combo box if it is anything else than a field unit and removed the combo box if it is a field unit.
Maybe it is better to disable the field then to fully remove it. Because otherwise the information that you opened a field unit is not seen anywhere. ALternatively we could add this information to the general Details View label as this is generally missing there somehow. Often one does not know what type of data is opened if this is not clear from the context. But this is a more general ticket. I would prefer to use the disabling. If this is for some reason difficult to implement we can also keep it as it is.
Hmm, I thought about it again and I think we can leave it as it is. Disabling also has disadvantages.
- Tracker changed from feature request to task
- Status changed from Resolved to Closed
- Assignee changed from Andreas Müller to Katja Luther
- % Done changed from 0 to 100
Also available in: Atom
PDF