OpenRS check-in: pickup-aware pull slips and a completed return

The 12 July checkpoint stopped with the item travelling back to its supplier. This run closes that gap: Hogwarts records the returned copy, DCB reaches FINALISED, and supplier pull slips now carry scannable identifiers and the actual pickup destination. This remains local smoke evidence, not a production-readiness claim.

ORS-Appliance is the library-facing bridge between local catalogue, identity, and staff work and the resource-sharing network. Its DCB integration uses NCIP v2.02 rather than requiring a proprietary client and protocol.

The local stack was rebuilt from clean volumes with dcb-ops/docker-local/qa-local.sh clean and qa-local.sh start. Then qa-local.sh smoke-fallback-host-dcb-request exercised Direct and PickupAnywhere routing across the synthetic Hogwarts, Unseen, and Chiark tenants. The automated path completed supplier and borrower circulation, supplier return receipt, DCB FINALISED, the NOT_SUPPLIED branch, and pull-slip batch generation. The running environment was then inspected in ORS-Appliance and DCB Admin for these screenshots.

Tested revisions: DCB Service 6a4afa6bb; DCB Admin 4db0de56; ORS-Appliance 4bec88e; ORS-Appliance SPA d6285c0; Discovery Service 7947d8c; Discovery SPA 89b34b4; and DCB Ops 595a741. All shown patrons, holdings, locations, and credentials are local QA fixtures. Physical printer/scanner use, accessibility, and production deployment were not tested. The environment remains available for inspection.

Pull slips start from supplier work

Supplier staff can group requests by item location and print the waiting shelf-search batch. The queue count reflects work not yet issued as a pull slip; printing the batch advances that local work, while reprinting later does not change the network request.

Hogwarts ORS-Appliance pull-slip queue with one request awaiting printing. — Hogwarts has one current shelf-search request, filterable by item location.

PickupAnywhere makes the distinction between borrower and collection point explicit. Here Unseen is the borrowing library, Hogwarts is the supplier, and Chiark Orbital Main Library is where the patron will collect the item. The supplier sees that route before retrieving or shipping the copy.

Hogwarts supplier request showing Unseen as borrower and Chiark as pickup destination. — The supplier request names the pickup library, location code, address, and PickupAnywhere workflow.

Reprint is a safe local action

The request page can prepare the supplier slip again without changing request state or sending another protocol message. Staff get a review step before opening the browser print dialog.

ORS-Appliance pull-slip reprint preview for a PickupAnywhere request. — A prepared reprint stays within the supplier workflow and preserves request state.

The printed page is the operational artefact. It includes the title, call number, item identifier, item barcode, request reference, patron and requesting library, plus the pickup name, code, address, and workflow. Code 128 barcodes cover both the item and request reference.

Printable pull-slip page with two barcodes and Chiark pickup-routing details. — The exact page rendered for printing: shelf-search data, two scannable references, and the real destination.

The return now closes

After the borrower ships the item back, supplier staff record its arrival. ORS-Appliance retains the supplier-side physical truth as SUP_RETURN_RECEIVED; the supply record is RETURN_RECEIVED, and no further supplier action is offered.

Hogwarts supplier request after the returned copy has been received. — Hogwarts has received the returned copy and the supplier workflow is complete.

DCB consumes that final evidence and closes its corresponding request. The current broker state is FINALISED, following COMPLETED, with the tested supplying and pickup agencies still visible.

DCB Admin request detail showing current status Finalised. — DCB Admin provides the network-side evidence that the request reached `FINALISED`.

What remains

This checkpoint turns the previous return-transit endpoint into a completed local lifecycle and gives supplier staff a useful physical document. The next proof should use real scanners and printers, measure keyboard and focus behaviour, and run the same path in an operator-managed environment with production-grade transfer, credential, monitoring, and recovery controls.