2018-09-06 Resource Access Meeting Notes

Date

06 Sep 2018

Attendees

Andrea Loigman

Discussion items

Time	Item	Who	Notes
5min	Housekeeping	Andrea Loigman	Note-taker
20min	Historical Data Migration questions	Sharon Markus	9/14 deadline - Historical Data Migration - Planning Questions for Functional Areas
5min	Staff permissions	Holly Mistlebauer (for Tania Hewes)	The Requests Sub-group has defined the following permissions needed for requests: View requests Edit & Cancel requests Create requests All permissions The breakdown of what would be allowed can be seen on the Requests tab of this spreadsheet: https://docs.google.com/spreadsheets/d/1IJnlWvi4k-wFatDNimx9fQ375evHSIIxtGMookHvs-I/edit#gid=525257038 Two things Tania would like signoff on (besides the general concept) are: Any user who can access requests is allowed to add a note - the reasoning is that if they are allowed to see a request, they should be allowed to add a note to it to annotate the request with any info that might be needed by another staff person who may have higher permissions and can act on a note Edit and cancel permissions can be tied to each other - right now in the back end they are using the same function. We could separate them but it would facilitate quicker development if the two functions don't need to be separately assigned. The subgroup thought this would be OK - does anyone know of a compelling reason to separate them?
5min	Display of cancellation reason	Holly Mistlebauer for Tania Hewes)	Display of cancellation reason + additional info on a cancelled request The full audit trail of what has happened to a request (changes in status, details of edits, cancellation, who did what and when, etc) is something we are working on for inclusion in a "Request actions" area of the request detail (similar to the Actions area of a Loan record). This will be handled by the change tracker, which is still under development. Request metadata (creation date/time, edit date/time) is already on the request record. While we wait for the change tracker to enable us to display a full list of Actions, we need a way to see the Cancellation Reason + any Additional Information that was entered during request cancellation. Tania has two primitive mockups of how the Request cancellation info might be displayed on a Cancelled request. Before she sends them for UX design, it would be nice to know if there is a consensus on which one is preferable. The subgroup favored one, but they didn't have a strong opinion. The mock-ups are below:
25min	Data elements review (con't)	Emma Boettcher Cheryl Malmborg	https://docs.google.com/spreadsheets/d/1l8cuzfljiaTYkCP34nO_rR6dDNfrSWAw_XJSMuyagRw/edit#gid=579719430