Bauhaus-Universität Weimar offers central storage space for personal file storage and for file storage in shared access hereafter referred to as »project storage space«.
Storage space in your own »HOME directory«
A »Homedirectory« is available to you for storing data. Your user directory has a storage space of 10 GB. Only you personally can access this directory.
Access to the central storage system
Access to the central storage system is only possible within the network of the Bauhaus-Universität Weimar. n principle, access within the network should be possible from any computer and any operating system. In some cases, access may be restricted for security reasons. Further information can be found in the section »Access requirements« on this page.
The data in the »HOME directory« can also be used from outside the Bauhaus-Universität. However, access from outside is subject to certain requirements. General information can be found in the section »Access from outside via VPN and WebDAV« on this page. Instructions with further information can be found in the »Further information« section.
Access requirements
The provision of storage space for users at the Bauhaus-Universität Weimar takes place in two different ways, on the one hand via the »CIFS-Protokoll« from the company Microsoft, which is provided as »Microsoft shares«, and on the other hand via the standardised Internet protocol »WebDAV«, which is provided via WebServer shares.
| Access via »CIFS« | \\speicher.in.uni-weimar.de\fs..... |
| Access via »WebDAV« | http[s]://webspeicher.in.uni-weimar.de/fs. |
All computers within the Bauhaus-Universität Weimar have the possibility to access the central storage via the protocol »WebDAV«.
Access via »CIFS« is the access option preferred by the SCC, but special security requirements must exist at the workstations for this, i.e. use is not possible from all systems within the Bauhaus-Universität Weimar.
The conditions that must be met for individual workstations are explained in the description »Access requirements for using CIFS/SMB/Samba« under the heading »Workstation classes«or you can ask the IT person responsible for you.
For centrally administered computers, it is possible to request extended access via »Microsoft Windows network shares«:
Extended access via »Microsoft Windows Sharing«
For security reasons, not every client system can be granted unrestricted access to the storage system, because not all client systems in the networks of the Bauhaus-Universität Weimar can be trusted equally.
An extension of the access is possible via »Microsoft Windows Shares«. Access must be requested individually and is bound to certain requirements.
Two types of shares are available for using the central storage system via »Microsoft Windows Sharing«.
| Types of »Microsoft Windows Sharing« | ||
|---|---|---|
| 1.) Advanced »Microsoft Windows Sharing« for centrally administered computers | \\in.uni-weimar.de\fs | |
| 2.) Standard »Microsoft Windows Sharing« for all other computers | \\speicher.in.uni-weimar.de\fs | |
Below these shares, as with »WebDAV«, there are the two folders »PJG and »HOME«, through which you can access your own projects and personal file storage.
Detailed and further information about the requirements and the access prerequisites can also be found here in the description »Access requirements for the use of CIFS/SMB/Samba« and in the description »Overview of the provision of the central storage requirement«.
Access via »WebDAV« and from outside via »WebDAV/VPN«
For security reasons, normal access to the central storage system is only possible via »WebDAV«.
In principle, this should be possible from any computer within the Bauhaus-Universität Weimar. Access is subject to certain restrictions, but these are largely protocol-specific and are not due to the server service in the central storage system. A detailed description of the access options can be found on the page »WebDAV/Web storage«.
If access is required from outside the Bauhaus-Universität Weimar, it is also necessary to first dial into the university's internal network via a VPN connection.
Sharing data in the »project storage space«
Files can be stored and edited by several users in a common directory.
Advantages of use
- Only participants of the group have access to the stored data.
- The access rights can be defined individually for the users. For projects in the project repository, it is therefore possible to define which individual users with which access rights can collaborate on shared datasets (access with »change/read« or only »read« possible).
- Provided standard storage volume: 25 GB
Application as a prerequisite for sharing
- A »project storage space« for sharing and editing by a group of users must be submitted to the SCC via the »Project Request form«.
- The application can only be submitted by employees of the Bauhaus-Universität or the University of Music FRANZ LISZT Weimar.
- Please use the applications in the »Forms« section on this page.
FAQ
What must be considered when moving files from one project directory to another?
It is important to know that the access rights to the file are taken along. Users often report the following error: A member has »moved« data to a shared project. However, other members cannot see this data.
Example:
- A project directory PROV_A belongs to the group GRUPP_A.
Members of this group are NUTZ_1 and NUTZ_2 .
A file DAT_A1 belongs to user NUTZ_1. - A project directory PROV_B belongs to the group GRUPP_B.
Members of this group are NUTZ_2 and NUTZ_3. - Member NUTZ_2 vnow moves the file DAT_A1 from directory PROV_A in the directory PROV_B.
- Member NUTZ_1 has access rights to this file, although NUTZ_1 is not a member of the group. Furthermore, member NUTZ_3 does not see this file, although NUTZ_3 has all rights for this directory.
Copy, instead of move!
To work around the problem, the file must be copied to the new directory and then deleted from the old directory.
Technical Background:
When moving, only the hint (pointer) where the data is located in the file system changes.
Moving does not update the security descriptions on these files, i.e. the data retain the security descriptions from their original project.
And that in turn means that users of the project do not have access to this »moved« data. The fact that users cannot see the data is due to the use of access-based enumeration. This means that only those files are displayed to which the user has access.