Difference between revisions of "API/Data Curation API/PREFER THOROUGHFARE NAME"

From CDQ
API/Data Curation API/PREFER THOROUGHFARE NAME
Jump to navigation Jump to search
 
Line 3: Line 3:
 
  | technical key = PREFER_THOROUGHFARE_NAME
 
  | technical key = PREFER_THOROUGHFARE_NAME
 
  | description = * thoroughfare value in address curation result is replaced by thoroughfare name
 
  | description = * thoroughfare value in address curation result is replaced by thoroughfare name
 +
| example =
 +
<pre>
 +
"thoroughfares": [
 +
{
 +
"type": {
 +
"name": "Street",
 +
"url": "https://meta.cdq.com/Address/thoroughfare/type/street",
 +
"technicalKey": "STREET"
 +
},
 +
"shortName": "Lukasstr.",
 +
"number": "4",
 +
"value": "Lukas",
 +
"name": "Lukas"
 +
}
 +
],
 +
 +
</pre>
 
  | api = API/Data Curation API
 
  | api = API/Data Curation API
 
}}
 
}}

Latest revision as of 12:23, 28 November 2022


Name Name of a concept, e.g. a data model concept. In contrast to terms, the name does not depend on a given context, e.g. a country-specific language. Prefer thoroughfare name
Description Informal and comprehensive human-readable definition of a concept.
  • thoroughfare value in address curation result is replaced by thoroughfare name
Technical key Defines a unique key by which e.g. data model concepts can be referenced in a technical integration context. These keys are unique in the CDL context. PREFER_THOROUGHFARE_NAME
Example A simple example supporting the understanding of a concept, business rule, etc. 
"thoroughfares": [
	{
		"type": {
			"name": "Street",
			"url": "https://meta.cdq.com/Address/thoroughfare/type/street",
			"technicalKey": "STREET"
		},
		"shortName": "Lukasstr.",
		"number": "4",
		"value": "Lukas",
		"name": "Lukas"
	}
],
API  API/Data Curation API
Profile The profile in which a feature is activated by default n/a


Retrieved from "https://meta.cdq.com/index.php?title=API/Data_Curation_API/PREFER_THOROUGHFARE_NAME&oldid=580722"