Our Blog > Blog Detail

Web Content Viewer- Asponte Custom Skin


Enhancing the Developer Experience:Portal Tagging and Rating REST API

  • Created By: Chris Knight
  • Updated: June 22, 2016
  • Tags: tagging, portal, rest, api, rating, developer, wcm


While trying to leverage the tagging and rating widgets, we were struggling with trying to mix jQuery with the necessary dojo widget that we only needed for the purpose of the tagging widget.  We started down the road of leveraging the SPI for tagging which can be found here:



While trying to leverage the create method of TagModelController, I ran across a result in google search for a page in the infocenter I had not previously seen.  Through some navigation, I came across this:




Tagging REST API example

The infocenter shows how this API can be leveraged, here's an example of what we used.  


I posted to the following URL:



And in the post, sent in the body of the request:

<?xml version="1.0" encoding="UTF-8"?><atom:feed xmlns:atom="http://www.w3.org/2005/Atom" 
         <atom:name>IBM WebSphere Portal/8.0</atom:name>
      <atom:title>IBM WebSphere Portal Model Feed</atom:title>
      <atom:link href="." rel="self" type="application/atom+xml"/>
      <atom:entry creation-context:private="false">
         <atom:title xml:lang="en_US">CMKTest</atom:title>
         <atom:id>uuid of the wcm item</atom:id>
         <atom:link portal:uri="rm:wcm:oid:uuid of the wcm item" rel="replies" href="example.org" />         

Note that for our use case, this was a WCM item so for the id we were using uuid values.

Also, for the 

<atom:link portal:uri="rm:wcm:oid:uuid of the wcm item" rel="replies" href="example.org" />         

I had to leverage the search center portlet to see what the format of the portal:uri tag was supposed to be.  In the case of a WCM item, that uri can just be rm:wcm:oid:uuid.


Contact Form- Asponte Custom Skin


Contact Us


Call Us 888-926-9434
Complementary Content