The window called ‘Users’ is divided into four panes:
This is the ‘User management’ window:
In the left column, under ‘Users’, you can create users who are to access the models. By right-clicking in the column “Users” you can choose “Add user”. The right mouse button menu is also used to edit or delete users. You also can use the buttons on the top of the column.
After having created a user you can set his or her user name (“login”) and password (“Password”) and his or her full name (“FullName”). You need to provide the email address of the user to let the user be able to use the ‘forgot password’ functionality.
The option “Own models’ shows how many different models the user can publish to the web.
The Role defines what a user can do;
- guest: Only access to certain models.
- user: right to publish a number of own models. The user is able to do user management on the web.
- administrator: all rights
The screen looks like this:
The right-hand column, under ‘Models’ allows you to manually add models to be available on the web. You may also edit, delete or clone models.
In the next window you may add a Description for the model and specify where the model resides physically (‘Path’).
Here are some advanced and optional settings:
Environment is an option only used when communicating with other applications or databases. Press
Updateif you have selected the file.
Form template gives the possibility of styling the model in the browser with a custom template. Defaults to ‘baseform.html’ in the HTML-directory.
Jump template, a similar function is served by ‘Jump template’, defining the structure of the jumplist the modelling author has defined (e.g. as a radiogroup versus a drop-down list). Defaults to ‘jumplist.txt’ in the HTML-directory.
Force restart with new session: Force that each time a case is opened, it starts at the beginning.
Automatically generate jumplist: Each time a new case is started, the server tries to run through the model without giving any inputs. If your model accepts that, the jumplist is automatically created. After the run, the case starts at the beginning.
Language: This options tells the server how to translate dates, e.g. 1 to January or Janvier.
Maintained by lets you manually assign an ‘owner’ to the model. The owner may update the model using Project > Publish in the Berkeley Studio and may get an overview of all cases that have been made on the basis of the model. When ‘nobody’ is listed as the maintainer nobody may update the model by means of ‘publishing’. When a model has initially been published the user publishing the model will also be the maintainer until changed here.
Anoymous: Can the model be anonymously be accessed. This option can also be set if you publish a model with the Studio.
The libraries are stored on the server, they can be managed just like models. Libraries have a description, a file and an owner.
The middle pane of the 'User management’-window lets you define which users have access to which models. This is done by domains. A domain is just a layer to help maintain access. You can add users and models to a domain. Each user has access to all the models in the domain. Just click on the arrows to add or remove users and models from a selected domain.
If a user is the owner of a model, he still gets access, no matter how the domains are set.
If a model is anonymous, all users can access that model, no matter how the domains are set.
Import a domain full of users. The first line of the CSV is ignored. The field are comma-separated.
The lines in 4.5 are without email, 4.6 does the import with email
If you press this button, you can select a login.xml file from another server. You can select all the desired users, and the will be imported, as long as the username not already exists.
If the button ‘Generate’ is pressed, the following form is shown;
The user can enter a prefix for username and password. The repeat-edit allows the user to dictate the number of to be created users. The created users will also be stored in a .csv file, as a list of comma-separated username and password, i.e. <username>,<password>