Difference between revisions of "Bibliographic/Hints and Tips/OOoRISExport.py"
(→Details) |
m (→Description) |
||
| Line 3: | Line 3: | ||
[http://bibliographic.openoffice.org/files/documents/124/3781/OOoRSIExport-1.py OOoRISExport.py] is a program to export the OpenOffice Bibliographic database contents in RIS format ([http://meerkat.adeptscience.co.uk/KnowledgeBase/KnowledgeBaseMk4.NSF/cbaf0788e6c2caa780256ddc004b746b/60df1dcd3f4dc07d80256e38004fe4f0/$FILE/RIS RIS Specification PDF]). The OpenOffice database access code is based on Michael Sowka's [http://bibliographic.openoffice.org/files/documents/124/3078/RISImport.py RISImport.py] programme. | [http://bibliographic.openoffice.org/files/documents/124/3781/OOoRSIExport-1.py OOoRISExport.py] is a program to export the OpenOffice Bibliographic database contents in RIS format ([http://meerkat.adeptscience.co.uk/KnowledgeBase/KnowledgeBaseMk4.NSF/cbaf0788e6c2caa780256ddc004b746b/60df1dcd3f4dc07d80256e38004fe4f0/$FILE/RIS RIS Specification PDF]). The OpenOffice database access code is based on Michael Sowka's [http://bibliographic.openoffice.org/files/documents/124/3078/RISImport.py RISImport.py] programme. | ||
| − | OOoRISExport.py works with the OpenOffice.org UNO which means that that it must be installed in the openoffice.org program directory and use the version of python that is installed as part of openoffice. And OpenOffice must be running for the progamme to work. If | + | OOoRISExport.py works with the OpenOffice.org UNO which means that that it must be installed in the openoffice.org program directory and use the version of python that is installed as part of openoffice. And OpenOffice must be running for the progamme to work. If OpenOffice is not running you get a error message like this: |
<pre> | <pre> | ||
| − | + | Traceback | |
| − | Traceback | + | [........] |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
__main__.com.sun.star.connection.NoConnectException: Connector : couldn't connect to socket (Success) | __main__.com.sun.star.connection.NoConnectException: Connector : couldn't connect to socket (Success) | ||
</pre> | </pre> | ||
| Line 24: | Line 20: | ||
the windows version. | the windows version. | ||
| − | OOoRISExport.py takes the export file path-name as a parameter so the complete command is like | + | OOoRISExport.py takes the export file path-name as a parameter so the complete command is like: |
<pre> | <pre> | ||
| − | + | /openoffice.org2.0/program> ./python.sh /OOoRSIExport-1.py /temp/test.ris | |
</pre> | </pre> | ||
| + | |||
| + | ===Debug=== | ||
| + | In the progam code I have set | ||
| + | DEBUG = True | ||
| + | so that the output can be seen when you run the program via the command line. You can turn this off by setting | ||
| + | DEBUG = False | ||
==Details== | ==Details== | ||
Revision as of 23:30, 18 November 2006
Contents
Description
OOoRISExport.py is a program to export the OpenOffice Bibliographic database contents in RIS format (RIS Specification PDF). The OpenOffice database access code is based on Michael Sowka's RISImport.py programme.
OOoRISExport.py works with the OpenOffice.org UNO which means that that it must be installed in the openoffice.org program directory and use the version of python that is installed as part of openoffice. And OpenOffice must be running for the progamme to work. If OpenOffice is not running you get a error message like this:
Traceback [........] __main__.com.sun.star.connection.NoConnectException: Connector : couldn't connect to socket (Success)
So to run OOoRISExport.py you need to set the local directory to
openoffice.org2.0/program
python.sh OOoRISExport.py filename (for linux)
or
python.bat OOoRISExport.py filename (for windows) I think .. I do not have
the windows version.
OOoRISExport.py takes the export file path-name as a parameter so the complete command is like:
/openoffice.org2.0/program> ./python.sh /OOoRSIExport-1.py /temp/test.ris
Debug
In the progam code I have set DEBUG = True so that the output can be seen when you run the program via the command line. You can turn this off by setting DEBUG = False
Details
Tag Mapping
The conversion method I have used to the RIS format is very basic. RIS allows many tags to flag data, but the Openoffice Bibliographic database has only a few database columns. Basically the program assigns the OOoBib columns - Identifier, Type, Address etc, the RIS tags - ID, TY, CY etc. in the dictionary structure called 'mappings':
mappings = {'Identifier':'ID','Type':'TY','Address':'CY','Annote':'KW',\
'Author':'AU','Booktitle':'BT','Chapter':'CT','Edition':'ET', \
'Editor':'ED','Howpublish':'M2','Institutn':'AD','Journal':'JO',\
'Month':'Y2','Note':'N1','Number':'IS','Organizat':'AD',\
'Pages':'EP','Publisher':'PB','School':'AD','Series':'T3',\
'Title':'TI','RepType':'M3','Volume':'VL','Year':'PY',\
'URL':'UR','Custom1':'AB','Custom2':'U2','Custom3':'U3','Custom4':'M2',\
'Custom5':'M3','ISBN':'SN'}
In particular I have not added name processing, what is in 'Author' goes into 'AU'.
If you want you can modify the two letter tags to better fit your needs. If you can suggest a better mapping to RIS tags let me know.
Character tidying
I had problems with non alpha-numeric characters (ie. CR LF) messing up the output so I stripped them out by replacing all types of non-white spaces with standard spaces - ' '.
Output character coding
You can set the character coding for the output by changing the setting for
CODEC = 'iso-8856-1'
Some of the possible encodings include utf-8, utf-16, ascii, iso-8856-1, unicode-escape. The RIS Specification recommends the 'Windows ANSI Character Set' which I guess is iso-8856-1 ???. I am not a expert on on this so I will take any advise.
