Assert consistent use of species and taxonKey, replacing name usage and nubKey
14700
Reporter: mdoering
Assignee: mdoering
Type: Improvement
Summary: Assert consistent use of species and taxonKey, replacing name usage and nubKey
Priority: Critical
Resolution: Fixed
Status: Closed
Created: 2014-01-14 10:52:10.017
Updated: 2014-06-27 17:32:22.728
Resolved: 2014-06-27 17:32:22.693
Description: for urls we should be using /species instead of name_usage all over by now. Assert we do not expose NameUsage anywhere anymore.
For keys consistently apply taxonKey everywhere (e.g. search parameters, class properties) instead of using usageKey or nubKey.]]>
Author: omeyn@gbif.org
Created: 2014-06-23 16:16:15.38
Updated: 2014-06-23 16:16:15.38
See also http://www.gbif.org/developer/occurrence#inventories
Author: mdoering@gbif.org
Comment: NameUsage class has a primary "key" property and then also a "nubKey" property that holds the key of the matching backbone usage. Should this be renamed to taxonKey instead? Feels to me we better leave this as nubKey to be clear what it is. But then we use "taxonKey" for the exact same thing in the Occurrence class, so guess its more clear to also use taxonKey in NameUsage then
Created: 2014-06-25 12:47:33.95
Updated: 2014-06-25 12:49:09.444