Status level data is not being stored in analytics. There are no plans as of yet to pull it over.
Thanks for the info. One last question on this topic though, can you help me understand how the following object types are being used within the analytics databse if no points or status level information is being captured in analytics? Are they not being used within analytics? If they are, what do they represent?
Thanks for the help.
These are constants used by the status level sub system, but they are not relevant for analytics.
Where did you obtain these monikers from? If they came from some analytics documentation them they are incorrect and we should probably remove them.
I obtained them after searching through the discussion logs for a list of object types and activity types. It looks like I fell upon the complete list of object types and not just those that are specific to the analytics side.
I don't think anything needs to be cleaned up as the list below is what I now see in the Jive SBS data model.pdf document which I also discovered through searching the discussions. My only question would be whether that list is completely up to date.
Object Type Value
DISCUSSION THREAD 1
DISCUSSION MESSAGE 2
COMMUNITY (Space) 14
TAG SET 42
USER STATUS 48
USER RELATIONSHIP 49
DOCUMENT VERSION 120
DOCUMENT VERSION COMMENT 121
SOCIAL GROUP 700
USER CONTAINER 2020
Mark - Not to beat a dead horse on this one, but I noticed the following reports available within the admin console related to points. From our conversations below it appeared that any type of point information was not currently available in the analytics database - is that true and if so where are these reports sourcing their data from? Thanks - John
In the image below you can see reports available for information on points rewarded for types Helpful, Solved and Total Points Awared.
1 person found this helpful
This is the old reports system that run queries against the SBS operational database. They have been around since Clearspace (SBS) 1.x. Each night a background task runs a query against the database to update counts for the day. These components are no longer being improved upon and the may even be removed in the next major release.
I figured they were coming directly from the app database. Thanks for the quick response. That answers my question.