Library Technology Guides

Documents, Databases, News, and Commentary

Select another Product Report:

Statistical Report for FOLIO -- EBSCO Information Services

Statistics according to type and size categories

The following table presents the 2024 results according to the type and size of the library.

2024 FOLIO -- EBSCO Information Services Responses by Sector
FOLIO -- EBSCO Information ServicesallAcademicPublicSchoolConsortium
smallmediumlargesmallmediumlarge
navgnavgnavgnavgnavgnavgnavgnavgnavg
SatisfactionLevelILS405.70 125.92115.8276.0000000
ILSFunctionality405.38 125.75115.3675.5700000
PrintFunctionality396.41 126.25106.7077.0000000
ElectronicFunctionality385.89 116.00116.3675.8600000
SatisfactionCustomerSupport385.82 116.45106.3075.0000000
CompanyLoyalty405.97 126.25116.5575.8600000



2024 Survey Results
Product: FOLIO -- EBSCO Information Services Response Distribution Statistics
CategoryResponses 0 1 2 3 4 5 6 7 8 9 ModeMeanMedian
ILS Satisfaction40 4 4 1 4 9 8 8 2 65.706
ILS Functionality40 1 4 5 2 4 9 11 4 75.386
Print Functionality39 3 1 3 3 9 6 8 6 66.417
Electronic Functionality38 2 3 1 3 3 10 5 8 3 65.896
Company Satisfaction40 4 3 1 4 2 6 8 4 8 75.887
Support Satisfaction38 3 3 3 4 1 5 6 7 6 85.827
Support Improvement0 00.00
Company Loyalty40 2 2 5 3 2 6 4 8 8 85.977
Open Source Interest36 4 2 2 1 3 1 4 3 5 96.723

CategoryTotalYespercent
Considering new ILS41 49.76%
Considering new Interface41 12.44%
System Installed on time?41 00.00%

Average Collection size: 1267360

TypeCount
Public0
Academic33
School0
Consortium0
Special1

Size CategoryCount
[1] Under 10,0001
[2] 10,001-100,00011
[3] 100,001-250,0006
[4] 250,001-1,000,00011
[5] 1,000,001-10,000,0008
[6] over 10,000,0011



2023 Survey Results
Product: FOLIO -- EBSCO Information Services Response Distribution Statistics
CategoryResponses 0 1 2 3 4 5 6 7 8 9 ModeMeanMedian
ILS Satisfaction28 1 1 5 11 6 4 77.147
ILS Functionality28 1 1 10 8 6 2 66.797
Print Functionality28 7 6 9 6 87.508
Electronic Functionality28 1 4 5 7 6 5 77.007
Company Satisfaction30 1 2 2 4 7 8 6 87.077
Support Satisfaction30 1 1 1 9 4 7 7 67.107
Support Improvement0 00.00
Company Loyalty29 1 2 3 2 5 7 9 97.248
Open Source Interest19 2 1 1 1 1 10 97.479

CategoryTotalYespercent
Considering new ILS30 13.33%
Considering new Interface30 620.00%
System Installed on time?30 00.00%

Average Collection size: 849424

TypeCount
Public0
Academic22
School0
Consortium0
Special2

Size CategoryCount
[1] Under 10,0003
[2] 10,001-100,0004
[3] 100,001-250,0006
[4] 250,001-1,000,00012
[5] 1,000,001-10,000,0004
[6] over 10,000,0010



2022 Survey Results
Product: FOLIO -- EBSCO Information Services Response Distribution Statistics
CategoryResponses 0 1 2 3 4 5 6 7 8 9 ModeMeanMedian
ILS Satisfaction22 1 2 9 8 2 77.367
ILS Functionality22 1 2 8 7 3 1 66.557
Print Functionality22 1 2 8 6 5 77.558
Electronic Functionality22 1 1 1 1 5 9 4 87.098
Company Satisfaction22 1 3 3 5 6 4 87.097
Support Satisfaction22 1 4 1 6 7 3 87.057
Support Improvement0 00.00
Company Loyalty22 1 1 1 5 6 8 97.688
Open Source Interest6 1 4 97.839

CategoryTotalYespercent
Considering new ILS22 14.55%
Considering new Interface22 313.64%
System Installed on time?22 00.00%

Average Collection size: 1525665

TypeCount
Public0
Academic20
School0
Consortium0
Special1

Size CategoryCount
[1] Under 10,0000
[2] 10,001-100,0002
[3] 100,001-250,0004
[4] 250,001-1,000,0009
[5] 1,000,001-10,000,0007
[6] over 10,000,0010



2021 Survey Results
Product: FOLIO -- EBSCO Information Services Response Distribution Statistics
CategoryResponses 0 1 2 3 4 5 6 7 8 9 ModeMeanMedian
ILS Satisfaction7 1 2 4 76.437
ILS Functionality7 3 2 2 55.866
Print Functionality7 1 2 3 1 76.577
Electronic Functionality7 1 3 3 77.297
Company Satisfaction7 1 4 1 1 77.297
Support Satisfaction7 1 4 2 77.437
Support Improvement0 00.00
Company Loyalty7 2 2 1 2 67.437
Open Source Interest3 010.0010

CategoryTotalYespercent
Considering new ILS8 00.00%
Considering new Interface8 00.00%
System Installed on time?8 00.00%

Average Collection size: 1458913

TypeCount
Public0
Academic7
School0
Consortium0
Special0

Size CategoryCount
[1] Under 10,0000
[2] 10,001-100,0001
[3] 100,001-250,0002
[4] 250,001-1,000,0003
[5] 1,000,001-10,000,0002
[6] over 10,000,0010


2 Responses for FOLIO -- EBSCO Information Services in 2020

0 Responses for FOLIO -- EBSCO Information Services in 2019

0 Responses for FOLIO -- EBSCO Information Services in 2018

0 Responses for FOLIO -- EBSCO Information Services in 2017

0 Responses for FOLIO -- EBSCO Information Services in 2016

0 Responses for FOLIO -- EBSCO Information Services in 2015

0 Responses for FOLIO -- EBSCO Information Services in 2014

0 Responses for FOLIO -- EBSCO Information Services in 2013

0 Responses for FOLIO -- EBSCO Information Services in 2012

0 Responses for FOLIO -- EBSCO Information Services in 2011

0 Responses for FOLIO -- EBSCO Information Services in 2010

0 Responses for FOLIO -- EBSCO Information Services in 2009

0 Responses for FOLIO -- EBSCO Information Services in 2008

0 Responses for FOLIO -- EBSCO Information Services in 2007

2024 : gen: 5.70 company 5.88 loyalty 5.97 support 5.82

2023 : gen: 7.14 company 7.07 loyalty 7.24 support 7.10

2022 : gen: 7.36 company 7.09 loyalty 7.68 support 7.05

2021 : gen: 6.43 company 7.29 loyalty 7.43 support 7.43

Comments (survey2024)

We are the very first cohort to use OpenRS. It is still being built out. We migrated from a Sierra ILS to FOLIO, hosted by EBSCO, at the same time we switched to OpenRS. I am still convinced that open source is a better road long term than dependence on vendors who are subject to mergers and acquisitions. However, since there are no coders on my staff we are dependent on the open source community developers and the third party entities (K-INT for OpenRS, EBSCO for FOLIO, with the MOBIUS consortium managing the developer conversations). We were dependent on III before and their enhancement process was slow, so either way, we have to wait for enhancements. It has been a challenge to migrate to a system that, while it does some things very well, has not yet built out certain functions that we use daily. The most notable downgrades for us at this point are: -Lack of volume sorting (volumes in a set display in random order) -In-house use statistics -Print serials check-in -Item status codes (all our old status codes map to AVAILABLE, IN USE or NOT AVAILABLE) -Ability to designate non-consortial borrowing at the individual item level (there is a code in the item record, but its function hasn't been implemented yet) -Create Lists Things we like better with FOLIO: -Label printing -856 fields reside in holdings record rather than MARC bib record -When we get more fluency with LISTS and BULK EDIT and FOLIO adds more record type options, I think we are going to like certain things about updating groups of records. However, staff will need a more modern skill set to be able to use these features. As a manager, I see pros and cons to this. Good opportunity for skill building for the staff who can adapt, but I'm not sure all my staff can make the leap. We adopted EDS at the same time as all of this. It was pretty smooth to implement, and definitely helps with seamless discovery of our subscription databases. (Library type: Museum; collection size: medium; ils satisfaction: 7)

A lot of our support queries are directed to the community rather than to the vendor. (Library type: Academic; collection size: very large; ils satisfaction: 8)

While FOLIO may be a good product for individual institutions with robust systems' staff, the EBSCO FOLIO product developed for our consortium seems woefully under or undeveloped. It has been a frustrating experience that has required a massive amount of staff time and energy to do basic library tasks. We had a functioning system and we are now being asked to help build a system for a company through very painful trial an error and without compensation. Patrons who trusted us and our consortium for decades, have become very frustrated with the experience of using the catalog, requesting items from other libraries, and routinely running into unexpected issues. We are very unhappy with our new ILS so far but feel like we have few choices because of our size and dependence on our consortium. (Library type: Academic; collection size: medium; ils satisfaction: 2)

Just no AI, okay? (Library type: Academic; collection size: small; ils satisfaction: 2)

FOLIO is a flexible system, but it is still in the process of consolidation. One factor that gives confidence in its growth in capacity, support and functionality in the coming years is that academic libraries with a wide reach throughout the world have implemented it, both with support from EBSCO, as well as from other providers or even in local installations, showing that it is a system that is not necessarily tied to EBSCO, offering different possibilities for institutions that wish to adopt it. FOLIO also allows the manipulation of information by the library with relative ease. The library has been able to approach the mechanisms that FOLIO uses, and ultimately the Internet, to communicate information through APIs, so FOLIO has been of great support in the integration with other platforms, as well as in the learning of these communication mechanisms by the library for the creation of customized solutions that can improve the user experience. It is expected that in the coming years, FOLIO will see its functionalities increase, as well as adopt new cataloging standards. Some of the basic functions still have some shortcomings, highlighting the impossibility of viewing the user's photograph when making a loan (since it requires viewing it in the user module), and making renewals by entering the item (since the renewal is done with the user identifier, while renewing by item code requires more clicks), as well as some details of the cataloging process that can make it unnecessarily complex for the acquisitions staff. Although these inconveniences have been noticeable for the staff, we also consider that other tasks related to the adjustment of information, configuration of policies, sending notifications to users, generation of quick lists, management of electronic collections (although this function is still in a very early phase) have provided the library with greater control over the data it safeguards and manages. In general, with the adoption of FOLIO some aspects have generated greater facilities, others are still in early development, which has posed challenges for both the library and the provider in generating solutions. Finally, different projects have been generated in which FOLIO plays a role directly or indirectly, being a tool of operational relevance, but also in terms of innovation needs. (Library type: Academic; collection size: very small; ils satisfaction: 8)

We are already using an Open source ILS, Folio. (Library type: Academic; collection size: very small; ils satisfaction: 6)

ILS