|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
1) One thing I noticed is that there's a difference between collection page and browse pages. The collection page contains a search/browse/subscribe widget, while
and the browse pages (upon clicking on Next) contain:
Jump to a point in the index:
Sort by: In order: Results/Page Authors/Record:
It would make sense for these to contain the same widget (a superset of both functionalities).
2) We need reverse chronological sorting by accessioned date available out of the box in order to replace the "recent items" functionality.
3) With the default browse index configuration, I tested all possible values for webui.collectionhome.browse-name. I found out that "dateissued" and "title" work, while "author" and "subject" don't display the list (both in Lucene and Discovery). So I think there's a problem with browse index type "metadata", while "item" type works fine.