[UXPROD-2985] Add flower release to System Information page Created: 15/Mar/21  Updated: 25/Jul/22

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

Type: New Feature Priority: P3
Reporter: Holly Mistlebauer Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: JPEG File Settings-System-information.jpg     PNG File Skärmavbild 2022-07-25 kl. 5.34.38 em.png     PNG File image-2021-03-15-13-37-41-869.png    
Issue links:
Relates
relates to FOLIO-1007 About FOLIO Page at {base-url}/settings Open
relates to FOLIO-1176 Add vagrant box name+version to softw... Open
relates to STCOR-603 Custom text on Settings -> About "Sof... Closed
relates to STCOR-591 Allow custom URL for Help link Closed
Development Team: None
Kiwi Planning Points (DO NOT CHANGE): 10
PO Rank: 0
Rank: Chalmers (Impl Aut 2019): R3
Rank: Cornell (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R3
Rank: U of AL (MVP Oct 2020): R4

 Description   

After an institution installs/upgrades FOLIO, they have no way of knowing which release they are actually running.  The Settings=>System information page provides release info for the various modules, but not for FOLIO as a whole.  We have been asked to include the flower release name somewhere on that page.  We will need to add the hot fix release as well, as shown in red text in the attached screen mock-up...

 



 Comments   
Comment by Zak Burke [ 15/Mar/21 ]

FYI, this has been discussed before in FOLIO-1007 Open .

While I understand folks' desire to know, "What [version] of FOLIO am I running?" an important point I think we need to resolve with clear language is exactly what "version" means on this page.

We have a bunch of okapi interface versions, and a bunch of backend modules that implement those interfaces, and a bunch of frontend modules that connect to those interfaces.

What happens when we publish okapi v5 (say it patches a critical bug in an optional feature we decide to remove) so none of the modules themselves change. Is that still Iris? What if a hosting provider decides to write their own version of a module that functions as a drop in replacement for the one we shipped (i.e. the interface version doesn't change, but the module name and version do). Is that still Iris? What if an institution adds their own UI module to the bundle. Is that still Iris?

To be clear, I'm not opposed to doing this work, but I think it is important that we be clear about what the information we display here means – and what it doesn't mean – and where it comes from.

Comment by Julian Ladisch [ 28/Apr/21 ]

My suggestion is to add an optional "Installation notes" section before the "User interface" section.

It displays an arbitrary string that the SysOp can set after installing or upgrading the system.

The string is stored and fetched from some mandatory module like mod-users or mod-configuration.

curl or wget can be used to set the string.

Installation and upgrade documentation should suggest to set that string.

Example:

Installation Notes

Iris Hotfix 2 has been installed on May 3, 2021.
Our app for the IoT Enabled Coffee Machine has been enabled and configured on May 15, 2021, the inital credit is 5 cups.

Comment by Ian Walls [ 14/Apr/22 ]

Knowing what Flower Release of FOLIO we're running is important for documentation purposes.  This related issue aims to have users taken to the appropriate documentation site for their version

Comment by Charlotte Whitt [ 25/Jul/22 ]

Index Data edits the welcoming message on the FOLIO landing page for uChicago, Duke, Spokane, and other of our customers to include the flower release name; e.g.

CC: Erin Nettifee Ian Walls Peter Murray

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