Uploaded image for project: 'ui-users'
  1. ui-users
  2. UIU-1156

CRUD Fee/Fine Lost Item Fee Policies

    XMLWordPrintable

Details

    • UNAM

    Description

      Purpose: Allow staff member to create/review/update/delete a lost item fee policy to be associated with a loan policy by the Circulation Rules Editor.

      SCENARIOS

      1. Scenario
      Given Settings ==> Circulation
      When displayed
      Display in format as show by attached screen mock-up 1-with-headings.png, adding Lost item fee policies for this user story

      2. Scenario
      Given Settings ==> Circulation ==> Lost item fee policies
      When no Lost item fee policies exist
      Then display blank list of existing Lost item fee policies as show in attached mock-up 1-with-headings.png, with option for adding a new one

      3. Scenario
      Given Lost item fee policies
      When New button selected
      Then open New lost item fee policy page as shown in attached mock-ups 2-new-lost-item.png and 3-new-lost-item-save.png, using defaults as shown in mock-up
      Validation

      • Lost item fee policy name is a required field and must be unique for the institution
      • If Items aged to lost after overdue entered, must be 0 or > 0 and, if > 0 must have interval selected
      • If Patron billed after aged to lost entered, must be 0 or > 0 and, if > 0 must have interval selected
      • Charge amount for item may be Actual cost or an amount, with a default of Actual Cost
      • Charge amount for item must be = 0 or > 0
      • Lost item processing fee must be = 0 or > 0
      • Charge lost item processing fee if item declared lost by patron must be Yes or No, with default set to Yes
      • Charge lost item processing fee if item aged to lost by system must be Yes or No, with default set to Yes
      • If For items not charged a fee/fine, close the loan after entered, must be 0 or > 0 and, if > 0 must have interval selected
      • Replacement process fee must be = 0 or > 0
      • Replacement allowed must be Yes or No, with default set to Yes
      • Lost item returned or renewed may be Charge overdues based on returned date up to maximum (if applicable) or Do not charge overdues, with a default of _Charge overdues based on returned date up to maximum (if applicable)
      • If No fees/fines shall be refunded if a lost item is returned more than entered, must be 0 or > 0 and, if > 0 must have interval selected
      • The field For items not charged a fee/fine, close the loan after is required in certain cases
        • Optional if Charge amount for item > 0 OR
        • Optional if Lost item processing fee > 0 AND Charge lost item processing fee if item declared lost by patron is Yes AND Charge lost item processing fee if item aged to lost by system is YES
        • Required in all other cases (error message if not entered: "This field is required if there is a possibility of no fee/fine being charged for a lost item"

      Save & close button should remain grayed out until all validation has been passed

      4. Scenario
      Given New lost item fee policy
      When Save & close button selected
      Then save entered data and display success toast as shown in attached mock-up 4-with-lost-item.png

      5. Scenario
      Given Settings ==> Circulation ==> Lost item fee policies
      When one or more Lost item fee policies exists
      Then display list of existing Lost item fee policies as show in attached mock-up 1-with-headings2.png, with option for adding a new one

      6. Scenario
      Given the Lost item fee policies list
      When one is selected to view
      Then display details of policy per attached mock-up 5-view-lost-item-policy.png

      7. Scenario
      Given the viewed Lost item fee policies
      When Edit button is pressed
      Then present full-screen version of Lost item fee policy for editing, as shown in attached mock-up 6-lost-item-edit.png
      Save & close button is grayed out until a field is edited and validation is complete

      8. Scenario
      Given the Edit - <Lost item fee policy name> page (as shown in attached mock-up 6-lost-item-edit.png)
      When Cancel option is selected
      Then reset fields to original values and close out page, going back to previous page

      9. Scenario
      Given the Edit - <Lost item fee policy name> page (as shown in attached mock-up 6-lost-item-edit.png)
      When Delete option is selected
      Then display Confirm deletion modal (as shown in attached mock-up 7-lost-item-delete-confirm.png)

      10. Scenario
      Given the Confirm deletion modal (as shown in attached mock-up 7-lost-item-delete-confirm.png)
      When Cancel button pressed
      Then close out Confirm deletion modal and display Edit - <Lost item fee policy name> page again

      11. Scenario
      Given the Confirm deletion modal (as shown in attached mock-up 7-lost-item-delete-confirm.png)
      When Confirm button pressed
      Then delete policy, close out page, going back to previous page, and display success toast as shown in attached mock-up 8-lost-item-delete-success.png

      12. Scenario
      Given Edit - <Lost item fee policy name>
      When changes made and validated
      Then Save & close button becomes active

      13. Scenario
      Given Edit - <Lost item fee policy name>
      When Save & close button pressed
      Then save changes and close out page, going back to previous page, and display success toast as shown in attached mock-up 9-lost-item-update-success.png

      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      DESCRIPTION

      The purpose of this user story is to allow a staff member to associate a lost item fee policy with a loan policy in the circulation rules editor. The circulation rules editor requires that each policy type be present, so even libraries that do not charge lost item fees will need one lost item fee policy set to 0 that is used by all circulation rules.

      The first step in this task to to change the design of the Settings ==> Circulation section of FOLIO as shown in the attached screen mock-up 1-with-headings.png" and "1-with-headings2.png. This section was getting very crowded and the designer decided to organize it. The "Fee/fine" section with two options is new. This user story focus on "Lost Item fee policies" only.

      The functionality of "Lost item fee policies" is very similar to the other policies within the "Circulation" section. We need to be able to create new policies, review existing policies, update existing policies, and delete unneeded policies, as shown in the attached screen mock-ups.

      The field validation is as follows:
      * Lost item fee policy name is a required field and must be unique for the institution
      * If Items aged to lost after overdue entered, must be 0 or > 0 and, if > 0 must have interval selected
      * If Patron billed after aged to lost entered, must be 0 or > 0 and, if > 0 must have interval selected
      * Charge amount for item may be Actual cost or an amount, with a default of Actual Cost
      * Charge amount for item must be = 0 or > 0
      * Lost item processing fee must be = 0 or > 0
      * Charge lost item processing fee if item declared lost by patron must be Yes or No, with default set to Yes
      * Charge lost item processing fee if item aged to lost by system must be Yes or No, with default set to Yes
      * If For items not charged a fee/fine, close the loan after entered, must be 0 or > 0 and, if > 0 must have interval selected
      * Replacement process fee must be = 0 or > 0
      * Replacement allowed must be Yes or No, with default set to Yes

      * Lost item returned or renewed
      may be Charge overdues based on returned date up to maximum (if applicable) or Do not charge overdues, with a default of _Charge overdues based on returned date up to maximum (if applicable)
      * If No fees/fines shall be refunded if a lost item is returned more than entered, must be 0 or > 0 and, if > 0 must have interval selected
      * The field For items not charged a fee/fine, close the loan after is required in certain cases
      – Optional if Charge amount for item > 0 OR
      – Optional if Lost item processing fee > 0 AND Charge lost item processing fee if item declared lost by patron is Yes AND Charge lost item processing fee if item aged to lost by system is YES
      – Required in all other cases (error message if not entered: "This field is required if there is a possibility of no fee/fine being charged for a lost item"

      After adding a new "Lost item fee policy" or updating/deleting an existing "Lost item fee policy", a "success toast" should be displayed. Prior to deleting an "Lost item fee policy" a confirmation modal should be displayed. (Mock-ups are attached.)

      Please see Holly with any questions or comments. Thanks!

      TestRail: Results

        Attachments

          1. 1-with-headings.png
            1-with-headings.png
            91 kB
          2. 1-with-headings2.png
            1-with-headings2.png
            82 kB
          3. 2-new-lost-item.png
            2-new-lost-item.png
            126 kB
          4. 3-new-lost-item-save.png
            3-new-lost-item-save.png
            127 kB
          5. 4-with-lost-item.png
            4-with-lost-item.png
            99 kB
          6. 5-view-lost-item-policy.png
            5-view-lost-item-policy.png
            177 kB
          7. 6-lost-item-edit.png
            6-lost-item-edit.png
            138 kB
          8. 7-lost-item-delete-confirm.png
            7-lost-item-delete-confirm.png
            139 kB
          9. 8-lost-item-delete-success.png
            8-lost-item-delete-success.png
            98 kB
          10. 9-lost-item-update-success.png
            9-lost-item-update-success.png
            86 kB
          11. changes-lost-item.jpg
            changes-lost-item.jpg
            155 kB
          12. screenshot-1.png
            screenshot-1.png
            21 kB

          Issue Links

            Activity

              People

                lluviaDGB Lluvia Manilla
                hollyolepm Holly Mistlebauer
                Holly Mistlebauer Holly Mistlebauer
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases