aboutsummaryrefslogtreecommitdiff
path: root/db/schema.rb
Commit message (Collapse)AuthorAgeFilesLines
* Add model foundation for classificationshellekin2020-10-081-1/+43
| | | | | | | | Taxonomy > Category > Section This commit adds models for it. https://doc.incommon.cc/#classifications
* Fix resources migrationhellekin2020-10-061-0/+4
| | | | | | | t.references already creates an index, so the second index actually broke things. You may need to rebuild the database!
* Add Resource modelhellekin2020-10-061-1/+9
| | | | | | Resources will be stored as JSON, in the (GeoJSON) :feature column. They are assigned an UUID upon creation if they don't comme with one. They belong to an Agent.
* Add Agent and Agency modelshellekin2020-10-051-1/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since IN COMMON is about collective management of data we're using the concept of Agent to describe a group of users acting together. In ActivityPub terms, Agent will be the Actor when manipulating data, so that any individual User (or application) member of this Agent will be able to manipulate data on behalf of this Agent. Therefore a User has many Agencies, and an Agent as well: the Agency model allows not only to create a joint table between Agents and Users, but also to manage User roles within the related Agent. Roles are defined as: - observer: one who can read and review or flag data - editor: one who create or edit data - maintainer: one who can edit data and manage maps - leader: one who can manage roles A User may have zero or more roles in an Agent. A User without a Agency record for a specific Agent will only be able to 'observe' public data from this Agent. (Note that this is not currently specified, but matches existing reflection on Agents) https://doc.incommon.cc/#agents
* Create database setuphellekin2020-10-051-0/+18