Thanks Kostas for the information,
I have started looking at this, and am able to get Bibtex working item by item
(trying to narrow out the bad ones). I was wondering if there is any thoughts
to have different configuration files based on the import type? That way one
does not need to change the bte.xml depending on the format they are using to
import the data? Second, I do not think it is possible at least by default, to
be able to split on multiple authors in a Bibtex authors line, and maybe be
able to intelligently split the first and last name up correctly?
Thanks,
Tom
From: Konstantinos Stamatis [mailto:[email protected]]
Sent: Wednesday, January 30, 2013 2:46 AM
To: [email protected]
Subject: Re: [Dspace-tech] Uploading Bibliographic information from RefWorks
Dear Thomas,
At the very beginning, we would like to thanks you for trying to use EKT's
contribution to DSpace in order to load records in your system.
As far as the bibtex exception concerns, it seems that the problem relies on
jbibtex library rather on the BTE implementation. My guess is that the exported
bibtex file includes invalid characters or something like that.
Regarding the issue that Endnote or RIS data are imported with no values in the
various fields, keep in mind that you have to specify your configuration in the
following file: dspace/config/spring/api/bte.xml
In this file, you have to specify in the output generator bean (<bean
id="outputGenerator"
class="gr.ekt.transformationengine.outputGenerators.DSpaceOutputGenerator">)
the schemas that you have in your DSpace installation and then, in each of
these schemas you need to specify a list of pairs (name of the field of the
imported data + the name of the schema element) like the following XML snippet :
<key>
<value>Title</value>
</key>
<ref bean="titleDSpaceMetadata" />
In the case of RIS format, values must be terms like AU, TY, PY and so on. The
default value "Title" is not going to work in your case.
The reference bean (titleDSpaceMetadata) must declare the element and qualifier
of your DSpace schema like the following lines:
<bean id="titleDSpaceMetadata"
class="gr.ekt.transformationengine.dspace.DSpaceMetadata">
<property name="schema" value="dc" />
<property name="element" value="title" />
</bean>
Hope it helps.
Should you need any further help, we would be more than happy to help you.
Best regards,
Kostas Stamatis
National Documentation Center, Athens, Greece
On 1/29/13 10:55 AM, "Thomas Misilo" <misilot@...<mailto:misilot@...>> wrote:
>Hi,
>
>I was wondering if anyone has used the new bibliographic upload for
>DSpace 3.0 yet with a refworks bibtex file?
>
>Below is what I have tried, and the ouput I got. If you want the refworks
>bibtex file, I can
>
>dspace import -b -m refworks-map.map -e misilot@... -c 123456789/6856
>-s refworkstest.txt -i bibtex
>INFO [main] (DSpaceKernelInit.java:52) - Created new kernel:
>DSpaceKernel:org.dspace:name=cf20d3c4-227c-4adb-82da-1def97a034c7,type=DSp
>aceKernel:lastLoad=null:loadTime=0:running=false:kernel=null
>INFO [main] (ConfigurationManager.java:1224) - Loading from classloader:
>file:/srv/dspace/config/dspace.cfg
>INFO [main] (ConfigurationManager.java:1224) - Using dspace provided log
>configuration (log.init.config)
>INFO [main] (ConfigurationManager.java:1224) - Loading:
>/srv/dspace/config/log4j.properties
>Destination collections:
>Owning Collection: Bibupload Holding
>INFO: Dataloader
>gr.ekt.transformationengine.dataloaders.dspace.BibTexDataLoader@<mailto:gr.ekt.transformationengine.dataloaders.dspace.BibTexDataLoader@>...
>will be used for the import!
>Started: 1359477659086
>Ended: 1359477660013
>Elapsed time: 0 secs (927 msecs)
>Exception: Lexical error at line 1, column 79. Encountered: "\u03b7"
>(951), after : ""
>org.jbibtex.TokenMgrError: Lexical error at line 1, column 79.
>Encountered: "\u03b7" (951), after : ""
> at
>org.jbibtex.LaTeXParserTokenManager.getNextToken(LaTeXParserTokenManager.j
>ava:303)
> at org.jbibtex.LaTeXParser.jj_scan_token(LaTeXParser.java:408)
> at org.jbibtex.LaTeXParser.jj_3R_6(LaTeXParser.java:270)
> at org.jbibtex.LaTeXParser.jj_3_3(LaTeXParser.java:253)
> at org.jbibtex.LaTeXParser.jj_2_3(LaTeXParser.java:242)
> at org.jbibtex.LaTeXParser.String(LaTeXParser.java:190)
> at org.jbibtex.LaTeXParser.Object(LaTeXParser.java:66)
> at org.jbibtex.LaTeXParser.ObjectList(LaTeXParser.java:46)
> at org.jbibtex.LaTeXParser.LaTeX(LaTeXParser.java:21)
> at org.jbibtex.LaTeXParser.parse(LaTeXParser.java:16)
> at
>gr.ekt.transformationengine.dataloaders.dspace.BibTexDataLoader.parseLaTeX
>(BibTexDataLoader.java:169)
> at
>gr.ekt.transformationengine.dataloaders.dspace.BibTexDataLoader.loadData(B
>ibTexDataLoader.java:132)
> at
>gr.ekt.transformationengine.core.TransformationEngine.transform(Transforma
>tionEngine.java:111)
> at
>org.dspace.app.itemimport.ItemImport.addBTEItems(ItemImport.java:649)
> at org.dspace.app.itemimport.ItemImport.main(ItemImport.java:575)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
>57)
> at
>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm
>pl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
>org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:183)
>
>
>
>I was able to load the data via an EndNote export from RefWorks, however
>all it did was create the ~400 records, with all Unknown data.
>
>Thanks for any help,
>
>Tom
>
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
