# Data model-oriented view of the architecture
According to the Feathers philosophy (opens new window) each data model is manipulated using a service interface (opens new window) to perform CRUD operations (opens new window) of the persistence layer (opens new window). So this data model-oriented view is a service-oriented view in the same manner.
Because data models internally rely on JSON (opens new window) they are by nature hierarchical. In the following diagrams each nested JSON object is represented as a smaller bubble in a bigger bubble (the nesting/parent object), the data model instance being the root JSON object or the biggest bubble. The name of the bubble is the name of the nesting object property owing the nested object.
Data models are dynamic by nature, allowing any plugin to add custom fields whenever required using hooks (opens new window). Each data model includes an implicit ObjectID (opens new window) _id field provided by the database.
# User data model
The most common properties of a user are described by the following data model:
The details of each property are the following:
- email : user e-mail used as an internal unique ID
- password : hashed user password
- locale : user locale when registering
- previousPasswords : hashed user password history if password policy has been enabled
- profile : user profile information including name
- [provider] : user profile information for associated OAuth provider, e.g.
google - [scope] : user permissions for associated scope, e.g.
groups - tags : user affected tags if any
- devices : user mobile devices if any, each time the user uses a new device it is registered
# Device data model
The most common properties of a device object are described by the following data model:
TODO
This data model is manipulated through the Device API.
The details of each property are the following:
- platform: the platform of the device, e.g.
Android - model: the model of the device, e.g.
SM-G930U - manufacturer: the manufacturer of the device, e.g.
samsung - uuid: UUID of the device
- registrationId: the ID of the associated device in the notification system (APNS or Firebase)
- arn: the ARN of associated SNS device
- lastActivity: the date/time of the last connection of this device
Most data are retrieved using the cordova-plugin-device (opens new window).
# Tag data model
The most common properties of a tag object are described by the following data model:
TODO
This data model is manipulated through the Tag API.
The details of each property are the following:
- scope: the scope of the tag (i.e. category), e.g.
skill - value: the value of the tag, e.g.
developer - count: the number of tagged objects
- context: the ID of the associated context object providing this tag if any (e.g. the organisation)
- topics: the ARN of associated SNS topics for each platform used to publish messages to tagged objects, used by the pusher service
# Organization data model
The most common properties of an organization are described by the following data model:
This data model is manipulated through the organizations service.
The details of each property are the following:
- name: the name of the organisation
- topics: the ARN of associated SNS topics for each platform used to publish messages to organization' members, used by the pusher service
the organization ObjectID is used as the internal DB name
# Group data model
The most common properties of a group object are described by the following data model:
This data model is manipulated through the groups service.
The details of each property are the following:
- name: the name of the group
- description: the description of the group
- topics: the ARN of associated SNS topics for each platform used to publish messages to group' members, used by pusher service