...
...
\uD83D\uDDD3 Date
01
🐶 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.Lref gdrive file url https://docs.google.com/spreadsheets/d/1nFhq4OeAsOgABos_1OQ7zGBz0lCgyeSrn1u3z0yGqIM/edit?gid=0#gid=0
🏘️ Housekeeping
Convener and notes: Tara Barnett
2024 Meeting and topic calendar
\uD83D\uDC65 Participants
Martina SchildtTara BarnettKristin Martin Laura E Daniels Owen Stephens Lloyd Chittenden Heather McMillan Kimberly Pamplin
\uD83E\uDD45 Goals
Prioritize the list of cross app tickets so that we can discuss them with the POs.
\uD83D\uDDE3 Discussion topics
Time | Item | Presenter | Notes |
---|---|---|---|
5 min | Announcements |
| |
55 min | Cross App Issue Prioritization | All |
|
Rankings, part 1 (see also
Lref gdrive file | ||
---|---|---|
|
: Out of Scope, Refer to Relevant POJira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-4670 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.
: MediumJira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-4506 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.
: HighJira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-3159 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.
: HighJira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-1647 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
: No preferenceJira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key PERF-217 This issue had no champions. No one attending felt particularly strongly about it.
: No preferenceJira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key PERF-216 This issue had no champions. No one attending felt particularly strongly about it.
: LowJira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-3742 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.
: REALLY CLOSEDJira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-4626 We don’t think we labeled this, and either way, it is fully closed.
: REALLY CLOSEDJira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-4242 We don’t think we labeled this, and either way, it is fully closed.
: REALLY CLOSEDJira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-961 This is closed for real. No more work here.
: REALLY CLOSED (captured fully by ERM SIG)Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UX-528 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?
: REALLY CLOSEDJira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key STCOM-1041 Almost certainly done. This is a stripes issue.
: LowJira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key STCOM-1021 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.
: REALLY CLOSEDJira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-1857 Probably not ours, and actually finished.
✅ Action items
- Choose a new label for the cross app SIG to use and apply it to all the issues that are really ‘ours’ (
crossAppSIG
?) Tara thinks: We might want an additional ‘current’ cross app label so we can access both our history and our current concerns. - Set a meeting to re-scope the SIG--what is our current charge, and what issues should we be investing our efforts in?