After setting up a testing 1.5.1 DSpace instance on Redhat by following
http://wiki.dspace.org/index.php/Installing_DSpace_on_Red_Hat_Enterprise_Linux_5#DSpace_1.5.x
I compared the ordering of the webui.browse.index.N lines in dspace.cfg
with the presentation of the 'browse navigation menu'; the ordering
matches in the case of my 1.5.1 Dspace testing instance
--- 1.5.1 DSpace testing instance dspace.cfg
webui.browse.index.1 = dateissued:item:dateissued
webui.browse.index.2 = author:metadata:dc.contributor.*:text
webui.browse.index.3 = title:item:title
webui.browse.index.4 = subject:metadata:dc.subject.*:text
--- 1.5.1 DSpace testing instance browse navigation menu
+ under communities & collections
issue date
author
title
subject
but the ordering doesn't match in the production instance, I expect
'subject' to come last on the browse navigation menu.
--- 1.5.0 DSpace production instance dspace.cfg
webui.browse.index.1 = dateissued:item:dateissued
webui.browse.index.2 = author:metadata:dc.contributor.*:text
webui.browse.index.3 = title:item:title
webui.browse.index.4 = subject:metadata:dc.subject.*:text
--- 1.5.0 DSpace production instance browse navigation menu
+ under communities & collections
titles
authors
subjects
by date
Should there be a mapping between webui.browse.index.N with the browse
navigation menu? Where would the string 'by date' for the navigation
menu be originating?
Thanks in advance.
--
Van Ly : University of Sydney Library
-----Original Message-----
From: Van Ly [mailto:[email protected]]
Sent: Wed 14/01/2009 11:41 AM
To: [email protected]
Subject: [Dspace-tech] error on browse by date
Hi Everyone,
I've a DSpace unable to respond without error to the following request:
http://ses.library.usyd.edu.au/browse?type=date
The local dspace.cfg has the following extra search.index lines than the
default:
search.index.13 = description:dc.description
search.index.14 = department:dc.contributor.department
After reading section 5.1.2 of the 1.5.1 DSpace Manual, I'm wanting to run
index-all
but it doesn't exist, index-init and index-update do, and I've tried running
them as user dspace and root without effect.
At a guess, I'm trying to fix the fault in the case the database was changed,
as suggested by those search index lines, but the index wasn't updated somehow.
Any clues to the solution?
Thanks in advance.
-- Van Ly : University of Sydney Library
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
