[OPEN-ILS-GENERAL] Self Check / ILL issue - Blocking checkout

[Ben Shum]

Presuming you mean the Evergreen web selfcheck, I could only think of
a workaround approach like follows:

If you were to designate the workstation for the selfcheck to be a
different org unit (like an opac invisible child unit of the parent
library), then include a circ policy in circ_matrix_matchpoint that
says, don't circ items of a particular copy location (the ILL one) or
circ modifier (if you have an ILL circ mod?), but leave the rest to
fallthrough back up to the parent org unit rules, then the selfcheck
could function differently with regards to those materials.

Otherwise, I've found it more common that staff wanted items to be
completely restricted and not allowed for checkout (i.e. circulate =
false on the item or copy location levels) and to deal with it at the
desk as you hint would be burdensome.

Some development required maybe if we want to avoid any crazy
workarounds like the one I posit above.

And if you're talking about SIP2-based selfchecks, that's a whole
other ball game entirely....

Just thinking aloud, hope some of that might prove helpful.

-- Ben

On Wed, Apr 6, 2016 at 12:02 PM, Josh Stompro
<stomproj at exchange.larl.org> wrote:
> Hello Everyone,
>
>
>
> My coworker is working on an issue with out of state ILL items, that we
> always want to have due on a specific date, even when the customer doesn’t
> pickup the item right away.  And she has been trying to figure out if there
> is a way to block a specific item from being checked out at the self check,
> but allow it to be checked out by staff without using an override.
>
>
>
> With these items we don’t want them to go on the holdshelf, since we need
> staff to read the documentation attached and set a specific due date.  But
> they will accidentally get placed on the hold shelf, so we would like the
> self checks to not process the checkouts.
>
>
>
> I’ve looked at hard due dates documentation, but that doesn’t seem like it
> would since this situation isn’t what it was designed for.  We have also
> looked at using item alerts, but blocking based on the alert event would
> affect too many users negatively in our system since we use the alerts for
> situations that don’t require a checkout to be blocked.
>
>
>
> We would like to avoid setting the items to non-circulate since that would
> require staff to override, which we don’t want to be a common occurrence
> that staff get used to.
>
>
>
> If something to address this doesn’t already exist, would anyone else find
> it useful to be able to block checkouts at the self check for specific
> items, but allow the checkout for staff users without an override?  Maybe
> the self check could block based on a list of circ_modifiers?  If something
> like this may be useful to more than one location, it might make a good
> enhancement.
>
>
>
> Thanks
>
> Josh
>
>
>
> Lake Agassiz Regional Library - Moorhead MN larl.org
>
> Josh Stompro     | Office 218.233.3757 EXT-139
>
> LARL IT Director | Cell 218.790.2110
>
>