Temporary list

What you can build

Patrons can browse and collect without an account, and keep what they found by saving it once they log in.

Typical flow

1. The client keeps the temporary list itself until the patron logs in.
2. The patron names the list.
3. The client creates it with CreatePatronList.
4. Each item is added with InsertItemToPatronList.

What the API provides

• The temporary list is not stored in PLAS. Only the saved list is.
• The client chooses the list's id when creating it.
• Items are added one call at a time. position decides where each one goes; without it, the item goes first.

What you can build

Patrons who have collected several titles reserve all of them at once, with one choice of pick-up location.

Typical flow

1. The client reads each publication's reserveId from GetHoldings.
2. The patron chooses where to pick up (2.5.8).
3. The client creates one reservation per publication with CreatePatronReservation.
4. The patron sees which reservations were made and which were not.

What the API provides

• There is no batch operation. Each reservation is its own call and can succeed or fail on its own.
• A publication without a reserveId cannot be reserved.
• Fees and the patron's reservation limits (daily, max) come from GetPatronConfiguration, as for a single reservation (2.5.1).