Data model-oriented view of the architecture

According to the Feathers philosophy each data model is manipulated using a service interface to perform CRUD operations of the persistence layer. So this data model-oriented view is a service-oriented view in the same manner.

Because data models internally rely on JSON 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. Each data model includes an implicit ObjectID _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
• subscriptions : user web push subscriptions if any

Subscription data model

As per feathers-webpush, subscriptions are attached to users through the subscriptions property.

Notification data model

As per feathers-webpush, notifications are sent according to subscriptions are attached to users.

This data model is manipulated through the push service.

Tag data model

The most common properties of a tag object are described by the following data model:

This data model is manipulated through the tag service.

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
• icon: the icon specification for this tag if any
• context: the ID of the associated context object providing this tag if any (e.g. the organisation)

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
• description: the description of the organisation

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