You may find yourself holding a camera worth more than your paycheck with no idea how to use it

The Story:  It has been decided that the library needs a new camera, mainly for event documentation.  The one currently in use is owned by the children's department, as they take the most event photos (because let's face it--kids' programs take way more fun pictures than grown-up ones...there are only so many angles of person-talking-in-front-of-powerpoint to be shot).  However, it is the reference department that decides not only to get a camera, but which one to get, without any input from the library staff who actually use the current camera, an 8-year-old point-and-shoot that while simple to operate, has seen better days.
So, what you're left with is an expensive mystery that should be able to take the perfect shot every time, but somehow manages to fall short.  The shots are blurry, the camera takes forever to snap a picture and you've already missed about twelve shots while you're trying to get the right focus on the first one, plus what you see on the screen/through the viewfinder differ greatly from what gets uploaded to the computer.  There is a whole bunch of extra ceiling and floor space that doesn't show up on the screen or in the viewfinder, making all your pictures unnecessarily far away.  Sure, you can crop it, but who wants to sit there and do that for a hundred pictures that you're just going to dump on facebook for all the kids' parents to tag each other in the comments section of instead of hitting the share button?  Sorry, got a little off-topic there.
Not only that, but the pictures are much higher resolution than the ones your old camera used to take, which means they take up a whole lot more space on the memory card.  You'll have to buy a bigger one or else delete photos after every transfer so as not to slow down already pokey picture-taking to a crawl.  This wouldn't be a big deal if you sorted and uploaded your pictures in a timely manner, but since nobody else on your staff is presently comfortable with sorting pictures and uploading them online, this step of program documentation generally takes a backseat.
Having a staff that isn't necessarily 100% comfortable trying new technology can be a problem when something like this drops in your lap.  It can mean that they default to using the old camera, not knowing that the memory card is in the new one, and they don't notice the glaring error message popping up on the screen every time they press the shutter button telling them that the picture isn't actually being saved.  Or, it can mean that they don't like covering programs any more because they feel stressed and intimidated by the new camera.  You can solve this by having your staff practice taking pictures of displays in the library with the new camera, things that are not going anywhere, so there's nothing to "mess up".  It helps if you discover the automatic mode where it senses what kind of picture you're trying to take first, and if you discover the on-off toggle for auto-focus, and the toggle for stabilizers, and point these things out to your staff.  There is also a button to turn the screen on and off, and toggling it one way or another seems to help a little with the extra space problem, and also warn those using it to zoom in more than they think they need to, because there will be extra space on the borders regardless.


The Lesson:  If you're buying a camera or other equipment that is an upgrade and will be used by the whole library, maybe consult each department about what their plans for it are, what concerns they have, etc.  Communication here is key.  There's no reason to surprise a department with new technology.  Surprises are not always a good thing, and that department may not have the skills nor time to really develop them to actually make that surprise "upgrade" worthwhile.

The Resources:  Honestly, the user manuals, how-to camera books, online tutorials, etc., all got really damn technical.  I didn't have the time to take a whole photography class just to learn how to make the expensive new toy take a decent picture.  In an active program, which most children's programs are, I just need to point, shoot, repeat, in rapid succession.  I'm sure this camera could do that, but I didn't know how to make it.  Learning about the auto-focus and smart-shooting mode helped, but not enough.  We did have a professional photographer who said they'd come in and show us how to use the camera properly, but it wound up not being an issue.  See the aside for that story.

An Aside:  About six months after we got this camera, maybe a little more, it got stolen.  Someone from reference used it to take pictures of a program and forgot to lock it up after, leaving it sitting out on the desk.  While all librarians were distracted with helping patrons, somebody swiped it.  By this point, we had a new memory card in it so we could at least go back to the old camera with the old card for a while.  The higher-ups were so mad about the loss of camera that it looked like we'd be stuck with the 8-year-old model until it was old enough to drive.  Eventually, though, they were persuaded to replace the expensive mishap with a less-expensive, but still high-quality camera that had fewer bells and whistles.  Thankfully, this one was easier to operate, and now staff were very careful about putting it away after use.  The technophobic members of the staff were a bit more comfortable with it, and now that's the only one we use if we can help it.

You may wind up not going to that off-site training after all

Stolen from the Google; impossible to tell who first took it

The Story:  I was notified by another town department that there were last-minute openings in a narcan (anti-overdose drug) training taking place off-site the next day in the evening, hosted by a local rehab clinic.  I got the OK from the boss, arranged after-work home plans, and emailed back the person from the other town department.  Huzzah, I got a reply the next day that I was signed up for that night's class.  I was told it was at such-and-such church the next town over.  I google said church, get an address, and head out.  The address takes me to a church whose name on the sign out front does not match the one I was given, but I figure it's got to be the right place because the address matches.  I drive around a little first just to make sure there isn't another church right up the road (because New England is lousy with churches and it's not uncommon to find them in clusters), but this one is all there is.

I get to the aforementioned church about ten minutes early, and walk straight into the middle of an AA meeting.  Someone in the meeting knows the rehab clinic people putting on my theoretical training, and tries to call them, but to no avail.  He then directs me to another church that while its name ALSO is not technically such-and-such, it is colloquially called that, and maybe that was the church the organizers meant.  So, I drive a few miles to the other church, and walk into the middle of a Christmas pageant rehearsal.  I ask a bewildered mom if there would be another such-and-such church, and she sends me to yet a third church whose name is not that, but that is sometimes called that.  I find my way there, and stumble upon a second Christmas pageant rehearsal.  A second bewildered mom tells me the only church she knows called such-and-such is the first one that I went to.  So, I go back there, find the AA meeting letting out, and ask someone if there is another meeting going on in the church proper or anywhere else that evening.  He says no, but that the pastor is in by now and maybe he can help me.  So, he takes me downstairs to the pastor's office, who has no clue about this meeting taking place at all, and he would be the one who does all the scheduling, so he would know.

He lets me use his computer, though, to check my email in case I got some stupid detail wrong, but I didn't, and I show him the email I got and he goes, "Well, that's us, and today, and the right time, but they're not here."  After shooting an email back to the organizer, I thanked him and left, and he wished me luck, but didn't bless me, which maybe means he knew there was no saving me from the type of lost I was.  I get in my car and call my boss, give him the short version of why after an hour of driving around I'm not going to the training, and decide to head home.  My phone then dies.  It was a miracle that it survived multiple GPS trips and a phone call as it was, but perhaps the divine destinations had something to do with that.  So, I head off in the direction I HOPE the highway is, and resolve to get some fast food on the way home for mollification, foregoing a pit stop at the liquor store.  Several hours after I get home, I get an email from the town department organizer, apologizing for giving me the wrong information.  Apparently it was at such-and-such library, not such-and-such church.

The Lesson:  The devil is in the details.  Piddly little things, like addresses, or the actual names of locations, can help attendees find their way to events.  Even if it seems straight-forward and obvious, always clarify these things before setting out.

The Resources:  I used old-fashioned printed google maps directions to get to the first location the first time, because I knew my phone was likely to die from a 15-minute GPS trip (even starting out at 100% charge, which it was), and I wanted to save it for in case I got well and truly lost.  Shockingly, this got me to the first church with no major hiccups.  After that, I just used the GPS app on my phone to get me to the other locations.  It did, in fact, die before making that phone call, and I sat in my car charging it for a while until it had enough juice to call my boss, before it died again completely.  It was 20 degrees and very dark out, and I didn't want to wait for it to charge again to maybe get me home, but I was lucky I had that car-to-phone charger handy anyway.