Lessons learned: Combat experience from failing to implement an ERM, or what should have been asked to begin with. USAF PHOTO BY SSGT JENNIFER C. WALLIS Amanda Yesilbas ER&L 2009

This is hard... Electronic journals brought new and exciting problems. Licensing Keeping track of journals moving around. Access. And all the old acquisition problems.

DON'T PANIC!! Meaning don't rush out and buy something.

And do not go..... WOW! It does everything we should buy it!

What do you want to do? What are your priorities? Spoiler ALERT!

What resources do you need to manage? /

What tasks are you trying accomplish? dooley/ /

Who is using the ERM? /

Where is the information going into the ERM coming from? /

Are you using the ERM for consortial work?

Do you need interoperability? parkle/ /

What kind of reports can you get? /

Do I really need an ERM? /

When Standards are not enough:or the spirit is willing but the flesh is weak. DLF standards Functional Requirements Workflow Data element dictionary /

Don't lose momentum Don't be afraid to ask your vendor for improvements. Participate in work groups/listservs Document Don't believe it until it is real =4&page=4

Thanks! Amanda Yesilbas Florida Center for Library Automation