Page Comparison

BugFest in progress! Difficulties in the bugFest environment, it's has been unstable. May extend BugFest testing due to these difficulties. More details are forthcoming.

Lists App and Bulk Edit working group are combining into one group. Slack channel will be renamed. Alternating meeting topics between Bulk Edit and Lists App. Meetings are Tuesdays at 11:00am EST

UAT for Lists App is open:  for anyone who still would like to provide feedback on the Lists app for the Poppy release: this form https://forms.gle/39Rv4kXMeRcGxSP26 will be open through Friday, November 3rd.

Slide deck: MM-SIG Bound-with UXPROD-3640 and UXPROD-3655 - simple edit solution

Sif has been working on Bound-with functionality.

1st iteration 

Solution is based on copying Holdings HRID into a modal in the edit screen

Creating Bound-with connection in UI

No special permissions needed.

Go to main record (primary/host/parent record) > Edit 

Bound-with and analytics accordian > click add button

Modal pops ups > paste in your Holdings HRIDs (current max. 7)

Save & close

Returned to edit mode! Must save and close the record to save the changes you made.

Demo in FOLIO snapshot environment

Deleting Bound-with connections in UI

Delete the child connections, System will clean-up the main record connection to the Bound-with table for you when there are no connections left.

Demo in FOLIO snapshot environment

Questions:

Sara: When you opened the modal again, there were 7 fields again, so every new time there are 7? Yes, that's correct. You start with a clean modal each time.

Misty: If I understand correctly, each time we reopen the modal, we will get another 7? Therefore, if we have a bound-with that has 25 or more titles, we could continually re-open to fill in as many modal fields as necessary? Yes, seven was the number chosen so the modal wasn't too long and it was the average number of bound-with connections. 7 was much better than 1 and should fit on most screens. Can continually open until you get all your titles connected.

Lynne: Will these connections be populated if they were connected in the UI in other flower releases? If you just used the UI and not the backend interface?

Jeannette: What if you had more than seven titles attached to a single item?  How would this be handled? You can add as many as you like. Just need to keep clicking the add button and add in batches of 7 titles. Recommend saving your record so you don't lose any links as you go along.

Analyzed series: Parent/child relationships on Instance records. Instance to Instance relations

Bound-with relationship demonstrated is Item to Holdings relationship

This is new Poppy work. Planned Poppy release at the end of November (currently hasn't changed)

2023-11-2 Product Council Agenda and Meeting Notes

Announcements:

1. The Re-architectural tri-council working-group will kick start their work next week. Jenn Colt is the convener.
2. Bulk edit and the List app working groups will be merged, and will work more closely together going forward
3. Bugfest - still test cases needs to be claimed
4. FOLIO Days in Sweden 25-26 October - 2 days event, 60 participants from more than 15 institutions. Decided to form a Swedish FOLIO Community

 UAT "User Acceptance Testing" test (continued talk):

Jennifer explained how UAT is being planed planned and conducted for Bulk Edit. Here the test is done in a local sandbox environment during a meeting. This is a good way to generate a good discussion while doing the test. Other UAT e.g. for Data Import new work. Overall a positive experience. Kristin Martin has also participated in UAT on some Order functionality. A group at uChicago worked through a very detailed list of questions in a Google form. This was a time consuming effort. Good to do the work with colleagues at uChicago, and the result/outcome was shared with the Acquisition SIG. Martina Schildt agreed that the Google forms are very detailed. Tested FYRO. Took time, but worth the effort. A test like this should be scheduled at least for 2 weeks. 

PC would like to ensure that UAT are not just for people who attend given SIG very regularly, but a broader group can attend. A new slack channel # UAT was discussed  but no decided. The purpose would be to broaden the word out. There is a wiki page on planning UAT. 

Jenifer did notice that planning and executing UAT takes a lot of time for the POs. There is also a little tendency of fatigue on attending all the misc. tests: UAT, Bugfest, and then typical local test at the institution when doing upgrades.