Allison Erhardt and Lisa O'Hara
University of Manitoba Libraries
Vendor expectations - library often has to tell vendor a lot of information
Cost Savings - different title lists between vendor and library often have significant cost differences
Maintain perpetual access rights - especially important for journal cancellation projects
U. Manitoba had own home-grown ERM that they liked for some things but that got less and less useful as their number of ejournals went up. Selected Verde because it was the only one that allowed adding local reportable fields.
Verde implementation is still ongoing - acquired in May 2009. Still transferring data from homegrown ERM to Verde; set up local fields based on reports they knew they wanted to run.
Allison shows the Local Fields tab in eProduct attribute. Their local fields are labeled for how they track stuff - fields for consortia, core titles (i.e.: what titles they have in a package), liaison names, publisher record, publisher customer codes, Sirsi record number (used less now).
Report of eProducts from Verde, filtered on active, pulling local fields; dedupe in Excel.
Compare with publisher list - where Verde and publisher agree, there's nothing to do. When delete these, what is left is oddball titles that need attention.
Reconciling has rewards in time, accuracy, and money.
Some things they don't like about Verde, including some quirks of reporting and the acquisitions attribute (ex: if include customer number in acquisitions attribute, it will wipe out when you redo the acq record for the next year or next renewal, so need to keep this aquisition-y info somewhere else.