Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Voyager to Alma Migration Query: Review of System Administration Circulation Policy Patrons Tab

    Created By: Laura Guy (contact)
    Created on: 9/18/2020



    When migrating from Voyager to Alma it may be helpful to review Circulation Policy Group > Patron Group settings in the System Administration module.  This query lists the values for each Circ Group Policy/Patron Group pairing.

    This query, which you can run using Voyager Prepackaged Access Reports, provides the information configured in the System Administration Patrons tab.  Note that if the patron group displays as *all, this policy applies to all patron groups in the circulation policy group.

    SELECT CIRC_POLICY_GROUP.CIRC_GROUP_NAME,
    IIf([PATRON_GROUP_CODE] Is Null,"*all",[patron_group_code]) AS PatronGroupCode,
    IIf([PATRON_GROUP_NAME] Is Null," ",[patron_group_name]) AS PatronGroupName,
    PATRON_GROUP_POLICY.FEES_APPLIES AS FinesLostItemFeesApply,
    CCur([MAX_OUTSTANDING_BALANCE]/100) AS MaxOutstandingBalance,
    CCur([MIN_BALANCE_FOR_NOTICE]/100) AS MinBalanceForNotice,
    PATRON_GROUP_POLICY.COURTESY_NOTICE_APPLIES AS CourtesyNoticeApply,
    PATRON_GROUP_POLICY.OVERDUE_NOTICE_APPLIES AS OverdueNoticeApply,
    PATRON_GROUP_POLICY.MAX_ITEM_LIMIT AS MaxItemsBorrowedInThisPolicyGroup,
    PATRON_GROUP_POLICY.ITEM_LIMIT AS MaxItemsBorrowedInThisPolicyGroupValue,
    PATRON_GROUP_POLICY.MAX_OVERDUE_RECALL_LIMIT AS MaxOverdueRecalledItemsApply,
    PATRON_GROUP_POLICY.OVERDUE_RECALL_LIMIT AS MaxOverdueRecalledItemsApplyValue,
    PATRON_GROUP_POLICY.MAX_RECALL_LIMIT AS MaxNumberOfRecallsApply,
    PATRON_GROUP_POLICY.RECALL_LIMIT AS MaxNumberOfRecallsApplyValue,
    PATRON_GROUP_POLICY.MAX_SELF_SHELVE_LIMIT AS MaxSelfShelfReturnsApply,
    PATRON_GROUP_POLICY.SELF_SHELVE_LIMIT AS MaxSelfShelfReturnsApplyValue,
    PATRON_GROUP_POLICY.MAX_CLAIM_RETURN_LIMIT AS MaxClaimedReturnsApply,
    PATRON_GROUP_POLICY.CLAIM_RETURN_LIMIT AS MaxClaimedReturnsApplyValue,
    PATRON_GROUP_POLICY.MAX_LOST_LIMIT AS MaxLostItemsApply,
    PATRON_GROUP_POLICY.LOST_LIMIT AS MaxLostItemsApplyValue,
    PATRON_GROUP_POLICY.MAX_CALL_SLIPS AS MaxCallSlipRequestsApply,
    PATRON_GROUP_POLICY.CALL_SLIP_LIMIT AS MaxCallSlipRequestsApplyValue,
    PATRON_GROUP_POLICY.MAX_TOTAL_SHORT_LOAN AS MaxShortLoanApply,
    PATRON_GROUP_POLICY.TOTAL_SHORT_LOAN AS MaxShortLoanApplyValue,
    PATRON_GROUP_POLICY.MAX_TITLE_SHORT_LOAN AS MaxShortLoanTitlesApply,
    PATRON_GROUP_POLICY.TITLE_SHORT_LOAN AS MaxShortLoanTitlesApplyValue,
    PATRON_GROUP_POLICY.MAX_DAY_SHORT_LOAN AS MaxShortLoanPerDayApply,
    PATRON_GROUP_POLICY.DAY_SHORT_LOAN AS MaxShortLoanPerDayApplyValue,
    PATRON_GROUP_POLICY.MAX_OVERDUE_LIMIT AS MaxOverdueItemsApply,
    PATRON_GROUP_POLICY.OVERDUE_LIMIT AS MaxOverdueItemsApplyValue,
    PATRON_GROUP_POLICY.PLACE_HOLD_INSIDE_LIB AS PlaceHoldsUsingTheOPAC,
    PATRON_GROUP_POLICY.PLACE_RECALL_INSIDE_LIB AS PlaceRecallsUsingTheOPAC,
    PATRON_GROUP_POLICY.PLACE_SHORT_LOAN_IN_LIB AS PlaceShortLoansUsingTheOPAC,
    PATRON_GROUP_POLICY.PLACE_CALL_SLIPS AS PlaceCallSlipRequestsUsingTheOPAC,
    PATRON_GROUP_POLICY.EMAIL_COURTESY_NOTICE AS EmailCourtesyNotices,
    PATRON_GROUP_POLICY.EMAIL_CANCELLATION_NOTICE AS EmailCancellationNotices,
    PATRON_GROUP_POLICY.EMAIL_ITEM_AVAILABLE_NOTICE AS EmailItemAvailableNotices,
    PATRON_GROUP_POLICY.EMAIL_OVERDUE_NOTICE AS EmailOverdueNotices,
    PATRON_GROUP_POLICY.EMAIL_OVERDUE_NOTICE_OTHER AS EmailOtherOverdueNotices,
    PATRON_GROUP_POLICY.EMAIL_RECALL_NOTICE AS EmailRecallNotices,
    PATRON_GROUP_POLICY.EMAIL_OVERDUE_RECALL_NOTICE AS EmailOtherRecallNotices
    FROM (CIRC_POLICY_GROUP INNER JOIN PATRON_GROUP_POLICY
    ON CIRC_POLICY_GROUP.CIRC_GROUP_ID = PATRON_GROUP_POLICY.CIRC_GROUP_ID)
    LEFT JOIN PATRON_GROUP
    ON PATRON_GROUP_POLICY.PATRON_GROUP_ID = PATRON_GROUP.PATRON_GROUP_ID
    ORDER BY CIRC_POLICY_GROUP.CIRC_GROUP_NAME,
    IIf([PATRON_GROUP_CODE] Is Null,"*all",[patron_group_code]);

    For other queries that may be useful, see my "Surviving Almanado: tips for a successful pre-implementation" presentation's Accompanying Materials.

    If you need assistance in running custom SQL queries in Prepackaged Access Reports, consult the Voyager Customer Listserv.