News

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

Bibus and RefWorks

From Bibus

Revision as of 17:34, 20 March 2008 by Lddubeau (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Migrating from RefWorks

One of the problems encountered in migrating from RefWorks to Bibus is the fact that the folder structure created in RefWorks is lost when the references are exported into the RIS format. So that structure must be recreated in Bibus. There is apparently no supported way to export the folder structure. You can perform a backup of your RefWorks database which contains the folder structure but that file is encrypted. Yet another good reason to avoid closed-source software. We present here one method to recreate the folders. These instructions assume that you know how to use RefWorks and that you know how to use Bibus. You do not need to be an expert with either but you need to have read the documentation of both because these instructions do not explain how RefWorks folders work or how Bibus keys work.

1. Use the RefWorks export feature to export each folder individually. Actually, depending on how you used your folders in RefWorks you may be able to avoid exporting all the folders. I was able to skip a few myself. However, it is not possible here to tell you which folders you can skip because this depends on how you organized your information. The safe thing to do is to export all folders individually.

  • In Tools->Export, you must select the "Bibliographic Software" option for the format.
  • Give a different name for each folder you export.
  • This means that after exporting everything you will have one file per RefWorks folder.

2. If you are concerned that you may have missed something, you should quickly check that you have the correct number of IDs in each file you exported. Here's an example of what can be done in *nix based systems. By doing performing this check, I quickly found that I had made a mistake when I exported one of the folders. I saved my files with the .ris extension and named them so that they would be in the same order as what I have on RefWorks. The following commands shows how many records are in each file which can be easily checked against the view in "Organize Folders" in RefWorks.

$ ls *.ris | xargs -iXX sh -c 'echo -n "XX "; grep "^ID  -" XX | wc --lines' 
abhidharma.ris 81
chinese-thought.ris 7
...

You can also check the total number of records in all the files with:

$ grep -h "^ID  -" *.ris | sort | uniq | wc --lines
486

3. In Bibus, you want to import one by one each file you created.

  • You have to go into File->Import->RIS, select the file you want and select the proper encoding. In the process I describe here, this means selecting the utf8 encoding.
  • Your references will appear in the Import Buffer.
  • Create an appropriate key under "References". For instance, that name could be the name of the original folder in RefWorks. Go to the Import Buffer, select all (Ctrl-A), copy (Ctrl-C), go back to your new key and past (Ctrl-V).
  • You need to do this for each file.

4. Once this is done, you may want to check again the number of references under each key to make sure that nothing is missing. Also check the total number of keys. These checks are not foolproof because for instance if an entry was missed and another one duplicated, you won't be able to detect it by just checking numbers.

Personal tools