Skip to main content
  • Subscribe by RSS
  • ExLibris Dev


    How do members of a fulfillment network in Alma work together?

    Members of a Fulfillment network in Alma work together by allowing their patrons to interact directly with other institutions in that network. Additionally, these members may be willing to accept and process items from other institutions, and ship them back. Two primary use cases are currently supported:
    • Walk-in Registration
    • Direct requesting
    • Return Anywhere
    In a Fulfillment Network process, Alma’s standard loan and item transit processes are used. In other words, as long as the item is held by the borrower, the standard loan control mechanisms for tracking overdue loans is used. After the item is checked in, standard transit routines are used to track where the item has been put in transit, where the item has been put in transit to, and when it is expected to arrive at its target destination.
    A single institution may participate in multiple fulfillment networks.
    Walk-In Service
    Walk-in scenarios take place when a patron of another member institution directly walks into a library of another institution, requesting services. The guest user will be considered a patron of the host institution from a fulfillment perspective.
    Walk-in patron identification is described in the diagram below, where John Smith of institution A walks into institution B and requests to borrow an item of institution B:
    Below is a capture of the screen that is used by the circulation desk operator to identify a patron that is registered at another institution:
    By clicking ‘Find User’, the patron information will be fetched from the patron’s home institution. The copied information includes address information, email address and phone numbers, as well as the patrons’ general information. Do note that identifiers, being an institution specific attribute, are not copied over from the home institution.
    Attributes, such as the imported patron’s user group and expiry dates, may be set up at the target institution by rules that depend on where the patron record is copied from. This is illustrated below.
    The user group that is applied to the patron at the host institution will be used in the fulfillment rules of that institution. This effectively enables institutions to use standard fulfillment rules to set the terms of use that will be applied to fulfillment services that are given to guest patrons.
    After copy-over, the copied patron records are independent of their source. The patrons will receive fulfillment services and have their fines and fees independently managed at the host institution, based on the copied patron record and its attributes. That said, updates of the source record automatically update the target record whenever the patron is active at the target institution.
    The scenario will therefore be:
    1. Patron at the desk wants to check out an item
    2. The patron identifies himself with his ID at another institution and the institution he’s affiliated with
    3. Circulation Desk Operator inputs:
      1. Patron ID (at his home institution)
      2. Linked institution
    4. Alma looks up the user and replies with:
      1. Failed\succeeded indication
      2. A pop up of the supplied information
    5. Operator continues with check out action
    6. Overriding blocks may be set to be disallowed for external patrons
    Direct Requesting
    Direct Requesting is a service that allows patrons of one institution to discover request-able resources of another institution, and directly place hold requests to be fulfilled by the owning institution. The Direct Requesting service depends on the participating institutions managing a shared Primo view into which records of all of the institutions are published, and a shared authentication method that can authenticate users regardless of their home institution.
    The Direct Requesting process starts with a patron discovering a record that is owned by more than one institution. A ‘More’ indication will indicate that the record is owned not only by his home institution.
    Using the ‘More’ link allows the patron to view the request options of the other institutions and directly place a request at one of these institutions. Clicking on the Request link enables placing a request that will be fulfilled at a pickup location that is physically in one of the libraries of the owning institution, as per its local configurations.
    When placing direct requests, the patron record is automatically copied over from the patron’s home institution to the owning institution that will be fulfilling the request as a walk in service.
    Return Anywhere
    Alma’s Return Anywhere capability allows a user from one institution that has a resource directly loaned out from another institution directly to return it at his “home” institution. Alma identifies these cases and seamlessly handles them based on a “Check In For” relationship that is set up between the institutions. Setting up this relation means that the institutions have the logistic means to deliver checked in items to each other.
    The detailed scenario may be described as:
    1. Patron\non patron facing return is done at (a primary) desk
    2. Item is identified as not local
      1. The patron says ‘This book belongs to another institution’
      2. The labels on the book identify its owner institution
    3. Operator selects the institution (based on “Check In For” relations) and wands in
    4. Remote institution is notified of the check in, and:
      1. Discharges item
      2. Places item in transit

    How are cross-institutional authorizations managed?

    Cross-Institutional Authorizations
    To support cross-institution collaboration in a consortial environment, along with joint workflow processing, institutions can define relationships among them for the sharing of user information. Institutions can define with which institution they will work – i.e., which institutions they will link to for user data. In addition, institutions control:
    • The linking institutions to which they expose their user information – i.e., which institutions they’re willing to serve as a linked institution
    • The user types whose data may be exposed
    • The user data elements that they are willing to expose
    The diagram illustrates the relationship between the Linked Institution, which provides the user information, and the Linking Institution, which consumes the user information.
    Linking institutions retain a link to the source linked institution’s record, and internally cache the user information, facilitating quick search and display of user information. The linking institution controls the roles and privileges which will be assigned to linked users.
    Additionally, with Alma-Primo interoperability, patrons from an institution in a Fulfillment Network can request an item from another institution in the network using their home institution’s Primo. If the patron does not have a user name in the non-home institution, Alma will automatically create a linked user in the non-home institution.

    Does Alma support requesting and pickup options from different institutions in the network?

    Alma supports an end to end workflow that can involve a number of institutions. The following workflow describes a scenario where a patron at Institution A (Alma University) requests an item at Institution B (Open University) for pickup at Institution C (University of Knowledge):
    A patron from institution A searches for an item in Primo:
    When she checks the holdings she discovers that the item exists in her institution, but is marked as missing:
    However, she notes (in the bottom left hand corner) that there is an available copy in Open University (Institution B). 
    She clicks on the link to see more information:
    She then clicks on the Request option, filling in all the relevant parameters - including pickup at Institution C (University of Knowledge):
    The staff member at Institution B sees the request on the Pickup Requested Resources screen together with the information that the item needs to be sent to Institution C:
    The staff member prints the slip which includes information about the pickup location.
    The items barcode is scanned in, and gets the status 'In Transit' (to Institution C). The staff user can clearly see the destination of the item.
    A transit slip is printed:
    The staff member at Institution C receives items from Institution B, and scans in the barcodes after checking the box ‘Item from other Institution’, and selecting Open University (Institution B):
    The item goes on the hold shelf, and a notice is sent to the patron:
    The patron comes to Institution C, and identifies herself as a patron from Institution A. The staff user finds the patron after choosing the option ‘Find user in other institution’ and selecting the Alma University (Institution A):

    The item on the hold shelf is identified, and the barcode is read in after checking the box ‘Item from other Institution’ option, and selecting Open University (Institution B):

    The item is loaned to the patron. The transaction clearly shows that the library owner is Open University (Institution B)
    When the item is returned, a message displays that it needs to be sent back to Institution B:

    Can member institutions of the network share all of their users?

    A consortium that shares other aspects of their resource management, such as managing a shared catalog, may also manage a single shared user file. This is not yet implemented in the system today, but is on the roadmap for 2017. In this scenario, the user file is managed once and is accessible to all consortia members that need to make use of it.
    Sharing a single user file is not mandatory for implementing shared fulfillment between institutions. Consortia members may manage their user files independently of one another, sharing a specific patron’s information on a ‘just in time’ manner – when the patron requests or borrows an item from another institution. When sharing patron information is done in this manner, institutions may hide some user types from having their information being shared with other institutions.
    Another applicable model is based on an ILL model, allowing resources of different institutions to be shared without sharing any patron information.

    Total views:

    • Was this article helpful?
    // feedback widged