Skip to content

Need additional handling for Scan request types for non-SAL3 items #2801

@saseestone

Description

@saseestone

For scan request types, we need to do some additional handling for requests dependent upon the scan destination (or the physical library doing the scanning)

In Folio location details, we have an existing key of "scanServicePointCode" and an associated value of the physical library doing the scanning. (i.e. SAL3 or GREEN)

We need to use that location detail value to determine what action to take in Folio, ILLiad or potentially neither.

For a value of SAL3: no changes needed. We should be creating an ILLiad transaction with all details from the request.
For a value of GREEN: create ILLiad transaction as we do now. Also create a Folio page request, with the Folio User Barcode = GRE-SCANDELIVER, and service point = Green Circulation Desk. Why? So the items appear on Folio pull slips for staff to retrieve and send to the Green scanning unit.

Coming soon
Marine Biology would like to add the ability to request a scan on their stacks items in February. They will be doing their own scanning, so we'll want to add a new value = MARINE-BIO then. An ILLiad transaction should be created as we do now for SAL3 and GREEN, but a different Folio User Barcode should be used. Once I have it, I'll submit a new ticket referencing this one.

Additionally....

Law, Business, and Lane are interested in allowing users to create a scan request through SearchWorks for their already existing scanning services. But instead of creating an ILLiad transaction, they would like the information to be provided to them in an email. I'll open another ticket when I have more of the details.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions