Last modified by Vincent Massol on 2024/11/19 16:12

Show last authors
1 Groups (1.5) Data Model
2
3 This document is meant to specify the groups data model when complete.
4
5 Needed items:
6
7 1. Group definition
8
9 2. Member list 3. Member profile for group 4. Member roles (and rights) 5. Request queue 6. Resources need to know about group ownership
10
11 1. Group definition
12 1. Display Name
13 1. Use the title of the group page
14
15 2. Description 3. URL shortcut 4. Membership policy (open/closed) 5. Language (2 character ISO value stored) 6. Default licence policy 7. Default access privileges 8. Topic (missing from spec text) Joshua, are these the same as current topic tree in users profile? -Todd Sherman 11/26/07 1:50 PM Yes. -David Ward 11/26/07 2:17 PM
16
17 9. Educational level (missing from spec text) Joshua, are these the same as in the curent users profile? -Todd Sherman 11/26/07 1:51 PM Yes. -David Ward 11/26/07 2:18 PM
18
19 10. Welcome message for group
20
21 1. This would probably be a separate object on the WebHome page Joshua thinks that this should be a wiki page on it's own. -David Ward 11/26/07 3:00 PM
22
23 {{html clean="false" wiki="true"}}
24 For the space used, I am currently assuming Group_<groupname> Determined that this is what will be used. -David Ward 11/26/07 2:57 PM
25 where the WebHome page contains the object containing the defining attributes.
26 <p/>
27 2. Member list
28 I am assuming that this will just be a normal Group list (named Group_<groupname>.Membership ?) to allow for dealing with privileges.
29 <p/>
30 3. Member profile for group
31
32 1. Role
33 1. This can possibly be just derived from the member roles groups.
34 <p/>
35 2. Using Group_<groupname>.Role_<rolename> group?
36 2. Allow email attribute - Ludovic to respond 11/27
37 3. Notify attribute - Ludovic to respond 11/27
38 4. Biography - Ludovic to respond 11/27
39 <p/>
40 I am not sure if this is better as an object (with group specified) on the user page, or if it would be better on separate pages (Group_<groupname>.Member_<user>), or even as multiple objects on one page (Group_<groupname>.Membership) in order to be able to query for the information easily in both the Group and the "My Curriki" sections of the site, and not get unwieldy data structures that can't easily be maintained.
41 <p/>
42 5. Active - Admins can "Remove from Group" any member. This removes / deletes the user. No banning. Admin alerts Curriki.
43 <p/>
44 4. Member roles
45 I am assuming that this will be normal Groups (named Group_<groupname>.Role_<rolename>) to allow for dealing with privileges.
46 <p/>
47 5. Request queue
48
49 1. Member requesting
50 <p/>
51 2. Role requested
52 3. Informational text
53 <p/>
54 This will probably be best as a set of objects on one page (Group_<groupname>.MembershipRequests) unless there will be a better API available shortly.
55 <p/>
56 6. Resources need to know about group ownership
57 At what points do we need to deal with group ownership of resources? Joshua, if a group is private, then all the resources would be private too? Same questions for hide from search. Need your logic and usage help here. -Todd Sherman 11/26/07 2:09 PM No, resources and groups have separate rights settings. This does need to be better defined if we want something other than what the defaults would be. -David Ward 11/26/07 2:19 PM
58 <p/>
59 We can use the location space (similar to what we have for users) (being Coll_Group_<groupname>) as one method to know when an item is from a group collection and display appropriate information when that is the case. Joshua and David, I suppose it could also be, Coll_<loginname>_<groupname>. So does a contribution belong to the individual and then the group or group then the individual. Search results are based on individuals or groups or both?. -Todd Sherman 11/26/07 2:02 PM No, this is the group SPACE (probably needs to be the same for the entire group), nothing to do directly with ownership. -David Ward 11/26/07 2:22 PMColl_Group_<groupname> -Todd Sherman 11/26/07 2:56 PM
60
61 {{/html}}

Get Connected