Bulk Edit Use Cases

Have the ability to identify a batch of item records with the same characteristic (e.g. temporary location = course reserve) and change them (e.g. remove the temp location)

Would expand to cover items matching multiple characteristics.

Would also want to be able to perform this based on a text list of barcodes, item hrids or item uuids.

Maybe ETL, but difficult to isolate single items on instances with multiple items

Have the ability to identify a batch of holdings records with the same characteristic (belonging to a set of batch loaded materials, in a particular location and belong to a particular campus) and then perform a change on any field in the FOLIO holdings. This change could include adding a prefix or suffix to urls or updating the url in holdings for electronic resources.

Would expand to cover holdings matching multiple characteristics.

Would also want to be able to do this based on a text list of hrids or uuids for the holdings records.

Inventory: Holdings

SRS: MARC Holdings

Difficult to isolate single holdings on instances with multiple holdings

Identify and isolate records in need of clean-up, for examples

• when the URL for our proxy server changes and we need to update 900,000 bib records to reflect the accurate URL.
• when adding a few million Hathi ETAS records for discovery (and then removing them!)

None known, except by staff labor. 

For URL changes, we "could" export the whole catalog, work in an outside system, and then overlay the identified records. This work-around is only functional when match and overlays are working for SRS records.

One-by-one processing

My understanding is that item status workflows will have their own logic / permissions to govern who can change a particular item status and who can't - so I'm not sure if that would make this its own use case or not.

Med

One by one. Currently data import doesn't do this.

ETL

Have the ability to identify approval order records from a specific date/load and update the vendor codes for those records

More generally, create a list of orders and bulk/rapid update funds, vendors, requestors, and notes.

Have the ability to identify SRS records containing specific MARC coding and bulk update that code. 

Example: When Czechoslovakia split into the Czech Republic and Slovakia, the country code for Czechoslovakia (cs) was replaced by xr (Czech Republic) and xo (Slovakia).

Example: One collection originally coded all names as personal names (700 field). We identified and recoded most of the corporate body names.

Add a similar feature to Sierra Global Update that allows you to see the data from the fields of the same type (author, subject, title, etc.) present in a set (review file) of records.  

Use case – Identify bib records from the daily headings reports that have not been sent for authorities processing. 

Example: Backstage inserts a code indicating that a bib record has been processed in the 040 field. I can view all the 040 fields from a set of records using the “toggle” function in Global Update and select records for future authorities processing. 

Use case – Find patterns of problems in a set of records. 

Example: During record loading, some MARC fields may end up being duplicated. Sierra Create List searching cannot find duplicate fields, but the “toggle” function in Global Update helps identify affected records. 

Ability to temporarily add or remove a MARC field in SRS.

Use case – To temporarily exclude some bib records from authorities processing, we add a 9XX note and re-write the monthly search query to exclude records using that note. 

Example: The recent EEBO record load was huge, so we had to temporarily exclude them from the month’s authorities processing query.  

One-by-one processing via UI, or scripting with existing APIs

Bulk edit to change due dates, considering pandemic situation or short-term temporary closure of a library/location), needs further clarification, e.g. execution based on which characteristics, all loans, loans from specific effective item location, specific library, etc.? Staff user should be prompted to enter the new due date.

Bulk renewals are business logic actions and should be looked at separately from the Bulk Edit app - 

What is the relationship to the applied loan policy (e.g. number of renewals allowed, loan period for renewals)?

Perhaps to be considered together with UXPROD-2375 (Automatic renewals)

Bulk edit expiration date for users. Criteria: Patron group, current expiration date, Blocking status, Department, Custom fields, etc.

Have the ability to identify a batch of instance records with the same characteristic (belonging to a set of batch loaded materials, with a particular status) and then perform a change on any field in the Instance or underlying SRS.

Would expand to cover instances matching multiple characteristics.

Would also want to be able to do this based on a text list of hrids or uuids for the instance records.

Batch delete items: Identify a batch of item records (e.g. scan barcodes, list of UUIDs, file from query) and delete all of them

*should not be able to delete any that are tied to, e.g., order or user data (item status checked out, on order, etc.) – system either does not delete these or gives warning and requires approval before deleting

Batch delete holdings: Identify a batch of holdings records (e.g., list of UUIDs, file from query) and delete all of them (including any underlying SRS records)

*should not be able to delete any that have dependent items – system either does not delete these or gives warning and requires approval before deleting

Batch delete instances: Identify a batch of instance records (e.g., list of UUIDs, file from query) and delete all of them (including any underlying SRS records)

*should not be able to delete any that have dependent holdings – system either does not delete these or gives warning and requires approval before deleting

Mark as suppressed (from discovery or from staff... or both):

Identify a batch of Instances and all associated holdings/items; Holdings and all associated items; or Items --

Mark all as suppressed

for Holdings, mark any associated items as suppressed also

for Instances, mark any associated holdings and any items associated with them as suppressed also

Mark for deletion:

Identify a batch of Instances and all associated holdings/items; Holdings and all associated items; or Items --

Mark for deletion

for Holdings or MARC Holdings, mark any associated items as suppressed also

for Instances, mark any associated holdings and any items associated with them as suppressed also

Ability to identify records with certain characteristics (a particular 650, for example) and permanently add a MARC field in SRS and Instance to those records.

Use case: In-house record enhancements (adding new controlled vocabularies such as LCGFT or LCMPT)

Bulk edit Patron blocks based on a list/file of users to be uploaded.

Use case: In Leipzig we get 

Move data from one type of record to another within an app

Example: I have a local note in my instance records. I want to move this note to any holdings records associated with these instances. Effectively, this requires copying the note(s), adding them to the associated holdings, deleting them from the instances.

Inventory: Instances, Holdings, Items

Others?

Metadata Management

Resource Management

ERM

User Management

We have identified mold in our stacks. Items in specific stack ranges need to have their Status changed to Unavailable (while they are sent off site for remediation). I need to identify the Items by their call number ranges and then bulk edit their Status. Once the items are returned, I will need to reverse the process.

See line 9 above for a similar use-case (added by Jacquie)

General / Consortia

Metadata Management

General / Consortia

Metadata Management

Ability to apply logic/calculations/conditions to bulk edit changes. For example formula for updating patron expiry, applying changes to fields when a certain value is met, or exceeded, or to apply changes only when a field is equal to a certain value.

Another example: during bulk edit on items, only change the item status to "Long missing" if the current status is "Missing"

?

High

• Change a large number of locations from active to inactive, or from inactive to active;
• Add or remove a service point if a library is changing buildings and/or service models;
• Add or remove a remote storage association

Manually add/create one-by-one

Data Import matching on Instance and holdings to create item records (currently only able to create one item record at a time)

Bulk adding a MARC field or replace a field in SRS MARC bibliographic records matching on an identifier (OCLC number, HRID)

Example: We need to add a unique 856 field to each MARC record after generating URLs from our digital repository (using a spreadsheet). Each record will have its own unique URL applied at the completion of the bulk edit.

Instance

SRS MARC bibliographic

Changing the Holdings electronic access relationship type.

We need to update the relationship type of the electronic access in the holdings. For example, from Resource to Related Resource