Richard, that helps tremendously!  Seems as though the BrowseIndex code 
was just breaking on the dashes (numbers seem to be ok) so I've changed my 
qualifiers in every place necessary, rebuilt and redeployed and all is 
well.  And yes, datecreated was defined lower down as 
webui.itemlist.sort-option.2 = datecreated:dc.date.created:date which it 
seems I had forgotten about.

Thanks so much for your help, I really appreciate it!

-Sarah Ryder
Web Development
Hampshire College
413.559.5477

On Fri, 29 May 2009, Richard Jones wrote:

> Hi Sarah,
>
>> Does anyone know if there is an updated version of the browse configuration 
>> page? This page in the wiki is relevant to older versions of DSpace: 
>> http://wiki.dspace.org/index.php/Modify_browse_fields_(JSP)
>> 
>> The old browse configuration made sense to me, but for some reason I'm not 
>> wrapping my head around how to change some browse configs.  What I 
>> currently have works, but not the way our librarians want it to work.
>> 
>> My current settings are:
>> webui.browse.index.1 = datecreated:item:datecreated
>> webui.browse.index.2 = author:metadata:dc.contributor.*:text
>> webui.browse.index.3 = title:item:title
>> webui.browse.index.4 = subject:metadata:dc.material.*:text
>> 
>> I want to change the author browse index to only index a specific 
>> contributor field, which is contributor.1-sort-name, but if I alter the 
>> setting to be webui.browse.index.2 = 
>> author:metadata:dc.contributor.1-sort-name:text then I get an error when 
>> trying to index.  Same thing happens if I change 
>> subject:metadata:dc.material.*:text to 
>> subject:metadata:dc.material.art-architecture:text. 
>
> Looking at the part of the BrowseIndex code which parses the configuration, 
> it appears that the metadata field declaration cannot contain numbers or 
> special characters, so your configuration is breaking on the "1" and the "-". 
> I think that counts as a bug.
>
> The fix is probably relatively straightforward, but would require you to 
> rebuild and redeploy your DSpace instance.  Let me know if this is viable, 
> and I can help you out.
>
>> I also am unsure of the datecreated browse index.  I want to make sure it 
>> is indexing the field date.created, but I can't quite tell if that's what 
>> it's doing.
>> 
>
> Anything with "item" on the right hand side refers to an actual list of 
> items, and the final part of the configuration tells the browse system which 
> sort term configuration to use.  So:
>
> webui.browse.index.1 = datecreated:item:datecreated
>
> Tells the browse system to create an item level browse on the sort 
> configuration "datecreated".  This is should be configured further down as 
> something like:
>
> webui.itemlist.sort-option.2 = datecreated:dc.date.created:date
>
> Telling the browse system which metadata field to sort by 
> ("dc.date.created"), and the datatype of that metadata field ("date").
>
> Hope that helps,
>
> Cheers,
>
> Richard
>
> -- 
> Richard Jones
> Head Repository Systems Architect, Symplectic Limited
> e: [email protected]
> t: 0845 026 4755
> t: +44 (0)207 7334036
> w: http://www.symplectic.co.uk/
>

------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian 
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com 
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to