Fondly Remembering Our Implementation of Eds: 2014 MDL Vendor Day
•Download as PPTX, PDF•
0 likes•422 views
The document summarizes the experiences of an implementation team at the University of Baltimore in installing and using a new discovery system called EDS. It provides quotes from team members about various aspects of the implementation process. While there were some complications, the team was able to work through issues and felt the system worked well overall for students and faculty once in place. The team highlighted effective communication and keeping the implementation simple as important factors in the project's success.
Recommended
More Related Content
Viewers also liked
Viewers also liked (9)
Similar to Fondly Remembering Our Implementation of Eds: 2014 MDL Vendor Day
Similar to Fondly Remembering Our Implementation of Eds: 2014 MDL Vendor Day (20)
Recently uploaded
Recently uploaded (20)
Fondly Remembering Our Implementation of Eds: 2014 MDL Vendor Day
- 1. Fondly remembering our implementation of EDS Bill Helman, University of Baltimore flickr.com/namsj/
- 2. And it was all smooth sailing. http://commons.wikimedia.org/wiki/File:Sailing_Ship_Illustration.jpg
- 3. Mostly. Or at least my parts were. But this was a team effort.
- 4. Mostly. Or at least my parts were. But this was a team effort.
- 5. Mostly. Or at least my parts were. But this was a team effort.
- 6. Our Implementation Team: Aiden Faust, Bill Helman, Betty Landesman, Michael Shochet, Susan Wheeler
- 7. “It was. Interesting” “It worked out pretty well once it was up.”
- 8. “Implementation has two faces. We had a lot of trouble with implementation as ‘install a new product,’ but implementation as ‘use a new product’ went very well.”
- 9. “From my perspective, the most important things were keeping it simple and effective communication.”
- 10. Every large scale project will have complications, implementing Discovery is no different.
- 11. Every large scale project will have complications, implementing Discovery is no different. Item level data for unique holdings in the catalog.
- 12. Every large scale project will have complications, implementing Discovery is no different. Things getting turned on without our permission.
- 13. Every large scale project will have complications, implementing Discovery is no different. CONTENTdm: being the liaison between OCLC and EBSCO.
- 14. “They had difficulty interpreting our needs, but once they understood they did get things ironed out. It just took awhile in some cases.”
- 15. “Particularly good for students who are new to libraries.” “Even faculty seem to like it once they are shown the filters on the left.”
- 16. “Gives us more time to focus on teaching evaluating information, and less time on the how to get to ‘peer reviewed’ results.”
- 19. Branding: WYSWYGkinda. Wait, where does that color go? Why are they tied together?
- 21. Search Box Integration? No complaints.
- 22. Search Box Integration? No complaints. Really.
- 23. Search Box Integration? No complaints. Really. SearchBox Builder was a great time-saving tool, and would be great for people who didn’t know what those crazy strings meant. (our main site)
- 24. Search Box Integration? Also worked well in our LMS and the UB Portal.
- 25. Search Box Integration? Well our LMS (Sakai) does have some issues with displaying insecure content. But I think that has more to do with local security settings in Sakai, than it does with EDS itself.
- 26. One Last Challenge: We wanted to use profiles in a way they probably did not have in mind. Didn’t work out well in user testing: when folks got caught in confusing silos.
- 27. Thanks. This presentation is available at: slideshare.net/whelman Bill Helman, twitter.com/thinkpol http://whelman.com