Thank you Graham, Very clear answer.
I guess the final goal I was pursuing while playing around with the browse configuration was to be able, for my Browse lists, to have one Date column that would display dc.date.submitted for ETDs and dc.date.issued for non-ETDs (and assuming there would be no issue date for ETDs), so I was hoping to be able to mix the content of various fields for the browse lists... In light of your explanations I don't see how this is possible. The closest I got was to have two columns (one for dc.date.submitted and the other one for dc.date.issued), or to have the submitted date in place of the issue date whenever the datesubmitted browse index or sort option was selected.... Or did I miss something? Regards, Marie-Hélène Vézina Librarian, Université de Montréal > -----Message d'origine----- > De : Graham Triggs [mailto:[EMAIL PROTECTED] > Envoyé : 22 septembre 2008 13:08 > À : Vezina Marie-Helene > Cc : [email protected] > Objet : Re: [Dspace-tech] Configuring the Browse List (JSPUI) > > Hi, > > > 2008-09-19 16:21:01,748 WARN > org.dspace.app.webui.jsptag.LayoutTag @ Exception > > javax.servlet.ServletException: javax.servlet.jsp.JspException: > > org.apache.jasper.JasperException: > javax.servlet.ServletException: > > org.dspace.browse.BrowseException: Browse Index > configuration is not valid: webui.browse.index.1 = > dateissued:dc.date.issued:date:full > > The above is the old pre-1.5 syntax. > > The 1.5+ syntax is: > > > 1. webui.browse.index.<n> =<index name> : metadata :<schema > > prefix>.<element>[.<qualifier>|.*] : (date | title | text) : (asc | > > desc) > > > > OR > > > > 2. webui.browse.index.<n> =<index name> : item :<sort > option name> > > : (asc | desc) > > > If limited to use the "old" syntax for defining browse > index, I don't understand how I can define new browse indices > of the "item" type (#2 above). I'm trying to create a browse > index based on the content of dc.date.submitted for our ETDs. > > I can't see where the content of the index can be defined, > for example, where, in the following default definition: > > > > "webui.browse.index.1 = dateissued:item:dateissued" > > > > is the index name related to the content of the > dc.date.issued metadata field? Is it hardcoded somewhere? > > Your syntax is essentially correct. The index name (the first > part after the =) can be anything you like - it's used to tie > the selection of an index in the interface to something less > fragile than the index numbers (which you'll change if you > want to re-order how the links appear) - so, when you select > the 'browse by date of issue' option, it will pass > ?type=dateissued as a parameter to the servlet, which refers > back to the index name in the above configuration. > > The key part that you are missing is in what an 'item' browse > represents. If you browse by date issued, or title (in the standard > configuration) - then what you have is always a list of > exactly the same length. It's one entry, for each item in > your repository. > > The only thing that differentiates those two browse lists > isn't what items are represented, but the order in which they > are presented. > > That was conflated in DSpace before 1.5, and has been > separated in the new config. So, what is important to > actually making your configuration work is the <sort option > name> - the dateissued at the END of your configuration line. > > This refers to a 'webui.itemlist.sort-option.X' entry, and > determines what metadata field is used to define the > ordering. In the standard configuration, this is the second > sort-option that is defined. > > Note that for 'item' browse (and search) lists, all of the > configured sort options are available to select in the > controls provided with the list. So, if you want to have your > items browsable by the accession date, the key thing is to > have a sort option configuration such as: > > webui.itemlist.sort-option.3 = > dateaccessioned:dc.date.accessioned:date > > you should only include a webui.browse.index - eg. > > webui.browse.index.5 = dateaccessioned:item:dateaccessioned > > if you want a link for it to appear in the browse navigation. > Without that webui.browse.index, you will still be able to > re-order an item-based browse list into date order from the > controls (providing the sort-option configuration has been specified). > > G > This email has been scanned by Postini. > For more information please visit http://www.postini.com > > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
