Regards
Sincerly yours, Yen-Tang Chen
Hi
it looks as a bug in DSpace-CRIS. It should be enough to add this line
c.turnOffItemWrapper();
here
Unfortunately I have no time today to verify, can you run a fast test and report if it solves so to include the fix in the next release?
--
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...@googlegroups.com.
To post to this group, send email to dspac...@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
-- Andrea Bollini Chief Technology and Innovation Officer 4Science, www.4science.it office: Via Edoardo D'Onofrio 304, 00155 Roma, Italy mobile: +39 333 934 1808 skype: a.bollini linkedin: andreabollini orcid: 0000-0002-9029-1854 an Itway Group Company Italy, France, Spain, Portugal, Greece, Turkey, Lebanon, Qatar, U.A.Emirates
mvn
package
, I can not find the method " turnOffItemWrapper()"...
Regards
Sincerly yours, Yen-Tang Chen
mvn
package
..ok mvn
package
..errorSincerly yours, Yen-Tang Chen
Sincerly yours, Yen-Tang Chen
Hi Yen-Tang Chen,
1) this is the default behavior of DSpace, it is not a bug or something that you can configure nor in DSpace nor in DSpace-CRIS. It depends on the metadata format that you use: oai_dc in your case that in turn involve https://github.com/4Science/DSpace/blob/dspace-5_x_x-cris/dspace-api/src/main/java/org/dspace/content/crosswalk/OAIDCIngestionCrosswalk.java.
If you can try to use the qdc (Qualified Dublin Core) or the DIM as you are harvesting another DSpace instance. Here you can find some documentation about the Harvesting client
https://wiki.duraspace.org/display/DSDOC5x/OAI#OAI-HarvestingfromanotherDSpace
You can also configure the webui.itemlist.columns propert
https://github.com/4Science/DSpace/blob/dspace-5_x_x-cris/dspace/config/dspace.cfg#L2234
as you did in DSpace JSPUI 5.5 but I don't recommend that as you will keep in your database records with very poor metadata and you will need to fix the configuration in a lot of other places, as for instance define an authority on dc.creator
https://github.com/4Science/DSpace/blob/dspace-5_x_x-cris/dspace/config/dspace.cfg#L2321
change the browse, the cris-enhancers, the ORCID mapping and much more.
2) I guess that you have rebuild dspace-cris using an old build.properties that is missing of some key so in the generated configuration files you have something like
a-configuration-property = ${a-configuration-property}
that result in an infinite loop when the application (or a script) start so the out-of-memory
Try to take the current build.properties
https://github.com/4Science/DSpace/blob/dspace-5_x_x-cris/build.properties
and edit you configuration inside this file.
Hope this help,
Andrea
ant fresh_install
What do I miss
of some key ?I have found some time today to make a try.
A slightly modified fix has been committed to our maintenance repository
https://github.com/4Science/DSpace/commit/7d52138d90eb9d177ac09e45eba21e22c9a7a550
Harvesting via OAI-ORE from DSpace-CRIS of the Official Duraspace DSpace demo now succeed.
https://dspace-cris.4science.it/handle/123456789/59
Andrea