Have you seen the trending contents API?
This should work in Jive 6+, and while it might not give you all the detail you want in 1 hit, it should get you a strong starting point.
Hope that helps.
Do you have any more detail and configuration we can do with Trending Content? I am trying to read anything that explain the Trending Content rules and I tested v3/contents/trending?filter=type(document,discussion) and still cannot find why a file or discussion is selected and another is not, or the order, nor if I can get more records.
As an example, I manually added views to help identify a pattern, this is what I had return ...
Reply Like Views type
0 0 300 document
1 0 160 document
3 0 154 discussion
6 0 186 discussion
Hi guys, here more comment
I see some REST API that could help me but they lack some detail in the documentation that would help me find the right API call.
The following query allows me to view information that is similar to what I would like to report
The main issue with the trending API is I don't know what are the criteria for a document to be displayed in the trending result.
Are they objects that were recently viewed, are they objects that gets lots of reply, are they objects that gets lots of like, how far does it go back (last 1 hour, last day)?
Does anyone know what does the /contents/trending API logic and is there any way to extend it?
Has anyone found how to find object most viewed in the last XX hours and the most reply in the last XX hours?
Seems like this didn't find a reply https://community.jivesoftware.com/message/1328554#1328554
I read Ryan response to https://community.jivesoftware.com/thread/271484, do we have an equivalent resource available for using REST in Jive 6?
The /contents services allows to find all document updated, but I wasn't able to set my count higher than 100, what is the limit? Is there options available change it and to sort result in view count or in reply count? It could resolve most of my issues ...
Jean, apologies. Since trending was first really introduced in Jive 6, there is not a lot of depth to the API in that version. My understanding is that the cache size on the trending was fixed (to what I do not remember) ... but in the RecommendationQueryServiceHelper class, I see some fixed references to 50 and 500 for various calls. This is a pre-collection before security is enforced.
As for the criteria, this is part of the Jive intelligence to denote relevant / trending content ... so it is based heavily on likes, activity, tags and user social graph...a lot of moving parts that are harder to influence (at least in Jive 6).
While not the answer you are looking for (and probably later than you'd like), I hope this helps.
Thanks Ryan. Am I correct in thinking we don't have a Trending Content or Trending Users widget that we can drop onto our site's homepage & we'd need to code this up ourselves to query the REST API if we wanted that info to display?
Yep, you could use the HTML widget and jquery Ajax to call the api and render contents.
Looks like REST v3 struggles with custom content types, including Events.. the subject/title doesn't come back in the JSON. The 2nd one I highlighted is one of our own custom content types.
Yet these come back correctly in the Activity page, which uses the v2 API;