Yoshio Imai wrote:

Is it possible to implement aliases for logbooks? We would like to use a new logbook for every beamtime, but many services need to read/write to the respective current beamtime logbook. It would therefore be nice to have logbook "aliases", so that e.g. a "virtual" logbook beam could be defined to be an alias/redirection to the current beamtime logbook, and all services could refer to that one instead of having to be reconfigured for each beamtime. This could also help to make sure everyone on shift writes the entries to the correct logbook ...

• the "move to" command from the menu (which you first have to enable. While this works fine for individual entries, I never tried this with a whole logbook (click on "all", then "select all", then move to). So better try this first on a backup
  
• moving the logbook entries on the file level. Go to the elog root, then enter "mv logbooks/<current>/* logbooks/<beamtime>/ where <current> is your current (online) logbook and <beamtime> is the new one you just created. You have to restart elogd so that it realizes the moved files
  

Options Client = ALL, Test one{2}, Test two{3}
#	 Test one
{2} Options Equipment = FWL0020, RT0015

#	 Test two
{3} Options Equipment = 

• In the remote logbook, prohibit any modifications. You can do that with the Menu commands = ... option, where you just remove New, Edit, Reply and Duplicate.
  
• Do not allow public write access, but public read access. The remote logbook server can read but not write. This requires a guest access, see the manual.
  
• Create a special user, let's call it "mirroruser". Use this user to log in from the remote elog server by using the command Mirror user = mirroruser. Now restrict the right of this user via

  Deny New = mirroruser
  Deny Edit = mirroruser
  Deny Reply = mirroruser
  Deny Duplicate = mirroruser