Skip to end of banner
Go to start of banner

2021-06-21 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 8 Next »


Date


Zoom

https://zoom.us/j/337279319

Attendees

Thomas Trutt

Marie Widigson

@Eileen Cravedi

Laurence Mini

Mark Canney

Monica Arnold

Brooks Travis

(OLD ACCOUNT) Erin Nettifee

lisa perchermeier

Andy Horbal

David Bottorff

Erin Weller

Stephanie Buck

Cheryl Malmborg

Cornelia Awenius

Andrea Loigman

Karen White

Dwayne Swigert

Christine Tobias

Martina Tumulla

Kimie Kester

@rebecca ?

Robert Scheier

Molly Driscoll

Darcy Branchini

tpaige@umass.edu

Jana Freytag


Discussion Items

TimeItemWhoDescriptionGoals/Info/notes
2minAdministrivia

Cancelling the 2021-07-05 meeting ?


------

Bugfest June 28, Monday to July 9, Friday

Info here: Bug Fest R2 2021 Juniper

10 MinCheck-in respons times
Holly Mistlebauer  16:27 Uhr (via Slack in #reaaource-access)

Looks like I didn't ask about check-ins/check-outs, but Cate did.  Please go to the "Performance" tab of the spreadsheet at https://docs.google.com/spreadsheets/d/1oa5PnM9HqbKQl1lAe08aKojz29Go_-amQCNiMzwPnZc/edit?usp=sharing.  The expectation is that it will take less than 1 second.  At Cornell is painfully aware, we aren't there yet.  I have created two Spike JIRA tickets for this and assigned them to the sprint that starts on Monday.  The tickets are UICHKOUT-726 and UICHKIN-269.  I have named Cornell and MO State as "Affected institutions".  Other institutions should add themselves as needed. 
45 MinTitle level requestsStephanie Buck (OLD ACCOUNT) Erin Nettifee

Continued discussion and updates on TLR

Slide deck: https://docs.google.com/presentation/d/1m1cP0A47tmS6DcROyhQfrzaDbNFbZCwp7vgfXpG9xes/edit?usp=sharing

Our TLR folder for additional info, with use cases, mock-ups and technical info: https://drive.google.com/drive/folders/1ao5l4aKi-aNLlXwzT5CJ-UCXaba5tEKE


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






























  • No labels