2024-07-10 Meeting notes: Prioritize the Cross App Tickets
Date
Jul 10, 2024
Homework
Please try to do the homework, but you are still more than welcome to attend even if you don’t have time!
Before this meeting, please review and add ratings to . Please see 2024-06-26 Meeting notes: Reflection on PO meeting for more details.
Housekeeping
Convener and notes: @Tara Barnett
2024 Meeting and topic calendar
Participants
@Martina Schildt@Tara Barnett@Kristin Martin @Laura E Daniels @Owen Stephens @Lloyd Chittenden @Heather McMillan @Kimberly Pamplin
Goals
Prioritize the list of cross app tickets so that we can discuss them with the POs.
Discussion topics
Time | Item | Presenter | Notes |
---|---|---|---|
5 min | Announcements | @Martina Schildt |
|
55 min | Cross App Issue Prioritization | All |
|
Rankings, part 1 (see also )
UXPROD-4670: Make receiving data available through RTAC for Unbound issuesIn Review: Out of Scope, Refer to Relevant PO
There’s significant variation across the community (since this depends on your discovery layer) and we think it’s unlikely that we’ll find consensus.
We wonder if this is really cross-app in nature. We don’t think this has been discussed by this group. We plan to remove our label from this one and refer it to the relevant PO.
UXPROD-4506: UI changes to "save" buttonOpen: Medium
We discussed this issue at length and it would be ideal to see this through.
This is not functionally crucial to any users we can think of. While users would like consistency, in individual SIGs other features are ranked higher.
Hygiene is not by its nature particularly urgent. We do worry that choosing not to attend to hygiene will lead FOLIO to diverge yet further. ERM SIG may prefer another design.
This is not an impediment to potential users of FOLIO--it does not affect the value of FOLIO.
UXPROD-3159: User Permission Management UI Improvements (Show perm metadata)Open: High
We spent several sessions on this topic. Permissions by their nature seem to fall to the Cross App SIG. While they appear in Users, they come from and affect all apps. There is no Permissions PO.
Many people ranked this high because managing permissions is challenging for their own institution and their peers. Updating permissions is very challenging.
This topic may need to be broken down further.
This issue is broadly accepted as high priority--it affects data integrity. It affects user experience and the value of FOLIO as a whole. We consider whether we are the owners of this because the solution is technical and requires an overarching solution (which has been agreed upon, but not uniformly implemented, it sounds like). On one level, this is really about how data stays in sync in FOLIO. Acquisitions-Inventory integrity is of particular interest to the group. This specific issue has been outstanding for some time. For a variety of reasons, we’d like to follow and advocate for this type of issue.
We discussed this previously at a working group: Cross-app data synchronization working group and this has been discussed a technical council: DR-000004 - Cross application data sync proposal
PERF-217: Performance testing: how long does the elastic search indexing/implementation take when doing larger data importsOpen: No preference
This issue had no champions. No one attending felt particularly strongly about it.
PERF-216: Performance testing: How long does it take to propagate a record change in Inventory to mod-search?Open: No preference
This issue had no champions. No one attending felt particularly strongly about it.
FOLIO-3742: Printing in FOLIO | cross-appOpen: Low
We believe this is important, but at least in this group, we don’t hear about it that often. We think this should be low on our list but not dropped.
UXPROD-4626: Update new field in inventory Item with Piece "Display Summary" field dataClosed: REALLY CLOSED
We don’t think we labeled this, and either way, it is fully closed.
UXPROD-4242: Allow independent acquisitions unit for ordering and receiving Closed: REALLY CLOSED
We don’t think we labeled this, and either way, it is fully closed.
UXPROD-961: Allow Inventory Instances to generate purchase order and purchase order linesClosed: REALLY CLOSED
This is closed for real. No more work here.
UX-528: Sort cards in a customisable orderClosed: REALLY CLOSED (captured fully by ERM SIG)
We believe that a UX design was captured and agreed to for a generalized implementation of cards. This is currently only used by ERM apps. The work that is remaining to implement the desired solution has been captured by the relevant apps--nothing further for us to follow up on.
We do wonder--how can we promote issues like this, where a solution has been formed, so that POs don’t reinvent the wheel?
https://folio-org.atlassian.net/browse/STCOM-1041: REALLY CLOSED
Almost certainly done. This is a stripes issue.
https://folio-org.atlassian.net/browse/STCOM-1021: Low
We discussed this significantly. It is closed because the investigation is complete and it is now possible to freeze columns, but it has not been implemented in individual apps, which may mean that further needed tickets were not filed.
https://folio-org.atlassian.net/browse/ERM-1857: REALLY CLOSED
Probably not ours, and actually finished.
Action items
crossAppSIG
?) Tara thinks: We might want an additional ‘current’ cross app label so we can access both our history and our current concerns.