...
Can we put pressure on EBSCO to get them to add databases with all the holdings from a publisher, but creating a selectable database? It seems as though EBSCO has all the data (titles, ISBNs or ISSNs, URLs), so it shouldn’t be a problem to get a new selectable package set up.
Discussion: We decided on a possible workaround- "Hide" the titles we don't subscribe to. EBSCO should be able to hide titles for us, if we send them an excel file. Best case scenario to get a selectable database.
- Let’s start using this file to quantify what data has and hasn’t been cleaned up during the migration from Intota to EBSCO/FOLIO: https://cornell.app.box.com/file/618902304246
- A lot of the tasks have already been done, but a lot is still needed, particularly title list reconciliation.
- I’ll go over some of the tasks listed, but we can discuss if anything else is needed.
- I am trying to plan out some projects for BERT folks to work on to help them get used to working in FOLIO.
Discussion: This will take a while to go through, 1+ years to complete everything. However, we can start by breaking down some of the tasks for specific people to do. For instance, Liz volunteered to test remote access to make sure that EZproxy is working for all providers. Emma will take care of many of the FOLIO related items (agreements, licenses, organizations), as she has already done much of this work. Liisa will generate holdings review projects for staff, for instance, she will ask Sally to review the PQ databases to make sure that all of our owned content is represented in FOLIO/EBSCO. Rebecca and Liz can work on e-journal title lists.