The axis-section resource
Introduction
In some application contexts, resources can be attached to analytical items. In most cases, the goal is to answer the needs of cost accounting. Axes are primarily used by Timmi Timesheet & Cleemy Expenses.
Both in Timmi Timesheet and Cleemy Expense, users can enter their working hours or expenses spent on projects, tasks, work sites, cost centers, etc… These are the AxisSection[]
, categorized in Axis[]
. These axes can have parent-children relationships, and their axis-sections as well.
Example
Let’s take an example. Say you expect your users to enter spent working hours on each project. Each project belongs to a single client, and is divided into tasks.
In other words:
- Clients
- (1..n) Projects: each project belongs to one, and one only, client.
- (n..n) Tasks: each task belongs to one or more project(s).
Then:
- Each client is an
AxisSection
in the “Clients”Axis
. - One client has zero or more projects, which are
AxisSection[]
in the “Projects”Axis
. A project is child to one and only one client. - One project has zero or more tasks, which are
AxisSection[]
in the “Tasks”Axis
. Each task axis-section is child to one or more project(s) axis-sections.
The JSON representation of these axes in the API would be:
Regarding axis-sections:
x > 1
Was this page helpful?