Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

Separate Jira tickets to follow for each implementation step.

Implementation is incremental:

  • Sequencing is expected to follow the order defined (excepting supplemental increments)

  • Preparatory work should be completed before feature development commences

Preparatory work

  1. Add mock tests for identifying and placing three-legged request

    Jira Legacy
    serverSystem Jira
    serverIda6f93653-ee50-3e81-88ad-29eb84ada35c
    keyDCB-1677

    1. Rename existing patronRequest API test for 2-legged requests (RET-STD workflow)

    2. Add additional patronRequest tests for 3-legged requests (RET-PUA workflow)

    Add consortial config to enable or disable pickup anywhere 

  2. Jira Legacy
    serverSystem Jira
    serverIda6f93653-ee50-3e81-88ad-29eb84ada35c
    keyDCB-1678

    1. https://openlibraryfoundation.atlassian.net/browse/DCB-1678Default: disabled

    2. Add to DCB Admin

    3. Include data change logging

    4. Reject at preflight if necessary TBC

    Expose pickup anywhere request data inside DCB Admin
  3. Jira Legacy
    serverSystem Jira
    serverIda6f93653-ee50-3e81-88ad-29eb84ada35c
    keyDCB-1679

    1. Extend raw local item and request status to pickup

    2. Add accordions to patron request page

Feature development

...

  1. Jira Legacy
    serverSystem Jira
    serverIda6f93653-ee50-3e81-88ad-29eb84ada35c
    keyDCB-1680

    1. Introduce REQUEST_PLACED_AT_PICKUP_AGENCY

    2. Extend DCB Admin to recognise new status

    3. Update FOLIO client to (a) be workflow aware and (b) create virtual service point

    4. Defer choice of abstracting virtual entity handling

    Extend tracking to detect state changes in pickup locations 
  2. Jira Legacy
    serverSystem Jira
    serverIda6f93653-ee50-3e81-88ad-29eb84ada35c
    keyDCB-1681
     

  3. Extend each transition for three-legged transactions to monitor hold and item state changes

    1. Delivery to pickup

    2. Received at pickup

    3. Ready for pickup

    4. Loaned

    5. Returned

    6. Complete (including finalisation)

  4. Extend patron cancellation for three-legged transaction transitions

  5. Extend supplier cancellation for three-legged transaction transitions

    1. Jira Legacy
      serverSystem Jira
      serverIda6f93653-ee50-3e81-88ad-29eb84ada35c
      keyDCB-1682

    2. Jira Legacy
      serverSystem Jira
      serverIda6f93653-ee50-3e81-88ad-29eb84ada35c
      keyDCB-1683

    3. Jira Legacy
      serverSystem Jira
      serverIda6f93653-ee50-3e81-88ad-29eb84ada35c
      keyDCB-1684

    4. Jira Legacy
      serverSystem Jira
      serverIda6f93653-ee50-3e81-88ad-29eb84ada35c
      keyDCB-1685

    5. Jira Legacy
      serverSystem Jira
      serverIda6f93653-ee50-3e81-88ad-29eb84ada35c
      keyDCB-1687

    6. Jira Legacy
      serverSystem Jira
      serverIda6f93653-ee50-3e81-88ad-29eb84ada35c
      keyDCB-1688

  6. Jira Legacy
    serverSystem Jira
    serverIda6f93653-ee50-3e81-88ad-29eb84ada35c
    keyDCB-1689

  7. Jira Legacy
    serverSystem Jira
    serverIda6f93653-ee50-3e81-88ad-29eb84ada35c
    keyDCB-1690

Supplemental

Info

This functional change is independent of preceding increments.

...

  1. Jira Legacy
    serverSystem Jira
    serverIda6f93653-ee50-3e81-88ad-29eb84ada35c
    keyDCB-1691

In Scope

From a user perspective the task of requesting can be broken down into

...