GOKb is fully integrated in FOLIO for v1 - you download the metadata from GOKb into FOLIO and use it with other FOLIO services - the problem with eHoldings is that it only contains data from EBSCO's kb - if you don't use the EBSCO kb you won't have any data in FOLIO
Tricky situation for institutions that don't use GOKb as their kb provider. Those institutions can still pull in bibliographic data from GOKb to link up to ERM functionality, but they will have to activate the resource within their external kb as well.
Consortial and reporting features are integrated
Discussion of integrating other kbs will be necessary moving forward
Peter is going to investigate whether or not the ProQuest/SerialsSolutions kb data can be integrated into FOLIO
Followup
Subscribers can download files showing their specific e-resource entitlements from their link resolver/data management vendor. These files could then be used to populate a local instance of the FOLIO ERM tool, after the library has modified the knowledgebase output to meet FOLIO input requirements. Customers are not harvesting all the data that’s available from a knowledgebase vendor; they are only collecting data that reflects the holdings at their institution.
Here are some specific instructions for several common knowledgebases:
EBSCO Holdings Management: Follow instructions at this link.
ExLibris SFX: (can someone fill in specifics here?)
OCLC WorldCat e-resources knowledgebase: (can someone fill in specifics here?)
ProQuest 360 Knowledgebase tools (former Serials Solutions): Go to Reports, then Management Reports. Select the “Tracked eJournals” dropdown option, name the output, and click the “Request Report” button. Very large files may take up to 10-15 minutes to be generated.
PMc, 8/31/18
Bjorn gave an update on the eUsage app:
Enter your SUSHI credentials and the app will automatically harvest COUNTER statistics on a monthly basis
The stats are stored and will be made available to other FOLIO apps like ERM through APIs
Aim to finish the UI and harvesting process by October 2018; will then start working on allowing for manual upload of non-COUNTER statistics
In-app reporting in the ERM app using eUsage app data
Types of records: MARC bib data, EDI invoicing, MARC holdings, MARC authority, delimited/flat files (interim solution: convert to MARC before loading), order API data (not via Batch Loader)
MARC details: binary and XML, JSON is out of scope for v1
Miscellaneous: loading single records into FOLIO, rollback the load, scheduler, queuing the loads, exporting files from FOLIO, full bib/holdings/item data migration from previous library system
Starting with one use case and fitting it against the wireframes to make sure the design works
User stories: only research spikes so far, no UI stories yet, no backend stories yet
Next steps: finalize UI and requirements, understand MARC loader development done to date, outline backend architecture, write backend stories, write UI stories
Timeline: prelim release in mid-October 2018 - live in January 2019
Kristin will create another version of this document that we can put our comments in
Institutional needs for migrating historical data - we should think about it in terms of acquisitions data (ERM data too if you have an integrated ERM)