Version 2

    Overview                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

    Starting with Jive 6.0, we have introduced the concept of Quests to help bring new users into the instance, and to ease the Onboarding process. At some point, you may find yourself curious about the overall effectiveness of these Quests, and the impact that they have had on your user base. This document will help you understand how we store the metrics in the jiveQuestProgress table.

     

    Table Details

    There are five columns in the jiveQuestProgress table:

    1. questprogressid = A unique identifier for a user's quest
    2. questid = Stores the id of which of the three quests this quest is
    3. userid = The user that is doing the quest
    4. completiondate = The unix timestamp for when all steps in the quest were completed (will be 0 if it hasn't been completed)
    5. data = Stores which steps have been completed for that quest.

     

    The schema for this table can be found here. So, an example of the jiveQuestProgress might look something like this:

     

    questprogressid |   questid   | userid | completiondate |                                   data                                   
    ----------------+-------------+--------+----------------+---------------------------------------------------------------------------
               1068 |   856595828 |  28971 |  1364642027594 | {"2.complete":true,"1.complete":true,"3.complete":true}
               1004 |   856595828 |  66735 |  1364624776775 | {"2.complete":true,"1.complete":true,"3.complete":true}
               1011 |   856595828 |  57332 |  1364636983739 | {"2.complete":true,"1.complete":true,"3.complete":true}
               1016 | -1790695889 |  32332 |              0 | {"4.complete":true,"1.complete":true}
               1002 | -1790695889 |  66735 |              0 | {"5.complete":true,"4.complete":true,"3.complete":true}
               1060 |   856595828 |  86596 |  1364641171632 | {"2.complete":true,"1.complete":true,"3.complete":true}
               7985 | -1790695889 |  27933 |              0 | {"4.complete":true}
               1027 | -1790695889 |  31406 |              0 | {"5.complete":true,"1.complete":true,"3.complete":true}
               1003 |  -775000491 |  66735 |              0 | {"2.complete":true,"4.complete":true,"1.complete":true,"3.complete":true}
               1014 |   856595828 |  87846 |  1364627286658 | {"2.complete":true,"1.complete":true,"3.complete":true}

     

    We can line up the questid and the data columns to the following quests and steps:

     

    Basic Quest (questID = 856595828)

    Step numberStep description
    1Learn how this system works
    2See how to connect to your colleagues
    3Tell us a bit about you

     

    Explore Quest (questID = -1790695889)

    Step numberStep description
    1Take a tour of the interface
    2Change your avatar
    3Like something
    4Join a group
    5Connect with your mobile device

     

    Contribute Quest (questID = -775000491)

    Step numberStep description
    1Comment on something
    2Post a status update
    3Start a discussion
    4Collaborate on a document
    5Try Jive Anywhere

     

    So, we can use all this information to determine that the first row of the jiveQuestProgress table above tells us that user 28971 completed the Basic Quest at 1364642027594, or March 30th 2013 at 04:13:47am.

     

    Note

    The quests can be turned on or off using the system property onboarding.enabled