2025-04-16 Meeting notes

Announcements

@Martina Schildt

• WOLFcon 2025 - Sessions proposals need to be in by April 25th

• WOLFcon 2025 will take place from September 23–25 at The Westin Kansas City at Crown Center in Kansas City, Missouri, USA.

• Are there any ideas on ERM topics?

• If you have any session ideas for WOLFcon 2025, please add those here: https://folio-org.atlassian.net/wiki/x/IIBLNQ?atlOrigin=eyJpIjoiN2Y0NWEwZjM4YTExNDQyNTgxM2RhNDk3NDk4MjYyNDMiLCJwIjoiYyJ9

• WOLFcon 2025 will be a hybrid conference

Development update

@Owen Stephens

Majority of time is around local KB stuff. The most recent sprint is keeping up with Sunflower Bugfest issues.

• Import JSON package to internal KB (via file upload): Log messages does not appearing in the Local KB Admin-App (just in the bugfest environmnet)

• General issue with Dashboard (on Eureka)

Sprint: short sprint (because of the Easter weekend)

• Main Topic: GOKB search integration

Integrating GOKB search into FOLIO

@Owen Stephens

Additional feedback to previous discussion: Integrating GOKb search into FOLIO?

Status update:
- First few stories are written for this
- see https://folio-org.atlassian.net/browse/UXPROD-5193
- Document (link see above) asks about these stories
- Talking to the GOKB team

Search Fields
- Story ERM-3697 is key story
- New search option "GOKB search"
- Search options consistent with FOLIO search options (style like Inventory Instance search)
- Offer: Search "Identifier (all)" or single identififer (eISBN, pISBN, eISSN, pISSN)
- Problem: Can't do a search via GOKB API for different kinds of identififer in one API call (but it's just a background issue)
- No preferences in the call for the specific search option
- Curatory group / scopes: titles don't have a curatory group or scopes. Might possible to have a filter somewhere else.
- Filter the list of titles by package: Owen doesn't think that this is possible at the moment (perhaps for later approach).
- Classification: Is not possible, the API doesn't support this at the moment.
- Publisher: That is possible.
- Question from Owen: There is a publisher field that can be searched: Exact string match or filter on the search results for publisher?
- Answer from Felix: Really mess in the kbart file, exact match wouldn't be helpful -> low priority

Search filters
- Type (Book, Journal, Database, etc.): GOKB call this "type", in local KB this is called "publication type" ("type" in local KB is monograph or serial).
- Question from Owen: How should this be called?
- Answer Gisela (in Chat): Publikation type, +1; Medium type would also be fine, +1
- Answer Felix: Medium type (because of the german translation: Publikationstyp and Medientyp)
- Answer Gisela (in Chat): Medium type would also be fine, +1
- Owen check with the developers to use the same label as it is used in the existing search (publication type in English, Medientyp in German)
- Moritz: Those fields are translated in the german GOKB. Fields are translated by a file that is hosted in the USA. For API calls you will get the original (english) values.
- Status: expected and retired status:
- Question Owen: Is it used for titles?
- Answer Moritz: Reference titles are current or deleted.
- Answer Felix: If we just have the current ones (and not the deleted ones), this would be okay.

Results lists: Which fields should be ideally displayed?
- Felix: "Status" can be deleted (since the search results only display current titles).
- Felix (from Chat): Publication date (print and online) for ebooks, publication period (start and end) for journals would be helful as well. Especially for journals to see if it is still being published. +1
- Tatjana (in Chat): This would be useful!!!
- -> Publication date (combining online, print, journal print dates)

Owen will discuss this with the development team. They will start coding.
This will be a topic for the next meeting as well.