Learn how to interpret the board or category or group hub from the ancestor node path.
The Bulk Data API gives you a node.ancestor_path
for applicable events that looks like /1/2/1440/1197/1222/
.
The node ancestor path collection node UIDs (numerical IDs) represent the parent-child hierarchy of the node subjected to user activity.
Using the API v1 calls, you can retrieve the details of the UID but you cannot find the UID in APIv2 or LiQL queries.
Based on the node.ancestor_path
, you can know the details of whether the node belongs to a category, board, or group hub.
To know the details of the node, you can try both /restapi/vc/categories/uid/X
and /restapi/vc/boards/uid/X
.
You can ignore whichever call returns an error.
For example:
/1/2/1440/1197/1222/
The node.ancestor_path
is described as follows:
-
/1 or /2
- This is the top category or root category, which is a special category equivalent to the community level. You can know the top category or root category by making the following request:https://[COMMUNITY DOMAIN]/restapi/vc/categories/uid/2
-
/1440
- This is a "top level" category, right under the community level. You can know the “top level” category by making the following request:https://[COMMUNITY DOMAIN]/restapi/vc/categories/uid/1440
-
/1197
- This would be a subcategory of the previous "top level" category. You can know this detail by making the following request:https://[COMMUNITY DOMAIN]/restapi/vc/categories/uid/1197
-
/1222
- This is the board object. You can know the board object details by making this request:https://[COMMUNITY DOMAIN]/restapi/vc/boards/uid/1222
ATLAS
Comments