Uploaded image for project: 'ui-organization'
  1. ui-organization
  2. UIORG-143

Add Hold Shelf Expiry Period to Service Point

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Priority: P2
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
    • Template:
    • Sprint:
      Core: F - Sprint 57
    • Story Points:
      5
    • Development Team:
      Prokopovych

      Description

      Purpose: To add a hold shelf expiration period to the service points where pickup location/service point = yes. This will be used as the default expiration period for items on the hold shelf at the service point. Hold shelf expiration date can be manually overriden in the request record, as well.

      User story:
      As a librarian who has checked in an item needed for a request at my service point
      I want the hold shelf expiration date to be set for that request based on the default expiration period for the service point
      So I know when the hold has spent enough time on the hold shelf without being picked up and I can re-shelve it

      Scenarios:

      1. Scenario
        • Given the Service point record (create, edit, view) in Settings > Organization > Service Points
        • When "Pickup location" = Yes
        • Then a new set of fields should display:
          • Label: Hold shelf expiration period
          • Field 1:
            • Type: Short field - There is a control in the Loan policy form for a similar field that disallows anything but integers so, if we use that, we don't need to have a validation error defined
          • Field 2:
            • Type: Dropdown
              • Default = Select interval
              • Values = Minutes, Hours, Days, Weeks, Months
          • Fields should look and behave like the similar fields in the loan policy form
      2. Scenario
        • Given the Service point record (create, edit, view) in Settings > Organization > Service Points
        • When "Pickup location" = No
        • Then these new fields should not display

      Acceptance Criteria:

      • Unit tests and big test coverage

      Mockup: https://drive.google.com/file/d/1WHqQ_3UDs9CkXibUCVLD7lIcwh22wyAM/view?usp=sharing

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                mpk35 Michal Kuklis
                Reporter:
                cboerema Cate Boerema
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases
https://issues.folio.org/browse/UIORG-143
issues.folio.org
crawl=CC-MAIN-2022-05
117880
application/http; msgtype=response
sha1:GQ3DVZDVHP4OM3RBIEHJCRNYYJ572XNW
<urn:uuid:eef2cc53-6ead-43fb-90be-795d7be5d5bf>
2022-01-21T11:39:16Z
52.71.11.239
text/html
sha1:CDD3AWVCVL5EIC3ICUH6FKMKERQQ5ZHE
<urn:uuid:fe349277-895e-46d9-a870-b8b4dbd0b275>
https://issues.folio.org/browse/UIORG-143
response
<urn:uuid:9317614a-2695-4c90-8f5d-c14baffbe8ca>
isPartOf: CC-MAIN-2022-05
publisher: Common Crawl
description: Wide crawl of the web for January 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-58
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.3-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/