Date
Attendees
Discussion Items
| Time | Item | Who | Description | Goals |
|---|---|---|---|---|
| 5 min | Housekeeping | Andrea Loigman |
| |
| 30min | Item History | Emma Boettcher | Status history for an item | Solicit feedback on wireframe, data about actions tracked, length of time to keep data |
| 15min | Missing items | Emma Boettcher | Decide how an item is marked as thoroughly searched (automated or manual) |
Meeting Outcomes
Functional Area | Product Owner | Planned Release (if known) | Decision Reached | Comments |
|---|---|---|---|---|
| Item state | Emma Boettcher | Q4 | For immediate development, prioritize seeing history of item (rather than history by service point or by action) Include title in table to make it more readable. Effective location, call number block would be nice depending on space constraint. Include renewals Include actions from discovery layer (e.g., patron pages an item) Preference not to limit time span of data, but needs to be at least as long as longest loan period if you are limiting it. 1-3 years minimum. Show destination service point (also show on item record) - less helpful historically, but if showing it on item record seems odd not to show it on audit | |
| Item state | Emma Boettcher | Q4 | Long missing: can be applied manually or in batch, but not automated process Long missing: can be applied to items without their first entering the Missing state (e.g., to Available or In transit items), but not to checked out items |