It is with an overwhelming amount of excitement that I can finally announce that the LibraryBox Project has been awarded a Knight Foundation Prototype grant. These grants are designed to take a nascent project that has potential to further the Knight Foundation’s goals of engaged and connected communities and help get them prototyped and improved to the point where they are capable of moving into the next stage of their development.
Earlier this month, I attended a series of workshops based on the principles of Human-Centered Design that will inform the process of moving LibraryBox into the next stage of its development. The goals for this next development round will begin with increasing the functionality across more devices, and adding significantly to the internationalization support, although goal setting and needed functionality will be set primarily by the library and education community through a series of outreach efforts.
This is a huge benefit for libraries everywhere, as I hope it illustrates that libraries and librarians are doing important and worthwhile work as community connectors and innovators. More large grant agencies should be looking at what individual librarians are doing, and helping them make their communities better. I am very excited to be able to make the LibraryBox Project one that can help libraries and educators reach communities here in the United States and all around the world. If you’re interested in helping out, you can find out more and join the LibraryBox community at http://librarybox.us
Today marks the launch of the LibraryBox v2.0 Release Candidate 2! Now available on the LibraryBox build page, the newest release of the v2.0 of the LibraryBox codebase fixes a number of bugs that were identified in the RC1, including:
- Chat not hiding when configuration set to “no”
- Chat not re-enabling when configuration set to “yes”
- Bug in changing system hostname
At this point, I’m still looking for bug reports, but I’m pretty confident that after a bit of testing, this will be the official v2.0 release of LibraryBox. If you do find any bugs, please file a bug report on the Github repository, and we will take a look.
If you are running RC1 and want to upgrade to RC2, you can do so by following the standard upgrade instructions.
After months of work, the v2.0 codebase for the LibraryBox Project has reached Release Candidate 1, which means it’s time for a Public Beta! There are a huge number of improvements, enhancements, and all around awesome things in the v2.0. I recommend you take a look at the About v2.0 page to see the highlights.
Just a reminder about what “Public Beta” means. This is absolutely releasable code, or I wouldn’t put it out there…but no code is fully tested until it’s deployed into the world. I’ve built over a dozen LibraryBoxen using this code, tested them, changed settings and set up Sync networks, FTP’d into them, and just about every other thing I could think of to make sure it was stable. There was a private beta among just a very small handful of testers, but to really make sure that this is ready for prime time, it needs to be in the public. So that’s what we’re doing.
Almost certainly this code will be the full release v2.0 code. But if one of you brave souls discovers something that we didn’t, I want to be able to fix it before we are officially at v2.0.
There’s a lot more coming regarding the release, including a couple of video tutorials and screenshots. But perfect is the enemy of the good, so I’m getting the code out before the website is totally ready. I’ll keep adding to the site as we move quickly towards the full release of the v2.0…if the public beta goes as expected, I imagine that will be very quick in coming.
Hello all you librarian types! Want to help out on the most awesome open source library project going today? If so, read on…
As a part of the Kickstarter Project for LibraryBox v2.0 (which is literally days away from being available), I asked people to provide me with a piece of content that they wanted included on the shipping LibraryBoxen. Well, they did, and it’s an amazing list of good stuff…unfortunately, it’s too much of a good thing, because even if I worked on it during every free hour I have, it would take me too long to get it done.
Because it requires a bit of knowledge (ebook file types, naming conventions) I can’t just throw it open to the world…but who better to help me sort out a collection of content than librarians? So here’s what I’m asking for help with: Below you’ll see two bookmarks. The first is to the open Google Doc of all of the content that people requested. The second is to an upload form.
If I could get a bit of crowdsourcing help, that would be amazing. Here’s the way I think it should work:
- Awesome Librarian #1 hits the google doc, and marks a row “busy” by making it yellow.
- They then click the link and download the content in question.
- They check the file, rename it if necessary, and then upload it using the form.
- When it’s done, mark the Google doc for that piece of content Green for done. Easy, peasey, and if a few people join in, it will all be done in no time.
- Filenames should be Title by Author.filetype, for instance: Dune by Frank Herbert.epub
- For ebooks, if there are multiple filetypes, grab both the epub and the Kindle version.
- If the content is not clearly licensed, the link is bad, or any other reason to be concerned about the content, mark the row Red.
- Use your judgment as to problems or issues…this is why I want librarians doing it instead of crowdsourcing it in general. Use the notes field in the Google Doc for feedback as to why there was a problem.
- If you would like a Thank You credit in the LibraryBox v2.0 code, drop me an email and let me know how you’d like to be credited (griffey at gmail) and I’ll add you to the credits.
Thank you in advance for ANY help at all, and I’m curious to see how quickly this can be done if it’s run in parallel instead of serial. Thanks for all the help.
Above is the weighted tag cloud of the text of President Obama’s State of the Union 2014 address. This is part of a series that I’ve done over the last 8 years, starting way back in 2007, as part of a visualization of what is on the minds of Americans. Previous years for comparison:
Over time, the issues shift from security to what appear to be the big four words from this year: Jobs, Help, Congress, New. Not hard to see where the focus is now for the President.
As of RIGHT NOW, for the first time, LibraryBox is available for purchase at the LibraryBox online store. Previously only available to Kickstarter backers, individuals and organizations can now pre-order a LibraryBox v2.0 for shipment in March 2014. The cost for a standard LibraryBox (MR3020 based and with 16GB of storage) will be $150, with special editions available for $200 that include a customized 3D printed container for your LibraryBox.
For those techies out there: LibraryBox is and will always be open source. I’m not going to be removing your ability to build your own or anything like that. It’s just that there are libraries and schools where it doesn’t make sense for them to build them themselves, or they would prefer knowing that the LibraryBox they end up with is tested and guaranteed working. The v2.0 code is very close to a release candidate, and as soon as we verify the code and push it to release, I will be posting up links to the repository on Github.
Here’s a link to the press release.
I’m so excited to see this next step in the development of this project. I hope that you are, too.
Over the last few months, MPOW has been working its way through a reorganization. As lots of you know, we’re building a brand new academic library on my campus, and with the new library and new services comes an examination of how we do things and how we could do things better.
So MPOW went all-in, and decided that if we were going to change things, let’s change things. So we totally reworked our structure, going from basically 5 departments down to 3, moving from department heads as the middle-management layer to team leaders, and generally moving lots of the management structure into a more vertical organization. Amidst and among all of this movement was the general consensus that IT didn’t make sense as a department unto itself any longer. Instead, the decision was made that IT be moved into what is effectively a “central services” department (Administration), as a unit that provides support to the entirety of the remainder of the library.
With this move, my existing title (Head of Library Information Technology) makes no sense, as there is no IT department as such any longer. While a lot of my actual day-to-day job stays basically the same, I needed a new title. After looking around and trying to come up with something that was indicative of what I do as well as gave me leeway to chart a new course, there were precious few that seemed to click. So after a lot of deliberation, it looks like I’m going to be the Chief Technology Strategist for the UTC Library moving forward.
I have my reservations about how the new structure is going to work, and I am interested to see what happens. I trust my colleagues, and the management of MPOW is the best I’ve ever worked with, so I’m hoping that my worries are for naught, and that the new structure gives us what we need to open and run the new UTC Library.
So I’ve had a ton of ALA types ask me about the hotel situation in Vegas for ALA Annual 2014, and I’ve been meaning to blog about it for awhile now…and then ALA goes and opens up registration. So for those looking for some insight into best bets for location and hotels for ALA Annual 2014 in Las Vegas, here’s my take on the subject.
First off, I’ll just say: I love Vegas. I would never live there, but I love going, visiting, staying there for a few days at a time. I’ve been going once or twice a year for nearly a decade now, for events and to see friends and I think I’ve got a pretty good sense of the lay of the land. So here is my take on Vegas 2014.
If you haven’t been to Vegas before, the main thing I need to emphasize is the size of it. It looks, on a map, as if the hotels are right next to each other. Even when you’re standing on the Strip itself, it can look like they are right there, easily walkable. The truth is that the scale is totally off, and your eyes are being fooled, and it can be a 10 minute walk just from the sidewalk to the front door of a hotel, much less from one hotel to the other. Some of the really enormous complexes can be miles and miles of walking, all inside the hotel.
This is complicated by the fact that the Convention Center isn’t anywhere near the Strip, it’s off Strip and WAY down at the end. So the hotels that are convenient to the Convention Center (the LVH, Courtyard Convention Center, Residence Inn Convention Center) will NOT be convenient to pretty much anything else in Vegas. The opposite end of the map (Ballys, Caesar’s Palace, Flamingo, Paris) are fine, mostly mid-Strip hotels, and Caesar’s is by far the nicest of that bunch, for my money, the place to stay for ALA Annual is either Harrah’s or The Quad.
Why? The secret of getting back and forth to the convention center is the Las Vegas Monorail, and Harrah’s and The Quad share a monorail stop. The Quad is brand-newly renovated, and was formerly Imperial Palace…under that name, it was not really well taken care of. But the recent renovations look to have improved the place. You can go out the back of the hotel, and be on the monorail and at the convention center in 10 minutes, when just walking inside Caesar’s Palace could take you that long to get to the door and across the street. Harrah’s isn’t fancy Vegas, but it’s clean, and is in one of the best locations on the Strip. It’s right next to The Venetian, which has a few of my very favorite restaurants (while you are in Vegas, you MUST go to Bouchon), and it’s an easy walk to the Bellagio for the fountain show. So, for my money, the place to be for ALA Annual 2014 is Harrah’s Las Vegas.
I’ll be organizing a 2/4 Limit Hold’em table at some point, let me know if you’re interested.
Just a funny video testing my equipment and showing how large some of the hotels are here in Vegas.
I’ve got more video coming over at the American Libraries The Scoop as soon as the weather cooperates and people get back into the office, as well as a prologue to my coverage and the first of several upcoming posts about specific tech and companies that I think libraries should be watching. But if you want 6 minutes of me walking, this is definitely the video for you.
With all of the discussion and fervor surrounding the ALA Statement of Appropriate Conduct at ALA Conferences (hereafter Code of Conduct) around the various library virtual communities (on Twitter, on Blogs, on Facebook, etc). There are several posts that stand out, (yes, all of those are from Andromeda Yelton, for my money she’s been the most consistent and thoughtful voice among many), but for a comprehensive read I suggest heading over to Lisa Rabey’s blog and following her timeline of discussions.
I have a suggestion that I’d love to see happen with the Code of Conduct. Someone (either ALA itself, or another group/individual) should:
- Reframe and present the Code of Conduct in such a way to allow for co-signers from other Library groups.
- Edit to make the language applicable to any Library conference.
- Put the text into a system that allows for change tracking and electronic signatures.
- Provide a space both for organizations to sign on, and for individual librarians to make a pledge to only attend conferences that have a Code of Conduct of this type.
This would allow state and international library organizations to easily have their own Code of Conduct for their local conferences, without everyone having to reinvent the wheel. I expect that the ALA’s Code is going to be a moving target, with edits to it for clarity and expansion of understanding, and so any system that does have a signatory function would need to track the version that was signed, or some other diff functionality showing how the Code has evolved.
Regardless of how it’s actually implemented, I think this would be a huge move forward, and would prevent local/state/international organizations from wasting enormous amounts of time drafting their own Codes. It would also ensure the spread of what I believe to be a very, very positive move for Librarianship. I’m thrilled by the positive feedback that the CoC has gotten, and I hope that someone somewhere can make the above happen so we can ease the burden for anyone who wants to participate, at any level, not just with the ALA.
I'm Jason Griffey, a librarian, technologist, writer and speaker. This is my personal/professional blog, but I also write Release Candidate (focusing on future tech) and for the ALA TechSource blog. Visit my homepage for more.