October 2009 : a new release (bibus 1.5.0)
- OOo3.1 compatibility
- Infinite number of file/http links
- Clever capitalization (lord of war => Lord of War ...)
- Better handling of journal abbreviations
- Import/Export filters can be added easily (plugin)
- journal abbreviations and shortcuts can be easily edited (simple csv file that can be edited in OOo/excel or a text editor)
- Lot of bug fixes
- Requires python2.5 (not a problem anymore under Windows since OOo3.1 includes 2.6)
- Requires wxpython-2.8
Access Shared Database
The information on this page is not finalised as yet.
With Bibus you can change the configuration of the application so that shared databases can only be accessed edited by certain people. This information has been summarised from this thread: 
The default setting is that any user can edit the Shared key but you can change this. Of course the best place to change these values are in bibus.config (in /etc or in the bibus install directory) by putting in it after the "import BIBbase" line.
In this case Admin, user1 and user2 will be able to edit the shared key: BIBbase.ADMIN = ('Admin','user1', 'user2')
In this case all users will be able to edit the shared key: BIBbase.ADMIN = ('*',)
The way to do it changing the code is explained in BIBbase.py. Look for the line starting with "# Shared keytree".
You can: 1) Remove the shared tree by setting: MULTI_USER = FALSE 2) Set the name of the Administrator: SHARED_DBNAME = "Admin" 3) Set the list of authorized users: ADMIN = ('*',) means everybody ADMIN = ('Admin',) will restrict shared key editing to user 'Admin'. Don't forget the comma, we need a python tuple! ADMIN = ('Admin','toto') will allow editing to 'user1' and 'Admin'