|Review addition of OA data to reports|
Include OA access into reports without cost association: Added Acces type field to be able to filter for access type.
|Review visualization mockups|
Cost per use report has additional line over bar diagram for title count -- this is hard to create for use per month because of missing data (fiscal year connection).
The group likes the visualization shown, no further comments so far.
Problem: frontfile and backfile would normally be handled in separate agreements -- so this report visualization will not be of much help in this respect.
Access distribution across agreement
Annika shows first idea for a visualization based on the use by month report data.
The group likes the idea.
Kristen will work out a mockup to discuss in next meeting.
|Review FOLIO app mockups|
Genereal discussion about integration into the agreements app
→ Martina will set up a poll for a technical meeting to discuss the integration into Agreements.
Preview in Agreements app
Kristen: would real-time data be important to the group?
Mockups show separate -”sub-accordions” for each report.
Matching UI inside of eUsage
Table with harvesting results:
Numbers for matched/unmatched titles will link to filtered lists
What should the status show?
Think about worflows.
→ How will users work with the matching process?
→ Which status parameters would help with those workflows? What would help to e.g. identify work to be done?