10min
| Development progress update | Owen Stephens | Mainly working on issues arising from Bugfest testing Fixed as many as possible, those fixes will be part of Ramsons All Agreements and Licenses test cases are done Major issue in Licenses module: uploading documents does not work; issue is existing since Poppy; will be fixed for Poppy and Quesnelia as CSPs Currently developing external Push KB service; will be tested in GBV first, but is available for everyone
|
15min | eUsage App - future development plans | Stefan Dombek | Stefan Dombek is Product Owner for eUsage app for 5 months now App is now in phase where there is more management needed than new development done Stefan can always be contacted directly via Slack Some additional requirements are already identified for further discussion Stefan presents plans for 2025 COUNTER 5.1 Support Improving the integration of aggregators Improvement of error handling Obtain feedback from the community and check and, if necessary, implement further requirements
eUsage is already in use by some institutions internationallly; others are testing it Question: Are you also going to work on the eUsage plugin that connects Agreements and eUsage? > this will be discussed next year
|
35min | URLs in Agreements and LIcenses documents | Owen Stephens | With the Q release, the validation of URL fields in Agreements and Licenses has changed. The URLs to wikis and Jiras, which only resolve internally, are no longer validated. Same happens to file paths. As a result, libraries can no longer save the records where they have entered respective information in the URL field. Wish: add another field for URLs that don’t fit the validation criteria. Alternative: allow flexibility in validation |