Hi, writing to update progress

My problem was solved when I quit from use the JSPUI tool for importing 
metadata and used the command line for doing so. It worked very well

Em sexta-feira, 9 de fevereiro de 2018 11:32:45 UTC-2, Hugo Carlos escreveu:
>
> Hello there!
>
> I am trying to ingest my dspace with RIS metada from Scopus.
>
> First of all I run my search on scopus. Based on results and info from 
> bte.xml I mapped every field name in RIS, BTE and Dublin Core. Then I  
> costumize the RIS tags in fieldmap of BTE RISdataloader bean. Also, I 
> customized the output map to match. Then, I uploaded my ris file using the 
> jspui batch import interface. As result, I obtained an error message, as 
> seem. Any clues?
>
>
>
>
> Error Message
> org.hibernate.LazyInitializationException: could not initialize proxy - no 
> Session
> at org.hibernate.proxy.AbstractLazyInitializer.initialize(
> AbstractLazyInitializer.java:165)
> at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(
> AbstractLazyInitializer.java:286)
> at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(
> JavassistLazyInitializer.java:185)
> at org.dspace.content.Item_$$_jvstfaa_4.getMetadata(Item_$$_jvstfaa_4.java
> )
> at org.dspace.content.DSpaceObjectServiceImpl.getMetadata(
> DSpaceObjectServiceImpl.java:129)
> at org.dspace.content.WorkspaceItemServiceImpl.create(
> WorkspaceItemServiceImpl.java:115)
> at org.dspace.app.itemimport.ItemImportServiceImpl.addItem(
> ItemImportServiceImpl.java:475)
> at org.dspace.app.itemimport.ItemImportServiceImpl.addItems(
> ItemImportServiceImpl.java:338)
> at org.dspace.app.itemimport.ItemImportServiceImpl.addBTEItems(
> ItemImportServiceImpl.java:242)
> at org.dspace.app.itemimport.ItemImportServiceImpl$2.run(
> ItemImportServiceImpl.java:1891)
>
>
>
> <!-- The keys in the RIS data loader map have to be the RIS tags that 
>  need to be loaded. -->
>  <bean id="risDataLoader" class="gr.ekt.bteio.loaders.RISDataLoader">
>  <property name="fieldMap">
>  <map>
>  <entry key="AB" value="abstract" />
>  <entry key="KW" value="allkeywords" />
>  <entry key="AU" value="authors" />
>  <entry key="AD" value="authorsWithAffiliation" />
>  <entry key="DO" value="doi" />
>  <entry key="SP" value="firstpage" />
>  <entry key="IS" value="issue" />
>  <entry key="PY" value="issued" />
>  <entry key="SN" value="jissn" />
>  <entry key="T2" value="journal" />
>  <entry key="LA" value="language" />
>  <entry key="EP" value="lastpage" />
>  <entry key="PB" value="publisher" />
>  <entry key="M3" value="subtype" />
>  <entry key="TY" value="title" />
>  <entry key="UR" value="url" />
>  <entry key="VL" value="volume" />
>  </map>
>
>
>
> Output Map:
>
>
> <!-- The output generator needs a configuration on how to map internal 
> records 
>  to DSpace metadata fields. The following map specifies this relationship. 
>  The value needs to be the label that the record internally associates 
> with 
>  the specific data and it is specified in the data loader beans. The key 
> is 
>  in the format of <schema>.<element>[.<qualifier>] and specified the 
> dspace 
>  metadata field that the value will map to. -->
>  <bean name="outputMap" class="java.util.HashMap" scope="prototype">
>  <constructor-arg>
>  <map key-type="java.lang.String" value-type="java.lang.String">
>  <entry value="jissn" key="dc.identifier.issn" />
>  <entry value="pisbn" key="dc.identifier.isbn" />
>  <entry value="journal" key="dc.source" />
>  <entry value="title" key="dc.title" />
>  <entry value="issued" key="dc.date.issued" />
>  <entry value="language" key="dc.language.iso" />
>  <entry value="subtype" key="dc.type" />
>  <entry value="authors" key="dc.contributor.author" />
>  <entry value="editors" key="dc.contributor.editor" />
>  <entry value="translators" key="dc.contributor.other" />
>  <entry value="chairs" key="dc.contributor.other" />
>  <entry value="abstract" key="dc.description.abstract" />
>  <entry value="allkeywords" key="dc.subject" />
>  <entry value="arxivCategory" key="dc.subject" />
>  <entry value="doi" key="dc.identifier" />
>  <entry value="publisher" key="dc.publisher" />
>  <!-- Not used - new metadata fields need to be declared for them in 
> DSpace registry -->
>   
>  <entry value="url" key="dc.description.uri" />
>  <entry value="note" key="" />
>  <entry value="fulltextUrl" key="" />
>  <entry value="authorsWithAffiliation" key="dc.contributor.institution" />
>  <entry value="pubmedID" key="" />
>  <entry value="publicationStatus" key="" />
>  <entry value="jeissn" key="" />
>  <entry value="volume" key="dc.description.volume" />
>  <entry value="issue" key="dc.description.issue" />
>  <entry value="firstpage" key="dc.description.startpage" />
>  <entry value="lastpage" key="dc.description.endpage" />
>  <entry value="eisbn" key="" />
>  <entry value="editionnumber" key="" />
>  <entry value="seriestitle" key="" />
>  <entry value="volumetitle" key="" />
>  <entry value="titleAlternative" key="" />
>  <entry value="authorAlternative" key="" />
>  <entry value="ncid" key="" />
>  <entry value="naid" key="" />
>
>
>  </map>
>
>
>
>
> And yet, it seems to have no effect.
>
>
>
>
>
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Reply via email to