[ 
http://jira.dspace.org/jira/browse/DS-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11208#action_11208
 ] 

Tim Donohue commented on DS-496:
--------------------------------

At a very quick glance, here are my thoughts (I'll admit, I don't know the 
Browse Index code that well -- so, I could be wrong).

First off, I'd agree, we should support the ability to index multiple metadata 
fields as the "title".  So, as Jeff mentions above, oftentimes Librarians 
consider "dc.title", "dc.title.other" and "dc.relation.ispartofseries" to all 
be forms of "titles" (there are likely others I'm missing here -- but you get 
the idea, "Browse By Title" should support multiple metadata fields).

To me, it looks like the way this actually *should* be configured is the 
following:

(1) leave "webui.browse.index3 = title:item:title" alone (as this actually 
references the corresponding "title" sort-option)
(2) Instead, edit "webui.itemlist.sort-option.1" to be the following:
     
      webui.itemlist.sort-option.1 = 
title:dc.title.*,dc.relation.ispartofseries:title

However, #2 above isn't possible in 1.5.x or 1.6.0rc2, as it looks like 
"webui.itemlist.sort-option" only accepts a single metadata field (and not a 
comma separated list of fields).   But, I still think this solution is the way 
it probably should work -- as it would allow for multiple title fields to be 
indexed in "Browse By Title", and that single title index would also become a 
sort option.

All in all -- in my mind, this is halfway between a "bug" and an "improvement 
request" (that the Browse Title index doesn't properly support multiple fields 
-- and I suspect it has been this way for some time).  In my opinion, it may 
need to wait for 1.6.1 to come up with a better solution to this problem -- but 
if anyone feels strongly (one way or the other), feel free to voice your 
opinions here!  

 (If I'm wrong about the proposed solution above, and there is a quick fix for 
1.6.0...let us know!)





> Title Browse index has initial/definite articles showing up.
> ------------------------------------------------------------
>
>                 Key: DS-496
>                 URL: http://jira.dspace.org/jira/browse/DS-496
>             Project: DSpace 1.x
>          Issue Type: Bug
>          Components: DSpace API
>    Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0
>         Environment: UNIX/LINUX/AIX
>            Reporter: Jeffrey Trimble
>
> The default property key for the TITLE BROWSE indexing is:
> webui.browse.index.3 = title:item:title
> If you decide to include other DC elements (or for that matter, other schema) 
> in this index, such as:
> webui.browse.index.3 = 
> title:metadata:dc.title,dc.relation.ispartofseries:title:full
> The indexes seemed to generate correctly, but the browse screens include any 
> title that begins with a definite
> article (the, an, a, der, die, das, etc.) in the index and as included in the 
> link.
> Thus, the title: "The Art of Fugue, BWV 1080, Contrapunctus 4" has the 
> following URL to link to the specific item:
> http://rspace.maag.ysu.edu:8080/jspui/browse?type=title&order=ASC&rpp=20&value=The+Art+of+Fugue%2C+BWV+1080%2C+Contrapunctus+4
> If you REMOVE 'The+' from the URL, the link works correctly.
> Our documentation instructs the administrator how to customize the browse 
> title correctly, otherwise, title.other, ispartofseries, and other title 
> entries
> would not interfile, which is absolutely necessary for the user to find all 
> things collocated together.  (titles, uniform titles, series, other titles 
> "should"
> be in one index.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to