Page Comparison

• Kirstin gave an update on the ERM Project Plan:
  • 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

• 
  

  Info
  icon false title 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

  
  

  Info
  icon false title Clarification
  Clarification Re "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." . The starting point for Folio ERM is harvesting the entire knowledgebase. The point I (badly) tried to make in the meeting was that this was information the library would have access to through existing access to the KB, and there was no intention for that data to be shared outside the subscribing library. I can see us looking at the possibility of only harvesting Local holdings from a KB, but that isn't the initial approach we are taking. Owen Stephens 4th Sept 2018

  
  
  

• 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
  • Link to eUsage app Project Plan: https://docs.google.com/document/d/1idybVzkap6b7cu4h8_o5e9MLPXLl1mZsUsDLERJOrc0/edit?usp=sharing

Kristin Martin and Dennis Bridges