Template
From Wikanual
Contents |
Folder Template
It can be handy if logins created via the add login function start out with a certain set of folders and files already in them.
Folder Templates when creating a folder
When a new folder is create INTERDUBS also offers to use a template. In comparison to the use of folder templates in logins there are the following differences:
* required templates are being ignored * default templates will be not selected automatically * the last template used will not be remembered
Setup
Below the structures to set up folder templates used when creating new logins or new folders:
folder: TEMPLATES
If you create a folder in the root folder called
TEMPLATES
then INTERDUBS will look in there for folders that it will offer during the creation of a new login. If there is a folder called
DEFAULT
inside of TEMPLATES then this will be selected default for newly created folders.
Request the use of a template via REQUIRED_TEMPLATES
A template folder called
REQUIRED_TEMPLATES
works exactly like a TEMPLATES folder. The difference is that INTERDUBS will require the user to choose one of the TEMPLATES that are in that folder. The none choice from the template selection is gone. Apart from this difference REQUIRED_TEMPLATES and TEMPLATES work the same way. The rest of this page uses TEMPLATES.
blocking the creation of new logins
Should you only create a folder called REQUIRED_TEMPLATES but leave it empty then admins can effectively not create new logins. While we find it hard right now to imagine how this could be useful we kept this a possibility in the system.
Examples
For the rest of this page folders will be denoted in the common path notation. If you like to start out all new logins with two folders called "audio" and "video" then you simply would create the following folders:
/TEMPLATES/DEFAULT/audio /TEMPLATES/DEFAULT/video
So if you create a new login called login01 then it would start out with the following folders:
/login01/audio /login01/video
when the user left the default selected. Likewise there could be an alternative structure like:
/TEMPLATE/commercial/previz /TEMPLATE/commercial/boards /TEMPLATE/commercial/cuts /TEMPLATE/commercial/reference
A user selecting 'commercial' for a login called 'login02' would end up with:
/login02/previz /login02/boards /login02/cuts /login02/reference
API
If you create a login via the Api then the folder /TEMPLATE/DEFAULT will be used if it does exist.
Other folders with special functionality
See Folders_with_special_functions for other folders with special functionalities.