Page tree
Skip to end of metadata
Go to start of metadata




  • GOBI integration

Discussion items

  • Who wants to be the note taker ? Ingolf.
  • New member Nico Toerl from UB Leipzig.

Upcoming F2F meetings
  • June 17-19 FOLIO working meeting in Crystal City, VA. The week before the ALA meeting in Washington, DC.
    • We want to meet with the developers and with each other there.
    • We see a need to discuss technical issues with the developers now, at WOLFCon (in 10 month) will be too late.
    • Registration fee will be $100, travel costs and logis must be paid by us.
    • We should apply for the funding at our institutions and see that as many of us as possible can go to the meeting.
    • If there should be no official meeting room for us, we will certainly be able to meet in some other location (café, pub).
    • Registration is not yet out, we will wait for an official registration site.
    • PC has assembled a planning commiteé for the meeting (agenda, lodging etc.)
  • WOLFCon will be in January 2020 (week of Jan 20). Texas A&M has agreed to host the WOLFCon.
10:20 EDTGOBI Integration

Ann-Marie will give a GOBI integration demo.

Meeting Notes

GOBI is a web-based acquisition tool. GOBI (Global Online Bibliographic Interface) was developed by YBP Library Services. YBP is one of the leading book providers for print books and ebooks in English language. Ann-Marie started working at YBP in 1997. YBP became a part of EBSCO in 2015 and developed into GOBI® Library Solutions. GOBI focuses on collection development and ordering workflow solutions for physical and eBooks for academic libraries.

An order is created in GOBI and moves to the FOLIO ILS via a series of APIs. Ann-Marie explains the workflow by means of an illustration ( There are two GOBI-specific modules which are connected to Okapi: edge-orders and mod-gobi. Other modules, which are not GOBI-specific, are involved, to authenticate the incoming API call and control interactions between the various acquisitions apps. GOBI creates a transaction ID called the YBP (GOBI) order key. An order is created automatically in FOLIO Orders. The FOLIO order line includes the GOBI order key. FOLIO returns the POL number that was assigned, so that GOBI will have that number for future invoice and cataloging record matching.

Ann-Marie shows the order in FOLIO (EBSCO demo site) Order App. PO line details have been created. Inventory Records in FOLIO will be created automatically based on the newly-created open PO. FOLIO creates the instance and

  • as many holdings as there are locations
  • as many items as there are copies mentioned on the order line.

See some slides of the PO-Inventory integration at

At point of receipt, acquisitions makes further updates to the inventory records. Data Import will also allow for loading fuller cataloging records.

Per Harry, the API has recently been improved for privacy concerns.


Ingolf thinks that this highly automated workflow will make the lives of librarians concerned with acquisition much easier.

Harry adds that Harrassowitz and (another big content provider) support some ILSes the same way as GOBI does. This makes working with the big vendors as efficient as possible, to have more time to cope with the little ones.

Ann-Marie refers us to Craig McNally for technical questions on GOBI integrations.

The group thanks Ann-Marie for this comprehensive demonstration and explanation of the workflows!

Next meetingsIngolf

Mar 22nd: Anton, Jason and Adam will get back to us about the JIRA issues for the deployment issues.

Mar 29th: Source Data and Integrations review with Harry. We need to find out what is already in JIRA.

Holiday planning
Ingolf will be unavailable on 3 consecutive Fridays in April (Apr. 12: Ingolf on FOLIO Days in Bremen ; Apr 19 Good Friday (Holiday in Germany), Apr. 26 Ingolf on holiday).

Action items