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

CRUD Patron Notice Policies - Loan-related notices only (part 1)

    Details

    • Epic Link:
    • Analysis Estimate:
      Large < 10 days
    • Front End Estimate:
      XL < 15 days
    • Back End Estimate:
      XXL < 30 days
    • Estimation Notes and Assumptions:
      Hide
      Modified issue - logic in notice policies instead of workflow or other policies (loan, fee/fine, request). Need new estimates. BE estimates assumes the scheduling, event triggers/listener logic is built specifically for PN rather than relies on existing functionality provided though UXPROD-594 and UXPROD-729

      Jakub: XXL for the backend since this may include coding internal scheduling logic. XL for the UI, the assumption is all logic lives on the server and UI is merely a configuration interface.
      Show
      Modified issue - logic in notice policies instead of workflow or other policies (loan, fee/fine, request). Need new estimates. BE estimates assumes the scheduling, event triggers/listener logic is built specifically for PN rather than relies on existing functionality provided though UXPROD-594 and UXPROD-729 Jakub: XXL for the backend since this may include coding internal scheduling logic. XL for the UI, the assumption is all logic lives on the server and UI is merely a configuration interface.
    • Development Team:
      Vega
    • Rank: Chalmers:
      go-live
    • Rank: Chicago:
      go-live
    • Rank: Cornell:
      go-live
    • Rank: 5Colleges:
      go-live
    • Rank: Lehigh:
      go-live
    • Rank: TAMU:
      go-live
    • Rank: U of AL:
      go-live
    • Rank: Bremen:
      go-live

      Description

      IMPORTANT NOTE: As a first pass, this feature has been modified for notices sent via email related to loan activities only. There are new features created for request-related notices and fee/fine-related notices as well as SMS and print notices.

      Needs to allow for scheduling, event triggers/listeners, and other conditions. This function will be configured using in policies, including loan, request and fee/fine policies, and general configuration for notices. Early hand-drawn mockups are attached.

      See UXPROD-110 for earlier reference to patron notices, as well as UXPROD-675 and UXPROD-723 for setting up the name, description and templates.


      Initially thought Workflow would be the right solution. Here's the original thinking on that:
      A visual representation of one use case is attached. It assumes a UI will be developed for the workflow engine. The attached visual shows two different notices sent at different points in time, overdue notice #1 is sent at Day 1 (maybe immediately is more appropriate here), and then overdue notice #2 is sent at Day 3. Additional criteria might include loan type, patron type (group), and/or loan policy.

        Attachments

        1. fee fine lost.png
          fee fine lost.png
          376 kB
        2. fee fine overdue.png
          fee fine overdue.png
          445 kB
        3. fee fine overdue options.png
          fee fine overdue options.png
          379 kB
        4. loan policy - notice 1.png
          loan policy - notice 1.png
          414 kB
        5. loan policy - notice 2.png
          loan policy - notice 2.png
          684 kB
        6. receipts.png
          receipts.png
          612 kB
        7. request available.png
          request available.png
          606 kB
        8. request available options.png
          request available options.png
          620 kB
        9. request - recall.png
          request - recall.png
          545 kB
        10. Screen Shot 2018-05-25 at 10.25.17 AM.png
          Screen Shot 2018-05-25 at 10.25.17 AM.png
          19 kB

          Issue Links

            Expenses

              Activity

              Hide
              cboerema Cate Boerema added a comment -

              Changed the title of this feature, as per Kostyantyn Khodarev, the expectation is that the CRUD aspects of this will get done before the end of the Q4 development period while. Making these policies effective will need to be done in Q1 2019 (see UXPROD-1386).

              Show
              cboerema Cate Boerema added a comment - Changed the title of this feature, as per Kostyantyn Khodarev , the expectation is that the CRUD aspects of this will get done before the end of the Q4 development period while. Making these policies effective will need to be done in Q1 2019 (see UXPROD-1386 ).
              Hide
              cboerema Cate Boerema added a comment -

              Per discussion with Kostyantyn Khodarev, if we change the scope of this to just CRUD patron notice, Vega will finish this prior to the start of the Q1 development period. However, since it didn't get completed prior to Feature freeze for Q4, we do need to change the fix version to Q1 2019. I will also tag it with Q4-2018pFF (for Q4 post-feature freeze).

              I will make sure the cap plan is not drawing time for this feature in Q1.

              Let me know if this doesn't make sense!

              Oh, and Darcy, since this is moving out of the Q4 release, could you please make a note in the Weekly Status Report? Thank you!

              Show
              cboerema Cate Boerema added a comment - Per discussion with Kostyantyn Khodarev , if we change the scope of this to just CRUD patron notice, Vega will finish this prior to the start of the Q1 development period. However, since it didn't get completed prior to Feature freeze for Q4, we do need to change the fix version to Q1 2019. I will also tag it with Q4-2018pFF (for Q4 post-feature freeze). I will make sure the cap plan is not drawing time for this feature in Q1. Let me know if this doesn't make sense! Oh, and Darcy, since this is moving out of the Q4 release, could you please make a note in the Weekly Status Report? Thank you!
              Hide
              kgambrell Khalilah Gambrell added a comment -

              Cate Boerema, what is the start date of the Q1 development period?

              Show
              kgambrell Khalilah Gambrell added a comment - Cate Boerema , what is the start date of the Q1 development period?
              Hide
              cboerema Cate Boerema added a comment -

              Hi Khalilah Gambrell, while the Q1 develoment period doesn't start until January 14th, I need to tag any work that is targeted for release in Q1 as fixversion = Q1 2019. Per Kostyantyn Khodarev, this work is in progress and will be completed before the Q1 development period begins so we are not factoring in additional time for it in Q1. I have tagged this with "Q4-2018pFF" to indicate it's being worked on in Q4 but after Feature Freeze.

              Show
              cboerema Cate Boerema added a comment - Hi Khalilah Gambrell , while the Q1 develoment period doesn't start until January 14th, I need to tag any work that is targeted for release in Q1 as fixversion = Q1 2019. Per Kostyantyn Khodarev , this work is in progress and will be completed before the Q1 development period begins so we are not factoring in additional time for it in Q1. I have tagged this with "Q4-2018pFF" to indicate it's being worked on in Q4 but after Feature Freeze.
              Hide
              cboerema Cate Boerema added a comment -

              Per Khalilah and Kostya, this is no longer planned to be completed by the end of Q4. I am removing the Q4-2018pFF tag and pulling down the full estimates for this work from the Vega capacity in the cap plan.

              Show
              cboerema Cate Boerema added a comment - Per Khalilah and Kostya, this is no longer planned to be completed by the end of Q4. I am removing the Q4-2018pFF tag and pulling down the full estimates for this work from the Vega capacity in the cap plan.

                People

                • Assignee:
                  dbranchini Darcy Branchini
                  Reporter:
                  dbranchini Darcy Branchini
                  Analysis Estimator:
                  Darcy Branchini
                  Front End Estimator:
                  Jakub Skoczen
                  Back End Estimator:
                  Jakub Skoczen
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  7 Start watching this issue

                  Dates

                  • Created:
                    Updated: