Last week’s action items:
- Update the “Systems Used for E-Resources” document (https://docs.google.com/spreadsheet/ccc?key=0Ap5Klzwi6yzSdDhyeXRWSkkzbU5tVEFnZXpwZFdiRkE&hl=en_US#gid=0) (Liisa/Susan) – done/done – Thank you
- Gather list of the people, tasks, and FTE time spent on troubleshooting activities (Joyce/Jesse) – Joyce – done, Jesse-drafted, needs some work before posting
As discussed, we are going to dig into:
- Review policies, practices, and workflows related to e-resources troubleshooting at both institutions to identify points of harmony and points of discord; Let’s exchange e-mails over the week with various thoughts on the with the goal of consolidating our ideas into a coherent list at our next meeting (3/1). The now updated Systems Used for E-Resources will be a great place to start.
Other items discussed:
- BrowserStack – Columbia has an account. Jesse will look into getting Cornell an account. Seems like a great “low hanging fruit” way to get at least one system in sync.
- License terms that we actually enter in our ERM (as opposed to just uploading the license document). Not officially in scope, but information in licenses sometimes come into play in troubleshooting. Liisa is sharing screenshots of Cornell ERM with Joyce.