This repository has been archived by the owner on Oct 31, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathREADME.txt
151 lines (114 loc) · 5.22 KB
/
README.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
This project was created by Yale University.
The current Sign-up tool is a beta version.
Section A: Installation
-----------------------
The Sign-up Tool is integrated into Sakai and it is not a standalone application.
The source code of the Sign-up Tool can be placed in your Sakai source tree and built
using Maven. If unfamiliar with installation of Sakai, please check the following links
for installation documentation of Sakai application:
Sakai 2.4
http://source.sakaiproject.org/release/2.4.0/
Sakai 2.5
http://confluence.sakaiproject.org/confluence/display/DOC/Install+Guide+(2.5)
sakai 2.6
http://confluence.sakaiproject.org/display/DOC/Install+Guide+(2.6)
Compatibility:
The Sign-up tool is currently compatible with Sakai versions from 2.4 to 2.6. Appropriate build
files are provided for both Maven 1 and Maven 2.
Requirements to run Sign-up tool:
Sakai 2.4 or higher.
Java JDK 1.5 version or higher.
Tomcat 5.5.20 version or higher.
For the initial creation of the Sign-up tool database tables, an Oracle/mySQL SQL scripts is available
at the folder of Sign-up tool’s source code:
sign-up\resources
If a MySQL Database is used, turn on the auto.ddl property value from false to true in the
sakai.properties (Production level is not recommended and should use db-scripts).
Customize the UI and Email Contents:
You could customize the UI labels and email message contents by modifying the following two
property files:
emailMessage.properties
messages.properties
Section B: Permission Setup
---------------------------
Permission levels
The following 13 permission levels have been defined to satisfy the various requirements:
*Create
a)signup.create.site - create events/meetings open to all site participants
b)signup.create.group - create events/meetings for the own group(s)
c)signup.create.group.all - create events/meetings for any/all groups in the site
*Delete
a)signup.delete.site - delete any site-wide event/meeting
b)signup.delete.group - delete any event/meeting of the own group(s)
c)signup.delete.group.all - delete any group event/meeting in the site
*Update
a)signup.update.site - update or edit any site-wide event/meeting
b)Signup.update.group - update or edit events/meetings of the own group(s)
c)signup.update.group.all - update or edit events/meetings for any group in the site
*Attend
a)signup.attend - attend (sign up) group level event/meeting if they are member of the group
and site level event/meeting if they are member of the site
b)signup.attend.all - attend (sign up) any event/meeting in the site and its groups
*View
a)signup.view - view group level events/meetings if they are member of the group or
site level events/meetings if they are member of the site
b)signup.view.all - view any event/meeting in the site and its groups
Example of Permission Setup
Roles can be assigned a combination of the above permissions. Here are suggested settings:
*Instructor
-signup.create.site
-signup.delete.site
-signup.update.site
-signup.view
-signup.view.all
*Teaching Assistant(TF)
-signup.create.group or signup.create.group.all
-signup.delete.group or signup.delete.group.all
-signup.update.group or signup.update.group.all
-signup.attend.all
-signup.view
-signup.view.all
*Student
-signup.attend
-signup.view
*Guest
-signup.view or signup.view.all
*Auditor
-signup.attend
-signup.view
*Study-Group Organizer Role (student)
-signup.create.group
-signup.delete.group
-signup.update.group
-signup.view
-signup.attend
*Maintain
-signup.create.site
-signup.delete.site
-signup.update.site
-signup.view
-signup.view.all
*Access
-signup.attend
-signup.view
*Important: The signup.view permission is required to use the tool.
Here is the summary of the possible permission settings for the corresponding roles:
---------------------------------------------------------------------------------------------------------------
Permissions Instructor TF Student Auditor Guest Maintain Access
---------------------------------------------------------------------------------------------------------------
signup.create.group X
signup.create.group.all (or X)
signup.create.site X X
signup.delete.group X
signup.delete.group.all (or X)
signup.delete.site X X
signup.update.group X
signup.update.group.all (or X)
signup.update.site X X
signup.attend X X X
signup.attend.all X
signup.view X X X X
signup.view.all X X (X) X
----------------------------------------------------------------------------------------------------------------
*Note: It is a good idea to set these permissions for the !site.template and !group.template.course
so they will be inherited in any new created sites or groups.