Automatic user configuration

Automatic user configuration

Some details of this process are not yet clear to me but...

When an experiment is approved by ... and scheduled by instrument scientist, User office provides appropriate information to [Catalog service], giving the user rights to access his data in the catalog. At some stage(what stage?) special file, which defines the participants of the experiment and the people who have access to the data of this experiment is placed on the internal server [should the address be public?] and automatically processed by issicompute configuration script [should the address of the script be public?]. The format of the file is .json and the contents looks as below:

{
"Last Updated": 20150413,
"experiments":
[
  {
   "RbNumber": "1234567",
   "Instrument": "MERLIN",
   "Cycle": "2013/4",
   "StartDate": "20131203",
   "Permissions": [
     {
       "email": "YYYY@stfc.ac.uk",
       "fedid": "XXXXX"
     },
     {
       "email": "warren.jeffs@stfc.ac.uk",
       "fedid": "gpq43739"
     },
     {
       "email": "alex.buts@stfc.ac.uk",
       "fedid": "wkc26243"
     }
   ]
 },
 { "NEXT RB NUMBER""
 }

The automatic configuration script runs twice a day on isiscompue server, creates user accounts and appropriate RB folders and give users permissions to access their RB folders. Alex Buts and FBU IT support FBU IT support (Jeffs Warren) have access and can modify this script. At the final stage this script runs the Mantid configuration script for inelastic instruments, which configures user's Mantid to access the data, auxiliary instrument files necessary to process these data and to provides users with initial configuration scripts. Alex Buts is responsible for maintaining this script.