"

Add and modify custom field values to an ODS user profile.

" . . "EntryPoint - user_customFields_set" . "GET" . "text/xml" . . . "

ODS allows to store any additional details in a user profile. This is simply done by storing the data in a private graph of the Virtuoso triple store.

Clients can provide as many custom fields as required, ie. repeat the parameters below an arbitrary number of times. Alternatively custom fields can be provided in JSON format (see below for an example).

  • \n\nproperty\n\n\n

    The field name. The property to store typically this is a full URL denoting the RDF property to use. It can, however, also be a simple string identifier like myCustomField. In that case ODS will use a default namespace as a prefix. Qnames will be expanded for all known prefixes.

    \n
    • \n
  • \n\nvalue\n\n\n

    The value of the property. By default all values are stored as strings. If the value can be converted into an integer then it is stored as such.

    \n
    • \n
  • \n\nfields\n\n\n

    A JSON stream of custom fields. This needs to be a JSON object containing simple key/value pairs (see below for an example).

    \n
    • \n\nExample: http://web.ods.openlinksw.com/ods/api/user.udpate.customFields?property=myField&value=Foobar&property=myOtherField&value=42\n

    JSON Example: {\n\"myField\":\"Foobar\",\n\"myOtherField\":42\n}\n

    An error code stating the success of the command execution as detailed in ODS Error Result Codes.

    \nAuthentication

    This function requries authentication via one of the supported authentication methods as described in ODS Authentication.

    \n

    " . . . . .