Skip to end of banner
Go to start of banner

2021-01-28 Resource Access Meeting Notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Date

Attendees

@christine Tobias

(OLD ACCOUNT) Erin Nettifee

Sharon Wiles-Young

Andrea Mohr

Joanne Leary

Cornelia Awenius

Monica Arnold

Erin Weller

Mark Canney

Molly Driscoll

Amelia Sutton

David Bottorff

@patty K (GVSU)

Andrea Loigman

Brooks Travis

Laurence Mini

Martina Tumulla

Stephanie Buck

Cheryl Malmborg

Kelly Drake

tpaige@umass.edu

mey

Jana Freytag




Discussion Items

TimeItemWhoDescriptionGoals/Info
2minAdministrivia



presentations by implementing libraries


none today

documentation


  • Work together to compile list of in-app reports, along with relevant information - e.g., where to find them, permissions needed to run them, situations when they won't be available to run, etc.
  • Come up with ideas for documentation that we'd like to see be developed - e.g.
    • come up with a list of RA/User workflows, and decide which ones need to be documented

https://drive.google.com/file/d/1Jr1FM9KNVdWZVkx2HcpuDgdBZENsQk5U/view?usp=sharing (uploaded by Molly Driscoll) This is a document I started right around the Goldenrod release. I haven't touched it in a while, but it may serve as a starting point for in-app report documentation.


RA Documentation ReviewKelly DrakeMarcia Borensztajn is working on another draft of the RA docs - and they are almost ready for review.  She's incorporating some more information they got from Molly Driscoll. She would like to know who should "signing off" on the RA docs.  

She is planning to ask for the review in a week or two, and that is be completed with a week. Does that seem reasonable?

RA Areas and Signer
Circ log


the implementation process
Molly Driscoll : How are you planning to train circulation staff? (e.g. all together, by role, format, timing)

Meeting Outcomes

Functional Area

Product Owner

Planned Release (if known)

Decision Reached

Reasoning

Link to supporting materials

Comments

e.g. loans, fees/finesNamee.g. Q4 2018, Q1 2019Clearly stated decision
  • Because...
  • Because...
e.g. mock-up, JIRA issue




























Notes


  • No labels