--- loncom/html/adm/help/tex/Domain_Configuration_Quotas.tex 2008/07/23 02:41:55 1.1 +++ loncom/html/adm/help/tex/Domain_Configuration_Quotas.tex 2015/03/26 18:46:58 1.4 @@ -1,15 +1,53 @@ \label{Domain_Configuration_Quotas} -Each user in your domain will receive an individual portfolio space -to which files may be uploaded. Students can submit items from their -portfolio to meet the requirements of assignments in their courses. -The default quotas you set for users in your domain will be overridden -by any quota you set for individual users. +By default, each user in your domain can create blogs, a personal +information page, and store files in an individual portfolio space. +Students can submit items from their portfolio to meet the requirements +of assignments in their courses. -Default quotas (in Mb) can be set to vary by institutional affiliation, -as defined for your domain (e.g., Faculty, Adjunct, Staff, Student). +You can choose to disable personal information pages, blogs and/or portfolios +for different groups of users defined for your domain (e.g., Faculty, Adjunct, +Staff, Student). If the ``Modify User'' utility in User Management is +used to explicitly set availability of these tools for a particular user, +that will override the corresponding settings determined by the user's +affiliation. + +If you choose to enable portfolios, default quotas (in MB) +can similarly be set to vary by institutional affiliation. If a user is affiliated with more than one group, whichever default quota is largest for the different groups is the one which applies. -Institutional types need to be defined in a customized version of -\&inst\_usertypes() in the localenroll.pm module installed on the -primary server in your domain. If no types have been defined, then -a single default quota will apply for all users from the domain. +Institutional types are defined in the ``Institutional user types'' +section on the ``Default authentication, language, timezone, portal, types'' +screen. If no types have been defined, then a single default quota +will apply for all users from the 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: +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:// $<$ hostname $>$ /webdav/ $<$dom$>$ / $<$ username $>$/ where dom is the domain +and username is the username of the Authoring Space owner. +Note: webDAV usage requires Apache with 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. +