Flatten the current model
To manage permissions easily, and according to the advices of the interop spec team, the more flat the data are organized in POD, the easiest it is to handle permissions.
Here is the current structure:
User
-
user/
: All the informations about the user online identity (name, address...) -
── account
: Additionnal informations about the user (email, password...) -
── communities
: List of the communities the user is in -
── membership-X
: Membership informations of the user in a project
Organization
-
community/
: Community of the organization -
── circles
: List of circles of the community -
── jobPostings
: List of job postings of the community -
── members
: List of members of the community -
── projects
: List of projects of the community -
circle/
: Circle of the organization -
── membership-X
: Information about a membership of the circle -
── threads/
: Discussions about the circle -
──── thread-X
: Details of a discussion -
── communities
: Communities the circle is member of -
project/
: Project of the organization -
── contactPerson
: Informations about the contact person of the project -
── businessProvision
: Informations about the business provision of the project -
── threads/
: Discussions about the projects -
──── thread-X
: Details of a discussion -
── invoices/
: Invoices of the project -
──── invoice-X
: Details of an invoice -
── communities
: Communities the project is member of -
jobPosting/
: Job posting of the organization -
── threads/
: Discussions about the job posting -
──── thread-X
: Details of a discussion -
── communities
: Communities the job posting is member of -
customer
: Customers of the organization
We should go for a more flat structure and update shapes and shapeTrees accordingly