My employer (LYRASIS) is a member of NISO (the accredited standards organization for information and documentation in the U.S.), and as the primary contact I see and consider ballots for standards issues that impact LYRASIS member libraries. The Interlibrary Loan (ILL) Application Protocol Specification (a.k.a. ISO 10160/10161) is up for its periodic review, and there is a bit of interesting movement on this standard. ISO 10160/10161 became a standard in 1993 so it predates the modern era of the web. The group shepherding the standard realized that progress had overtaken the specification and they started work on a reformulation of inter-machine ILL standards. This ballot and its supplemental documentation gives a view of the plans.
This is a review of the Airbender Bluetooth keyboard by New Trent (model IMP38W). I have been testing this unit since January 28, 2013, and traveled with it to Code4Lib in Chicago where I relied on the combination of the Airbender keyboard and iPad for a day of presentations with writing notes and searching the web for information. I received the unit from New Trent for testing and evaluation.
ResourceSync — a joint effort of NISO and the Open Archives Initiative (OAI) team with work funded by the Sloan Foundation — has published a draft specification that I urge members of the library technology community to look at. Building on the OAI-PMH strategies for synchronizing metadata, this project is modern web architecture technologies to enable the synchronization of the objects themselves, not just their metadata. From the abstract of the draft specification:
This ResourceSync specification describes a synchronization framework for the web consisting of various capabilities that allow third-party systems to remain synchronized with a server’s evolving resources. The capabilities can be combined in a modular manner to meet local or community requirements. The specification also describes how a server can advertise the synchronization capabilities it supports and how third party systems can discover this information. The specification repurposes the document formats defined by the Sitemap protocol and introduces extensions for them.
Last month’s HathiTrust newsletter had an interesting technical tidbit at the top about access to out-of-print and brittle or missing items:
One of the lawful uses of in-copyright works HathiTrust has been pursuing is to provide access on an institutional basis to works that fall under United States Copyright Law Section 108 conditions: works in HathiTrust that are not available on the market at a fair price, and for which print copies owned by HathiTrust member institutions are damaged, deteriorating, lost or stolen. As a part of becoming a member, institutions are required to submit information about their print holdings for fee calculation purposes. We have also been requesting information about the holdings status and condition of works, to facilitate uses of works where permissible by law (specifications for HathiTrust holdings data are available at http://www.hathitrust.org/print_holdings).
Two phishing1 attempts made it through the work spam filter earlier this month, and they show the creativity of bad guys as they try to get access to your machine. The attempts at social engineering were interesting enough I thought I’d describe them here. We’re getting pretty close the line where we can’t tell a legitimate e-mail from ones with nasty side effects.
The Fake Bounced Message
This message has the appearance of being a bounced e-mail from a server called ‘cyber.net.pk’.
Last week I saw a post on the IETF Announcement List seeking feedback on the possible formation of a “Reputation Services” working group. That posting has more information, but the basic abstract is posted below. Now I will admit up front that I tend to see the world through librarian-colored glasses, but creating a mechanism that helps uses make a “meaningful choice about the handling of content requires an assessment of its safety or ‘trustworthiness’” sounds like something librarians should be involved with.
I was doing some maintenance on the Amazon EC2 instance that underpins DLTJ and in the process managed to mess up the .ssh/authorized_keys file. (Specifically, I changed the permissions so it was group- and world-readable, which causes `sshd` to not allow users to log in using those private keys.) Unfortunately, there is only one user on this server, so effectively I just locked myself out of the box.
$ ssh -i .ssh/EC2-dltj.pem email@example.com Identity added: .ssh/EC2-dltj.pem (.ssh/EC2-dltj.pem) Permission denied (publickey).
After browsing the Amazon support forums I managed to puzzle this one out. Since I didn’t see this exact solution written up anywhere, I’m posting it here hoping that someone else will find it useful. And since you are reading this, you know that they worked.
The W3C Library Linked Data (LLD) Incubator Group invites librarians, publishers, linked data researchers, and other interested parties to review and comment on drafts of reports to be published later this year. The LLD group has been chartered from May 2010 through August 2011 to prepare a series of reports on the existing and potential use of Linked Data technology for publishing library data. The group is currently preparing:
Wandering into public or semi-public wireless networks makes me nervous because I know how my network traffic can be easily watched, and because I’m a geek with control issues I’m even more nervous when using devices that I can’t get to the insides of (like phones and tablets). One way to tamp down my concerns is to use a Virtual Private Network (VPN) to tunnel the device’s network connection through the public wireless network to a trusted end-point, but most of those options require a subscription to a VPN service or a VPN installed in a corporate network. I thought about using one of the open source VPN implementations with an Amazon EC2 instance, but it isn’t possible with the EC2 network configuration judging from the comments on the Amazon Web Services support forums. (Besides, installing one of the open source VPN software implementations looks far from turnkey.) Just before I lost hope, though, I saw a reference to using the open source DD-WRT consumer router firmware to do this. After plugging away at it for an hour or so, I made it work with my home router, a AT&T U-verse internet connection, and iOS devices. It wasn’t easy, so I’m documenting the steps here in case I need to set this up again.