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

Declared lost item: Manual fee setting for ACTUAL COST fee/fine type

    XMLWordPrintable

Details

    • Prokopovych

    Description

      Summary
      Each item that circulates has multiple policies associated with it, including a Lost Item Fee Policy. The Lost Item Fee Policy includes a setting that indicates if the patron should be charged a set cost for the lost item (example: $100 for a lost book) or the actual cost of a lost item. If a set cost is to be charged, the patron is billed automatically for the set cost indicated in the Lost Item Fee Policy. If the actual cost is to be charged, the patron cannot be billed automatically. Instead, the library must determine the actual cost to be billed to the patron and then enter a manual charge for the lost item. The manual charge Fee/fine type for "Lost item actual cost fee" (or whatever the library wants to call it) must be added in the Manual charges table, which can be done today. What needs to be added to the Manual charges table is a way to indicate which manual charge Fee/fine type is the one used for billing the patron for actual cost. This is needed in the case where the item is ultimately returned and a refund of a paid fee/fine or waive of an unpaid fee/fine is needed. FOLIO needs to be able to identify which transactions are related to the charging, paying, waiving, transferring, etc. of the actual cost fee.

      Concern
      This creation of this new setting fixes one problem, but creates another. A declared lost item may be returned many months (or longer) after the patron has paid the actual cost for a lost item. When CIRC-716 and CIRC-717 are accessing the Manual charges table to locate the Fee/fine type used when charging the lost item fee for the actual cost, the setting may have changed over the last 6 months or so. CIRC-716/CIRC-717 will assume the patron was not billed a lost item fee and, therefore, did not pay a lost item fee. The workaround will be for the library to issue a manual waive and refund. It's not the end of the world, but I want to point this out. I don't think it's worth saving historical values. At least not for the MVP.

      Scenarios

      1. Scenario
        Given Manual charges page within Settings > Users > Fee/fine
        When page displayed
        Then modify page to display as shown in attached mock-ups 1-fee-fine-manual-charges-view.PNG and 1-fee-fine-manual-charges-view2.jpg which includes -
        • New setting Use for actual cost above existing setting Default charge notice
        • Info logo to right of Use for actual cost with this test appearing if info logo pressed: "This fee/fine type will be used when charging lost item fee for actual cost of item." (As shown in attached mock-up 2-fee-fine-manual-charges-edit.PNG)
        • Light box around three settings (Use for actual cost, Default charge notice and Default action notice) edited via Edit button (to make it clearer that they are edited together)
        • Place EDIT button to top right of box mentioned above
        • Darken the text for Default charge notice and Default action notice
        • If possible, info logo to right of Fee/fine type selected as one to Use for actual cost,with this text appearing if info logo: "This fee/fine type will be used when charging lost item fee for actual cost of item." (As shown in attached mock-up 2-fee-fine-manual-charges-edit.PNG)
      2. Scenario
        Given Manual charge page displayed and no setting for Use for actual cost
        When EDIT button pressed
        Then populate drop-down for Use for actual cost with all manual Fee/fine types for Fee/fine owner
        (Note: Default charge notice and Default action notice are existing settings and should continue to work as they have been.)
      3. Scenario
        Given Manual charge page displayed and there is a setting for Use for actual cost
        When EDIT button pressed
        Then populate drop-down for Use for actual cost with all manual Fee/fine types for Fee/fine owner, with the currently selection option on displaying
        (Note: Default charge notice and Default action notice are existing settings and and should continue to work as they have been.)
      4. Scenario
        Given Manual charge page setting Use for actual cost changed to blank
        When SAVE button pressed
        Then save the changed value to Use for actual cost and go back to display mode for Manual charges page
      5. Scenario
        Given Manual charge page setting Use for actual cost changed to a different value
        When SAVE button pressed
        Then save the changed value to Use for actual cost and go back to display mode for Manual charges page
      6. Scenario
        Given Manual charge page setting Use for actual cost does not change
        When SAVE button pressed
        Then go back to display mode for Manual charges page
        (Note: This already happens. We do not check to see if anything has actually been changed to activate the SAVE button, nor do we confirm the change. If the user attempts to leave the page in the middle of editing we don't confirm that they really want to do that. It's not that critical.)
      7. Scenario
        Given Manual charges page in EDIT mode
        When CANCEL button pressed
        Then go back to display mode for Manual charges page
        (Note: This already happens.)
      8. Scenario
        Given Manual charges page in EDIT mode
        When SAVE button pressed
        Then save the changes and go back to display mode for Manual charges page
        (Note: This already happens. We do not check to see if anything has actually been changed or confirm the change. If the user attempts to leave the page in the middle of editing we don't confirm that they really want to do that. It's not that critical.)

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                hollyolepm Holly Mistlebauer
                hollyolepm Holly Mistlebauer
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases