feature request #7888
closed
TypeSpecimenEditor: Collection date should be timespan
Added by Wolf-Henning Kusber over 5 years ago.
Updated about 5 years ago.
Description
There is an uncertainty in many old and new publications, for example only mm.yyyy or Autumn YY given, this can be handled easyly by a time span.
Currently no data are entered, if they are not precise.
Collection geo reference: uncertainty already solved
- Subject changed from PhycoBank TypeSpecimen Editor Usability to TypeSpecimenEditor: Collection date should be timespan
- Description updated (diff)
- Priority changed from New to Highest
- Target version changed from Unassigned CDM tickets to Release 5.5
In the GatheringEvent the gatheringDate setter and getters only operate with Partials but the gatheringDate value is transformed into a timeperiod which is stored in the base class EventBase
:
public void setGatheringDate(Partial gatheringDate){
this.setTimeperiod(TimePeriod.NewInstance(gatheringDate));
}
public void setGatheringDate(Calendar gatheringDate){
this.setTimeperiod(TimePeriod.NewInstance(gatheringDate));
}
It would make sense to allow using timeperiod for gatheringDate in general.
For the TypeSpecimenEditor
we will use the timeperiod
field instead of gatheringDate
- Status changed from New to Resolved
- % Done changed from 0 to 50
- Assignee changed from Andreas Kohlbecker to Wolf-Henning Kusber
- Status changed from Resolved to Closed
- Assignee changed from Wolf-Henning Kusber to Andreas Kohlbecker
- % Done changed from 50 to 100
Time span implemented as wished.
The data format might be reformated
Currently (German style): 1.1.2000-2.2.2010
This would be a different ticket.
Also available in: Atom
PDF