[UXPROD-1993] Detail Record should display in a full pane Created: 12/Aug/19  Updated: 16/Sep/20  Resolved: 15/Jul/20

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: P3
Reporter: Khalilah Gambrell Assignee: Khalilah Gambrell
Resolution: Won't Do Votes: 0
Labels: ux
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Requires
requires UIEH-772 eholdings app: Always open detail rec... Closed
requires UIU-1376 Users App: Detail Record always displ... Closed
Front End Estimate: XXL < 30 days
Front End Estimator: John Coburn
Development Team: Stripes Force
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R2
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R2
Rank: GBV (MVP Sum 2020): R2
Rank: Lehigh (MVP Summer 2020): R2
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R4

 Description   

FOLIO community feedback has been overwhelming that the current three/four pane view is challenging when it comes to navigating results list and more importantly when working with a record.

This feature will work to display a detail record in a full view AND support a user's need to easily return to his/her results list.

Work required

  • Updated UI design
  • Possible pane and routing updates needed


 Comments   
Comment by Kristin Martin [ 14/Aug/19 ]

Is this only applying to metadata management (Inventory) or this is FOLIO-wide?

Comment by Khalilah Gambrell [ 14/Aug/19 ]

Kristin Martin - FOLIO-wide. Removing label.

Comment by John Coburn [ 16/Nov/19 ]

STSMACOM-251 Closed puts us on a path to being able to do this in SearchAndSort modules. 3 Sprints for potential variance to get all modules doing this. I'm not sure we can do it all within SearchAndSort, so a first step would be a spike to have all SandS modules do this with a centralized change. This is easy to do at the module level if routing has been refactored (similar to ui-users) - that work can be broken out and distributed. If the solution cannot be completely centralized, the bulk of the module-level work for dev teams would be splitting any resources that the search view (Search and filter pane, results list) uses apart from the resources used by the detail view and using the API introduced in STSMACOM-251 Closed to handle the navigation appropriately. This would mean a single sprint (possibly less) work at the module level.

Comment by Khalilah Gambrell [ 26/Nov/19 ]

John Coburn so the work to do this requires

  • Centralized change across all apps using Search and Sort
  • AND if that is not possible then each app must do routing refactoring?
Comment by Khalilah Gambrell [ 15/Jul/20 ]

Implemented resizable panes

Generated at Fri Feb 09 00:20:13 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.