What Your Tech Wants You to Know
•
0 recomendaciones•796 vistas
No, your library's tech staff doesn't hate you. Or try to confuse you on purpose. They even speak the same language as you do! Yet, often, conflict arises between tech and other library staff. Everyone gets frustrated, and issues don't get solved as quickly as everyone would like. Discover what you can do to make communication easier and make problem resolutions happen faster. Hear stories and some words of wisdom from techs on the front lines of library technology. Learn how to approach troubleshooting like your tech does, and even some basic things you can even do on your own.
Recomendados
Recomendados
Más contenido relacionado
Destacado
Más de Laura Solomon
Más de Laura Solomon (16)
Último
Último (20)
What Your Tech Wants You to Know
- 1. What Your Tech Wants You to Know An webinar Laura Solomon, MCIW, MLS laura@designforthelittleguy.com Infopeople webinars are supported by the U.S. Institute of Museum and Library Services under the provisions of the Library Services and Technology Act, administered in California by the State Librarian.
- 3. Not all IT people are the same. No, really, this matters.
- 5. We make it look easy, but…
- 6. Real life IT
- 7. “What did you do before Al Gore invented it?”
- 8. It’s not new & shiny
- 10. It’s not always what you think it is
- 13. Understand that we’re jugglers
- 14. Be careful what you say
- 16. No, you’re not stupid
- 17. Ask & Pass
- 20. From Hitchhiker’s Guide to the Galaxy
- 21. Respect channels
- 22. “The computer is down!” • The ILS software temporarily lost network connection • A workstation lost network connection • All workstations lost network connection • A workstation will not boot • An unexplained message appeared on a workstation • A given website will not load • Someone has disconnected the display from the workstation, or almost any other possible occurrence.
- 23. “Take the time to explain your problem. If your explanation is one sentence, it’s probably not enough.” --IT guy at Stanford University
- 24. A picture is priceless
- 25. What to include? • Tell the truth • Is it reproducible? • What happens if you try another computer or browser? • Screenshot and/or actual text of error message • Don't just say it's broken, say HOW it's broken
- 26. We go here
- 28. ????
- 29. + + FTW FTW
- 30. Understand dependencies If “A” doesn’t work, then “B” probably won’t, either. A B
- 31. Simple things count • Check power, cables and paper • Is the computer frozen, or just the program? • Recognize that printing directly from the Web or from an email is often a losing proposition
- 32. reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot reboot
- 33. Skills to learn • Check & clear the print queue and the printer’s buffer • Copy & paste from the keyboard • Which emails are scams
- 35. Me: Hi what’s you problem? Caller: my computer is giving me an error. Me: Okay, what’s the error message say? Caller: I don’t know I just clicked OK and it went away. Me:……………………………..?
- 37. “I was once instructed to refer to the computer as a monitor and the monitor as a computer in order to suit the outlook of a particular co-worker. “
- 38. Printer pickle
- 39. Not thinking it through
- 40. Once a year
- 41. A patron story
- 42. Not always about the tech
- 44. 4 surefire ways to annoy IT staff
- 45. 1. Staring at plugs
- 48. 4. Anecdotes
- 50. Reporting matters. A lot.
- 52. YOU *are* a tech
- 54. We are not the enemy
Notas del editor
- Libraries are technology-driven.