Discovering Discovery at LITA Forum

Notes from a ┬átalk by Annette Bailey of Virginia Tech at the LITA National Forum, “Discovering Discovery.”

Virginia Tech has been a Summon customer since 2010. They have leveraged Summon to change cataloging practices locally. Still using original Summon (1.0) interface.

Library users are shifting behaviors. Increasing usage of online resources, physical spaces — but not physical resources. Discovery largely happens through Summon. How can VT know what its users are doing? COUNTER provides some information, but its delayed, and hard to process. Summon provides aggregate data on search terms and click data. How can we know what users are doing in real time? And share it with other members of the community, show visually what research is happening, live?

Discovery VisualizationThat is the heart of Discovering Discovery — what are users clicking on in Summon, in real time. Can’t tell if they use the item, but can tell that they accessed it.

This tool helps everyone — librarians, the public, students — to understand what is being done in the library. User does a search. There’s some custom JavaScript in the Summon interface that sends a record of the click to the visualization server, which stores it in a database. A visualization tool then makes a display on demand. It grabs the Summon record ID, unique for each item. They then use the Summon API to grab the metadata for that query — because Summon IDs are not persistent over the long term. All of that is stored in an SQLite database.

As a side note, they can tell how many unique items were clicked on over time — hard to do otherwise.

Current log analysis extracts and tabulates data at 1 minute, 5 minute, 1 day, 1 week intervals. Tabulates by discipline, content type, source of record, publication year. All comes from Summon, which means data are problematic. Does word frequencies for abstract, title, and abstract & title combined, and keywords & subject terms.

Use the d3.js library to do visualizations. It’s a powerful tool, but hard to work with. Follows jQuery in style. Also uses a variety of server-side technologies.

Summon 2.0 — not there yet. Unlike Summon 1.0, there is now an officially sanctioned way to include JavaScript (it’s a hack in 1.0). It now includes d3.js in Summon — they do not appear to be using it yet, but it’s there. Look out for visualizations at some point…. But they need to reverse engineer Summon 2.0 to achieve the same effect as in Summon 1.0.

Using this with other discovery services. You need to be able to record clicks, in real time. You need an API to get the machine data. If you use a different discovery service and want to try adapting this code, VT would like to work with you.

The visualization is the hard part; getting the data was the relatively easy part. Code needs to be consolidated, into a cloud solution, to make your version for your own use. (Like the Libx edition builder).

The 4th Floor and Library Transformation

This is the second keynote address at the LITA Forum in Louisville. The speaker is Nate Hill, assistant director of the Chattanooga Public Library. Follow him on Twitter at @natenatenate.

Nate Hill speaking at LITA Forum 2013The 4th Floor project is more a community organizing project than a technology project. When Nate started there a few years ago, the Chattanooga Library was seriously broken. Technology improvements are just one portion of the overall improvements being made. Chattanooga has gigabit networking throughout the city. So the city has a lot of potential and lots of recognized need for change and reinvention.

Unlike many brutalist all-concrete buildings, the CPL has large amounts of open space on each floor — it was designed with an open plan, so they aren’t as constrained by solid concrete walls. This gives them some flexibility.

Nate is going to focus on one aspect of this reinvention. We’ll start with the “why:” moving from Read to Read/Write. Everyone in the LITA audience at the moment can create something and make it available to everyone. Before that was possible, we needed libraries to store relatively rare copies of things. Library was about access. Now, it’s about providing tools to create things. Connectivity is a key underpinning to these tools.

CPL uses their 4th floor space as a “beta space” — the library can experiment, and the public can experiment. 14,000 square feet of space was used as an attic. They solved the problem collaboratively — invited people to meet in that space. Started brainstorming what might be useful to do. This started about 18 months ago (around January 2012).

Had a public auction, got rid of all the stuff. Net profit: $1500.

So, now what? A vast amount of empty space, with no added staff resources to do new things. Answer? Strategic partnerships with other organizations. First was with the Chattanooga chapter of AIGA. AIGA got a home for their meetings, brought in presentations, and started the seeds of current programming.

The next major milestone was the first DPLA “appfest” — 100 people came to CPL from around the country. Realized that people didn’t necessarily want to work at desks in these informal arrangements, so started to create less rigid workspaces.

Next was a local collaboration space, co.lab. Got 450 people to attend a series of pitches — entrepreneurial ideas. Again, community was amazed to see what the library could do.

The library is losing ownership of the space; it’s becoming a community platform.

“We make all of this stuff up all the way.” CPL has an amazing tolerance for experimentation and trial-and-error.

They moved their IT staff to the 4th floor, creating a coworking space.

Using Chattanooga’s gigabit network, they have done performances where dancers in two locations perform with projected images, passing the image back and forth between two locations in the city.

Making Maker Libraries — LITA Forum Keynote

I’m attending LITA National Forum 2013 in Louisville, Kentucky. I’ll be posting some conference notes sporadically. The opening keynote session is a talk by Travis Good, contributing editor of Make Magazine. His blog is http://make.goodpursuits.com/. He talked about “Making Maker Libraries.”

Travis Good

Once a “nerd” was not a particularly flattering thing to be called. Now, that has changed. Nerds are the smart guys you go to in order to solve a problem. Nerds have arrived. Library IT groups have solved, in a nerdy way, many kinds of problems: online catalog, computer workstations, wired Internet access, wireless internet access, ebooks… It is not just making things work, though; it is making things work comfortably in a library context.

Through making wifi available, we redefined why people go to a library.

Changes in technological landscape are a threat — and an opportunity. We will talk about just one of these changes: the maker movement. It’s a broad movement with lots of definitions. Humans have been making things since we developed opposable thumbs and tools.

What was “making”? It was done by craftsmen, focused on trades, with years of training and practice, with rudimentary tools. Took lots of practice to do well because the tools were “dumb.” Now, tools are “smart”, and more people can make things. Moore’s law has affected tools. Technology brought smarts to making; computers can manage processes. Costs drop, power rises, steadily. Tools are smarter, more powerful, and more capable. The Internet has simultaneously opened up collaboration across distributed communities. Open source software came along. And now… open source is not just software. It is hardware, too.

New, smarter, tools are already here. CNC Mill (Computer Numerically Controlled) Mill. It’s a subtractive tool — it mills away something, until what is left is the product you want. Designs can be shared, tailored, and made. 3D printing is the opposite, in a sense — it extrudes material to make something. An additive tool.

Laser cutters — these are two dimensional, and cuts a flat surface with a laser. Can cut wood, leather, acrylic, metal, and similar materials. Can create very intricate designs.

For all of these products, there are libraries of models that you can download, modify, and make yourself. Powerful tools and shared designs can make anyone a maker of things.

At the same time, we are getting cheap, flexible electronic micro controllers, sensors, and actuators. Sensors make measurements of things; actuators create a response of some kind.

Simple embedded electronics made a turn signal for a bike rider — left arrow, right arrow LEDs on the back, and a switch in each sleeve for the biker to turn them on and off. Another example — a switch in a chair that turns the TV on when you sit on it; turns the TV off when you stand up. Third example — an Arduino on a Venetian blind that opens or closes the blinds when the room is too cool or too warm.

Barriers to creating things have been reduced. Long apprenticeships to become competent are no longer required. And it’s now easier to become good at lots of things. So more people can make, more making can take place, and more people can be collaborating.

The question that arises: where is this making happening? You need spaces in which people can learn, create, share, and collaborate. Threshold to entry is low, but you still need to cross it. This is a clarion call to libraries. Libraries are already the places that offer lifelong learning. And are looking for new ways to deliver on their traditional missions.

Libraries are experimenting with maker spaces in different ways. Experimenting with different tools and technologies, seeing what local patrons will want to use. Can vary from branch to branch.

Maker spaces are catching on in libraries. It is seen, broadly, as an opportunity to be valuable to the community (in public & academic libraries). There is lots of experimentation on what kinds of services and tools to offer — it is something of the Wild West.

There are some basic things that are needed to foster the growth and development of maker spaces:

  1. A source of best practices. Why does every library need to invent this service on their own?
  2. A database of maker helpers. People who would come to your library and talk about specific topics. Tap into maker spaces, meet up groups, etc. But there is no vetting — lots of interested people, but needs to be a way to make sure the volunteers are good teachers, reliable, etc.
  3. New sources of funding. There is lots of competition for scarce resources (e.g., IMLS). Corporations are interested in funding maker spaces — they see it as future employees and future innovations. Skills of successful makers are the skills of successful innovators and inventors.
  4. Kits that fit into a library. A maker space in a box, and maker supplies that are reusable and affordable. For example, Arduino prototyping kits that can be reset and tested for basic functionality by completely non-technical library staff.
  5. Finding good projects. This is already in the works. Make it @ Your Library (http://makeitatyourlibrary.org/). 100,000 crowdsourced projects have been uploaded and categorized.

We can build tools for our library community at large.

The power of making grows when the various maker communities collaborate and communicate — libraries, incubators, schools, government. It’s a network.