Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-82

Automated Patron Blocks

    XMLWordPrintable

    Details

    • Template:
    • Potential Workaround:
      Hide
      Holly: We currently have Manual Patron Blocks, which are set in User Information. Automated Patron Blocks allow the library to set limits that are enforced automatically. For example, if a patron owes over $100 in fines they can be automatically blocked from checking out any more items. Or they can be blocked if they have more than 10 claimed-returns, etc. Whatever limits the library wants to set. The workaround for this would be for the library to run a query against the database (the data warehouse?) to find out who is violating their rules and then enter Manual Patron Blocks for the patrons who need to be stopped.
      Show
      Holly: We currently have Manual Patron Blocks, which are set in User Information. Automated Patron Blocks allow the library to set limits that are enforced automatically. For example, if a patron owes over $100 in fines they can be automatically blocked from checking out any more items. Or they can be blocked if they have more than 10 claimed-returns, etc. Whatever limits the library wants to set. The workaround for this would be for the library to run a query against the database (the data warehouse?) to find out who is violating their rules and then enter Manual Patron Blocks for the patrons who need to be stopped.
    • Epic Link:
    • Front End Estimate:
      Large < 10 days
    • Back End Estimate:
      XXL < 30 days
    • Confidence factor:
      Medium
    • Estimation Notes and Assumptions:
      Hide
      The estimate on this feature was very low prior to October 1, 2019, but was raised after it was discussed in detail with the RA SIG.
      Show
      The estimate on this feature was very low prior to October 1, 2019, but was raised after it was discussed in detail with the RA SIG.
    • Development Team:
      Vega
    • Calculated Total Rank:
      122
    • PO Rank:
      97.7
    • Rank: BNCF (MVP Feb 2020):
      R1
    • Rank: Chalmers (Impl Aut 2019):
      R4
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R2
    • Rank: FLO (MVP Sum 2020):
      R4
    • Rank: GBV (MVP Sum 2020):
      R2
    • Rank: hbz (TBD):
      R1
    • Rank: Hungary (MVP End 2020):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R1
    • Rank: Leipzig (Full TBD):
      R1
    • Rank: Leipzig (ERM Aut 2019):
      R5
    • Rank: MO State (MVP June 2020):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R1

      Description

      Feature Split on June 19, 2020

      Feature UXPROD-2547 was split from UXPROD-82 because two automated patron blocks user stories were not completed by the Q2 2020 deadline:

      Until MODPATBLK-18 is completed, the following automated patron blocks will not work...

      • Maximum number of overdue items
      • Maximum number of overdue recalls
      • Recall overdue by maximum number of days

      The following automated patron blocks are available as of Q2 2020...

      • Maximum outstanding fee/fine balance
      • Maximum number of items charged out
      • Maximum number of lost items

      We originally had one JIRA feature (UXPROD-82) that was for both automated Item Blocks and Blanket Blocks. Given that Item Blocks will use Loan Policies/Rules rather than the Patron Group Limits Table (UXPROD-390) to determine criteria for blocking, it makes more sense to separate the two types of automated blocks. Item Blocks are now covered by UXPROD-1591.

      The Patron Group Limits Table (UXPROD-39)0 will be used to identify criteria institution wants to use in determining who to block and from what. The limits needed by each FOLIO institution have been recorded at https://docs.google.com/spreadsheets/d/1ePWOFp6wNe4GchNsFMIhvZ46RsNvMSq8FmUbrqLRd4c/edit?usp=sharing. The attached document Patron Blocks Mockups.pdf includes what was beings considered the last time the Product Owner/Resource Access SIG discussed Patron Blocks, which was quite some time ago.

      Updated 9/18/18: Holly changed Chalmers rank from go-live after emailing Lisa and learning they only need manual patron blocks for go-live. Manual patron blocks have been broken out of UXPROD-82.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                hollyolepm Holly Mistlebauer
                Reporter:
                cboerema Cate Boerema
                Front End Estimator:
                Holly Mistlebauer Holly Mistlebauer
                Back End Estimator:
                Holly Mistlebauer Holly Mistlebauer
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases