...
| App | Topic | Description/ use case | Date added | Provided by Name, Institution | Has been discussed in meeting: Link to minutes | Actions / JIRA ticket | Status | ||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Agreements All | Review tables across ERM to have frozen headings on MCLs | e.g. Agreement Lines - if you scroll you lose the headings on the MCL |
| Martina Schildt based on a comment by Sara Colglazier in ERM SIG | 2022-06-15 Meeting notes: Implementers topics: UX/UI | John Coburn notes that we can do this now by setting a static height for the table. Upside: frozen headings! Downside: table height is always fixed, whether there are 3 rows or 300 rows.
|
| ||||||||||||||||||||||||||||||||||||||||
| ALL | Review tables across All Apps that use MCLs (Inventory, Orders, Agreements, Invoices, Receiving, Finance, etc.)–MCL navigation | when there are more columns that can be normally/generally viewed at once, and you have many lines, and depending on your screen size, then when you scroll down, you lose the column headings, and when you are at the top, you may not be able to access the horizontal scroll bar to scroll over to see the column you need to see without scrolling down and then not being able to see your headings, also you scroll away the first column information which for your line is often the defining bit of info and needed for context as well as to know what line you are in | 29 April 2022 | Sara Colglazier & Related to / expandingMartina Schildt 's entry above | 2022-06-29 Meeting notes: Implementers topics: UX/UI |
| |||||||||||||||||||||||||||||||||||||||||
| ALL | Warning Modals needed when deleting any record in any App when it is the source of truth for other records | To avoid dead links, or even disappearing records and information, when deleting a record to which other Apps link or connect or downstream display information regarding, a warning modal should appear informing the user that if they confirm the deletion then the following other records in such-and-such apps will be unlinked or deleted as well | 29 April 2022 |
| |||||||||||||||||||||||||||||||||||||||||||
| ALL | Modals or other popups need to move–should not be fixed in place on the screen | In various Apps functional Modals be moved out of the way while in use but at the same time cover over information that is needed while using the Modal. Modals need to be able to be moved. Not all modals are "Look-up" modals, some are "Fill-out" modals and so info is on the screen now hidden–e.g.: in the Receiving App, the Receiving Note. Additionally, I often want to copy and then paste into the pop-up modal info from the screen behind, but no longer can. I would hope that if I can move it out of the way, I then would also be able to copy off it to pate into fields in the popup–my demo example would get be when I am creating a piece in the Receiving App. Martina Schildt as an addition: it would be helpful to be able to change the size of the popup (e.g. enlarge to view more lines / more information) | 10 May 2022 | Sara Colglazier | 2022-07-27 Meeting notes: Implementers topics: UX/UI |
| |||||||||||||||||||||||||||||||||||||||||
| ALL | Wildcards (truncation marks) need to be standardized across all Apps | Currently depending on what App either % or * or even $ is the truncation mark to use. I have to have a post-it note to remember which one for which App. | 10 May 2022 | 2023-05-31 Meeting notes: Implementers topics: UX/UI Discussion at WOLFCon 2023 |
|
| |||||||||||||||||||||||||||||||||||||||||
| ALL | How Dates are formatted and entered | 2022-05-10 vs 05/10/202 and that the user must type the punctuation mark rather that system automatically supplying it as the user types as is standard in most systems and generally online when filling out forms etc. | 10 May 2022 | Sara Colglazier | 2023-05-31 Meeting notes: Implementers topics: UX/UI Requirements: Date formatting |
|
| ||||||||||||||||||||||||||||||||||||||||
| Across All | Spaces handling | Example: In Inventory 'extra' spaces are eliminated, while in Orders they can exist and impact search & retrieval: From Orders: Newspaper of extra spaces becomes Newspaper of extra spaces in Inventory. If you copy Newspaper of extra spaces from Inventory to search in Orders by Orders Lines, you retrieve nothing, until you add the spaces back | 10 May 2022 | Sara Colglazier | 2023-05-31 Meeting notes: Implementers topics: UX/UI Discussion at WOLFCon 2023 |
|
| ||||||||||||||||||||||||||||||||||||||||
| Across All | lowercase vs. CAP in Search | Use of lowercase vs CAP re: searching not consistent, barcode example (in my case, B891369-MHC vs. B891369-mhc) or KW in Inventory searching for something that is an Identifier for example, in my case (MHeb* works but not (MHEB* ... ... different in other apps | 15 May 2022 | Sara Colglazier | 2023-05-31 Meeting notes: Implementers topics: UX/UI Discussion at WOLFCon 2023 |
| |||||||||||||||||||||||||||||||||||||||||
All | Sort "cards" in logical or alphabetical order | Cards are sorted differently earch time a user visits a page in both apps. Example ERM Order: j, e, k, e
Order: e, k, j, e
Discussed in ERM: 7/8 Meeting minutes |
| Martina Schildt for ERM SIG | Meeting with UX/UI designers |
|
| ||||||||||||||||||||||||||||||||||||||||
| Edit mode: Add a just "save" button, instead of having only "Save & close" or "cancel" | A user is editing a record and wants to save the current state of the record; the user then does not want to leave the edit mode, cancel the editing or close the record
|
| 2023-06-28 Meeting notes: cross-app implementers topics 2023-07-17 Meeting notes: Sorting of results |
|
| ||||||||||||||||||||||||||||||||||||||||||
| ALL | Horizontal scrolling | Avoid horizontal scrolling | Martina Schildt - this was raised in one of our meeting s | 2023-11-06 Meeting notes: Implementers topics |
| ||||||||||||||||||||||||||||||||||||||||||
| Notes | Add table to Notes helper app / notes details | I should have mentioned this in our meeting yesterday, but forgot it. It would be helpful if one could also create tables in the "Details" section of the Notes app to store information like:
This is a screenshot from our internal Wiki. The information is suitable to be maintained in the ERM system. It's about the creation of analytic records in our catalogue. | 2020-06-04 | Felix, ZBW | 2023-11-06 Meeting notes: Implementers topics |
Forwarded from ERM | |||||||||||||||||||||||||||||||||||||||||
| ALL | MCLs - scrolling | I noticed a little stumbling block today when navigating in Folio: If you make the browser window quite narrow, then horizontal scroll bars appear at the bottom of the first and second columns. For the third column, there is usually no such bar, because the contents of that column are rearranged so that they are distributed more downward than to the right. So far everything is fine. However, if the third column contains a table that is both deeper and wider than the column, then initially no scroll bar is displayed, see the first attached screenshot.
You have to scroll to the bottom of the table first to see the table specific horizontal scrollbar, which can be a long way if the table is long, see 2nd screenshot.
In my opinion, this can make navigating through large tables difficult. It is possible to scroll left and right with the mouse wheel at any point in the table, but I'm not sure if every mouse supports this - and this possibility is not obvious from the display as long as no scrollbar is visible. Therefore, I would like to suggest that a scrollbar is permanently displayed below the entire 3rd column if a table is included that is wider than the column. |
| Martina Schildt on behalf of GBV | 2023-11-06 Meeting notes: Implementers topics |
|
...