This is technical story needed to split effort for .

In scope of this story we have to implement Age to lost scheduled job described in the technical design.

Here is the overall algorithm of the job.

1. Scenario

• Given Item Status = 'Claimed returned'

• Then:

  • Do no further aged to lost processing for item

2. Scenario

• Given Item Status NOT = 'Aged to lost' and NOT 'Claimed returned'

• When Items aged to lost after overdue interval (see Lost Item Fee policy) = 0 or blank

• Then:

  • Do no further aged to lost processing for item

3. Scenario

• Given Item Status NOT = 'Aged to lost' and NOT 'Claimed returned'

• When:

  • Items aged to lost after overdue interval > 0;

  • System date is NOT Items aged to lost after overdue interval (see Lost Item Fee policy) from item due date

• Then:

  • Do no further aged to lost processing for item

4. Scenario

• Given Item Status NOT = 'Aged to lost' and NOT 'Claimed returned'

• When:

  • Items aged to lost after overdue interval > 0;

  • System date is or more then Items aged to lost after overdue interval from item due date

• Then:

  • Set item status and loan.itemStatus = 'Aged to lost'

Acceptance criteria:

• The job is implemented;

• Unit tests are created;

• Make sure all DB indexes in place;

Notes:

• Dev only story;