Recent changes to Features

Features modified by Uwe Eisele

Uwe Eisele — Sun, 20 Oct 2013 15:38:16 -0000

--- v16
+++ v17
@@ -1 +1 @@
-This page has been migrated to Redmine ().
+This page has been migrated to Redmine ().

Features modified by Uwe Eisele

Uwe Eisele — Sun, 20 Oct 2013 15:37:55 -0000

--- v15
+++ v16
@@ -1,113 +1 @@
-This page summarizes all the features our programm should have.
-
-# Control Panel, Admins
-
->##### Login (Authentication / Authorization)
-1. login
-2. forgot password
-
->##### Members/Users
-1. add (Admin)
-2. delete (admin / the member itself)
-    * no complete deletion
-    * only disallow the person to login
-    * keep person to still have historical information
-3. change -> My profile (admin / the member itself)
-    * Name, contact info, email, password
-    * Activate, de-activate
-    * roles (only if status is active) [Permissions and Roles]
-4. show all members
-    * sorting
-    * filtering
-
->##### Volunteer Group
-1. create
-2. define group manager
-3. add volunteers
-
->##### Locations
-1. Add event location to system (name, address, available places, fees)
-
->##### Band
-1. create (Admin, Planer)
-    * with the minimum information needed;
-2. edit (Admin, Planer)
-2. Bands list view: 
-    * filtering/search
-3. Each band has full detailed view:
-    * Gallery, add, edit photos for the band
-    * Previous and upcoming events events
-    * Contact person/-s 
-    * band members (historical)
-    * genere
-
->##### Events
-1. Create event: -> via defined process
-2. Add Group manager to an event (Planer)
-3. Add volunteers to an event (Group Manager)
-    * All volunteers of a group
-    * Single volunteers
-
-3. edit event (all Planer): (can volunteer also do all this? Or only admin?* Not sure if all volunteers can do so, but if you look at slide 7, you can see that there are multiple people who are working on organizing the band for the event ... so I think for each event there are organizers(if I am aligned organizers=volunteers, if not we should have organizers for the event) those ones do the photos, description, set the costs and so on ... but we have to make sure how that works with JAK *) -> I think creating events is the task of the Planer role
-    * band or bands to the event
-    * event information, dates, place and these information (is it necessary to manage places)
-    * insert all necessary fees (band, place?)
-    * ticket prices
-    * sold tickets
-    * insert discount for members in % and in abs.
-    * add pictures
-    * create a newslettertemplate for all/journalists
-    * invite a contact or a contact group by email to a certain event
-
->4. Maybe: notification sys by email for the upcoming events for ( members, admins, contact groups).
-
->5. show the events:
-    * show the events in a list with filtering/search options.
-    * each event has full detailed single view.
-
->7. During each step show relevant information
-    * when inviting bands show previous fees of the band
-    * show volunteer groups in order of activity
-
->* handle the process of negotiation with management (I guess we don't need to provide feature for negotiation in the system)
-
->##### Contacts? 
-I guess its better to have a module for contacts, which can hold any type of contacts grouped in groups ( individual contact, groups ( journalists or what ever) ... What do you think guys?
-    * contacts: create, delete, edit, asign to contacts group
-    * contact groups:create, delete, edit, show contacts
-    * search contacts: by email, name, active ...
-    * send emails for groups at once,
-    * ! maybe we could assume the News letter as a contact group?
-    
-
->##### Newsletter
-(I would allow a subscriber to add the genere in which he is interessted. When disseminator sends newsletter only the interessted subscribers are informed. For subscribers we only need to store the email, the genres and subscriber type (normal, journalist). Maybe a subscribe can set the type.)
-1. subscribe (confirm per EMail)
-2. unsubscribe
-3. select templates
-4. add templates (only text blocks)
-5. send newsletter to all subscriber
-
->##### Log system, for the admin to see the updates on the DB and who did them:
-1. Logs list, search/ filtering
-
-
-
-# JAK website, for normal users
-
->##### Homepage:
-1. Menu: home, program, Archive, Vorverkauf, news, Gutscheine, Über den JazzClub, Bildergalarie, Service, Anfahrt, Kontakt, Impressum
-2. The home page content
-    * Maybe show some information about the association and the last updates for events, news, upcoming events, gallery ... ?!
-
->##### Events
-1. Events list view, with search/ filtering options.
-2. Each event has full detailed view:
-    * Gallery
-    * some statistics, e.g number of audience
-3. Maybe? Normal users can subscribe to this event by email, to get updates and notification.
-
-
-
->##### Newsletter
-1. subscribe (confirm per EMail), unsubscribe
+This page has been migrated to Redmine ().

Features modified by Uwe Eisele

Uwe Eisele — Tue, 15 Oct 2013 13:56:54 -0000

--- v14
+++ v15
@@ -20,6 +20,14 @@
     * sorting
     * filtering

+>##### Volunteer Group
+1. create
+2. define group manager
+3. add volunteers
+
+>##### Locations
+1. Add event location to system (name, address, available places, fees)
+
 >##### Band
 1. create (Admin, Planer)
     * with the minimum information needed;
@@ -31,12 +39,16 @@
     * Previous and upcoming events events
     * Contact person/-s 
     * band members (historical)
-    * genere (for newsletter -> send only to interessted persons)
+    * genere

 >##### Events
-1. Create event: who can do this? the planner? admin maybe? What is the minimum amount of information needed to create a band?
-2. Add volunteers (only active members) / add a group of volunteers
-3. the creator and the volunteers can add, edit: (can volunteer also do all this? Or only admin?* Not sure if all volunteers can do so, but if you look at slide 7, you can see that there are multiple people who are working on organizing the band for the event ... so I think for each event there are organizers(if I am aligned organizers=volunteers, if not we should have organizers for the event) those ones do the photos, description, set the costs and so on ... but we have to make sure how that works with JAK *) -> I think creating events is the task of the Planer role
+1. Create event: -> via defined process
+2. Add Group manager to an event (Planer)
+3. Add volunteers to an event (Group Manager)
+    * All volunteers of a group
+    * Single volunteers
+
+3. edit event (all Planer): (can volunteer also do all this? Or only admin?* Not sure if all volunteers can do so, but if you look at slide 7, you can see that there are multiple people who are working on organizing the band for the event ... so I think for each event there are organizers(if I am aligned organizers=volunteers, if not we should have organizers for the event) those ones do the photos, description, set the costs and so on ... but we have to make sure how that works with JAK *) -> I think creating events is the task of the Planer role
     * band or bands to the event
     * event information, dates, place and these information (is it necessary to manage places)
     * insert all necessary fees (band, place?)
@@ -53,33 +65,11 @@
     * show the events in a list with filtering/search options.
     * each event has full detailed single view.

->6. Event creation process
-    * Guide the planer through the creation process (store status)
-        1. define date / event information / available tickets
-        2. set event location
-        3. add group of volunteers
-        3. invite bands / negotiate fees
-        4. define ticket price / discount for members
-        5. publish event
-    * Guide the disseminator (gets information when planer has created an event)
-        1. create newsletter message and send to subscribers
-        2. announce event (not coverd by application)
-        3. add pictures after event (via web and smartphone)
-    * During presale set amount of sold tickets (who can do that?)
-
 >7. During each step show relevant information
     * when inviting bands show previous fees of the band
     * show volunteer groups in order of activity

 >* handle the process of negotiation with management (I guess we don't need to provide feature for negotiation in the system)
-
->##### News? should we add news module to the website? that the normal users can see them on the website
-1. Add, edit
-2. News List view with filtering/ search 
-3. Send news to a group of contacts or to the news letter
-
-
-

 >##### Contacts? 
 I guess its better to have a module for contacts, which can hold any type of contacts grouped in groups ( individual contact, groups ( journalists or what ever) ... What do you think guys?
@@ -98,14 +88,6 @@
 4. add templates (only text blocks)
 5. send newsletter to all subscriber

->##### Locations
-1. Add event location to system (name, address, available places, fees)
-
->##### Volunteer group
-1. create
-2. define group manager
-3. add volunteers
-
 >##### Log system, for the admin to see the updates on the DB and who did them:
 1. Logs list, search/ filtering

@@ -118,10 +100,6 @@
 2. The home page content
     * Maybe show some information about the association and the last updates for events, news, upcoming events, gallery ... ?!

->##### News:
-1. News list view, search/filtering options
-2. Each news has full view
-
 >##### Events
 1. Events list view, with search/ filtering options.
 2. Each event has full detailed view:

Features modified by Uwe Eisele

Uwe Eisele — Tue, 15 Oct 2013 12:04:13 -0000

--- v13
+++ v14
@@ -2,9 +2,36 @@

 # Control Panel, Admins

->##### My Profile, the logged in member
-1. update: Name, contact info, email, password
-2. Activate, de-activate
+>##### Login (Authentication / Authorization)
+1. login
+2. forgot password
+
+>##### Members/Users
+1. add (Admin)
+2. delete (admin / the member itself)
+    * no complete deletion
+    * only disallow the person to login
+    * keep person to still have historical information
+3. change -> My profile (admin / the member itself)
+    * Name, contact info, email, password
+    * Activate, de-activate
+    * roles (only if status is active) [Permissions and Roles]
+4. show all members
+    * sorting
+    * filtering
+
+>##### Band
+1. create (Admin, Planer)
+    * with the minimum information needed;
+2. edit (Admin, Planer)
+2. Bands list view: 
+    * filtering/search
+3. Each band has full detailed view:
+    * Gallery, add, edit photos for the band
+    * Previous and upcoming events events
+    * Contact person/-s 
+    * band members (historical)
+    * genere (for newsletter -> send only to interessted persons)

 >##### Events
 1. Create event: who can do this? the planner? admin maybe? What is the minimum amount of information needed to create a band?
@@ -52,24 +79,7 @@
 3. Send news to a group of contacts or to the news letter

->##### Band
-1. create, edit : with the minimum information needed;
-2. Bands list view: filtering/search
-3. Each band has full detailed view:
-    * Gallery, add, edit photos for the band
-    * Previous and upcoming events events
-    * Contact person/-s 
-    * band members (historical)
-    * genere (for newsletter -> send only to interessted persons)

-
->##### Members
-1. add
-* delete (?)
-* change 
-    * personal data
-    * status
-    * roles (only if status is active)

 >##### Contacts? 
 I guess its better to have a module for contacts, which can hold any type of contacts grouped in groups ( individual contact, groups ( journalists or what ever) ... What do you think guys?

Features modified by Uwe Eisele

Uwe Eisele — Sun, 13 Oct 2013 19:24:48 -0000

--- v12
+++ v13
@@ -27,22 +27,22 @@
     * each event has full detailed single view.

 >6. Event creation process
-- Guide the planer through the creation process (store status)
-1. define date / event information / available tickets
-2. set event location
-3. add group of volunteers
-3. invite bands / negotiate fees
-4. define ticket price / discount for members
-5. publish event
-- Guide the disseminator (gets information when planer has created an event)
-1. create newsletter message and send to subscribers
-2. announce event (not coverd by application)
-3. add pictures after event (via web and smartphone)
-- During presale set amount of sold tickets (who can do that?)
+    * Guide the planer through the creation process (store status)
+        1. define date / event information / available tickets
+        2. set event location
+        3. add group of volunteers
+        3. invite bands / negotiate fees
+        4. define ticket price / discount for members
+        5. publish event
+    * Guide the disseminator (gets information when planer has created an event)
+        1. create newsletter message and send to subscribers
+        2. announce event (not coverd by application)
+        3. add pictures after event (via web and smartphone)
+    * During presale set amount of sold tickets (who can do that?)

 >7. During each step show relevant information
-- when inviting bands show previous fees of the band
-- show volunteer groups in order of activity
+    * when inviting bands show previous fees of the band
+    * show volunteer groups in order of activity

 >* handle the process of negotiation with management (I guess we don't need to provide feature for negotiation in the system)

@@ -71,35 +71,33 @@
     * status
     * roles (only if status is active)

->##### Contacts? I guess its better to have a module for contacts, which can hold any type of contacts grouped in groups ( individual contact, groups ( journalists or what ever) ... What do you think guys?
+>##### Contacts? 
+I guess its better to have a module for contacts, which can hold any type of contacts grouped in groups ( individual contact, groups ( journalists or what ever) ... What do you think guys?
     * contacts: create, delete, edit, asign to contacts group
     * contact groups:create, delete, edit, show contacts
     * search contacts: by email, name, active ...
     * send emails for groups at once,
-    ! maybe we could assume the News letter as a contact group?
+    * ! maybe we could assume the News letter as a contact group?

 >##### Newsletter
+(I would allow a subscriber to add the genere in which he is interessted. When disseminator sends newsletter only the interessted subscribers are informed. For subscribers we only need to store the email, the genres and subscriber type (normal, journalist). Maybe a subscribe can set the type.)
 1. subscribe (confirm per EMail)
-* unsubscribe
-* select templates
-* add templates (only text blocks)
-* send newsletter to all subscriber
-(I would allow a subscriber to add the genere in which he is interessted. When disseminator sends newsletter only the interessted subscribers are informed. For subscribers we only need to store the email, the genres and subscriber type (normal, journalist). Maybe a subscribe can set the type.)
+2. unsubscribe
+3. select templates
+4. add templates (only text blocks)
+5. send newsletter to all subscriber

 >##### Locations
-- Add event location to system (name, address, available places, fees)
+1. Add event location to system (name, address, available places, fees)

 >##### Volunteer group
-- create
-- define group manager
-- add volunteers
+1. create
+2. define group manager
+3. add volunteers

 >##### Log system, for the admin to see the updates on the DB and who did them:
 1. Logs list, search/ filtering
-
-
-

Features modified by Uwe Eisele

Uwe Eisele — Sun, 13 Oct 2013 19:17:15 -0000

--- v11
+++ v12
@@ -8,10 +8,10 @@

 >##### Events
 1. Create event: who can do this? the planner? admin maybe? What is the minimum amount of information needed to create a band?
-2. Add volunteers (only active members)
-3. the creator and the volunteers can add, edit: (can volunteer also do all this? Or only admin?* Not sure if all volunteers can do so, but if you look at slide 7, you can see that there are multiple people who are working on organizing the band for the event ... so I think for each event there are organizers(if I am aligned organizers=volunteers, if not we should have organizers for the event) those ones do the photos, description, set the costs and so on ... but we have to make sure how that works with JAK *)
+2. Add volunteers (only active members) / add a group of volunteers
+3. the creator and the volunteers can add, edit: (can volunteer also do all this? Or only admin?* Not sure if all volunteers can do so, but if you look at slide 7, you can see that there are multiple people who are working on organizing the band for the event ... so I think for each event there are organizers(if I am aligned organizers=volunteers, if not we should have organizers for the event) those ones do the photos, description, set the costs and so on ... but we have to make sure how that works with JAK *) -> I think creating events is the task of the Planer role
     * band or bands to the event
-    * event information, dates, place and these information
+    * event information, dates, place and these information (is it necessary to manage places)
     * insert all necessary fees (band, place?)
     * ticket prices
     * sold tickets
@@ -25,6 +25,24 @@
 >5. show the events:
     * show the events in a list with filtering/search options.
     * each event has full detailed single view.
+
+>6. Event creation process
+- Guide the planer through the creation process (store status)
+1. define date / event information / available tickets
+2. set event location
+3. add group of volunteers
+3. invite bands / negotiate fees
+4. define ticket price / discount for members
+5. publish event
+- Guide the disseminator (gets information when planer has created an event)
+1. create newsletter message and send to subscribers
+2. announce event (not coverd by application)
+3. add pictures after event (via web and smartphone)
+- During presale set amount of sold tickets (who can do that?)
+
+>7. During each step show relevant information
+- when inviting bands show previous fees of the band
+- show volunteer groups in order of activity

 >* handle the process of negotiation with management (I guess we don't need to provide feature for negotiation in the system)

@@ -41,6 +59,8 @@
     * Gallery, add, edit photos for the band
     * Previous and upcoming events events
     * Contact person/-s 
+    * band members (historical)
+    * genere (for newsletter -> send only to interessted persons)

 >##### Members
@@ -63,8 +83,17 @@
 1. subscribe (confirm per EMail)
 * unsubscribe
 * select templates
+* add templates (only text blocks)
 * send newsletter to all subscriber
+(I would allow a subscriber to add the genere in which he is interessted. When disseminator sends newsletter only the interessted subscribers are informed. For subscribers we only need to store the email, the genres and subscriber type (normal, journalist). Maybe a subscribe can set the type.)

+>##### Locations
+- Add event location to system (name, address, available places, fees)
+
+>##### Volunteer group
+- create
+- define group manager
+- add volunteers

 >##### Log system, for the admin to see the updates on the DB and who did them:
 1. Logs list, search/ filtering

Features modified by Qusai Jouda

Qusai Jouda — Thu, 10 Oct 2013 13:16:18 -0000

--- v10
+++ v11
@@ -9,7 +9,7 @@
 >##### Events
 1. Create event: who can do this? the planner? admin maybe? What is the minimum amount of information needed to create a band?
 2. Add volunteers (only active members)
-3. the creator and the volunteers can add, edit: (can volunteer also do all this? Or only admin?)
+3. the creator and the volunteers can add, edit: (can volunteer also do all this? Or only admin?* Not sure if all volunteers can do so, but if you look at slide 7, you can see that there are multiple people who are working on organizing the band for the event ... so I think for each event there are organizers(if I am aligned organizers=volunteers, if not we should have organizers for the event) those ones do the photos, description, set the costs and so on ... but we have to make sure how that works with JAK *)
     * band or bands to the event
     * event information, dates, place and these information
     * insert all necessary fees (band, place?)

Features modified by Alla Shapira

Alla Shapira — Thu, 10 Oct 2013 12:37:42 -0000

--- v9
+++ v10
@@ -9,7 +9,7 @@
 >##### Events
 1. Create event: who can do this? the planner? admin maybe? What is the minimum amount of information needed to create a band?
 2. Add volunteers (only active members)
-3. the creator and the volunteers can add, edit:
+3. the creator and the volunteers can add, edit: (can volunteer also do all this? Or only admin?)
     * band or bands to the event
     * event information, dates, place and these information
     * insert all necessary fees (band, place?)

Features modified by Qusai Jouda

Qusai Jouda — Thu, 10 Oct 2013 10:22:01 -0000

--- v8
+++ v9
@@ -74,7 +74,7 @@

-# JAZ website, for normal users
+# JAK website, for normal users

 >##### Homepage:
 1. Menu: home, program, Archive, Vorverkauf, news, Gutscheine, Über den JazzClub, Bildergalarie, Service, Anfahrt, Kontakt, Impressum

Features modified by Qusai Jouda

Qusai Jouda — Thu, 10 Oct 2013 10:18:41 -0000

--- v7
+++ v8
@@ -1,6 +1,10 @@
 This page summarizes all the features our programm should have.

 # Control Panel, Admins
+
+>##### My Profile, the logged in member
+1. update: Name, contact info, email, password
+2. Activate, de-activate

 >##### Events
 1. Create event: who can do this? the planner? admin maybe? What is the minimum amount of information needed to create a band?