Verde implementations - Monday 8am
Jennifer Weintraub, Yale (single-instance install)
Betty Day, U of MD (consortial install)
Ted Koppel, Ex L - an early peek at the next version of Verde
I'm going to attempt to blog live so some of my notes may not make much sense... and forgive the typos!! The room is packed! An ALEPH/Verde customer from Towson in MD is sitting next to me. They've been on ALEPH (the equiv of Voyager) since 2003 and are waiting to go live with Verde.
UCSD has a Verde install.
Weintraub: STILL Creating Green Space for e-resources: Verde at Yale. Jen is in Coll Dev
Have worked 9 mos. as of June; last 6 months a lot done. Now in production.
Has Voyager ILS; SFX link resolver
Challenging with legacy systems that must be used for imports
Why Verde: 22 libraries, 600 dbs, 35,000 ejournals
Had homegrown ERM, runs A-Z list
chose Verde because of their exp with SFX; production with SFX since 2002
have dedicated staff working with SFX
15% of ejournals are not in SFX: had some impact on implem of Verde
3 mos. of pre-implmenetation, including what attrituges of DLF ERMI fields
beta July 2005; 1.0 Verde in Sept.
implementation group has 10 members plus others: 2 TS, 3 selectors, 1 systems, 4 e-coll people
subgroups also: 1. how to describe dbs; 2) training for those looking at Verde; 3) how to re-con license info from homegrown system
What do we want Verde to do
who will use Verde
what do we want to change in Verde
is data accurate
do we have a back up
thought they'd be done in a year but needed to wait until Verde 2.0
beginning this spring, smaller group will work on system
homegrown used for holdings and title info (SQL db)
didn't have contact info or which libr
A-Z list running from the SQL
now in beta with SFX for A-Z (had to negotiate with pub srvs staff!)
who will use:
all selectors? ha!
editors will be limited - some selectors who will edit contact info
(version 2.0 allows setting up access rights)
change in Verde
have set up fields which should be used in each attribute & ID'd 'which tabs are not used at all
used as ref to prepare documentation
attributes: package type, status, selection status, sponsr lib, concurrent users, +
took out some fields from drop downs so not so confusing
is data accurate?
migrated as much as they could from their homegrown
had bad data: ISSNs didn't match, so had to do clean-up
clean-up was a training opportunity for staff
uploaded spreadsheets of journals that are not in SFX
do we have backup server?
right now will lose a day's worth of data but they're okay with that; would like a backup server so they don't get too far behind
10 people can edit
will add info as we touch each record (recon of data is difficult - adding data in project style
Verde mgm group will manage further implementation
impact on staff: positive - previously menial tasks, working on spreadsheet; much more meaningful
since Verde updates holdings info; did have to learn a whole new system
used a 'playground' environment for traning
centralizing mgm of e-resources (previously selectors did some license negotiation, worked on details)
managing expectations: had to do some PR with other depts. about why Verde would be great - almost like sliced bread
Things are going to be different now, and that is okay.
train those who will look at Verde
pulling info into SFX menus
usage stats through SUSHI
managing SFX from Verde
Rerpots: what reports do we need and what do we do with them afterwards
more people editing and using workflows and alerts
connection to Acq records in Voyager (Voyager data will be pulled out on a web page, that will be linked from Verde)
Get a training instance (playground) : being 100% accurate from the beginning is very important because you have to re-set ??? and work is repetitive
who is going to keep Verde going?
more library staff will grasp complexity of E-r mgm
8FTE total across Yale libraries managing e-resources (1 also works in acq)
acq info: can't do dynamic linking so output it in HTML & link
what level are staff: 4 librarians, 4 support staff
next speaker: Betty Day from MD
Implementing Verde in the USMAI Consortium:planning and implementation
has been acccum data that is financial, legal, etc.
selection criteria and decision
planning before implementation
planning the implementation
where we are today & how we got there
basic criteria for selection
DLF ERMI standards
SFX interoperability (wanted their indiv libraries to maintain their local SFX instance)
ability to handle combination of consortial and individual library needs
planning before implementation
not just a product but rather a process
implementation in phases: not all libraries at once; not all functionality at once
- basic admin data and SFX
- licensing data
- links to acq (haven't started yet)
- usage stats / SUSHI and others as they follow (haven't started yet)
self analysis: what are our needs? what are the workflows?
Betty reviews the consortial set up in MD
THis is getting very long so I'll save and start a new entry.