2025-07-22 BELA Meeting Notes
@Attendees (please add your name)
@Magda Zacharska@Vivian Gould @Jennifer Eustis @Mary Aycock @Corrie Hutchinson @Amanda Ros @Sara Colglazier @Aaron Neslin @Jackie Magagnosc @Kimberly Pamplin @Kimie Kester @Kathleen Moore @Kim Wiljanen
Note Taker: @Jennifer Eustis
Meeting Recording
Recording and chat:Bulk Edit Working Group (FOLIO) | FOLIO Meeting Recordings
Links to Implementers' Topics
Bulk Edit Resource Management Implementation Topics Page
List App Resource Management Implementation Topics Page
Discussion:
Topic | Agenda | |
|---|---|---|
| 1 | Housekeeping |
Amanda is part of the Documentation SIG and will continue to search for someone to take over. It would be great to have someone familiar with the Users side. |
| 2 | Bulk edit |
The Trillium are mostly in refinement with a few blocked. Firebird will spend time on additional fields for bulk edit and the query builder. With the profiles, these will be in Settings. Some demo profiles will be created. The focus will be on the item profiles. Work to handle repeatable fields (see linked issue above): We will support the fields that have free text that are repeatable such as administrative notes. A list of fields will be defined. Kimie created some mockups for the instance, holdings, and items. See recording to see those. Question: What is the difference between contains and wildcard? There is a wiki page on Supported Operators for Repeatable Fields. This wiki page has examples for contains which is the old operator. There will a script for any lists that use the old operators. Those operators act on the entire string. The equals is the entire value of 1 field. Wildcards will be worked for Umbrellaleaf. Do wildcards have to be used at the beginning or end of the string? No. The wildcards can go wherever you want. This is very resource greedy - and queries may take longer to get results. Repeatable fields by Record Type: This lists the repeatable field and operators supported for each field such as Alternative title or administrative notes. For the Holdings records, the holdings statement and those statements for supplements and indexes will be added along with former identifiers. Query Classifications & Identifiers: Querying Classification document. Question: There is value in finding exactly the call number with the punctuation. Sometimes you need to find the ones you need to fix. The search is case insensitive. The search does preserve the spacing and punctuation. Rather than exact match, you could use contains to find the variations. Question: What about call number ranges? This isn’t in scope of this search. There is no support for less and greater than. These examples are useful. There is also a list of examples for the NLM Classification, Dewey Classification, and other. For Identifiers: LCCN search is case insensitive like above and spaces are removed at the beginning and end. The search does take into account spaces in the string. See examples in document. Bulk Edit 18 Month Roadmap: See presentation. 35 features completed, 3 features in progress, 39 features remaining of which 27 is to support new data, 3 for job scheduling, 5 for bulk deletion, and 4 for other enhancements. There are 3 areas to concentrate on: scheduling jobs, expand support for record types, support bulk deletion. Questions: Cancelling bulk edit jobs: If killed in the middle of a job, will the job have completed half and will there be a report out? It depends on when you kill the job. If a job is cancelled during updates, and some records are changed a report will be provided. You can revert the changes if you want. There is no automatic way to revert changes. The 3rd column for the bulk delete: Are the issues in priority? Yes, user records has been implemented in a robust way. For inventory, the dependencies aren’t handled in the back end only in the ui. Question: In our previous system, you could run the job without having the job take action and you would get a report on which records had dependencies. This was used to troubleshoot and cleanup. There was also an option to override the dependencies. Core functionality will be developed hopefully by the end of 2026. |
| 3 | Lists app |
|
| 4 | Implementation topics |