Open Collections

UBC Library and Archives

Meeting the challenge : creating a sustainable renewals calendar Westbrook, Danielle W. 2013

Your browser doesn't seem to have a PDF viewer, please download the PDF to view this item.

Item Metadata

Download

Media
494-Westbrook_D_Meeting_challenge.pdf [ 921.65kB ]
Metadata
JSON: 494-1.0223725.json
JSON-LD: 494-1.0223725-ld.json
RDF/XML (Pretty): 494-1.0223725-rdf.xml
RDF/JSON: 494-1.0223725-rdf.json
Turtle: 494-1.0223725-turtle.txt
N-Triples: 494-1.0223725-rdf-ntriples.txt
Original Record: 494-1.0223725-source.json
Full Text
494-1.0223725-fulltext.txt
Citation
494-1.0223725.ris

Full Text

 Meeting the Challenge:        Creating a Sustainable Renewals Calendar LITA/ALCTS Electronic Resources Management Interest Group 2013 ALA Midwinter Meeting Danielle W. Westbrook UBC Library @dwattersw  Today’s Topic  Meeting the Challenge: Successful Electronic Resources Management in the Absence of a Perfect System  Why Renew?  Why a Renewals Calendar? Purpose  •Track and display important renewal dates  •Allow the library to proactively assess electronic resources  •Permit strategic decisions about realigning/grouping renewals  Requirements  •Sustainable  •Accessible to all stakeholders  •Integrate into existing work    We created a renewals calendar...  How did we do it?  1. Mapped workflows for how we were disseminating renewal information at the time  2. Identified where UBC renewal data was living  3. Assessed our ERM’s functionality for managing renewals  4. Investigated how other libraries were tracking renewals  5. Developed a plan for managing and calendaring our renewal data   Existing Renewals Workflow (direct subscriptions) Reactive Manual Data Integrity Issues  What about our ERM? • Serials Solutions 360 Resource Manager • No calendar view • Renewals data stored at the license-level      *Based on the functionality of Resource Manager in summer 2012. Serials Solutions recently upgraded Resource Manager so that renewals are resource specific (at the journal/database level). This is great news. I talk about how this affects our Why Renew? project work at the end of the presentation. The Vendor License  Jan. 1 – Dec. 31 C Wrong renewal alert for resource C A B The Vendor Invoice  Sept. 1 – Aug. 31  What are other libraries doing? Informal Survey: What sorts of strategies and tools (calendaring software, ERM alerts, etc.) do you use to make renewal decisions? Homegrown solutions in lieu of or alongside an ERM  - “Giant unwieldy Excel spreadsheet”  - Separate renewals database (built in-house)  - Using Google Sites to house vendor contact, licensing, statistics, and a renewal calendar   Looked for Literature on Library Renewal Calendars (unsuccessfully)  Shapiro, Steven. (2010). Using Google Calendar as an Email Alert System for Electronic Resource Renewals. Journal of Library Innovation, 1(1), 52-56. Retrieved from: http://www.libraryinnovation.org/.  So what did we do? Simplified • Direct subscriptions only • Stick to core information • Generic non-renewal notice (90 days)*  Paid attention to data integrity  Looked to currently supported tools first • Voyager ILS Module • Microsoft Outlook         *Determined based on an analysis of the renewal terms outlined in licenses.  Renewals Query = Renewals Report  • Represents work formerly done by hand  • Report is appropriate for library-wide distribution  • Create calendar upload from report    Renewals Report + Calendaring template  Microsoft Outlook CSV. Template • Core information from the renewals report • Minimal reformatting • Could be part of a monthly or quarterly process     Moving forward  This is still a work in progress. At the end of the Why Renew? project we had a renewals calendar, but the ongoing implementation hasn’t happened.  Serials Solutions recently updated their Resource Manager to permit resource-level renewal management. We will need to evaluate the functionality that now exists in our ERM to see if we can begin storing our renewals information there.  Although this change to the ERM comes on the heels of us developing a UBC-specific solution to managing renewals, the Why Renew? project has made us more knowledgeable about our needs for storing renewals data; it forced us evaluate workflows and data management – something we needed to do, whether to maintain our own solution or to move our data to our ERM.   Questions?   Danielle W. Westbrook UBC Library @dwattersw danielle.westbrook@ubc.ca

Cite

Citation Scheme:

        

Citations by CSL (citeproc-js)

Usage Statistics

Share

Embed

Customize your widget with the following options, then copy and paste the code below into the HTML of your page to embed this item in your website.
                        
                            <div id="ubcOpenCollectionsWidgetDisplay">
                            <script id="ubcOpenCollectionsWidget"
                            src="{[{embed.src}]}"
                            data-item="{[{embed.item}]}"
                            data-collection="{[{embed.collection}]}"
                            data-metadata="{[{embed.showMetadata}]}"
                            data-width="{[{embed.width}]}"
                            async >
                            </script>
                            </div>
                        
                    
IIIF logo Our image viewer uses the IIIF 2.0 standard. To load this item in other compatible viewers, use this url:
http://iiif.library.ubc.ca/presentation/dsp.494.1-0223725/manifest

Comment

Related Items