Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
HEIN+FRICKE
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Talk:Functional Document
(section)
Add topic
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
Add topic
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== 3.2 Lifecycle of Directories === The basic idea of DIPS is to manage all operations on directories and their permissions via a self-service portal that requires manual steps only from those ordering actions and, if necessary, approvers. All technical steps to carry out operations in the file system, Active Directory or other systems are carried out automatically and are therefore highly quality assured and reliable. DIPS provides you with information about the status of order processing at any time. * '''Create a new directory:''' When ordering, the necessary information about data ownership, authorizations, retention periods, and archiving is provided so that the automatic creation can take place. You will then see the new directory as a completed order in DIPS and as a directory in the desired location in Windows Explorer * '''Granting permissions:''' a previously unauthorized person can request permission to read or write directories. Alternatively, a data owner can proactively set up permissions for others. Only read permission can be granted for directories that contain other DIPS-managed directories. Write permissions are only granted to directories at the lowest level managed by DIPS. These inherit their permissions to their content. Your substructure and files are managed by those authorized to write them themselves via Windows Explorer. * '''Changing directory properties and transferring ownership of the directory:''' these processes allow changing the characteristics specified when creating a new directory or passing on data ownership. An important basic principle in DIPS is that there can be no orphan data areas. Each directory has a primary data owner. * '''Create subdirectories:''' the structure can be expanded by ordering subdirectories. Each subdirectory, which is also managed by DIPS, can receive its own permissions or simply adopt the permissions of a parent directory. Below the directory levels managed by DIPS, those authorized to write can create their own structures quickly and easily using Windows Explorer, as usual. * '''Delete directory:''' if a directory is no longer needed, data owners can of course delete it again. It will be removed from the file system. Directories that are automatically archived can only be deleted when there are no more files in the associated archive.
Summary:
Please note that all contributions to HEIN+FRICKE may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
HEIN FRICKE:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)