30.05.2013 Views

2012 Best Practices for Government Libraries

2012 Best Practices for Government Libraries

2012 Best Practices for Government Libraries

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

173<br />

BEST PRACTICES <strong>2012</strong><br />

There are a million details to keep track of. Fortunately I have a very motivated<br />

staff, and we have good relations with the myriad of other parties affected. But<br />

one crucial point is that you have to keep a close watch on it. No one—No One—<br />

cares about your project as much as you do. Planning is good, contracts and<br />

Statements of Work are all very well, but there’s no substitute <strong>for</strong> keeping watch all<br />

the time.<br />

We have identified some issues with the whole off-site concept Library staff will<br />

retrieve materials <strong>for</strong> use by the College and Post communities. We expect to send<br />

a van once a day, a trip of about 40 miles one-way, so some delays in service are<br />

inevitable. Faculty have expressed understanding, but worry about the loss of<br />

browsing and the unavoidable delay. Our micro<strong>for</strong>m collections will be in the cave,<br />

and we have several patrons who regularly research them on weekends. They will<br />

have to do a little planning.<br />

Clausewitz famously spoke of friction, the general tendency of things to not work<br />

right or get muddled in wartime. It’s true when moving a library, too. Are there<br />

enough shelves where we need them? Did Kansas really have to reduce the bridge<br />

over the Missouri to one lane just when we needed it? We’ll we have a van and a<br />

driver to zip down to the cave every weekday, but how much more staff time will<br />

be eaten up paging and reshelving? What’s the tornado plan <strong>for</strong> the temporary<br />

building, which will essentially disintegrate into shrapnel during a windstorm? Did<br />

anyone bring cookies?<br />

As I write this, the move to the cave is nearing completion, and the move to the<br />

temporary building starts next week. I have no doubt that plenty of friction will<br />

arise during and after our move. We will have the opportunity to experiment with<br />

some service features that may or may not pan out. For instance, staffing a<br />

reference desk in the main classroom building, which is about 200 yards away.<br />

How we handle the photocopiers, scanners, fax machine, and digital sender is still<br />

somewhat up in the air. Our summer reading program will not depend on masses<br />

of moppets from the Child Development Center inundating the library, but will<br />

instead have librarians traveling to the kids with armloads of delectable books. If<br />

the off-site location <strong>for</strong> our microfilm works well, we may relocate those resources<br />

to a less accessible place when we return; after all, I haven’t bought a fiche<br />

collection in ten years. I’m retiring a platoon of analog micro<strong>for</strong>m reader-printers in<br />

favor of two digital ones, which should enhance the abilities of our researchers.<br />

And, needless to say, there is the exciting and terrifying issue of technologic change<br />

in the library profession as a whole. We know we are increasing network resources<br />

when we return, in an attempt to entice more customers and provide a better<br />

environment <strong>for</strong> our core academic users. Will we be adequately mobile-friendly?<br />

Can the Army’s administration keep up with the need <strong>for</strong> usable, accessible,<br />

content-rich web pages? How much manpower should I devote to our (justly)<br />

popular digital library (http://cgsc.contentdm.oclc.org/cdm/)? Will our reserve<br />

shelves be replaced with e-resources next year? Next week? Stay tuned. If there’s<br />

one thing <strong>for</strong> sure, it is that change is coming.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!