Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Resource sharing settings control aspects of the ReShare system that relate to the Request and/or Supply apps.

...

Setting

Description

Values

Host LMS integration

Allows the user to specify their LMS for local integrations.

An option is available for each of the supported host LMS integrations.

Accept item

When an item is received by the requesting library, ReShare will create a temporary record in the LMS and place a hold for the requesting patron.

  • NCIP: This integration will be performed using the NCIP protocol.

  • None: This integration is disabled.

Borrower check

When a new request is placed, ReShare will look up the patron in the LMS to ensure that they have a valid account.

  • NCIP: This integration will be performed using the NCIP protocol.

  • None: This integration is disabled.

Check in item

When a request is completed, ReShare will check in the item in the LMS.

  • NCIP: This integration will be performed using the NCIP protocol.

  • None: This integration is disabled.

Check in request when returned by patron

When a request is marked returned by patron, ReShare will check in the item in the LMS.

  • On: This integration will be performed using the NCIP protocol.

  • Off: This integration is disabled.

Check out item

When a request is filled, ReShare will check out the item in the LMS to an institutional patron account.

  • NCIP: This integration will be performed using the NCIP protocol.

  • None: This integration is disabled.

ReShare will check out the item in the LMS to an institutional patron account.

  • NCIP: This integration will be performed using the NCIP protocol.

  • None: This integration is disabled.

Host LMS item loan policies

These settings allow the user to manually add and/or update host LMS item loan policy codes used by the auto-responder.

Note: Not all LMS return item loan policies as part of their z39.50 holdings response.

Setting

Description

Values

Item loan policy

A description of the name of the host LMS item loan policy as provided by a Z39.50 auto-responder response.

This field will contain the same value as the item loan policy code returned by the Z39.50 auto-responder response when a new item loan policy is added to a tenant’s list. This field is editable and the default item loan policy can be changed to a more descriptive name if desired.

Item loan policy code

The name of the host LMS item loan policy as returned by a Z39.50 auto-responder response.

This field will contain the exact value returned by the Z39.50 response when a new host LMS item loan policy is added to a tenant’s list. Once added to the list by the auto-responder, this field will be non-editable.

If a user manually adds a host LMS item loan policy to the list, the value entered in this field must exactly match what is returned in the host LMS’s Z39.50 response in order to work.

Lendable?

Determines if items with the item loan policy are considered lendable in ReShare

A ✔ in this field indicates that an item loan policy is considered lendable.

An ✖ in this field indicates that the item loan policy is not lendable.

Actions

A control that allows the user to toggle an item loan policy to the edit view or remove the entry from the list.

  • Edit (pencil icon): Allows the item loan policy description and lendable? fields to be edited.

  • Delete (trash can icon): Allows the item loan policy to be removed from the list. If the item loan policy is associated with a request, the item loan policy will not be deleted but hidden from display. The next time the item loan policy is returned by the Z39.50 auto-responder response it will re-display in the list with the same settings it had before it was “hidden”.

Host LMS locations

These settings allow the user to add and/or update host LMS locations, supplying priorities and related directory entries to locations used by the auto-responder.

...

These settings allow the user to manually add and update requesting privileges by patron profile / patron type as returned in the NCIP LookupUser response.

Note: In Release 1.8 the check on patron profile will only occur when staff submit a request on behalf of patron through the Request app. Release 1.9 will support the validation of a patron’s profile / blocking of placing a request when a patron attempts to place a request through discovery (e.g. VuFind).

...

Setting

Description

Values

NCIP app profile

The name of a profile configured within the local LMS to identify NCIP parameters specifically to be used for ReShare. The name of this profile will be defined locally and found within your local NCIP settings.

Free text

Format we expect the Due Date to be in

This field allows users to specify the format of the due date returned in the CheckoutItem response. Date formats vary by LMS.

[default] yyyy-MM-dd[ ]['T']HH:mm[:ss][.SSS][z][XXX][Z]

NCIP from agency

A code that defines the sender of an NCIP message. You must configure this within your local NCIP settings.

Free text

NCIP server address

The address of your local NCIP server. You should be able to get this information from your local NCIP settings or request it from your LMS vendor.

URL

NCIP to agency

A code that defines the receiver of an NCIP message. You must configure this within your local NCIP settings.

Free text

Use due date received from NCIP

A field that determines if the due date returned from the CheckoutItem response is used as the due date for the request in ReShare.

On

Off

Network

These settings allow users to control time variables for iso18626 messaging across tenants.

Network

Setting

Description

Values

Maximum number of times we attempt to send the message before we error (0 means we just keep retrying)

default = 0

If we hit a network error, number of minutes before we try again

default = 10

Number of seconds before we give up waiting for a response, after sending a message

default = 30

Other settings

Setting

Description

Values

Cancellation reasons

A reason for cancellation can be added by the requester when cancelling the request. The reason for cancellation will be visible to the supplier as a note. ReShare includes a default list of reasons.

  • Duplicate request

  • Requested item is locally available

  • User account is invalid

  • User requested cancellation

The library can add additional custom reasons to this list.

...