Posts in academic libraries

To Criticize, To Hope, and To Library

I’ve been struck by something on library Twitter recently. I doubt that anything has changed, but i seem to be noticing this more and wanted to dig deeper into my response to it. What I’m seeing is a lot of “either for us or against us” response to criticism of libraries. A lot of what I’m seeing is good push back, I’m certainly not arguing against the content of what people are saying. Instead, what I want to do is to look at criticism of and in libraries and see if there is something to learn in the general reaction, as opposed to simply choosing a side or deciding who is right and who is wrong. 

This is coming from a place of self-contemplation. At my intersections of gender, race, class, and other demographics I’m learning how to examine my initial emotional responses to external criticism and temper my defensiveness with listening. For example, when friends post online “Men are awful!” or something to that effect, instead of responding “YOU’RE WRONG! I’m not awful.”  I’ve been taught to listen to the complaint and to try not to be awful. When this happens, above all, don’t say #notallmen.

Maybe because I’ve been paying more attention to how I respond when groups I belong to are publicly criticized, I’ve seen that when libraries and librarianship are criticized, our first responses aren’t quite what they could be. So there are three examples of criticism of libraries and librarians that showcase our response. Again, my point in writing this is not to determine who is right and who is wrong, but instead, I want to figure out how can we best respond to criticism.

@theangriestlibrarian’s excellent rant to an uninformed library critic

(librarians) are so convinced that we must defend libraries against threats that we are defending libraries against improvement

In this lovely rant, @HalpernAlex takes down someone who suggests that libraries are no longer needed, or at least are no longer the most efficient way to provide the public with access to information. I have zero criticisms of the rant; I think that it’s is accurate. What I’m worried about is that we, as a profession, are more interested in preserving libraries as institutions than we are in fulfilling the mission of libraries. When we see bad ideas about replacing libraries, whether it’s this one (give the books to schools and close the buildings) or others (buy everyone Kindle Unlimited and stop funding libraries or academic libraries are vanity project that have already been replaced with smartphones) we (myself included) gleefully dogpile on the poor benighted fools who dare question the invaluable contributions of our vocation to the public good. My question is this: when librarians face a choice between libraries and something new that more efficiently serves our mission, how will we respond? Part of me worries that it will be with torches and pitchforks.

At least, this is what I’m afraid of. I’m afraid that we (librarians) are so convinced that we must defend libraries against threats that we are defending libraries against improvement.1)Though, obviously in this case, just dumping books in schools and closing libraries is the opposite of improvement.

@rdlankes’ tweet about a continuum of library quality and @lisalibrarian (& others)  response to this.

I’m really intrigued by this exchange. There are two good (and not mutually exclusive, in my view) arguments being made here. One: some libraries do bad work or at very least, bad libraries are the result of bad library work. The other: referring to library work as bad in public forums is disrespectful of library workers. So what do we do about libraries that fail in some aspect of their work?

The first example that comes to mind is the Florida librarian who broke the law and patron privacy ethics by calling the FBI to report on suspected library usage by 9/11 perpetrators.  If that is too ambiguous an example, nina de jesus’ article Locating the Library In Institutional Oppression and Cheryl Knott’s book Not Free, Not For All: Public libraries in the age of Jim Crow provide undeniable examples of not just bad libraries and bad librarianship, but libraries (the concept writ large) in the service of oppression.

if good library work is our goal, positive and nurturing conversation is more likely to achieve it than running down and disrespecting our colleagues

So I guess I’m taking a position here. I’m against the unwritten rule that orders librarians not to tell the truth about bad library work. On the other hand, I’m on board with the argument that says if good library work is our goal, positive and nurturing conversation is more likely to achieve it than running down and disrespecting our colleagues. As a personal rule, I try to talk about bad libraries and bad library work, but not bad librarianship or bad librarians. Failing this, if I’m talking about bad librarianship, it’s best to assume I’m talking about myself. We’ll see in the next example that I don’t always follow my rule here, but similar to the first example there’s a tension between telling the truth about library work and providing a consistent narrative most likely to lead to better library work in the future.

My tweets about bad library instruction and the responses to them.

I wrote some tweets earlier this month about bad library instruction and my response to it. There was more engagement with these thoughts than there is with most of what I write, so I appear to have struck a nerve with others. However, it wasn’t the same nerve that I had struck in myself. Reading how others responded to what I wrote, I saw a lot of people concerned about their own library instruction being seen as shit. I was more concerned with interacting with the course instructors–what do we do when then inevitable bad day of instruction happens? How do we safe-guard instruction programs from instances of low-quality work? I know that author intent theory is dead and what I intended is not more important that what the readers perceived, but it was hard to see the thread of conversation get away from me.

It was especially hard because my casual use of profanity and the scatological metaphor 2)I’m sure this reads as pompous, but it was SO MUCH FUN to type that I’m leaving it in. only amplified the disconnect. When instruction librarians are fighting for the time, respect, and resources we need to succeed, it must have felt awful to have another librarian say that our work is shit.3)I wasn’t trying to say that at all, but that’s really beside the point. Swearing about librarianship helps me, as a professional practitioner, to shed rose-colored glasses I have to wear at work. There are a lot of contexts in which I rightfully treat librarianship as holy. These make it necessary to have a space where I can blaspheme with critical thought. Otherwise I’ll have no choice but to believe my own marketing copy and drink the Kool-Aid. When we’re shifting perspectives or code-switching, hyperbole, profanity, and blasphemy can be contextually confusing. I’m confused as well. I still strongly believe that the library instruction I was writing about was undeniably shitty and that talking about shitty library instruction is a first step towards making better library instruction. Yet by not making my criticism general enough or impersonal enough 4)I really don’t think it matters if original  example was someone bad at their job or just someone having the inevitable bad day. I appear to have disrespected my colleagues and caused pain.

So What Do We Do About Criticism?

What do we do about criticism? We accept it. We listen to it. We don’t have to agree with it or obey it, but we should hear it. Librarians should strive to hear criticism of our profession without treating it as a personal attack. Library critics (myself included) should strive to hear the push back that tells us overly mean criticism tears down rather than building up. Criticism is a means to an end and that end is the public good, the good of the people who use libraries. The end we are pursuing is not the good of libraries or librarians, it is the mission of libraries.

We embrace criticism and we pursue to provide better criticism. We seek out criticism that provides hope for better libraries to come. I don’t have a better example of this than a talk given by Eli Neiberger in 2010.  Neiberger tell us that libraries are screwed, explains why, and then gives us reason for hope and a vision for services that better meet the information needs of our communities. For me, this is the platonic ideal of how do provide criticism. I worry that if we’re not able to hear that libraries are screwed, if we’re not able to hear that there are bad libraries out there or that if we make bad choices, we get bad libraries, and if we’re not able to hear that some library instruction is shitty, then we’re not able to avoid these fates.

 

There’s no intrinsic value in making us feel bad about libraries. There’s nothing to be gained in nihilism or in being a pretentious know-it-all who looks smart by correctly predicting that there is no hope. However, the path towards hope, the path towards a better future, the path towards better libraries goes through criticism, not around it.

Vocational Awe: A concept that helps us go forward here

Finally, I want to refer to someone else’s words and thoughts that do a better job of describing the dangers I’m trying to write about. Fobazi Ettarh wrote a great piece on Vocational Awe I strongly encourage y’all to read it. I’ve pulled two key passages here to explain the term vocational awe:

As we were brainstorming, I mentioned that I was interested in deconstructing this idea of vocational awe in librarianship. I saw the concept as the root of a lot of problems within librarianship, especially in creating a work/life balance and in larger critiques of the field. ~Fobazi Ettarh

So what exactly is “vocational awe?” Well simply put, it is the idea that libraries as institutions are inherently good. It assumes that some or all core aspects of the profession are beyond critique, and it, in turn, underpins many librarians’ sense of identity and emotional investment in the profession. The closest that Sveta found to a similar concept was occupational mythology in the journalism world.

My fear is that we (librarians) feel so much protective love for our work and our patrons and we feel so much justified fear that changing attitudes towards funding the public good and changing information technologies will undermine and destroy libraries; we feel this so much that we lash out against all criticism, even the criticism we need in order to have hope for a better future. Vocational awe is a thing that keeps us from building better libraries because we are afraid of listening to criticism. Vocational awe is what makes us define program assessment as “making the library look good to the administration so they don’t cut our funding” instead of as a practical tool to doing our work better. We can do better.

Hope.

Here’s the hope I have to offer. No matter how real the threats we face are, our cause is just. We can wrap ourselves in the confidence that when we teach people to find and use quality information, we are improving their lives. When we help kids learn to love literature, stories, and information we are making their futures brighter. When we library5)That’s right, a library isn’t a book warehouse, library is a verb! , we are doing the good work. This confidence is well-founded and it can replace vocational awe. We don’t have to be afraid of criticizing the library that we love, because we know that the library is unquestionably lovable. We don’t have to shy away from ugly truths about the shifting foundations beneath our feet, because our mission is clear.

We’re going to have to face a lot more ugly truths about the future need for today’s library services. We’re going to have to confront the ways in which our library structures prop up oppressive structures in society. We’re going to have to face the unpleasantness of learning that some of the ways in which we library are misguided. We are wrong about a lot of our thinking about libraries. That’s where the hope is. We can do better. We can find new ways to library that aren’t shit. We can find new ways to library that don’t exclude the marginalized. We can find new ways to library that continue to meet the changing information needs of our service populations. As long as people need information, librarians need to library.

 

Note: This post has been updated to correct the spelling of Fobazi Ettarh’s name. My sincere apologies for being careless.

Notes   [ + ]

1. Though, obviously in this case, just dumping books in schools and closing libraries is the opposite of improvement.
2. I’m sure this reads as pompous, but it was SO MUCH FUN to type that I’m leaving it in.
3. I wasn’t trying to say that at all, but that’s really beside the point.
4. I really don’t think it matters if original  example was someone bad at their job or just someone having the inevitable bad day.
5. That’s right, a library isn’t a book warehouse, library is a verb!

Library Instruction West 2014 Recap #liwest2014

tl;dr Library Instruction West is a Marvelous Conference.

My brain is still buzzing and feels pleasantly tingly from all of the good thoughts, emotions, and interactions I had at the Library Instruction West 2014 conference. I walked away energized by the people I met and by the content they shared. Portland State University was a fantastic host and the organizing committee, led by Joan Petit, did a lovely job bringing brilliant people with excellent content together in a well-run event. <tips cap>

Three things that made #liwest14 a special conference:

Beyond my general glowing endorsement, I want to highlight specific aspects that made Library Instruction West 2014 stand out from other library conferences. To start, this conference draws from a specific and well defined community of practice and these are my people. The conference also stands out because instruction librarians are skilled and engaging presenters; spending our careers speaking with groups of students pays off with impressive presentation skills. The rewards of attending are both practical and intellectual; I left with two ideas I’m already using in my instructional design and with big picture thoughts that I’ll be reflecting on for a while.

These are my people.

Library Instruction West is about library instruction and not really anything else. This means that sessions are targeted and participants have a lot of shared passions and interests. If you are an instruction librarian, this niche marketing makes Library Instruction West much more valuable in terms of content than larger national or regional conferences. I was taken aback by the emotional impact I experienced listening to lovely colleagues talk about inquiry-based-learning, nurturing curiosity in our students, using narrative methods in our instruction, teaching format-as-practice [1], teaching with digital badges, assessing game-based pedagogy, and clever teaching hacks for survey software.I’m a bit of a utility infielder in library work. I do systems stuff; I do some web stuff; I do some instruction stuff; I’m trying to learn how to do more metadata stuff. That said, I came into the field as an instruction librarian and no matter how far my curiosity takes me, my core values come from instruction. Of course, as with most good conferences, the best information is transferred informally between sessions, at meals, or socially. I got to meet a lot of folks in person I’ve come to respect and admire through Twitter. I was able to put faces to Twitter names and spend a couple of days with some truly lovely people. It’s nice to be surrounded by one’s people, to feel part of a tight-knit community of practice.

Instruction librarians are skilled and engaging presenters.

It is a real treat to watch experienced presenters who have a good body of practice work with an audience. In my two days at Library Instruction West I learned as much from watching how presenters interacted with their audiences as I did from the information being transferred. This is a rare treat. At other conferences, I’ve learned AMAZING THINGS from people whose job descriptions don’t include being interesting at the front of a room and I’ve also realized after a talk that the charming and engaging speaker really didn’t say anything profound or useful, but attending a conference full of engaging speakers who are intentional about their presentation style is WONDERFUL. It is also nice to have sessions where attention is paid to active learning, various learning preferences or styles, and non-traditional visual presentation techniques. I had the opportunity to observe small break-out sessions with group work, activities based on physical objects, self assessment exercises, and excellent question and answer sessions. I also got to learn from people giving very traditional talks using slide decks that were well designed and rich with information. Being able to see, hear, and interact with really talented colleagues practicing excellent pedagogy is a learning experience that I really can’t duplicate by reading about it. So if my effusive praise above hasn’t already convinced you to attend Library Instruction West 2016 in Salt Lake City, this may be the most appealing aspect: you’ll have the opportunity to experience experienced and skilled library instructors demonstrating what they do best first hand.

I left the conference with two ideas I’m already using in my instruction and with big picture thoughts that I’ll be reflecting on for a while.

Idea the first:

In Zoe Fisher’s session Live the Question, Love the Question: Inquiry-based learning in the one-shot she described a method of helping students craft rough topics into functional research questions. This is exactly what I need for a very large multi-section class I work with. Each semester the largest barrier I see to student success is the inability to see a topic, research question, and thesis as three separate things. Zoe used inquiry-based learning theory to design an exercise where the students explain what they know and then using that foundation to tease out interesting questions. My History faculty have already signed off on using the “what I know / what I want to know” table she described in their Fall classes. Hopefully, this will help us move from the first spark of student curiosity to potential research questions more smoothly and naturally.

sample table for what I know | what I want to know excercise
Sample “what I know | what I want to know” table. Click for larger view.

Idea the second:

In Kevin Seeber’s session Teaching “Format as Process” in an Era of Web-Scale Discovery he delivered a well-founded argument for a turn towards teaching process and away from teaching formats. Process being the critical thinking steps that make up scholarship and formats being the packages information is delivered in. He sums up his reasoning as: “the way we search is changing, we need to teach things that are constant” and “don’t teach the interface, teach the results.” His entire line of reasoning is a treat, so please don’t miss reading the whole presentation. Using what I learned from Kevin’s talk, I’m going to embrace the statement “Information literacy is not about knowing “how.” It’s about knowing “why.”” and do as much as I can to re-write the instructions for an assignment in the course mentioned above to explicitly refer to process instead of to formats. For example, there won’t be a “Finding Newspapers” section, but there will be a section that uses newspapers to “Find current information on your topic.” The reason for this shift is to reinforce the scaffolding in a semester-long assignment. Students are too often jumping through hoops to complete the assignment, I want to reinforce that the hoops are part of a method and not just arbitrary busy-work.

Big picture thoughts:

As I listened and interacted with the presenters and brilliant librarians around the event, I found my mind returning to a couple of big-picture concepts that I’m going to need some time to chew on. The first was the subject of Anne-Marie Deitering and Hannah Gascho Rempel’s talk, methods to engage student curiosity in research. Allie Flanary also had good things to say about curiosity in conversation between the sessions. She’s working on a sabbatical project on student curiosity, which I’m anticipating with great interest. Engaging curiosity is a big reason I’m a teacher and it’s the most rewarding aspect of the work. Seeing librarians identify curiosity as the keystone of our instruction work is inspiring and I want to explore where this line of thinking leads people.

A second big-picture thought that I came back to at several points during the conference is the impact of web-scale discovery tools on library instruction. This is a topic that I’ve been fixated on for a few years now. Search interfaces for web-scale discovery tools closely resemble search interfaces for single databases or catalogs even though the underlying architectures are very different. At what point should we teach students that this is a different kind of search? It’s not obvious, but it’s significant. The search we do now is increasingly different from searching a single index and the gap widens every day. For a great reading on this, see Aaron Tay’s excellent post Why Nested Boolean Search Statements May Not Work As Well As They Did. Even though search interfaces look the same, the underlying math is very different. Web search and discovery layers look more simple than a database search, but underneath they are MUCH more complicated. I realize not every student needs to be an expert in big data, but “How much does a competent searcher need to know about how these new tools work?” is a live and relevant question that we don’t have an answer to.

Wrapping up

Library Instruction West is a small, intimate conference focused on issues of library instruction, the librarians who do this work, and the students we work with. It is full of excellent content and is attended by fascinating librarians who are there to share the best work being done in the field today. If this sounds like your cup of tea, the 2016 edition will be hosted in Salt Lake City. I hope to see you all there.


Notes

[*] For what it’s worth, I thought the shiniest spark in a brilliant couple of days was Kevin’s presentation. (back)

The Mobile App Design Process: A Tube Map Infographic

**This post was originally published in ACRL TechConnect on March 4, 2013***

The Mobile App Design Process Tube Map:

Last June I had a great experience team-teaching a week-long seminar on designing mobile apps at the Digital Humanities Summer Institute (DHSI). Along with my colleagues from WSU Vancouver’s Creative Media and Digital Culture (CMDC) program, I’ll be returning this June to the beautiful University of Victoria in British Columbia to teach the course again [1. http://dhsi.org/]. As part of the course, I created a visual overview of the process we use for app making. I hope you’ll find it a useful perspective on the work involved in crafting mobile apps and an aid to the process of creating your own.

topological map of the mobile app design process
A visual guide to the process of designing and building mobile apps. Start with Requirements Analysis in the upper-left and follow the tracks to Public Release. (Click for full-sized image.)
Creating the Tube Map:

I’m fond of the tube-map infographic style, also know as the topological map[2. https://en.wikipedia.org/wiki/Topological_map], because of its ability to highlight relationships between systems and especially because of how it distinguishes between linear (do once) and recursive (do over and over) processes. The linear nature of text in a book or images in slide-deck presentations can artificially impose a linearity that does not mirror the creative process we want to impart. In this example, the design and prototyping loops on the tube-map help communicate that a prototype model is an aid to modeling the design process and not a separate step completed only when the design has been finalized.

These maps are also fun and help spur the creative process. There are other tools for process mapping such as using flowcharts or mind-maps, but in this case I found the topological map has a couple of advantages. First and foremost, I associate the other two with our strategic planning process, so the tube map immediately seems more open, fun, and creative. This is, of course, rooted in my own experience and your experiences will vary but if you are looking for a new perspective on process mapping or a new way to display interconnected systems that is vibrant, fun, and shakes things up a bit the tube map may be just the thing.

I created the map using the open source vector-graphics program Inkscape[3. http://inkscape.org/] which can be compared to Adobe Illustrator and Corel Draw. Inkscape is free (both gratis and libre) and is powerful, but there is a bit of a learning curve. Being unfamiliar with vector graphics or the software tools to create them, I worked with an excellent tutorial provided by Wikipedia on creating vector graphic topological maps[4. https://en.wikipedia.org/wiki/Wikipedia:Graphic_Lab/Resources/Draw_topological_maps]. It took me a few days of struggling and slowly becoming familiar with the toolset before I felt comfortable creating with Inkscape. I count this as time well spent, as many graphics used in mobile app and icon sets required by app stores can be made with vector graphic editors. The Inkscape skills I picked up while making the map have come in very handy on multiple occasions since then.

Reading the Mobile App Map:

Our process through the map begins with a requirements analysis or needs assessment. We ask: what does the client want the app to do? What do we know about our end users? How do the affordances of the device affect this? Performing case studies helps us learn about our users before we start designing to meet their needs. In the design stage we want people to make intentional choices about the conceptual and aesthetic aspects of  their app design. Prototype models like wireframe mock-ups, storyboards, or Keynotopia[3. http://keynotopia.com/] prototypes help us visualize these choices, eventually resulting in a working prototype of our app. Stakeholders can test and request modifications to the prototype, avoiding potentially expensive and labor intensive code revisions later in the process.

Once both the designers and clients are satisfied with the prototype and we’ve seen how potential users interact with it, we’re ready to commit our vision to code. Our favored code platform uses HTML 5, CSS 3, jQuery Mobile[4. http://jquerymobile.com/], and PhoneGap[5. http://phonegap.com/] to make hybrid web apps. Hybrid apps are written as web apps–HTML/JavaScript web sites that look and performlike apps–then use a tool like PhoneGap to translate this code into the native format for a device. PhoneGap translates a web app into a format that works with the device’s native programming environment. This provides more direct and thus faster access to device hardware and also enables us to place our app in official app stores. Hybrid apps are not the only available choice and aren’t perfect for every use case. They can be slower than native apps and may have some issues accessing device hardware, but the familiar coding language, multi-device compatibility, and ease of making updates across multiple platforms make them an ideal first step for mobile app design. LITA has an upcoming webinar on creating web apps that employs this system[6. http://www.ala.org/lita/learning/online/HTML5].

Once the prototype has been coded into a hybrid app, we have another opportunity for evaluation and usability testing. We teach a pervasive approach that includes evaluation and testing all throughout the process, but this stage is very important as it is a last chance to make changes before sending the code to an app marketplace. After the app has been submitted, opportunities to make updates, fix bugs, and add features can be limited, sometimes significantly, by the app store’s administrative processes.

After you have spent some time following the lines of the tube map and reading this very brief description, I hope you can see this infographic as an aid to designing mobile web apps. I find it particularly helpful for identifying the source of a particular problem I’m having and also suggesting tools and techniques that can help resolve it. As a personal example, I am often tempted to start writing code before I’ve completely made up my mind what I want the code to do, which leads to frustration. I use the map to remind me to look at my wireframe and use that to guide the structure of my code. I hope you all find it useful as well.

 

(This was originally published on the ACRL TechConnect site. If you care to comment, please join the conversation there.)

#DigiWriMo #acwrimo 2012 What I’m doing

Ok, so the title of this post may be misleading. I’m not certain I know what I’m doing, other than I’m doing #digiwrimo and #acwrimo this year. This means I’m going to focus on getting a metric shitte-tonne of writing done in the month of November. Follow the links above for the official rules, but I’ll be breaking those. These are my rules:

  • I’m going to write for at least two pomodoro units each work day. This isn’t very much.
  • I’m going to make progress on at least my accepted Online Northwest presentation and an article I should have written 18 months ago.
  • I’m going to include non-text-entry parts of writing such as editing my own writing and others’ work and also my own project management as “writing” tasks
  • Twitter and other social networking doesn’t count. (They don’t move me toward my productivity goals.) Neither do things like writing Goodreads book reviews. (These are things I do instead of writing.)
  • I’m going to pursue a thought I’ve been chewing on until I either have a draft or I’ve decided it is stupid. The thought is that library public services can be split into two approaches: UX design and the hacker ethic. One has few barriers to access but incentivizes  a passive approach to receiving pre-digested information. The other is more difficult and has technology and skill barriers but incentivizes an active approach to creating and integrating new knowledge. For now I’m calling the two approaches “Jobs” and “Woz.”
The Main Project

The main project I want to progress on is a paper on the effects teaching search engine architecture and SEO have on students information literacy. I’ve presented a few times on this subject but need to write an actual paper. It’s based on my classroom experiences, but I’ve also started a review of textbooks used to teach search in Information Science / Information Management graduate programs to track how much information architecture librarians are provided with in their graduate education. My hypothesis is that searchers who understand how both keyword-relevance algorithm search tools and traditional databases, indexes, and well-ordered sets of metadata are structured are able to make better practical decisions in their search processes.

What I need to do is to gather and collate a couple years of divergent projects and false-starts and squish them together into a cogent outline.

Side Project One:

I have promised to build some training materials for the ACRL LITA Code Year Interest Group on working w/ APIs. I’ve decided to work w/ OCLC’s Worldcat Local API to solve an annoying problem with our catalog. (OK, the problem is in the DATA, not in the tool that searches the data.) Currently, government documents in electronic form are cataloged as books. So, when students search our catalog looking for locally held books they can check out, they have to wade through pages of electronic government reports, white papers, and hearings. Weeding out these items that are not physical books on our local shelves takes an insanely complex series of Boolean operations that I once discovered by failed to write down.

My project will be to write a simple search web-app that can be used either as a search box on a web page or as a mobile app that automates this complex search as a simple “find books I can find on the shelf” search box. As I build this, I’ll record the steps and publish a training guide to simple deployment of OCLC’s Worldcat search API.

Side Project Two:

I mentioned I’m looking into the hacker ethos and UX design as competing priorities in public services librarianship. Perhaps they are in a dynamic balance instead of directly competing, but this is something worth thinking/reading/writing/mulling over.

Side Project Three:

Library Boxen. I’ve orderd a couple of the routers used in the Library Box project and I have an implementation plan for one of them. I’ve just hacked a spare home wifi router w/ DD-WRT, so I think I”m ready to install Open-WRT on the hardware, then the Pirate Box software, and then Jason Griffey’s Library Box code on top of that.

I’m hoping to deploy my first Pirate Box at the Fort Vancouver Historical Site in support of the CMDC’s mobile project there. My CMDC faculty colleagues Brett Oppegaard and Dene Grigar have been developing mobile apps to help present rich historical content available to visitors at the site. The historic fort is remote and out of range of wifi and most cellular broadband signals. The Library Box would be a solution to offer visitors the chance to download the app itself or rich media content to help make their visit to the site more informative.

This is primarily a making/hacking project, but I’m betting I’ll find some way to write (yack) about the project before I’m done.

Side Project Four:

I’m currently a blogger for ACRL’s TechConnect blog. I’m struggling to get my work in on time. (Translate: missing deadlines pretty badly) If I sit down to write every day, there is no reason I can’t hammer out a couple of posts to keep on hand, giving me a buffer. This week, in fact, I’d like to finish my piece on the Hacker Ethos and Librarians. This will detail both mindsets and tools librarians can use to empower us to remake our online and physical environment to meet our needs. No longer will we have reason to complain about our tools. If they don’t meet our needs: remake them until they do! I recently gave a talk to a class of undergrads new to digital media on the ethics of hacking and I’d like to modify that content for my library colleagues.

Yack Yack

If I get half way through half of these things, it will be a highly productive month. I’m not interested in 50k words in 30 days. I’m interested in building new workflows that get some work done. I’ve got plenty of interesting things to think about, #digiwrimo and #acwrimo are, for me, a chance to DO THINGS instead of just keep lists of interesting possibilities.

 

As the (tenth) Doctor says: “Allons-y!”