Forum Discussion

adtucs's avatar
adtucs
Helper
9 days ago

Help identifying XML fields for message attributes in Khoros data export

I'm working on a project where I need to parse and process a Khoros XML data export of my community, and I'm trying to map out the right entities and fields for several message-level attributes.

Specifically, I'm trying to figure out which XML files, entities, and fields correspond to the following:

  • Visibility scope of a message i.e how can I tell a message is private, draft or archived 
  • Whether the message is a solution and solution is marked by which user / user_id and when (time)  
  • Whether the message is read only or has comments blocked
  • Moderation status - whether the message was rejected, approved etc
  • Kudos - How can I find the kudos count and individual kudo for a message e.g user, time and weight info
  • similarly, where is the MeToo data stored for a message?

Any help with field names, entity references, look in would be a huge help.

1 Reply

  • AI_Answer's avatar
    AI_Answer
    Contributor
    8 days ago
    Automatic Answer 1 citation
    It sounds like you're diving into a complex project with the Khoros XML data export, and I can see how identifying the right fields can be quite challenging. For the visibility scope of a message, you should look for the "status" or "visibility" fields within the message entity. These typically indicate whether a message is public, private, a draft, or archived, although the exact field names can vary depending on your specific export setup. To determine if a message is a solution, you can check for a "solution" flag or similar attribute, often accompanied by fields that reference the user ID of the person who marked it as a solution and the timestamp of when it was marked. Additionally, for moderation status, look for fields like "moderationStatus" which will indicate whether a message has been approved, rejected, or is under review. For kudos, the kudos count can usually be found in a "kudos" or "likes" field, and individual kudo details such as user ID, timestamp, and weight may be nested within a "kudosDetails" structure or similar. The same goes for MeToo data, which may be stored in a comparable nested structure. While specifics can differ based on your version or configuration, these general guidelines should help you navigate the XML data export more effectively. If you have access to the Khoros documentation or community forums, those can also be invaluable resources for field names and structures specific to your instance [1].
    ★

    Expert Contributors