Not logged in : Login

About: EntryPoint - user_customFields_set     Goto   Sponge   NotDistinct   Permalink

An Entity of Type : schema:EntryPoint, within Data Space : ods.openlinksw.com associated with source document(s)

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). property 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. value 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. fields A JSON stream of custom fields. This needs to be a JSON object containing simple key/value pairs (see below for an example). Example: http://web.ods.openlinksw.com/ods/api/user.udpate.customFields?property=myField&value=Foobar&property=myOtherField&value=42 JSON Example: { "myField":"Foobar", "myOtherField":42 } An error code stating the success of the command execution as detailed in ODS Error Result Codes. AuthenticationThis function requries authentication via one of the supported authentication methods as described in ODS Authentication.

AttributesValues
type
schema:url
schema:httpMethod
  • GET
schema:contentType
  • text/xml
http://www.openlin...es#isWebServiceOf
http://www.openlin...vices#endPointURL
schema:shortDescription
  • Add and modify custom field values to an ODS user profile.

http://www.openlin...ices#hasParameter
schema:name
  • EntryPoint - user_customFields_set
schema:description
  • 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).

  • property

    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.

  • value

    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.

  • fields

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

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

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

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

Authentication

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

is schema:target of
Faceted Search & Find service v1.17_git132 as of May 12 2023


Alternative Linked Data Documents: iSPARQL | ODE     Content Formats:   [cxml] [csv]     RDF   [text] [turtle] [ld+json] [rdf+json] [rdf+xml]     ODATA   [atom+xml] [odata+json]     Microdata   [microdata+json] [html]    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 08.03.3332 as of Sep 11 2024, on Linux (x86_64-generic-linux-glibc25), Single-Server Edition (15 GB total memory, 2 GB memory in use)
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2024 OpenLink Software