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

Future Fees/Fines: In-app report - Lost items for replacement consideration

    XMLWordPrintable

Details

    • UXPROD features
    • Hide
      Holly: The workaround would be for a library to run a query against the database (or data warehouse?) to see which items have been lost more than 6 months and cross reference the circulation data for the item to determine if the lost item is work replacing.
      Show
      Holly: The workaround would be for a library to run a query against the database (or data warehouse?) to see which items have been lost more than 6 months and cross reference the circulation data for the item to determine if the lost item is work replacing.
    • Medium < 5 days
    • Low
    • We haven't done any canned reports yet so I have no idea what will be involved.
    • Vega
    • 1
    • 0
    • R5
    • R4
    • R2
    • R4
    • R3
    • R4
    • R2
    • R2
    • R2
    • R2
    • R5
    • R5
    • R4
    • R4
    • R2

    Description

      Purpose: To supply the selectors with a list of items that have been lost and not replaced by patrons. Would be best to wait about 6 months before producing report, giving time for lost items to appear. Selector would want to see information about the item's usage--may decide to not replace item if not used much.

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases