John Layt: Replaced content with "= Model ="

2018-01-25T11:14:18Z

Replaced content with "= Model ="

John Layt: Created page with "= Model = === Site Module === A new core module for Sites will be added to support recording of metadata about a site. The data schema will be configurable the same as other..."

2016-10-30T15:14:56Z

Created page with "= Model = === Site Module === A new core module for Sites will be added to support recording of metadata about a site. The data schema will be configurable the same as other..."

New page

= Model =

=== Site Module ===

A new core module for Sites will be added to support recording of metadata about a site. The data schema will be configurable the same as other modules, but certain default fields will be enforced. This will be a special case module that does not appear in the modules for a site.

=== Address Book / Actors / Users ===

Currently actors are allocated at a site level. This may not scale very well to a major corporate install, for example LP or WCC, with a staff of 30-50 and hundreds of sites. Repeatedly allocating new actor IDs for each site could result in a user possibly having hundreds of actor IDs which could make reporting harder, site creation more effort, and is not very RESTful.

It is proposed instead to to rename the Address Book module as the Actors module and add a new global level of actors in addition to site-specific actors. Users will be in the global list, and allocated to sites with roles. Choice can be made between global level roles across all sites, or site specific roles. Non-user global actors can also be defined, can be referred to without allocation. Local site actors can be created.

It is also proposed to have the Actors module be the only source of actors for the Action dataclass, simplifying the storage and access.

← Older revision		Revision as of 11:14, 25 January 2018
Line 1:		Line 1:
	= Model =		= Model =
−
−	~~=== Site Module ===~~
−
−	A new core module for Sites will be added to support recording of metadata about a site. The data schema will be configurable the same as other modules, but certain default fields will be enforced. This will be a special case module that does not appear in the modules for a site.
−
−	~~=== Address Book / Actors / Users ===~~
−
−	Currently actors are allocated at a site level. This may not scale very well to a major corporate install, for example LP or WCC, with a staff of 30-50 and hundreds of sites. Repeatedly allocating new actor IDs for each site could result in a user possibly having hundreds of actor IDs which could make reporting harder, site creation more effort, and is not very RESTful.
−
−	It is proposed instead to to rename the Address Book module as the Actors module and add a new global level of actors in addition to site-specific actors. Users will be in the global list, and allocated to sites with roles. Choice can be made between global level roles across all sites, or site specific roles. Non-user global actors can also be defined, can be referred to without allocation. Local site actors can be created.
−
−	~~It is also proposed to have the Actors module be the only source of actors for the Action dataclass, simplifying the storage and access.~~

ARK2/Model - Revision history

John Layt: Replaced content with "= Model ="

John Layt: Created page with "= Model = === Site Module === A new core module for Sites will be added to support recording of metadata about a site. The data schema will be configurable the same as other..."