Short Description: The various initiatives associated with the account.
Long Description: Initiatives are dynamic and allow the account to "divide and conquer" as they say. Initiatives can have groups as well as initiatives embedded within them.
Also, Authority Document lists can be assigned to Initiatives.
Initiatives, unlike Groups, do have begin and end dates.
This element connects to the following elements:
JSON Calls documentation:
This element is comprised of the following fields:
|country||string||The country the address is located in.|
|postal_code||string||The postal/zip code for the address.|
|time_created||string||The date and time the record was created.|
|time_updated||string||The date and time the record was last updated.|
|unspsc_code||string||The United Nations product and service code most applicable to the record.|
|account.id||integer||ID of the account record.|
|active_status||string||The status of the list. 'A' = active. 'D' = deprecated.|
We humans have to use numbers. However, when entering numbers, we humans also have a tendency to screw up the entry or copying of those numbers. A Dutch mathematician named Jacobus Verhoeff conducted a study of 12,000 numerical errors J. Verhoeff, Error Detecting Decimal Codes, Mathematical Centre Tract 29, The Mathematical Centre, Amsterdam, 1969, cited in Wagner and Putter, "Error Detecting Decimal Digits", CACM, Vol 32, No. 1 (January 1989), pp. 106-110. and from that, proposed a check digit calculation scheme http://www.augustana.ab.ca/~mohrj/algorithms/checkdigit.html#verhoeff that catches all single errors as well as all adjacent transpositions and most other errors.
To ensure that the IDs assigned by the system have integrity during input as well as distribution while being transferred into various formats (such as Excel, Word, Text, XML), each ID will also have its own checksum value stored in a checksum field.
Currently, the methodology for creating and verifying the checksum follows the Verhoeff calculation format.
The CheckDigit is created along with the record's ID as a calculation by the UCF database system. As such, once assigned it should never change because the ID will never change. A sample calculation format is shown in the use case scenarios.
|creator._href||URL||URL to get the user who created the list.|
|creator.id||integer||The ID of the user who created the list.|
|groups._href||URL||URL to get the list's groups from.|
|name||string||The record’s name derived from the harmonized dictionary term assigned to the record.|
|account._href||URL||URL to get the list's account information from.|
|ad_lists._href||URL||URL to get the list's Authority Document information from.|
|description||string||This is a CSS formatted HTML entry containing the Authority Document’s Official Name, it’s ID, availability, the current number of citations associated with it, and when it was last reviewed and released.|
|map_coordinates||string||The geographic coordinates associated with this record.|
|map_points||string||The coordinate points used to create a geographic fence.|
|map_zoom||string||The zoom level for the map associated with this record.|
|users._href||URL||URL to get the list's user information from.|
|end_date||date||The date that the initiative ends.|
|start_date||date||The date that the initiative begins.|
Please sign in to leave a comment.