We have been creating a custom IBM Connection’s widget for a client that allows a user to upload a series of predefined tags to their (or someone else’s) profile. This in effect gives the user a catalogue of tags to choose from that are broken into sections, allowing them to rapidly populate their profile with tags that have meaning across the organisation. A couple of things came up as part of this development, firstly, what is the format of the ATOM message that is required?
To save you from using the help, what you need to do is upload the entire tags for the user, which means that if you want to add a single tag, you need to download the existing tags and add the additional tags to the list. The format of the ATOM file that needs to be sent is as follows (note this needs to be sent as a HTTP PUT):
1 2 3 4 5 6 7 8
<categories xmlns="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:snx="http://www.ibm.com/xmlns/prod/ns"> <atom:category term="arabic"></atom:category> <atom:category term="english"></atom:category> <atom:category term="french"></atom:category> <atom:category term="italian"></atom:category> <atom:category term="mandarin"></atom:category> <atom:category term="other language"></atom:category> </categories>
This seems to work a treat in the testing that I have done so far. One interesting point to note is that this method of updating the tags allows you to insert tags into a profile that includes spaces – see the “other language” value above. This appears to work in the backend as well because it renders properly in the tags widget:
If you would like to discuss customizing your IBM Connections implementing using widgets, then please email me at [email protected] for more information.