Difference between revisions of "Importing from Endnote"

From EPrints Documentation
Jump to: navigation, search
m
m (re-word sentence: Using Textpad and saving it as a ANSI/Unix file seems to work.)
Line 4: Line 4:
 
* In Endnote, ensure ‘Edit > Output Styles > Endnote Export’ is selected
 
* In Endnote, ensure ‘Edit > Output Styles > Endnote Export’ is selected
 
* 'File > Export' (as text file)
 
* 'File > Export' (as text file)
* You may need to open the file in a text editor and changed the file type. Endnote seems to save the file as UTF-8, which does not appear work with the en2eprints script (save as ANSI, or some other format). I use textpad and also save as a UNIX file.
+
* You may need to open the file in a text editor and changed the file type. Endnote seems to save the file as UTF-8, which does not appear work with the en2eprints script (save as ANSI, or some other format). Using Textpad and saving it as a ANSI/Unix file seems to work.
 
* Copy to eprints server (eg with filezilla)
 
* Copy to eprints server (eg with filezilla)
 
* ./en2eprints [user id] (not username) < input > output
 
* ./en2eprints [user id] (not username) < input > output
 
* /opt/eprints/bin/import_eprints <siteid> <dataset> <xmlfilename>
 
* /opt/eprints/bin/import_eprints <siteid> <dataset> <xmlfilename>

Revision as of 09:39, 29 November 2006

Download en2eprints from the old wiki (should probably be moved across)

Steps to import from Endnote:

  • In Endnote, ensure ‘Edit > Output Styles > Endnote Export’ is selected
  • 'File > Export' (as text file)
  • You may need to open the file in a text editor and changed the file type. Endnote seems to save the file as UTF-8, which does not appear work with the en2eprints script (save as ANSI, or some other format). Using Textpad and saving it as a ANSI/Unix file seems to work.
  • Copy to eprints server (eg with filezilla)
  • ./en2eprints [user id] (not username) < input > output
  • /opt/eprints/bin/import_eprints <siteid> <dataset> <xmlfilename>