Metadatas are a convenient way to add a layer of data on top of DoYouBuzz datas (for each of your user). You can for example use metadatas to assign your own skillset to your users or wathever you want. Then, you can later use the search to get the users who have been assigned this metadata.
Datas are stored as a unique key for each user. You can also can add several keys for each user.
Of course, you can use this key as a key/value storing system: a key can be "key:value" or "key->value" or "key_value".
A same user can have a lot of different metadatas, posted by you or by other applications. To avoid name collision, you sould use a namespace mechanism to be certain your key is unique. For example a company called "Acme, Inc." wanting to add the skillset of ID 178 to a user could store the following key: com.acmeinc.skillset:178
The attributes are given in XML in the POST body.
POST https://api.doyoubuzz.com/metadata/update?apiKey=:apiKey
This is the general purpose method that handles all the different operations you might want to do on metadatas (assign, unassign)
You can use wildcard '*' for unassigning metadatas (eg. com.acmeinc.user.kind:*)
777
com.acmeinc.user.kind:*
com.acmeinc.user.kind:awesome-user
deprecated : use the 'update' method instead
POST https://api.doyoubuzz.com/metadata/assign?apiKey=:apiKey
This request will assign the metadata tid:456 to the user 1979.
com.acmeinc.skillset:178 1979
deprecated : use the 'update' method instead
POST https://api.doyoubuzz.com/metadata/assign?apiKey=:apiKey
You can also remove all the metatadas assigner to a user. If you send a reset and a metadata assignment in the same request (as shown below), the reset will be applied before the assignment. After sending this request, the user will have one key assigned: "com.acmeinc.skillset:178".
com.acmeinc.skillset:178 361551 361551
deprecated : use the 'update' method instead
POST https://api.doyoubuzz.com/metadata/unassign?apiKey=:apiKey
com.acmeinc.skillset:178 1979