2023-11-28 List App Meeting Notes

Housekeeping

• Attendees  - please add your name to the list of attendees
• Meeting host -  please turn on Transcript option for the meeting 
• Who can take notes today?

Lists app - duplicating a list - UXPROD-4454

Powerpoint with mockups 

Users want to use an existing list as a starting place to create a new list. This will allowing for quick list creations/variations without having to build the query from scratch.

• When duplicating a list, the QUERY for the list is duplicated. The record set of the list does not change. 
• users can duplicate an existing user created list, or a canned list
• the new list is prepopulated with the query from a source list, which can be edited prior to saving a list
• by default the name of the new list should have a suffix to make it distinct from the list it's a copy of. Something like "List name - copy"
• an alternative that's used elsewhere in folio is forcing the name to be changed in order to save. 

Takeaways:

1. The consensus was that we do not need to remove the requirement to test a query prior to saving a list. 
2. Should consider renaming the 'Test query' button, as well as changing the placement to make it more user friendly

Notes/discussion:

Q: When is testing a query required?

• when creating a new list and building the query, the query needs to be tested, then the list can be saved
• when editing the query of an existing list, the query needs to be tested prior to saving
• the query does not need to be tested to refresh the record set for an existing list
• from the Lists app documentation: "Click the **Test query** button to see how many records are returned and to preview the record set of the list. The first 100 records will display in the preview pane and the total count of records will appear at the top of the preview pane."

What are the expectations for testing when creating a list? 

• Preference to use 'Test' button to preserve resources. Concern of bringing down other areas of folio by mistake by running multiple large lists at the same time (might be done by accident by different departments)
• Do you need to be able to see sample results? yes
• Do you need to wait for the count to return? yes - provides valuable info if you're only expecting a few hundred records but thousands are returned
• Does the count need to be exact? 
• Is there value in being able to create a list without testing it? perhaps, however, conserving resources via the 'test' button was the preferred approach

Powerpoint with takeaways