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
Import from Endnote
Importing references from Endnote / Exporting references to Endnote
Importing references from Endnote is quite easy, but might be tricky too.
First of all, you must launch Endnote and select the style "Endnote Export". (From the menu: Edit --> Output Styles --> "Endnote Export". If "Endnote Export" is not there use Edit --> Output Styles --> Open Style Manager, and check "Endnote Export")
Then use the menu File --> Export and export your references to an export.txt file. Now launch Bibus and select File --> Import --> Refer (Endnote). Select your "export.txt" file. Bibus will ask you which code to use, and will suggest by default to use cp1252. You should change to "latin_1".
(When using EndNote 8, which apparently supports Unicode, the code to use is "utf_8". Selection of the correct code can be checked by verifying that international characters such as é, à, ö etc. are correctly imported)
If it does work (we hope so!) the imported references will appear inside the "Import" tab (left side of the main menu). Select the references which you want to import or use Edit --> Select all (Ctrl-A). Drag the selected references and drop them into the desired tab (for instance "All"). You are done.
Exporting references to Endnote is quite easy as well.
(currently tested with Bibus 1.2 and Endnote 8 on Windows 2000)
In Bibus, select the references you want to export (not necessary if you want to export all records). Then select File->Export->Refer (Endnote). A window comes up which allows you to select if you want to export all or only the selected records. Next, you are asked to specify a file name to be exported to (you can use "export2endnote.txt"). When asked for the coding specify "latin_1" (even for EndNote 8!)
Now launch EndNote and open/create the file where you want your imported records to go. Then choose File->Import. In the Import dialog, choose the "export2endnote.txt" file you just created using the Export function of Bibus. Select "EndNote Import" under "Import Option", "Import All" under "Duplicates" and "No translation" for "Text translation". After clicking OK your records will be added to the current EndNote file.
You are done.
Detail: It is not entirely clear why data needs to be encoded as "latin_1" even for EndNote 8. Somehow EndNote reverts to "latin_1" when importing Bibus Refer files, but not when importing its own Refer files which are UTF-8. This is probably related to the way Bibus exports to Refer format: without dots after the author initials whereas Endnote 8 puts dots after the authors initials when exporting Refer
Note on data integrity The integrity of the data during Import/Export has not been checked thoroughly. This may mean that some data can be lost or altered. Please report any loss of data here, so that other users know what to expect.
- Endnote record numbers are not retained when executing an import (Endnote -> Bibus) / export (Bibus -> Endnote) cycle.
- The author initials are sometimes not properly imported into Bibus, especially when there are no spaces (only dots) between them in the original Endnote database. E.g. "Cleland, W.W." will not be imported properly, whereas "Cleland, W. W. " will. You may use the find/replace of a text editor to clean up your Endnote exported file.
- Endnote 8 (OS X) does not read the URL (%W) row from Bibus 1.2.0 exports, it instead places it in the same row as the journal volume number.
Good luck and enjoy bibus!