Cargando…
The myth and magic of library systems /
The Myth and Magic of Library Systems not only defines what library systems are, but also provides guidance on how to run a library systems department. It is aimed at librarians or library administrations tasked with managing, or using, a library systems department. This book focuses on different sc...
| Clasificación: | Libro Electrónico |
|---|---|
| Autor principal: | |
| Formato: | Electrónico eBook |
| Idioma: | Inglés |
| Publicado: |
Waltham, MA :
Chandos Publishing,
[2015]
|
| Edición: | First edition. |
| Colección: | Chandos information professional series.
|
| Temas: | |
| Acceso en línea: | Texto completo |
Tabla de Contenidos:
- Front Cover; The Myth and Magic of Library Systems; Copyright; Contents; Acknowledgments; About the Author; Preface; A missive to administrators; A missive to library IT department heads and library IT administrators; A missive to new librarians in IT and students; A missive to library school faculties and administrators; A missive to IT committee members and other engaged library employees; List of figures; Chapter 1: Atlantis wasn't a magical place and library systems are just library IT ; 1.1 World building and the creation of systems; 1.2 How IS turned into IT.
- 1.3 Library systems are IT minus two things plus those same two thingsUniversity Librarian; University Librarian; Library Director; Dean of Libraries; 1.4 Library roles are specialized today, so are IT roles; Chapter 2: Creatures of ancient myth: The Titans and the systems librarian; 2.1 In the land of the blind, the one-eyed librarian is king; 2.2 Even specialized MLIS programs don't provide IT fundamentals; 2.3 You meant automation librarian, didn't you? Say yes; 2.4 The disappearing act: Making your own position obsolete; Chapter 3: Customers, patrons, users, and unruly mobs.
- 3.1 Ignorance, repetition, and conflicting priorities: Why the customer isn't in charge3.2 Don't ignore 10,000 people to serve one person; 3.3 Dealing with problem customers; 3.4 Your IT unit is a therapist's couch and priest's confessional; Chapter 4: Reading users' minds; 4.1 Divining what happened from incomplete information; 4.2 Knowing the common errors and common resolutions; Chapter 5: Sleight of hand: Service or the appearance of service; 5.1 Resources versus service levels: An exercise; 5.2 [insert thing] as a service; 5.3 Tiered helpdesk, just like tiered reference.
- 5.4 Using technology the way it was intended5.5 Teach your users how to Google their own solutions; 5.6 Don't share complete information, share popular information; 5.7 Apologize like the user is your significant other (it doesn't matter if he or she is wrong); 5.8 Pretend your user is smarter than you: Ask stupid questions; 5.9 You can't over-communicate; 5.10 Stop the bleeding instead of applying bandages; 5.11 Do a thing well before you do a thing twice; 5.12 Do a thing well before you do more things; 5.13 Don't do a thing if you can't do it well.
- 5.14 Set your IT unit's priorities: An heuristic for calculating impactChapter 6: Taking on apprentices: Educating your customer base; 6.1 Prevention: You can lead a horse to water, but can you teach a user to fish?; 6.2 Self-documenting interfaces, teachable moments, and point of need help; 6.3 Train the trainer and online videos (clever ideas for lazy cheapskates); 6.4 Skills and inventory assessment; Chapter 7: Do the impossible: Slaying dragons without time, people, or money; 7.1 Redefine the problem; 7.2 Triage the hell out of the problem; 7.3 Solve the visible tip of the iceberg.