Hi Päivi,
We also encountered this problem recently and it appears that something has
changed on the sonatype side.
The fix we where able to come with it was to use maven 3 instead of maven 2
to build our DSpace.
Hope this helps,
Kind regards,
[image: logo]
Kevin Van de Velde *@mire*
*2888
Hi Javier,
What version of java are you running ? Because a client of ours had the
same problem with java 7 update 25, so we downgraded to java 6 no crashes
have occurred since.
Hope this helps,
Kind regards,
[image: logo]
Kevin Van de Velde *@mire*
*2888 Loker Avenue East, Suite 315
Hi George,
This is a known bug in DSpace 3.x, a fix is in the works for this. For more
information see: https://jira.duraspace.org/browse/DS-1432.
Hope this helps,
Kind regards,
[image: logo]
Kevin Van de Velde *@mire*
*2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010*
*Esperantolaan 4
Hi Nason,
I would suggest removing the *write.lock* file from the data directory and
rerunning the index command, that should fix it.
Hope this helps,
Kind regards,
[image: logo]
Kevin Van de Velde *@mire*
*2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010*
*Esperantolaan 4, Heverlee
/DSpace/DSpace/blob/dspace-3.0/dspace-xmlui/src/main/resources/aspects/Submission/sitemap.xmap#L238
).
Hope this helps,
Kind regards,
[image: logo]
Kevin Van de Velde *@mire*
*2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010*
*Esperantolaan 4, Heverlee 3001, Belgium*
www.atmire.comhttp
dc.title in hmo.title should do the trick.
Kind regards,
[image: logo]
Kevin Van de Velde *@mire*
*2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010*
*Esperantolaan 4, Heverlee 3001, Belgium*
www.atmire.comhttp://atmire.com/website/?q=servicesutm_source=emailfooterutm_medium
,
[image: logo]
Kevin Van de Velde *@mire*
*2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010*
*Esperantolaan 4, Heverlee 3001, Belgium*
www.atmire.comhttp://atmire.com/website/?q=servicesutm_source=emailfooterutm_medium=emailutm_campaign=kevinvdv
On 15 March 2013 17:22, aaronhelton hel...@un.org
Hi Ian,
There was an issue with the read field in rc3. This has been fixed for the
DSpace 3.0 release with the following commit:
https://github.com/DSpace/DSpace/commit/d9df145a4e9628fcb649d8bdeb7454085ae2cc53#diff-4
Kind regards,
[image: logo]
Kevin Van de Velde *@mire*
*2888 Loker Avenue
Hi Shaun,
Try running: {dspace-dir}/bin/dspace update-discovery-index *-f *. This
will force discovery to reindex its content.
*
*
*
*
Kind regards,
Kevin Van de Velde
@mire
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 - Carlsbad, CA 92010 - USA
atmire.com
Hi Howard,
May I ask what DSpace version you are using at the moment ?
Kind regards,
Kevin Van de Velde
@mire
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 - Carlsbad, CA 92010 - USA
atmire.com - Institutional Repository Solutions
On 30 January 2012 18:13
Hi Guillermo,
This is just a thought but have you also upgraded your database with the
database_schema_17-18.sql file located in the {dspace.dir}/etc/postgres
directory ?
Kind regards,
Kevin Van de Velde
@mire
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305
/list
/property
Kind regards,
Kevin Van de Velde
@mire
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 - Carlsbad, CA 92010 - USA
atmire.com - Institutional Repository Solutions
On 3 December 2011 21:59, Jason Stirnaman jstirna...@kumc.edu wrote
also increased, information about the improved discovery can be found on
the following location:
https://wiki.duraspace.org/display/DSDOC18/Discovery#Discovery-DSpace1.8Improvements
.
Kind regards,
Kevin Van de Velde
@mire
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite
Van de Velde
@mire
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 - Carlsbad, CA 92010 - USA
atmire.com - Institutional Repository Solutions
On 26 October 2011 15:40, Blanco, Jose blan...@umich.edu wrote:
Have you tried
** **
[dspace]/bin/dspace index-init
(this is the
current unreleased DSpace demo site).
If you have any further questions about discovery feel free to ask.
Kind regards,
Kevin Van de Velde
@mire
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 - Carlsbad, CA 92010 - USA
atmire.com - Institutional Repository
.
Kind regards,
Kevin Van de Velde
@mire
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 - Carlsbad, CA 92010 - USA
atmire.com - Institutional Repository Solutions
On 7 September 2011 18:03, Jim Coble jim.co...@duke.edu wrote:
Issuing a command like /usr/local/dspace
If you want to hide the recent results on the home page you will need to add
the following template to the theme.xsl
xsl:template
match=dri:div[@id='aspect.discovery.SiteRecentSubmissions.div.site-home']
/xsl:template
This will ensure that the div isn't shown on the home page.
Kevin Van de
I can take a
look at it ?
Kind regards,
Kevin Van de Velde
@mire
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 - Carlsbad, CA 92010 - USA
atmire.com - Institutional Repository Solutions
On 24 August 2011 18:19, Antonio Calderón neocalde...@gmail.com wrote:
Hi
Hi Susan,
Do you have any disk space left on your hard disk where you run the indexing
?
Kind regards,
Kevin Van de Velde
@mire
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 - Carlsbad, CA 92010 - USA
atmire.com - Institutional Repository Solutions
On 22
at the following location:
https://wiki.duraspace.org/display/DSPACE/DSpace+Discovery#DSpaceDiscovery-DiscoveryinDSPace1.8.0
Kind regards,
Kevin Van de Velde
@mire
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 - Carlsbad, CA 92010 - USA
atmire.com - Institutional
}/bin directory.
After that your issues should hopefully be solved.
Kind regards,
Kevin Van de Velde
@mire
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 - Carlsbad, CA 92010 - USA
atmire.com - Institutional Repository Solutions
On 5 June 2011 05:51, Nemiz, Elvi S
Hi Muñoz,
No It is not disabled so it should be operational.
Kind regards,
Kevin Van de Velde
@mire
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 - Carlsbad, CA 92010 - USA
atmire.com - Institutional Repository Solutions
On 2 June 2011 23:41, Francisco J. Muñoz
only metadata fields that are in the configuration end
up in the autocomplete.
Kind regards,
Kevin Van de Velde
@mire
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 - Carlsbad, CA 92010 - USA
atmire.com - Institutional Repository Solutions
On 25 May 2011 01:14
this can be found here:
https://wiki.duraspace.org/display/DSPACE/Discovery+Configuration
Kind regards,
Kevin Van de Velde
@mire
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 - Carlsbad, CA 92010 - USA
atmire.com - Institutional Repository Solutions
On 20 May 2011 17:04
This is caused because the discovery index is out of date I would attempt to
run the following in your {dspace.dir}/bin
dspace update-discovery-index -f
Hope this helps,
Kevin Van de Velde
@mire
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 - Carlsbad, CA 92010
just to be sure).
Kind regards,
Kevin Van de Velde
@mire
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 - Carlsbad, CA 92010 - USA
atmire.com - Institutional Repository Solutions
On 12 May 2011 16:26, César Sabater csaba...@unr.edu.ar wrote:
Hi all,
I'm using
reindex the discovery content and
the auto complete should work.
I hope this helps,
Kevin Van de Velde
@mire
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 - Carlsbad, CA 92010 - USA
atmire.com - Institutional Repository Solutions
On 6 May 2011 05:42, Nemiz, Elvi S
since this is something strange that shouldn't be
happening.
Kevin Van de Velde
@mire
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 - Carlsbad, CA 92010 - USA
atmire.com - Institutional Repository Solutions
On 4 May 2011 02:52, Nemiz, Elvi S. esne...@seafdec.org.ph
in that property.
Kind regards,
Kevin Van de Velde
@mire
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 - Carlsbad, CA 92010 - USA
atmire.com - Institutional Repository Solutions
On 3 May 2011 00:48, Jennifer Whalan jennifer.wha...@nt.gov.au wrote:
Bram,
Unfortunately, we
Have you already tried running the update discovery command with the -f
option, it will force a complete reindex.
- dspace update-discovery-index -f
Kind regards,
Kevin Van de Velde
@mire - www.atmire.com
533 2nd Street - Encinitas, CA 92024 - USA
Technologielaan 9 - 3001 Heverlee
for the following reason,
the field in which you copy your dc.subject content is called *
subject_filter*, DSpace will add the _filter postfix so subject should
be enough in your facets config.
After changing the property restart your tomcat and it should work.
Kind regards,
Kevin Van de Velde
@mire
Esperantolaan
the tomcat and re index discovery and the
field should be removed from the index.
I really hope this helps.
Ps: I do plan to create a patch to fix this issue (so that non indexable
fields can be configured) as soon as I find the time to create one.
Kind regards,
Kevin Van de Velde
@mire
Hi Thomas,
Have you tried running the update-discovery-index command with the
*-f*option like shown below:
./dspace update-discovery-index -f
By adding the *-f* you are forcing discovery to reindex all your items.
Hope this helps,
Kevin Van de Velde
@mire - www.atmire.com
533 2nd Street
is the exact solr query you are trying to execute ?
3. In your solr index, are there any values present in the var field ?
Ps: the search.index.x properties in the dspace.cfg aren't used by
discovery, the solr discovery index indexes all metadata fields.
Kind regards,
Kevin Van de Velde
@mire
Hi Germán,
What I would do is duplicate any xsl you would want to alter from the
navigation.xsl, paste these in {your.theme}.xsl and alter them there.
By doing it this way it is much easier to keep track of your changes.
best regards,
Kevin Van de Velde
@mire - www.atmire.com
533 2nd Street
=div1
div id=div2
xsl:apply-templates/
/div
/div
/xsl:template
I hope I was able to solve your problem.
best regards,
Kevin Van de Velde
@mire - www.atmire.com
533 2nd Street - Encinitas, CA 92024 - USA
Technologielaan 9 - 3001 Heverlee
Hi,
The error is implying that your metadata format registry is not up to date.
You might want to take a look at the following link:
http://www.dspace.org/1_6_0Documentation/ch05.html#N14D45
If you need further help for this please let me know.
Kind regards,
Kevin Van de Velde
@mire
);
list.addItem().addXref(contextPath+/feedback,T_feedback_link);
list.addLabel(T_email);
String email = ConfigurationManager.getProperty(mail.admin);
list.addItem().addXref(mailto:+email,email);
*/
best regards,
--
--
Kevin Van de Velde
@mire NV
B-3001 Leuven, Belgium
http
(collection.getHandle(),collection.getMetadata(name));
}
}
This will however list these collections in the simple search as well.
best regards,
--
Kevin Van de Velde
@mire NV
B-3001 Leuven, Belgium
http://atmire.com/consultancy.php - DSpace maintenance, support and custom
development
2008/11/7
39 matches
Mail list logo
