UX Overhead (UXPROD-836)

[UXPROD-443] Enhanced Pane header dropdown Created: 01/Apr/18  Updated: 14/Dec/18  Resolved: 14/Dec/18

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q4 2018
Parent: UX Overhead

Type: New Feature Priority: P3
Reporter: Khalilah Gambrell Assignee: Khalilah Gambrell
Resolution: Done Votes: 0
Labels: stripes-force, technical, ux
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Screenshot 2018-07-10 12.31.35.png    
Issue links:
Relates
relates to STCOM-193 Action Menu for PaneHeader Closed
relates to UIIN-272 Implement the pane header component (... Closed
relates to STCOM-388 Upgrade PaneHeader to allow for advan... Closed
relates to STCOM-389 Create MenuSection Component Closed
Epic Link: UX Overhead
Development Team: Stripes Force

 Description   

Feature

Allow for custom controls to be added to pane dropdown menus (see attached screenshots)



 Comments   
Comment by Cate Boerema (Inactive) [ 05/Jun/18 ]

Khalilah Gambrell, I am trying to figure out what epic this fits into. Is it responsiveness, accessibility, general UX enhancement?

Comment by Khalilah Gambrell [ 06/Jun/18 ]

Cate Boerema - General UX enhancement. Feature was initiated by a RA SIG request https://folio-org.atlassian.net/browse/UX-114

Comment by Khalilah Gambrell [ 06/Jun/18 ]

Filip Jakobsen and John Coburn, do you have additional details (documentation and prototypes) regarding the more complex version noted in this feature?

Comment by Filip Jakobsen [ 10/Jul/18 ]

Thank you so much for your question, Khalilah and sorry for the late reply.

The "more complex version" here mentioned refers to, I would say, not one additional iteration, but all the additional iterations arising from functionality elsewhere in the system that will provide actions and preferences that are relevant as candidates for the content of this menu.

I've attached a sketch showing some examples of the kinds of things that we might want to show in this menu, depending on which functions we have available at any given time in the system; which third party apps are installed; and how far along the development of the UI components are (e.g. the MCL and its ability to adjust responsively to zoom levels, screen widths, pane widths and user preferences).

I think the most important thing about this vision of a more sophisticated version of the Pane Header Context Menu, is this: In terms of what the end user actually sees, not much will change. However, the ability for the system; third party apps; and super components, to "register" functions to show up in the appropriate area of the menu (just like e.g. App Icons show up in the Universal Header, when an app is registered in the FOLIO system's infrastructure) defines a significant change to the infrastructure surrounding the Pane Header Context Menu and the means by which the interface receives the data and actions to display in it.

I think this all will and should develop over time, but there will need to be bursts of development focused on setting up the infrastructure to support the various sections of the menu, and their allowance of displaying things that the app developer in question might not even know would be there (because the app developer who makes the app containing the Pane Header Context Menu can never know which other apps are installed on a given installation of FOLIO).

Let me know if I have been unclear in my response, or if you have any other questions, advice or ideas regarding this.

Thanks!

CC John Coburn, Rasmus Wølk

Comment by Khalilah Gambrell [ 10/Jul/18 ]

Thanks Filip Jakobsen. I added your comment to the description. Given the description, should the Front end estimate change? And should there be an analysis estimate added?

Comment by Filip Jakobsen [ 10/Jul/18 ]

Khalilah Gambrell, I think we should let John Coburn decide on those questions, perhaps with help from Rasmus Wølk

Comment by Khalilah Gambrell [ 03/Sep/18 ]

We need to review and determine what features are needed for Jan 2019. We can create new features for future features.

Comment by Rasmus Wølk [ 05/Sep/18 ]

I'd like to further discuss the implementation of this issue with John Coburn. I'll get back with some more information once I have talked with John.

Comment by Cate Boerema (Inactive) [ 13/Sep/18 ]

UXPROD feature assignee = product owner. I am assigning this to Khalilah for now, as she is the temporary PO for UX/stripes

Comment by Khalilah Gambrell [ 09/Dec/18 ]

Rasmus Wølk - I believe you completed the work that allows for the functionality in the mockup included in the description?

Comment by Khalilah Gambrell [ 14/Dec/18 ]

Will create additional features for phase 2

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