#13 Implementation of channels

[Mirco Gatz]

Specify and implement the channel feature.

!!!Before creating the channels Statuses must be usable!!!

After we discussed the required fields for a channel this is the result

Required fields (not mentioned are the default persistant object fields):

• ChannelId (unique)
• Name (to display, localizable right after localization is implemented)
• Description
• ParentUUID
• StatusUUID (allowed / possible statuses are to be discussed)

Please create:

• SQL-Script for structure (including the tables and the "root"-channel with has to be there and is therefore no demo content)
• POJO (consider using the extensible object base class -> remember creating the table for the extension)
• Manager
• Controller and Views for CRUD (very basic)

Channel feature description

• a channel has at least a name and a default locale (more attributes have to be defined)
• channels have one root channel that contains a admin user which is necessary and allows managing all the other channels
• a user login always requires a channel
• access rights are always granted on a per channel base but can be inherited from parent to child channel
• a channel always has a parent (except the root channel)
• channels can have multiple child channels
• child channels can define if they use the parents data objects or if they have their own scope
• the data created by a channel is available in the channels scope or in its childs scopes if they use the parents data
• every persistent object must directly belong to a channel or it must be related to exactly one object that belongs to a channel (the related object could also be related to a channel belonging object instead of belonging to one itself and so on)

[Mirco Gatz]

• Description has changed:

Diff:

--- old
+++ new
@@ -10,5 +10,4 @@
 * channels can have multiple child channels
 * child channels can define if they use the parents data objects or if they have their own scope
 * the data created by a channel is available in the channels scope or in its childs scopes if they use the parents data
-* a child channel cannot manipulate its parents data (shared or not)
 * every persistent object must directly belong to a channel or it must be related to exactly one object that belongs to a channel (the related object could also be related to a channel belonging object instead of belonging to one itself and so on)

[Mirco Gatz]

provide some screens

[Mirco Gatz]

Moved to milestone 0.3 because channels are a core function

[Mirco Gatz]

• Description has changed:

Diff:

--- old
+++ new
@@ -1,6 +1,30 @@
 Specify and implement the channel feature.
+==============================

-**Channels:**
+!!!Before creating the channels Statuses must be usable!!!
+==============================
+
+After we discussed the required fields for a channel this is the result
+------------------------------
+
+**Required fields (not mentioned are the default persistant object fields):**
+
+* ChannelId (unique)
+* Name (to display, localizable right after localization is implemented)
+* Description
+* ParentUUID
+* StatusUUID (allowed / possible statuses are to be discussed)
+
+**Please create:**
+
+* SQL-Script for structure (including the tables and the "root"-channel with has to be there and is therefore no demo content)
+* POJO (consider using the extensible object base class -> remember creating the table for the extension)
+* Manager
+* Controller and Views for CRUD (very basic)
+
+
+Channel feature description
+-----------------------------

 * a channel has at least a name and a default locale (more attributes have to be defined)
 * channels have one root channel that contains a admin user which is necessary and allows managing all the other channels