The M-CaReM-AI Method: Defining Work for AI / Unit 8 MCM 198 review, 2 to 3 minutes
Loan Periods by Item Type, Traced
The idea
A worked example, constructed for this course, walks a proposed change through the library's Loan matrix row by row.
In practice
The director proposes loan periods by item type: three weeks for books, one week for films and laptops, two days for new releases. First, the things: the Loan and the Loan Policy Version, and possibly the Item Category, which will now decide the period. Then the walk. In the policy row, a new Loan Policy Version is needed, with an effective date. In the cards row, Create Loan and Renew Loan both calculate due dates and must change; Generate Overdue Notice quotes the period and must change. In the data row, the loans table is unaffected, but the nightly overdue job must read the item category, and the council export must still count loans the same way. In the screens row, the kiosk shows the due date and needs no change; the member's account shows a loan period that would now be wrong. In the reports row, the overdue list is unaffected, but the monthly report's average loan length will shift and needs a note. In the testing row, new suites are needed for each item type, and renewals finally get tests. In the operations row, the desk manual and training must change. In the AI row, the chatbot's answers about due dates must be updated, or it will tell members the old period.
Where people slip
Every row except two found something, which is normal for a core thing. Without the matrix, the team would have changed the checkout calculation, the part everyone remembers, and left the notices, the account page and the chatbot telling members the wrong dates.
Your place on the trail
Every lesson rests on earlier ones and opens later ones. Tap any to jump.
Unlocks
Something wrong in this lesson? Flag it · Sources for The M-CaReM-AI Method: Defining Work for AI