[ https://jira.duraspace.org/browse/DS-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24405#comment-24405 ]
Tim Donohue commented on DS-956: -------------------------------- This ticket was briefly discussed in the Developers meeting on March 7, 2012. The general consensus was that this seems like a good idea, but it may be a larger change than anticipated. Currently, unless you are using Discovery, the Browse & Search mechanisms are entirely separate. So, you'd need to know what the user is browsing or searching and keep that "state" information somewhere, so that you can allow the user to move from item to item within that result set. All in all, we agree this seems like a good idea. We just need to find a developer volunteer to investigate a way to implement this feature. If there are any interested volunteers out that, please get in touch via this ticket. [20:01] <tdonohue> starting with DS-956 [20:01] <kompewter> [ https://jira.duraspace.org/browse/DS-956 ] - [#DS-956] Skip from Item page to next Item in Browse results without having to return to Browse results page - DuraSpace JIRA [20:02] <mhwood> Sounds like a nice feature, but we would have to save a lot of state somewhere. [20:02] <tdonohue> yeah, would definitely require saving some state info [20:03] * mdiggory (~mdigg...@rrcs-74-87-47-114.west.biz.rr.com) has joined #duraspace [20:04] <tdonohue> anyone in this chat interesting in looking into ways we could implement Ds-956 (maybe your institution is interested in this?). Just thought I'd ask. I agree, it sounds like a nice feature [20:05] <tdonohue> I think Ivan has a nice idea for embedding some state info into XMLUI (though you probably need more than just a next/previous reference) [20:05] * aschweer (~schw...@schweer.its.waikato.ac.nz) has joined #duraspace [20:06] <mhwood> So, thinking back to last week's discussion, how do we factor that out, since JSPUI sites will want it too. [20:06] <mdiggory> We've actually been doing something like this in Discovery Instead [20:06] <mhwood> (And Freemarker sites....) [20:07] <tdonohue> mdiggory -- so, Discovery can/will do this eventually? [20:07] <mdiggory> In that case, we retain the Discvoery Search Results and the Position in the Results, then add navigation links at the top of the page. [20:08] <tdonohue> is this something that is planned for a future Discovery release then? Just wondering if we should add comments here that Discovery plans to implement this issue in a future release. [20:09] <mdiggory> I"m not sure it will be in the contribution at this point [20:11] <mdiggory> It was actually very light wieght, an XMLUI aspect and some theming changes [20:11] <mhwood> Anyway, is there some way to make this a service of the browse provider, that the UIs just call on? [20:11] * PeterDietzHome (~an...@d60-65-161-223.col.wideopenwest.com) has joined #duraspace [20:11] <tdonohue> mhwood -- I think that'd be the idea if it was in Discovery. Then any UI which is made Discovery-compatible could use it [20:11] <mdiggory> Its actually more like "View Search Results One at a Time" than it is retain navigation on the Item View itself [20:13] <tdonohue> ok. well, we might as well move on for now. Not sure that we will get anywhere more with this? Basically we need a volunteer for Ds-956 [20:13] <mdiggory> mhwood: there are some ideas in that direction, yes [20:13] <tdonohue> Ds-956 Summary: Good idea, needs a volunteer. Perhaps implement in Discovery as an option? [20:13] <PeterDietzHome> hmm, I was thinking of a previous and next direction to go from an item [20:14] <PeterDietzHome> i.e. viewItem @ handle/12345/3344.. you could click a link to go to handle/12345/3344/next which then has the controller go to next item [20:14] <mdiggory> I would say that if we want to continue on the topic of Discovery being default in 3.0, this would ease implementation of these sort of features to again, only need to focus on one implementation to be able to accomplish them. [20:14] <PeterDietzHome> like mhwood said, to allow the state from a search to have an item's next, would require a bit more state [20:15] <mhwood> But the Item doesn't know what's in your browse result. [20:15] <mdiggory> PeterDietzHome: that is the general approach, yes [20:15] <tdonohue> +1 mdiggory. That's my thoughts too. If we manage to get behind Discovery, then that simplifies the number of solutions we need [20:15] <mdiggory> mhwood: that is why I said "mdiggory: Its actually more like "View Search Results One at a Time" than it is retain navigation on the Item View itself" [20:16] <tdonohue> PeterDietzHome: like mhwood said -- 'handle/12345/3344/next' wouldn't have any meaning without knowing whether you are browsing, searching, etc. [20:17] <PeterDietzHome> then you would have more state search/rocket+NASA/item/34556 that can have a next [20:17] <mdiggory> Here is an example of our URL retaining the state. [20:17] <mdiggory> http://host/handle/10211.6/179?order=DESC&rpp=10&sort_by=score&page=1&group_by=none&etal=0 [20:18] <tdonohue> ok, should we move along for now? [20:18] <mdiggory> the next Item is [20:18] <mdiggory> http://host/handle/10211.6/161?order=DESC&rpp=10&sort_by=score&page=1&group_by=none&etal=0 [20:19] <mdiggory> so, it just exposes discovery query detains in the Item Page [20:19] <mdiggory> detains = details [20:19] <PeterDietzHome> i guess we can proceed [20:19] <tdonohue> makes sense - I suggest we move along for now & put the above discussion in comments of Ds-956, so that hopefully we can find a volunteer for it > Skip from Item page to next Item in Browse results without having to return > to Browse results page > -------------------------------------------------------------------------------------------------- > > Key: DS-956 > URL: https://jira.duraspace.org/browse/DS-956 > Project: DSpace > Issue Type: New Feature > Components: JSPUI > Reporter: Sue Walker-Thornton > Priority: Major > > We would like to see a new feature in DSpace where a User could "skip" from > the Item short (or long) listing to the next Item in either Browse or Search > results without having to return to the Browse or Search results page. Let's > say I do a search from the DSpace home page on "rocket". I get a list of all > Items in DSpace that contain the word rocket, either in the metadata or in a > filtered bitstream. Say I click on the first Item in the list and the Item > short-listing page is displayed. We would like to be able to review that > Item, then "skip" to the next Item that was returned in the Browse or Search > results, WITHOUT HAVING TO GO BACK TO THE BROWSE OR SEARCH RESULTS PAGE. > Optimally, I'd like to see an icon or button that says "Next Item" or > something like that. Once I've scrolled to the next item, then there should > be a "Previous Item" and a "Next Item" icon or button, if applicable. This > would be SOO cool! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel