Abstract

PurposeThis article seeks to provide insight on how librarians managed through the recession. It aims to highlight key areas of concern such as budgets and personnel. It is the culmination of two surveys administered in the succeeding summers of 2009 and 2010.Design/methodology/approachThe library community was notified of the surveys and provided the surveys' link via numerous library listservs. The same listservs were used for each survey. The responses received were from representatives of academic, special and public libraries.FindingsAn examination of the surveys reveals that budget cuts were worse in fiscal year (FY) 2009 than they were in 2010. Suggesting the cuts enacted in FY 2009 were effective thus less severe cuts were needed in FY 2010. Stress levels were high for FY 2009 and inched higher in FY 2010. There was no significant help, in terms of cost sharing for purchases, from the departments within the organizations the libraries served. Best practice suggestions were offered in many areas to include communication, purchasing and personnel.Originality/valueWhen the economy experiences a contraction, businesses, governments and the general population begins to rein in expenses. This affects libraries of all types, special, academic and public. The article explores how the library community dealt with this issue and provides information that generates problem solving ideas for those in budgetary and leadership roles.

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.