Handling Subscriptions & Account Hierarchies

Handling Accounts Hierarchies

The only data requested is a 2 columns file indicating each parent-child relation
Hierarchies management allow for a node to have multiple parents & multiple children.
It works as many n-levels hierarchy.

Squid Solutions will handle a differential process to tag the lifetime of every hierarchy branch. This is to ensure a correct reporting of hierarchies & 0 usage along the reporting period selected.

Handling Subscriptions

You must provide also all databases subscribed by accounts.
By default all children are inheriting content owned by the owner, through their subscriptions.
But you can manage suspensions & exclusions:

• Suspension is at global level: the whole subscription access is temporarily removed across the full hierarchy

• Exclusion is at a child level: the subscription's content isn't granted to this particular child (& only this one, not his children if any)
  Squid Solutions will handle a differential process to tag the lifetime of every subscription. This is to ensure a correct reporting of 0 usage along the reporting period selected.

Working with Subscriptions & Hierarchies

The hierarchy also allows to select and sum up usage at the reporting level of your choice with the help of 3 selections:

• Parent Account: Node from which the content is granted (content owned or inherited)

• Account: Reporting node onto which the content will be counted.

• Child Account: Node from which the content usage is counted (user of the content, or parent user of the content)

Let's illustrate that with an example or a hierarchy & subscriptions:

In orange, these accounts pay for some database subscriptions. Accounts in blue are not paying for anything. Also color links help identifying a path
For example,

• Account D inherit database 1 from A & database 2 from parent C

• Only account G can see DB4 but inherit database 1 from parents A or B and database 2 from parent C
  With the hierarchy logic implemented in the Counter App, by:

• Selecting a parent you restrict the databases to the ones owned by him or its parents

• Selecting a child you restrict the usage to him or its children

• Selecting the account you want to rollup corresponding usage at this level

In the example above we want to report usage of child E & grandchild G into account C only if content is provided by parent A. So we will only count DB1 content usage if it being paid by parent A (if it comes from parent B, it will not be counted).

If you select parent = account = child, you count any content provided by the account or his parents, across all children of the account, including himself. This allow for example to view usage at Consortium level, including all children but also rollup at any level, to view usage at a sub level but only on one path by selecting the correct parent to handle properly 0 usage & databases exclusions (like for account F) Include /exclude children according to the time they join/leave the hierarchy.

---