| 2023-05-03 17:22:13 |
Benjamin Kalish |
description |
In the staff client, when viewing a patron screen, the page title is composed of two parts. The first part is derived from the patrons name and the second part is meant to provide context as to how you are interacting with the patron record. Some of these page titles make sense, but many are less than helpful:
These look good:
- /checkout: PATRON NAME - Checkout
- /items_out: PATRON NAME - Items Out
- /holds: PATRON NAME - Holds
- /bills: PATRON NAME - Bills
- /messages: PATRON NAME - Messages
- /edit: PATRON NAME - Edit
But then we start running into trouble:
- /alerts: PATRON NAME - Other
- /notes: PATRON NAME - Other
- /triggered_events: PATRON NAME - Other
- /message_center: PATRON NAME - Other
- /stat_cats: PATRON NAME - Other
etc.
Each page should have a descriptive title. "Other" really isn't very helpful! |
In the staff client, when viewing a patron screen, the page title is composed of two parts. The first part is derived from the patron's name and the second part is meant to provide context as to how you are interacting with the patron record. Some of these page titles make sense, but many are less than helpful:
These look good:
- /checkout: PATRON NAME - Checkout
- /items_out: PATRON NAME - Items Out
- /holds: PATRON NAME - Holds
- /bills: PATRON NAME - Bills
- /messages: PATRON NAME - Messages
- /edit: PATRON NAME - Edit
But then we start running into trouble:
- /alerts: PATRON NAME - Other
- /notes: PATRON NAME - Other
- /triggered_events: PATRON NAME - Other
- /message_center: PATRON NAME - Other
- /stat_cats: PATRON NAME - Other
etc.
Each page should have a descriptive title. "Other" really isn't very helpful!
Observed in Evergreen 3-7-4. |
|
