feature request #2985
closedImprove Specimen details display
100%
Description
split of from to #2411
1. Altitude¶
AbsoluteElevationMaximum can be left out if it is the same as Minimum. Better we show:
- Altitude: 3400 m or
- Altitude: 3400 -3500 m
Always use meter as unit as the field is defined this way !!
DONE
2. There is further information available that does not show up like¶
2.a additional areas¶
should be shown with the area level such as
- level: area label
Best would be if ordered by levels
DONE implemented as names area page
2.b Extensions¶
best shown as
ExtensionType: text
On the very bottom
DONE
2.c Determinations (not so urgent, but data exists)¶
Later we will also need "duplicates" but this still needs further discussion
Worksforme
Related issues
Updated by Andreas Kohlbecker almost 11 years ago
- Subject changed from Improve Sepecimen details display to Improve Specimen details display
Updated by Andreas Kohlbecker about 8 years ago
- Target version changed from cdm_dataportal RELEASE 3.5.0 to cdm_dataportal RELEASE 3.5.1
moving tickets to next milestone
Updated by Andreas Müller about 8 years ago
- Target version deleted (
cdm_dataportal RELEASE 3.5.1)
move open 3.5.1 tickets to next milestone after release
Updated by Andreas Kohlbecker almost 8 years ago
- Keywords set to Flore-Afrique-Centrale, Specimen,
Updated by Andreas Müller almost 8 years ago
- Target version deleted (
cdm_dataportal RELEASE 3.8)
Review issue 1 in milestone 3.9. Issue 2 is not that important but probably fast to implement.
Updated by Andreas Müller over 7 years ago
- Target version deleted (
Release 3.12)
Updated by Andreas Müller about 7 years ago
- Target version changed from Release 4.0 to Release 4.1
Updated by Andreas Müller about 7 years ago
- Target version changed from Release 4.1 to Release 4.2
Updated by Andreas Müller almost 7 years ago
- Target version changed from Release 4.2 to Release 4.3
Updated by Andreas Müller over 6 years ago
- Target version changed from Release 4.3 to Release 4.4
Updated by Andreas Kohlbecker over 6 years ago
- Description updated (diff)
- Status changed from New to In Progress
- Private changed from Yes to No
Updated by Andreas Kohlbecker over 6 years ago
- Description updated (diff)
- % Done changed from 0 to 10
Updated by Andreas Kohlbecker over 6 years ago
Hi Andreas M.
the the original ticket you wrote:
additional areas should be shown with the area level such as
level: area label
Best would be if ordered by levels
I guess you are referring to the Country field. For this I don't see the necessity to add the area level and thus will abstain from implementing this feature.
Updated by Andreas Müller over 6 years ago
Andreas Kohlbecker wrote:
Hi Andreas M.
the the original ticket you wrote:
additional areas should be shown with the area level such as
level: area label
Best would be if ordered by levelsI guess you are referring to the Country field. For this I don't see the necessity to add the area level and thus will abstain from implementing this feature.
No, I refer to the additional areas (GatheringEvent.collectingAreas). For them it is often important to know if they are provinces, states, cities, ...
Updated by Andreas Kohlbecker over 6 years ago
- Description updated (diff)
- Status changed from In Progress to Resolved
Andreas M: please review
Updated by Andreas Kohlbecker over 6 years ago
- Assignee changed from Andreas Kohlbecker to Andreas Müller
Updated by Andreas Müller over 6 years ago
- Description updated (diff)
- Status changed from Resolved to Feedback
- Assignee changed from Andreas Müller to Andreas Kohlbecker
1) works well
2a) works well in terms of area level being shown, but I wonder if the new Named Area page could not be more comprehensive. Why does it not show abbrev label, description, named area type, URI, valid period, and maybe also supplemental data.
Also the ordering by levels is not yet implemented
2b) works correctly, however, if possible I would remove the label "Extensions": extensions are thought to be dynamic attributes to avoid model limitations; for users of the data portal it should not make a difference if information is stored as extension or in an explicit "top level" field like locality, so information stored in extensions should show up as if they were top level information
2c) generally works, but maybe some minor improvements could be done:
- if no description is given the string ends with a comma, a trailing comma should be avoided
- taxa, if available (and maybe also names, if only name is available) could be linked
- if a modifier is given a space is missing between the name and the modifier
- preferably use abbrev label for the modifier, only if not available use label (however, the determination modifiers are not yet correctly implemented in the model as they can be found at various positions in the name, so we need a model change and a fomatter for these before it can be handled really correctly
Updated by Andreas Müller over 6 years ago
Updated by Andreas Kohlbecker over 2 years ago
- Tags changed from flore-afrique-centrale, specimen to flore-afrique-centrale, specimen, specimens-view-path
Updated by Andreas Kohlbecker over 2 years ago
- Copied to feature request #9244: Improve NamedArea page added
Updated by Andreas Kohlbecker over 2 years ago
- Copied to feature request #3502: extensions not yet handled in compose_cdm_specimenOrObservation() added
Updated by Andreas Kohlbecker over 2 years ago
- Copied to task #8419: Harmonization of the different specimen representations added
Updated by Andreas Kohlbecker over 2 years ago
- Status changed from Feedback to Closed
- % Done changed from 50 to 100
remaining issues and suggestions from comment 23 copied to other issues.
So we can close this issue now.