Check that a verbatim value can actually exist with a null interpreted enum
10733
Reporter: kbraak
Assignee: kbraak
Type: SubTask
Summary: Check that a verbatim value can actually exist with a null interpreted enum
Description: As per title. Ideally, we would still show a verbatim value if the interpreted could not be found. Otherwise, I have a hunch that if no interpreted value is found, the interpreted enum as a whole is null.
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2012-02-01 17:21:21.435
Updated: 2013-08-29 14:46:01.344
Resolved: 2012-11-21 11:30:42.597
Author: kbraak@gbif.org
Created: 2012-11-16 15:33:43.222
Updated: 2012-11-16 15:33:43.222
The following API model object's fields use InterpretedEnum:
In Registry:
Contact.type
Dataset.dataLanguage
TaxonomicCoverage.rank
Author: kbraak@gbif.org
Created: 2012-11-16 17:28:00.964
Updated: 2012-11-16 17:28:00.964
Screenshot shows Contact.type and Dataset.dataLanguage show the verbatim value, even though no interpreted enum exist.
Outstanding is TaxonomicCoverage.rank
Author: kbraak@gbif.org
Comment: Attached patch for registry-metadata-service preserves verbatim rank when it can't be interpreted. Currently, when it can't be interpreted, null is returned instead of the InterpretedEnum with verbatim value set. After this is committed (waiting for Registry to build on Jenkins), I need to ensure these verbatim ranks appear on Taxonomic Browser section.
Created: 2012-11-16 17:30:37.117
Updated: 2012-11-16 17:30:37.117
Author: kbraak@gbif.org
Comment: Non interpreted (verbatim) ranks are now displayed, change made in http://dev.gbif.org/code/changelog/gbif-registry?cs=3347
Created: 2012-11-20 17:54:24.745
Updated: 2012-11-20 17:54:24.745
Author: kbraak@gbif.org
Comment: There is no need to show the interpreted and uninterpreted ranks differently. Therefore, this issue can be closed.
Created: 2012-11-21 11:30:42.638
Updated: 2012-11-21 11:30:42.638
