2024-05-28 BELA Meeting Notes
Attendees (please add your name):
@Magda Zacharska@Jennifer Eustis @Erin Weller @Sara Colglazier @Christine Tobias @Jackie Magagnosc @Erin Weller @Kathleen Moore @Kimie Kester @Thomas Trutt @Robert Scheier
Note Taker:
Christine Tobias, Jennifer Eustis, Lynne Fors
Meeting Recording:
Recording and chat: https://recordings.openlibraryfoundation.org/folio/bulk-edit-working-group
Discussion:
Topic | Notes | |
---|---|---|
1 | Housekeeping
| Notes: Jennifer Eustis
We have 2 new pages that track new ideas and features for both the Bulk Edit and List App. |
2 | Wolfcon 2024 | List of libraries that expressed interest in sharing their experience:
Is there anyone else also interested in sharing their experience? |
3 | Ramsons release update |
Instance notes are already in progress. MARC instance notes is being prepared. There will also be work on cross tenant ECS functionality in particular for Library of Congress. Demo for instances:
If the instance is source=MARC, then this will not update. There will be an error message saying the source=MARC and needs to be updated via the MARC Fields bulk edit.
In this instance, there statistical code isn’t found. This error will not prevent bulk editing. Do you think this is confusing and should we suppress records that don’t affect bulk edit? Should the information be kept to allow to act on bad data? You can download the errors from the action menu. Can we suppress the errors that don’t affect the job from display but in the Action menu logs to download? The easiest way is to suppress them. There is a feature to separate errors from warnings. This would fall under warnings. Do you think we should introduce the error and warning accordions? For issues that don’t affect bulk edit, they should go into warnings. Having this distinction is important. In various Apps, you see the word “error” and it has been changed. It’s difficult to know what is the “error”. It is important to make this distinction because this helps us expect certain behavior. Does this error/warning make sense as is? The error says statistical code was not found by id. It means that the code in the record has an statistical code UUID that doesn’t exist. Having a way to find bad data is super important. We tend to stumble across bad data. |
4 | Bulk edit queries - follow up from Slack chat | Bulk Edit Queries Examples and follow up questions about expected behavior and acceptable response time: Magda used this list for the query builder. Based on this list, Magda created a document.
The URL Relationship wasn’t included in the index and this can’t be searched using search or advanced search. Could we use this here in the bulk edit query builder? This would be Electronic Access field. Please review the spreadsheet. What would be the expected time to wait for the response? It would be nice to schedule a query build or have a message to come back when it’s ready. In the 90s, it was 10 sec was appropriate. If it a large export, some are willing to wait. In Nolana, Stanford waits up to 10 minutes for large files to load. Do you expect the query to filter out those instances that are staff suppressed or included in the query builder? Some of the circulation staff don’t have access. Having an option to include or not the staff suppressed would be great. Repeatable fields: Like Contributor: How do you search? It’s hard because there are so many variations. You might have to use contains or sometimes just use starts with. Would you in your search include both spellings of the name or just one? If you know all the variations, you could do an or search. OR is contains any. The important one here is Electronic access because there’s no way to search for this right now. For this and contributor, we search for this by searching on the various elements of that data field. For example, Electronic access contains any in the URL and have URL relationship of Resource. |
5 | Bulk Edit - in app approach - statistical codes - (UXPROD-3714) | Need clarification on whether bulk edit is supposed to update the statistical codes only in records and not in the Settings. 2 thumbs up. |