2020-06-04 Fulfillment & ILL FG Meeting notes

Fulfillment and ILL FG zoom meeting with ExLibris

Regarding Fulfillment Network configurations and rota templates:

Ideally inter-campus (UC) requests could be filled by campuses closest to them before going to a randomized rota.

SUNY divided their rotas into four parts. They are using Resource Sharing, in theory functionality should be the same.

Remote storage can be configured to be preferential to over other locations.

It could be that we create region specific rotas.

A number of rotas can be created and with partners assigned to them.

Fulfillment > Resource Sharing > Rota Assignment Rules: Configures how rotas are used.

Temporary items are created when using a fulfillment network.

Some things may be tested in the Vanguard.

Institutions can configure their indexes in Primo to prioritize search results based on different criteria. (physical location).

Migrating existing Alma patron databases:

These databases will be copied into separate IZs and be moved over as-is.

Vanguard access for FG:

Yes we will have access. Should be able to configure and test.

What happens if an Alma instance goes down?

All of the institutions will be on one server. If that server goes down it will affect all institutions.

In Fulfillment Network. What happens if an account is updated while another institution is lending an item simultaneously, what happens?

Each transaction is recorded separately. If the block exists, it should stop the transaction.

How long does it take to retrieve a user from their home institution?

This should be quick, like searching for any patron.

How do local blocks impact consortial borrowing?

Consortia blocks need to be configured and enabled.

Patron limits can be configured based on use group and can be set for walk-in patrons.

User groups set up in the NZ could override local configurations. If the settings are the same, this could be an option.

Consortial blocks have to be set manually. They can’t be triggered by an event like exceeding a loan or fine limit.

Existing internal records for students from other institutions. Can we pull in their stub account once migrated?

User records can be merged. It is recommended to merged to new linked account in Alma.

If a user has the same identifiers between different campuses. What appears as the stub record within an FN? Will Alma generate a new primary identifier?

When patrons are pulled into a new campus, they will be assigned a new identifier.

Linked accounts can be purged if they have nothing on their account.

What level of loan rule harmonization between institutions is required for a fulfillment network setup?

Consortia generally decide on common loan rules. They can also differ from campus to campus.

Can pick-up be set up for any institution?

Terms of Use (TOU) rules can be defined so that the user can select their pickup location.

A rule can be created with parameters and user groups set for fulfillment.

TOUs can be set up at the NZ and shared.

Everything is recorded at the item’s home institution.

Once the environment is delivered we can start working on configuration.

There are forms used to collect configuration information. This can be done at a future meeting.

It seems like rota based would give us more control of who lends.

Item based lending is easier to configure.

Parking Lot

x/x