For RUresearch collection, HOW you get to it affects what you are shown. Can the direct link also show what you get browsing?

Project:RUcore/NJDH/Partner Portal Search
Component:Searching - Service Agent
Status:Moved to JIRA

For a user accessing an RUresearch collection, they may see two differing page displays, depending on how they get to the collection.

1) Using a direct URL link to the collection, such as (Primate Teeth)
- with this approach, the user is NOT presented with the "Project Components" table in the lower left side of the page. Thus, they have no direct way of knowing whether the collection contains data files, documents, etc.

2) If the user BROWSES through the RUcore repository, e.g. "browse all projects", or through a search of the research portal, and select a collection, the user is presented with the "project components" table, which makes it easier/more understandable to identify content.

Is this something we can figure out how to standardize? I'd prefer that users see the display from path #2 (including the project components table), regardless of how they get to the collection.




Project:RUcore Website» RUcore/NJDH/Partner Portal Search
Version:7.6» 7.7
Component:User interface» Searching - Service Agent


Assigned to:chadmills» aletia.morgan
Status:active» test

This should be addressed with this issue.

The RUresearch display priority will need to be above the root/default display in the portal configuration. Let me know when testing if this prioritization needs to be checked.


Version:7.7» 8.0
Category:bug report» task
Status:test» need info

I'm working on alternate mockups of the RUresearch Data portal page. I don't see any point in spending a lot of time cleaning up the existing interface. I'm marking as "Need Info", since we have to review a design, and the behavior of the page. Also put off to rel 8.0, though that may not be correct.


Version:8.0» 8.1

Ok. Let's work on this in 8.1. *.0 is a Fedora upgrade only release. Thanks for looking at it.


Status:need info» Moved to JIRA

Back to top