Primary work is updating the above linked page; new columns added. Thus far mainly focused on first use case.
Need to write each out in much more detail. Discussed use of persona to make the use cases more specific
Understanding from EBSCO that work being done for LC is to be aligned with what the community is asking for
Possible: situate use cases within workflows and/or institutional sensibilities. Make clear when/how use cases can align with different institutional; different pieces of functionality may be needed based on how one accomplishes some type of work
Timing: to get work more momentum, may need to meet more frequently. Much more work needed
2020 use cases were the starting point - but this is a bit of a blocker to getting deep into it and/or raising new work that we might've not imagined in 2020. Perhaps we need to write this in a different way
ACTION ITEM: Jacquie to think about how to expand view beyond 2020 cases
How specific do we need to be at this point with the use cases?
If not specific, dev could happen without us being aware and then that development conceptually aligns with the use cases but doesn't meet needs
Development Scheduling and Methodologies: this is very waterfall - working things out in great detail before code is committed. Is there an opportunity for close collaboration with Gloria's team to move this into more storyboard conversations. If spend months writing detailed use cases, there will already be code written. No coding has been done yet.
ACTION ITEM: Jason ask Gloria about the above alignment and also whether LC has use cases
LC and EBSCO working on use cases now; Gloria can share some at the next use case subgroup meeting
What does this mean wrt entity management work? Abstraction for authorities that is a simplified data model and source for that abstraction may be a MARC authority; abstraction is stored elsewhere and linked to inventory (id and label stored in inventory)
Need to have more detail on technical solution (not the UI)