Use InterpretedField for interpreted non enum fields in the API

11552
Reporter: mdoering
Assignee: mdoering
Type: NewFeature
Summary: Use InterpretedField for interpreted non enum fields in the API
Priority: Major
Resolution: WontFix
Status: Closed
Created: 2012-07-11 13:10:50.814
Updated: 2013-12-09 13:40:46.431
Resolved: 2012-09-04 13:07:56.325
        
Description: We have started to use InterpretedEnum fields for model class properties that have a matching enum. But there are other fields, mostly of type String, that are also slightly interpreted. Replace those fields in the model classes with an InterpretedField instead.

Start by listing candidate fields in the comments. It might me that there are none in which case we can safely close the issue.]]>
    

Author: mdoering@gbif.org
Comment: with the new VerbatimNameUsage class this is not needed anymore, we will also remove the InterpretedEnum fields
Created: 2012-09-04 13:07:56.35
Updated: 2012-09-04 13:07:56.35