Generally, I find developers implementing scenarios, such as “As a User, I need to iterate over X Social API, so I can find the right content.” The scenario implies that the social metadata is included, however many developers iterate over the entries in the feeds to discover the Tag metadata. If you read the documentation parameters, you can find optimizations to include metadata in the feed request, such as:
Specifies whether or not the tags that are displayed on the file welcome page are included in the returned Atom document. This parameter takes a Boolean value of either true or false. By default, the tags are not returned.
The URL Parameter that reduces the total number of requests needed. For instance, the request for a each of the 10 entries in a feed, and then the tags for those 10 entries appears to require 11 API calls with the includeTags=true it can be accomplished in one request.
You can also optimize the request by manipulating the page size – 1,10 or 25.
In some cases, you can further optimize with batch requests when creating content. Example, the Activities API enables batch deletes of Members or the OpenSocial ActivityStream API which enables batch creation of updates.
A customer ran into a problem calling the BSS APIs against the IBM Connections Cloud (IBM SmartCloud for Social Business) C1 Test Environment. The default environment is setup with Open Authorization, and you can configure your own environment.
A tip for those folks out there programming with IBM Connections and Java. IBM Connections uses UTC dates/time within the API calls. You may run into some funky times if you process it in your local timezone.
Don’t make any timezone conversions, don’t set UTC, just simply deserialize the ATOM feed, and then extract the date/time, and parse it as in the following snippet. *The Key is using the proper date format – “yyyy-MM-dd’T’HH:mm:ss.SSS’Z'”