2024-11-12 Discovery working group
At Meeting
Name | Association |
|---|---|
Marie Widigson | Chalmers |
Demian Katz | Villanova University |
Bernd Oberknapp | Freiburg University Library |
Tammy Wolf | EBSCO |
Nicole Trujillo | CU Boulder |
Uwe Reh | hebis |
Meeting room Link
2024 Discovery API Improvements
Agenda
Discovery outreach
Are we a SIG? Should we submit to monthly SIG report?
Goal is to make ourselves more visible/part of the FOLIO conversation at a higher level.
Half our subjects are technical, while the other half are user-centered/practical (both what and how)
Currently part of the Sys Ops SIG. Latest meeting notes.
Might not be the best match, we do not report to Sys Ops.
2024-11-07 Product Council Agenda and Meeting Notes
To apply to be a SIG, we need to apply to the Product Council and have a Charge
Linked data space and charge (new group)
Action Item: Write a draft charge. Marie will start, others invited to start if they have time.
If we become a SIG, will follow SIG direction to reorder documentation.
Should we do topic meetings?
Discovery and Resource Access (aka patron empowerment)
Discovery and Linked Data
Discovery and Serials, Bound-Withs, and other complicated records.
Prioritizing Development in Discovery: How do I get my feature developed?
Could be good first step for the SIG, would need to decide on time and structure on each topic.
Any additional steps for listed improvements?
VuFind 2024 Summit Roadmapping Session
FOLIO driver improvements, including loan type service points
EDS - Customize column labels
We would love a set of pre-determined label options: Like Shelf mark vs Call number, Status vs Availability, Holdings info vs Holdings statement, etc. Anyone care to provide comment and suggestions?
Current: Status: | Due date: | Loan Type: | Location: | Call Number:
I added a few more Jira tickets, including MODINVSTOR-1266
How do we prioritize our Jira tickets? Ongoing conversation at Product Council right now, different SIGs are working on how to do this.
All POs are worried about a long tail of old unresolved tickets.
As a SIG, we can adopt tickets, can help clarify ticket or remove ticket from que.
Tickets are often bound to one module, lack of overview of connected tickets. We could also help link tickets, create epic tickets.
Next meeting
Tuesday at 10:00 am EST, Nov 26. Working meeting to prepare/discuss SIG draft.