version 1.2, 2011/05/23 20:29:28
|
version 1.3, 2014/06/26 15:07:10
|
Line 11 used to explicitly set availability of t
|
Line 11 used to explicitly set availability of t
|
that will override the corresponding settings determined by the user's |
that will override the corresponding settings determined by the user's |
affiliation. |
affiliation. |
|
|
If you choose to enable portfolios, default quotas (in Mb) |
If you choose to enable portfolios, default quotas (in MB) |
can similarly be set to vary by institutional affiliation. |
can similarly be set to vary by institutional affiliation. |
If a user is affiliated with more than one group, whichever default |
If a user is affiliated with more than one group, whichever default |
quota is largest for the different groups is the one which applies. |
quota is largest for the different groups is the one which applies. |
Institutional types need to be defined in a customized version of |
Institutional types are defined in the ``Institutional user types'' |
\&inst\_usertypes() in the localenroll.pm module installed on the |
section on the ``Default authentication/language/timezone/portal/types'' |
primary server in your domain. If no types have been defined, then |
screen. If no types have been defined, then a single default quota |
a single default quota will apply for all users from the domain. |
will apply for all users from the domain. |
|
|
Default portfolio quotas which can be set for users in your domain |
Default portfolio quotas which can be set for users in your domain |
will be overridden by any quota you set for an individual user via: |
will be overridden by any quota you set for an individual user via: |
the ``Modify User'' utility. |
the ``Modify User'' utility. |
|
|
|
Additional options for authoring spaces can be set for the various user |
|
types: (a) whether webDAV is active, and (b) the default quota for Authoring Space. |
|
These only come into effect for a particular user, when an author and/or one or |
|
more co-author roles have been assigned to a user to provide access to one or more |
|
Authoring Spaces. |
|
|
|
WebDAV allows a user to connect to an Authoring Space in the same way as removable |
|
media, and to use their own laptop/desktop computer's file management tools and |
|
applications to move, edit and delete files. In the case of MacOS, the user selects |
|
the ``Go'' item in the Finder toolbar and selects ``Connect to Server''. |
|
The user will then enter a URL for a library server where the authoring space is located: |
|
e.g., https://s10.lite.msu.edu/webdav/msu/sparty/ where msu is the domain and sparty |
|
is the username of the Authoring Space. Note: webDAV usage requires Apache/SSL to be |
|
running on the library server. The user will be prompted to enter a username |
|
(this will be the LON-CAPA username, if the user is also the author, or username:domain |
|
of the user, if the access is for a co-author), and the user's LON-CAPA password. |
|
|
|
The requirement to obsolete published files before moving or deleting them, which applies to |
|
the regular web browser-based management of Authoring Space, also applies in the webDAV |
|
environment. Moving and deleting directories in the webDAV environment is prohibited if |
|
the directory, or any (nested) subdirectory contains a non-obsolete published resource. |
|
|
|
Given the ability to easily delete unpublished content in webDAV (without the ability to |
|
reverse the deletion), it is important that authors assigned webDAV access are especially |
|
careful when working in the webDAV environment. |
|
|