/
2025- Discovery SIG Meetings

2025- Discovery SIG Meetings

Meeting room Link

2025-11-11 Agenda

Updates

Discussion

  • Create wiki page with directory of which FOLIO organization is using what discovery system(s)? (Nicole)

    • Yearly survey to update?

  • Review closed tickets on prioritization/Jira board

    • Next steps - add label to remove from list?

  • Review new/other tickets on the Discovery SIG Jira Ticket Review

    • What do we do with bugs?

2025-10-28 Agenda

Updates

  • WolfCon 2025 updates

  • https://folio-org.atlassian.net/browse/UXPROD-3651

    • Update comments to reflect possible technical solutions, as well as timed test with renewing lots of items in the discovery environment (100+), and numbers on how many patrons have lots of items to renew.

      • Nicole and Sarah gathering information for this ticket.

      • Why so much effort going into multiple item request and not renew?

        • Locate also does not have the ability to renew multiple items at a time, but requesting has been prioritized.

        • Part of the work going on with the requesting in Locate is because there is both item and title level requesting going on, so there’s a lot more to figure out there

        • Hope is to use the same api model for renewing.

          • Bernd will update the ticket to put this on pause until request is completed so we can use that for this ticket.

Discussion

  • Prioritization Discussion - Review new Jiras, identify any as high priority.

    • What do we do with bugs?

      • discuss next meeting

    • What do we do with closed tickets in our dashboard?

      • discuss next meeting

2025-9-16 Agenda

Updates

  • Follow up from PO meeting: Our Draft Community Priorities need to become open. Only POs can make these open.

    • I did meet with Anne Ekblad about https://folio-org.atlassian.net/browse/UXPROD-3651 last week. Her advice was to flesh out this work item as much as possible with details. Adding use cases from different discovery products is helpful as it indicates a broader community need. She also suggested it would be helpful to better understand any prerequisites or any other work that is directly related, such as https://folio-org.atlassian.net/browse/UXPROD-4805 She also said the status information of tickets can be found at https://folio-org.atlassian.net/wiki/spaces/PO/pages/2670064

    • Technical description:

      • List all of the processes that need to be done before renewing? Circulation rules, service point validation (so all of the current checks for single check outs

      • Possible other solutions? (Bernd, Sarah)

    • Human description:

      • Currently Discovery products renews the items one by one on the discovery side.

      • Can someone try checking out and renewing a large number of books on the different interfaces? Then place the results of the test back in the ticket.

        • Test on FOLIO UI?

        • Nicole can test out for VuFind interface - how long it takes, any error messages?,

        • Pull reports for 100+ and 50+

Discussion

  • Prioritization Discussion - Finishing the list/tags. Please look at tickets before the meeting and add your comments/questions!

    • Homework for next time, review non draft tickets in 2024/2025 and add to Prioritization list.

Next meeting is October 28th, 2025 (unless someone can convene Oct 14?)

2025-9-2 Agenda

Updates

Discussion

  • Prioritization Discussion - Finishing the list/tags. Please look at tickets before the meeting and add your comments/questions!

    • Damien will add the tags decided on to the ticket

2025-8-19 Agenda

Updates

  • Prioritization Discussion - Please look at tickets before the meeting and add your comments/questions!

    • Damien will add the tags decided on to the ticket

    • Tags created so far for topics: discovery-sig-metadatadisplay, discovery-sig-search, discovery-sig-recordtransfer, discovery-sig-request, discovery-sig-boundwith, discovery-sig-serials, discovery-sig-coursereserves, discovery-sig-patroninfo (see table below)

    • Tags created for general (every ticket gets one of these): discovery-sig-old, discovery-sig-topics, discovery-sig-resolved

  • Tickets added by OPAC search, what should we add to the list of potentially relevant tickts? - Bernd will move to the Prioritization Discussion table to discuss at next meeting.

  • Other updates

    • Nicole will follow up on the LD4D (Linked Data 4 Discovery) meeting planned for October to discuss FOLIO, FOLIO Discovery Services, and Linked Data.

    • Maccabee is following the Bulk edits list app working group and will update on any discovery related content.

Tags for topics

discovery-sig-metadatadisplay

discovery-sig-search

discovery-sig-recordtransfer

discovery-sig-request

discovery-sig-boundwith

discovery-sig-serials

discovery-sig-coursereserves

discovery-sig-patroninfo

2025-8-5 Agenda

Updates

Discussion

  • Multi-item request process

    • Who has it? VuFind: No. Blacklight: Yes.

    • Locate (EBSCO catalog) is developing multi-item request process.

      • Currently allowing users to select all of their volumes, then on the backend sends each request via api one at a time.

      • Question: How can we best design multi-item request process.

        • Is this multi requesting on items on a single holding? Or is this about requesting multi-instances at the same time?

          • For now, items on a single holding.

        • Do we offer patrons the ability to request based on the type of item it is? Like serial vs non-serial. Or offer it to every item?

          • Currently we have a complicated logic to separate multi-volume vs multicopy. Is there a better way to differentiate these two types?

            • LEADER 07 could be used? It should say it’s multi-volume. Would need to talk to MM-SIG if there is a MARC field/s that could be used for this.

            • You can use mode of issuance and nature of content to determine type? Note every library has implemented this.

            • Could we use the request policy/circulation rule settings to inform this?

            • We do want a way to limit this to certain records, but it’s hard to know how libraries will want to limit this.

        • Also many different libraries have many different rules (location vs material type vs loan type vs patron type decides how a user can request an item).

        • Issue: Course book with 7 copies, can 1 user request all books? (they can do this now)

        • Issue: Limit of how many items you can request at a time.

    • FOLIO functionality question from Stephanie:

      • Library of Congress has asked for the ability to request multiple serials for patrons. see UXPROD-5398 and UXPROD-3458

  • Linked data presentation for LD4 Discovery Affinity Group

    • Offered two dates: Tuesday, October 7, 9 AM PT/10 AM MT/12 PM ET, Tuesday, October 21, 9 AM PT/10 AM MT/12 PM ET

    • Also want to hear from FOLIO Linked Data SIG

    • Can anyone from this group present? EBSCO author cards, other?

    • Will start reaching out to EBSCO about the author cards. Shape presentation around “What is the user problem that is being solved by this?” Interest in proof of concept and user testing.

Prioritization

  • https://folio-org.atlassian.net/browse/UXPROD-4805 - no more PO? Will reach out to see why.

  • MOVED TO NEXT MEETING

    • Prioritization of Jira tickets for discovery

    • Discovery SIG Jira Ticket Review

      • Can we update the search?

        • As we improve the SIG search, replace the ticket review Dashboard. Improvements could include adding “OPAC”

        • If anyone has additional search terms, post in #folio-discovery and Bernd will update.

      • How do we organize our Jiras?

        • Topics, how do we group? Create labels for different discovery topics. Discovery SIG top 5 label?

        • Please review tickets and mark as relevant, not relevant and suggest labels

    • Product Council List Community Priorities Dashboard Development

      • Replace MODINVSTOR-1387 with UXPROD-1625 - Done

2025-6-10 Agenda

Agenda

Prioritization - moved to next meeting

Updates

  • June 17th 11 am meeting with FOLIO implementers SIG to discuss discovery options for FOLIO, and demo of Locate?

    • Nicole will reach out to confirm date/EBSCO involvement.

  • WolfCon 2025

    • No news yet!

At Meeting:
Marie Widigson (Chalmers), Melissa Mondro (OU), Nicole Trujillo (Boulder)

2025-5-27 Agenda

Agenda

Prioritization

Wiki structure

Miscellaneous

  • Wolfcon 2025, any decisions yet?

    • Submissions are under review.

  • Next meeting June 10

2025-5-13 Agenda

Prioritization

Wiki structure

  • Discussion of Bernd's proposal.

    • Examples, ERM SIG, Acquisition SIG

    • Implementer's topic page - is this a draft? brainstorm document?

    • To do: Create label for discovery sig - Demian

      To do: Go through the Jira tickets. Attach label to tickets that are our concern. - Bernd

      To do: Create and embed a dashboard. - Nicole

      To do: Create a table for tracking “pre Jiras” and outside - Nicole

Miscellaneous

  • Product Council working on a Community Priorities Dashboard. I used our old priorities list to submit ours.

  • VuFind adjustment to block users from doing empty searches on EDS. Historically used FT Y OR FT N.

  • More EBSCO API resources

  • Locate: Huge changes coming for Library of Congress, roll out in June/July. Feb release features roll out and new features.

2025-4-15 Agenda

Prioritization

  • Status update UXPROD-4805 - Bulk renewals - no updates yet.

Wiki structure

WolfCon 2025 presentation

  • Coordination of the Lightning Session

    • Mention Jira tickets with discovery elements; should those tickets be presented to/viewed by the discovery SIG? For Product Owners, how may they interact with the discovery SIG?

  • Other suggestions?

    • Patron accounts presentation panel - draft write up

      • Beyond presentation, repository of user studies on this confluence site?

    • Lightning talk to follow up on api reconfiguration

      • work starting in autumn, presentation before kick up

    • OLF Projects and accessibility - contact Maccabee Levine

Miscellaneous

  • Government documents MARC mapping to format? Still working on best method.

  • Discovery Layers - Feature for users to “vote” on a record? (for example, some records selected for deleting, users can vote to keep by clicking a link).

    • See ‘Collection weeding: Innovative processes and tools to ease the burden’ - for working example. Is on the search results page.

    • For VuFind,

      • there is a link section designed for the 856, you could add links here, or should we investigate another area in which to place these links?

      • not way to collaborate on a list (thinking of ways to use VuFind code to do the vote function)

      • there is also a VuFind feedback form that can out put to various things. LeHigh added to their action bar (cite, etc.)

      • what data to send, where to send it, and how to work with that data.

    • Relates to

      • See also “report a problem” forms for eResource or Record metadata. Or special collections' special forms. - Feature that can be placed on a record and take metadata information and place it in a form.

      • Stanford/Blacklight - general feedback link (capatcha), report a connection problem, report a problem with a Google Book cover “cover image doesn’t match the book”, - triage group that meets every week to go over the feedback

    • Where do discovery systems put links that are not full text access?

…Next meeting: April 29th at 10:00 EST.
At Meeting:
Demian Katz (Villanova/VuFind®), Marie Widigson (Chalmers), Sarah Seestone (Stanford), Melissa Mondro (OU), Ricky Lee II (Texas A&M), Sarah Seestone (Stanford), Uwe Reh (hebis, Frankfurt), @Jennifer Bolmarcich (Mount Holyoke College), Maccabee Levine (Lehigh), Paivi Rentz


2025-4-1 Agenda/Notes

Prioritization

UXPROD-4805 - Bulk renewals
After the last meeting Demian Katz reached out to Khalilah and Charlotte Witt to ask what we can help out with.
Unfortunately, Khalilah hasn't been able to respond yet. But Charlotte has been helping to sharpen the ticket

Wiki structure

Bernd suggested combining the Prioritization/JIRA and Topics pages into one Implementer's Topic page, as in other SIGs. If we move the topics from the old Discovery API Improvements page and maybe some from the survey, they can be reviewed and updated as needed. Demian supported this idea.

WolfCon 2025 presentation

From Tara: Hi SIG Conveners! The App Interaction SIG wants to do a Lightning Session (5 minutes) at WOLFcon explaining what our SIG is, what our SIG does, and what kinds of issues we handle. We were thinking that this would be a really cool session if we banded together with other SIGs into a kind of "SIG Showcase" of Lightning Sessions. We think that this would be particularly valuable for new community members figuring out where they want to be involved, but would also provide a nice overview for community members who are curious about the work/scope of other SIGs.

It was agreed that we should have at least one lightning session to present our new status as a SIG. Since the register form is open until 25. April, we still have time to collect thoughts in the channel and discuss the abstract of the presentation in the next meeting (April 15th).

Miscellaneous

  • Sarah mentioned that she was looking for a smart solution to find the last delivered issue of a series. Uwe promised to send her the algorithm implemented in his connector.

The meeting ended at 10:30.

Next meeting: April 15th at 10:00 EST.

At Meeting:
Demian Katz (Villanova/VuFind®), Bernd Oberknapp (Freiburg University Library), Ricky Lee II (Texas A&M), Sarah Seestone (Stanford), Uwe Reh (hebis, Frankfurt), @Jennifer Bolmarcich (Mount Holyoke College), Maccabee Levine (Lehigh)

2025-3-18 Agenda

  • Prioritization

    • UXPROD-4805 - Bulk renewals

      • From Khalilah: "Team Vega will review this feature to determine a release to consider this functionality. If the Discovery SIG and RA SIG wants to help with this feature, we would love development, requirements analysis and/or QA assistance."

        • Demian Katz will reach out to Kalilah and Charlotte Witt to ask what we can help out with.

    • Any others? UXPROD-5180 Authority - Discovery/OPAC support

      • (I didn’t catch what was said about this./Marie)

    • Subject headings changes Gulf of America etc.

      • LoC has decided on the propsed changes. In theory that would mean that existing records will be changed.

      • With data import we can as a local practice add (and protect in data import) local subject headings in MARC.

    • Linked data
      The subject heading changes could be seen as good linked data use cases.

      • Linked data in EDS? Not yet to our knowledge.

      • Linked data in VuFind? Intention to make it easier to plugin any kind of services to enable linking.

      • Linked data at Stanford? Working on “Small links” that can be useful to users to “go off some place” with good information. Inspiration from Cornell.

      • What would be useful for users? And would actually be used? What are the expectations, probably varies from one group/person to another.

    • Other things discussed

      • Stanford is working on creating their own citation tool. Among a lot of other things.

      • Call number browsing (= browse what is on the physical shelf). Stanford is working on

      • Next meeting April 2025-04-01. Uwe will be convening with support from Demian.

At Meeting: Nicole Trujillo (Boulder), Marie Widigson (Chalmers), Demian Katz (Villanova/VuFind®), Bernd Oberknapp (Freiburg University Library), Ricky Lee II (Texas A&M), Sarah Seestone (Stanford), Melissa Mondro (OU), Jen Bolmarcich (5 Colleges), Uwe Reh (Hebis, Frankfurt)

 

2025-3-4 Agenda

  • Authentication and Eureka: How disruptive is this going to be for consumers of the FOLIO API? Can we use this to increase patron privacy/make sure patrons can only see their own data?

    • EBSCO Locate Rep Radhakrishnan Gopalakrishnan: How Eureka will impact authentication in Discovery

      • VuFind uses OKAPI to make call requests, how will Eureka change that? What alterations will we have to make to the code?

        • Locate is switching from OKAPI based platform to a Eureka based platform. The biggest difference is the fact that tokens will now expire. Previously we were using EDGE api calls and using a key to get the information back. If you’re using OKAPI you need to supply username/password. What you get back is a token, and this token will expire. For every call that we make we check the response code and if its' 401 or 403 we refresh the token using a standard.

        • Refresh token is in OKAPI already, VuFind already supports that.

        • Permissions have been migrated to Capabilities sets. We are assuming during the migration (OKAPI to Eureka) permissions will be the same, just now “capabilities”

        • Different platform might use a different hashing algorithm, so FOLIO might need new passwords

      • Can we no longer rely on a service account (in VuFind this is a single account where you can do all things for the users) for authentication? Eureka is based on OA2, can you get a token for the user and use that for the user to get access?

        • Patrons are not supposed to login to FOLIO, so very unlikely you’d have patron accounts in FOLIO with the right permissions. Currently users in FOLIO do not have permissions/capabilities that can read/write user accounts in FOLIO.

        • Locate does not have a service account, it has an institutional user that uses EDGE API which has very limited FOLIO capabilities.

          • VuFind service account is similarly scoped.

        • Can we restrict access to a service account to just the VuFind Server using IP address in Eureka? This would help unauthorized access to lots of data.

        • Other concern that other patron data could be leaked to patrons. When you’re doing a GET, you got to be sure you’re only getting the user data.

      • Discussed having further conversation with Craig McNally, Radhakrishnan Gopalakrishnan.

  • Prioritization

    • UXPROD-4805 - Bulk renewals

      • Need a PO champion: Tammy will reach out to Magda Zacharska?

        • Not her area, suggested Stephanie Buck, Tammy is reaching out.

  • Becoming a SIG

    • DISCO PO?

    • Todo: Prioritization/JIRA page, Topics page

    • Other? Checklist, issues.folio.org no longer running, I don’t think we still do mailing lists

    • Slack will be used for all OLF products, should we change our FOLIO Slack name to something like FOLIO-Discovery?

  • New Issues/updates

    • LOCATE can now change FOLIO Statuses to a different name (aka “In Process” can be labeled “Available in back office - place request”)

      • Originally took 12 statuses and mapped to three, not changeable

        • Some libraries like limited, because less confusing for the patrons

      • Available for EDS? Yes, it is in EDS

      • Available for ICS (ILS Catalog Services) customers only or all customers? ICS only

        • ICS created in order to quickly get some critical functionality.

        • Decisions that you make in the EBSCO LOCATE questionnaire tie into EDS

        • EDS still cannot do some functions like reserves. You can use LOCATE or make your own course reserves (5 colleges). VuFind and Blacklight also can do course reserves. Course reserves api needs updating, for example for some data element (instructor?) there’s no way to get a list of the data element because you have to download everything to get this; we download to solr than use.

      • Should we do a Jira for a discovery display name for the status?

At Meeting: Nicole Trujillo (Boulder), Marie Widigson (Chalmers), Demian Katz (Villanova/VuFind®), Bernd Oberknapp (Freiburg University Library), Jen Bolmarcich (5 Colleges), Tammy Wolf (EBSCO/Locate), Melissa Mondro (OU), Cory Lown (Stanford)

Previous meeting: 2025-2-18

Next meeting: 2025-3-18