You are here

Feed aggregator

D-Lib: Data Stewardship in the Earth Sciences

planet code4lib - Wed, 2015-07-15 11:44
Article by Robert R. Downs, Columbia University, Ruth Duerr, University of Colorado at Boulder, Denise J. Hills, Geological Survey of Alabama and H. K. Ramapriyan, Science Systems and Applications, Inc. and NASA Goddard Space Flight Center

D-Lib: The DOI -- Twenty Years On

planet code4lib - Wed, 2015-07-15 11:44
Opinion by Mark Bide

District Dispatch: ALA applauds initiative to support broadband for public housing residents

planet code4lib - Wed, 2015-07-15 11:00

The American Library Association (ALA) today welcomes President Barack Obama’s announcement of the ConnectHome initiative to expand high-speed broadband to public housing residents. The ALA is proud to be a partner in realizing a shared vision to empower more people to thrive online.

“Librarians know from our work in communities every day that far, far too many Americans currently lack the technology access and skills to participate fully in education, employment and civic life,” said ALA President Sari Feldman. “Broadband is essential, and we are so pleased the Obama administration has made home broadband access a priority.

“As part of this initiative, libraries will provide tools and training so that residents can maximize broadband access to advance job skills, complete homework assignments, pursue online learning and certifications, and protect their privacy and security of personal information as they expand their online lives. This is what libraries do every day—catalyze individual opportunity and community progress—and we look forward to expanding our connections with public housing residents to advance their goals.”

The ConnectHome pilot program is launching in 27 cities and one tribal nation and will initially reach over 275,000 low-income households – and nearly 200,000 children – with the support they need to access the Internet at home. Internet Service Providers, non-profits and the private sector will offer broadband access, technical training, digital literacy programs, and devices for residents in assisted housing units.  ConnectHome is the next step in the President’s continued efforts to expand high-speed broadband to all Americans and builds on the ConnectED initiative to connect 99 percent of K-12 students to high-speed Internet in classrooms and libraries over the next five years.

Current data illustrates the urgency of increasing broadband adoption. While 92 percent of households with incomes between $100,000 and $150,000 have broadband service, the adoption rate is only 47 percent for households with income below $25,000. Pew Research Center analysis of American Community Survey data finds that some 5 million households with school-age children do not have high-speed internet service at home. Low-income households – and especially black and Hispanic ones – make up a disproportionate share of that 5 million.

Susan McVey, director of the Oklahoma Department of Libraries, will join President Obama in Durant, Okla., later today. “Our nation’s libraries are part of the solution in advancing national priorities like this one—what we call The E’s of Libraries™. With the Expert assistance of library professionals, we help facilitate: Education, Employment, Entrepreneurship, Empowerment, and Engagement for Everyone, Everywhere.

“In many rural Oklahoma communities like Durant, the library is the only place with high-speed Internet. Broadband access is a vital issue for urban, rural and tribal residents alike.”

Support for the ConnectHome initiative builds on work underway in libraries for decades to create community technology hubs in more than 16,000 locations, as well as reaching beyond library walls with bookmobiles, laptop labs and wireless hot spots to bring more resources and training to more people in more places. To learn more about libraries and digital literacy, visit the District Dispatch or

The post ALA applauds initiative to support broadband for public housing residents appeared first on District Dispatch.

DuraSpace News: Welcome Graham Triggs: New Technical Lead for the VIVO Project

planet code4lib - Wed, 2015-07-15 00:00

Winchester, MA  The DuraSpace organization is pleased to announce that Graham Triggs has accepted a position with DuraSpace as the Technical Lead for the VIVO Project effective September 21, 2015. In his new role as VIVO Technical Lead, Graham will work closely with Mike Conlon, the VIVO Project Director, VIVO project governance, and the VIVO community to implement the roadmap for VIVO, the open source semantic web platform that creates an integrated record of the scholarly work of an organization.

DuraSpace News: Welcome Graham Triggs: New Technical Lead for the VIVO Project

planet code4lib - Wed, 2015-07-15 00:00

Winchester, MA  The DuraSpace organization is pleased to announce that Graham Triggs has accepted a position with DuraSpace as the Technical Lead for the VIVO Project effective September 21, 2015. In his new role as VIVO Technical Lead, Graham will work closely with Mike Conlon, the VIVO Project Director, VIVO project governance, and the VIVO community to implement the roadmap for VIVO, the open source semantic web platform that creates an integrated record of the scholarly work of an organization.

Cynthia Ng: Cascadiafest: Browser JS Afternoon Part 1 Notes

planet code4lib - Tue, 2015-07-14 19:28
A little late from looking for harbour seals. Here is the first part of the afternoon on CascadiaJS Browser Day. Courtney Hemphill: Algorithms for Animation – Simple formulas to activate your UI Slides Animations started as cognitive aids. Motion is something that humans inately respond to without help bubbles and breadcrumbs to help users move … Continue reading Cascadiafest: Browser JS Afternoon Part 1 Notes

DPLA: Open Call about DPLA and Ebooks: Wednesday, July 15, 2:00PM Eastern

planet code4lib - Tue, 2015-07-14 17:30

The DPLA will lead an open call on Wednesday, July 15 at 2:00 PM Eastern to discuss and field questions about the DPLA Open Ebooks Initiative.

To register for the open call, complete the short registration form available below.

To find out more about DPLA’s efforts around ebooks, visit the DPLA & Ebooks page.

Peter Murray: Announcing “The Future of Library Resource Discovery” — a NISO Two-day Forum in October in Baltimore

planet code4lib - Mon, 2015-07-13 20:44

Cover page from the NISO white paper “The Future of Library Resource Discovery”

In early October, NISO will be hosting a two-day forum on the future of resource discovery in libraries. This is an in-person meeting to extend the work of Marshall Breeding’s paper on the same topic that was published earlier this year:

  • Full paper, PDF, 53 pages
  • Summary from Information Standards Quarterly, Spring 2015, 27(1): pp. 24-30.

Marshall will start the forum with a presentation on the topics presented in the paper. Participants will then break up into smaller groups to go into more depth on the ideas and the implications with reporting back to the larger group. I will finish up the forum on the second day with a keynote that wraps together the ideas expressed during the meeting and a vision of where resource discovery in libraries is heading.

If you can, attend the face-to-face meeting with all the rich interaction of the breakout sessions. If you can make it to Baltimore on October 5th and 6th, sign up to watch and interact through a live webcast. Details on registration are on the NISO web page for the forum.

Link to this post!

FOSS4Lib Upcoming Events: Paris Fedora 4 Workshop and User Group Meeting

planet code4lib - Mon, 2015-07-13 17:53
Date: Friday, September 25, 2015 - 09:00 to 19:00Supports: Fedora Repository

Last updated July 13, 2015. Created by Peter Murray on July 13, 2015.
Log in to edit this page.

For details, see Paris Fedora 4 Workshop and User Group Meeting: 25 September 2015 - Community News and Events - DuraSpace Wiki

FOSS4Lib Recent Releases: Sufia - 6.2.0

planet code4lib - Mon, 2015-07-13 17:50

Last updated July 13, 2015. Created by Peter Murray on July 13, 2015.
Log in to edit this page.

Package: SufiaRelease Date: Thursday, July 9, 2015

Eric Hellman: The Library Digital Privacy Pledge

planet code4lib - Mon, 2015-07-13 17:33
I've been busy since my last post! We've created the Free Ebook Foundation, which will be the home for and GITenberg. I helped with the NISO "Consensus Framework to Support Patron Privacy in Digital Library and Information Systems", which I'll write more about soon. And some coding.

But I've also become a volunteer for the Library Freedom Project, run by radical librarian Alison Macrina. The project I'm working on is the "Library Digital Privacy Pledge."

The Library Digital Privacy Pledge is a result of discussions on several listservs about how libraries and the many organizations that serve libraries could work cooperatively to (putting it bluntly) start getting our shit together with regard to patron privacy.

I've talked to a lot of people about privacy in digital libraries, and there's remarkable unity about its importance. There's also a lot of confusion about some basic web privacy technology, like HTTPS. My view is that HTTPS sets a foundation for all the other privacy work that needs doing in libraries.

Someone asked me why I'm so passionate about working on this. After a bit of thought, I realized that the one thing that gives me the most satisfaction in my professional life is eliminating bugs. I hate bugs. Using HTTP for library services is a bug.

The draft of the Library Digital Privacy Pledge is open for comment and improvement  for a few more weeks. We want all sorts of stakeholders to have  a chance to improve it. The current text (July 12, 2015) is as follows: 
The Library Digital Privacy Pledge of 2015 The Library Freedom Project is inviting the library community - libraries, vendors that serve libraries, and membership organizations - to sign the "Library Digital Privacy Pledge of 2015". For this first pledge, we're focusing on the use of HTTPS to deliver library services and the information resources offered by libraries. Building a culture of library digital privacy will not end with this 2015 pledge, but committing to this first modest step together will begin a process that won't turn back.  We aim to gather momentum and raise awareness with this pledge; and will develop similar pledges in the future as appropriate to advance digital privacy practices for library patrons. We focus on HTTPS as a first step because of its timeliness. At the end of July the Let's Encrypt initiative of the Electronic Frontier Foundation will launch a new certificate infrastructure that will remove much of the cost and technical difficulty involved in the implementation of HTTPS, with general availability scheduled for September. Due to a heightened concern about digital surveillance, many prominent internet companies, such as Google, Twitter, and Facebook, have moved their services exclusively to HTTPS rather than relying on unencrypted HTTP connections. The White House has issued a directive that all government websites must move their services to HTTPS by the end of 2016. We believe that libraries must also make this change, lest they be viewed as technology and privacy laggards, and dishonor their proud history of protecting reader privacy. The 3rd article of the American Library Association Code of Ethics sets a broad objective:We protect each library user's right to privacy and confidentiality with respect to information sought or received and resources consulted, borrowed, acquired or transmitted.

It's not always clear how to interpret this broad mandate, especially when the everything is done on the internet. However, one principle of implementation should be clear and uncontroversial: Library services and resources should be delivered, whenever practical, over channels that are immune to eavesdropping. The current best practice dictated by this principle is as following: Libraries and vendors that serve libraries and library patrons, should require HTTPS for all services and resources delivered via the web. The Pledge for Libraries:1. All web services and resources that this library directly controls will use HTTPS by the end of 2015.2. Starting in 2016, this library will not sign or renew any contracts for web services or information resources that do not commit to use HTTPS by the end of 2016. The Pledge for Service Providers (Publishers and Vendors):1. All web services that we (the signatories) control will enable HTTPS by the end of 2015.2. All web services that we (the signatories) offer will require HTTPS by the end of 2016. The Pledge for Membership Organizations:1. All web services that this organization directly controls will use HTTPS by the end of 2015.2. We encourage our members to support and sign the appropriate version of the pledge. Schedule:This document will be open for discussion and modification until finalized by July 27, 2015. The finalized pledge will be published on the website of the Library Freedom Project. We expect a number of discussions to take place at the Annual Conference of the American Library Association and associated meetings.The Library Freedom Project will broadly solicit signatures from libraries, vendors and publishers.In September, in coordination with the Let's Encrypt project, the list of charter signatories will be made announced and broadly publicized to popular media. FAQ Q: What is HTTPS and what do we need to implement it?A: When you use the web, your browser software communicates with a server computer through the internet. The messages back and forth pass through a series of computers (network nodes) that work together to pass messages. Depending on where you and the server are, there might be 5 computers in that chain, or there might be 50, each possibly owned by a different service provider. When a website uses HTTP, the content of these messages is open to inspection by each intermediate computer- like a postcard sent through the postal system, as well as by any other computer that shares a network those computers. If you’re connecting to the internet over wifi in a coffee shop, everyone else in the coffee shop can see the messages, too.

When a website uses HTTPS, the messages between your browser software and the server are encrypted so that none of the intermediate  network nodes can see the content of the messages. It’s like sending sealed envelopes through the postal system.

Your web site and other library services may be sending sensitive patron data across the internet: often bar codes and passwords, but sometimes also catalog searches, patron names, contact information, and reading records. This kind of data ought to be inside a sealed envelope, not exposed on a postcard.

Most web server software supports HTTPS, but to implement it, you’ll need to get a certificate signed by a recognized authority. The certificate is used to verify that you are who you say you are. Certificates have added cost to HTTPS, but the Electronic Frontier Foundation is implementing a certificate authority that will give out certificates at no charge. To find out more, go to Let’s Encrypt.

Q: Why the focus on HTTPS?A: We think this issue should not be controversial and is relatively easy to explain. Libraries understand that circulation information can’t be sent to patron on postcards. Publishers don’t want their content scooped up by unauthorized entities. Service providers don’t want to betray the trust of their customers. Q. How can my library/organization/company add our names to the list of signatories?A. Email us at Please give us contact info so we can verify your participation. Q. Is this the same as HTTPS Everywhere?A. No, that's a browser plug-in which enforces use of HTTPS. Q. My Library won't be able to meet the implementation deadline. Can we add our name to the list once we've completed implementation?A. Yes. Q. A local school uses an internet filter that blocks https websites to meet legal requirements. Can we sign the pledge and continue to serve them?A. Most of the filtering solutions include options that will whitelist important services. Work with the school in question to implement a work-around.

Q. What else can I read about libraries using HTTPS?A. The Electronic Frontier Foundation has published What Every Librarian Needs to Know About HTTPSQ. How do I know if I have implemented HTTPS correctly?A. The developers behind the “Let’s Encrypt” initiative are ensuring that best practices are used in setting up the HTTPS configuration.  If you are deploying HTTPS on your own, we encourage you to use the Qualys SSL Labs SSL Server Test service to review the performance of your implementation.  You should strive for at least a “B” rating with no major security vulnerabilities identified in the scan.

Q. Our library subscribes to over 200 databases only a fraction of them currently delivered via https. We might be able to say we will not sign new contracts but the renewal requirement could be difficult for an academic library like ours. Can we sign the pledge?A. No one is going to penalize libraries that aren’t able to comply 100% with their pledge. One way to satisfy the ethical imperatives of the pledge would be to clearly label for users the small number of insecure library resources that remain after 2016 as being subject to surveillance.

Q. I/We can contribute to the effort in a way that isn’t covered well by the pledges. Can I add another pledge?
A. We want to keep this simple, but we welcome your support. email us with your individualized statement, and we may include it on our website when signatories are announced.

Library of Congress: The Signal: Exploring Web Archiving at the Library of Congress

planet code4lib - Mon, 2015-07-13 13:22

The following is a guest post by Samantha Abrams, an intern for the Web Archiving Team at the Library of Congress.

Madison, Wisconsin’s Lake Mendota, where the The iSchool at UW-Madison sits. Credit: Samantha Abrams

As a library school graduate student, I developed an interest in archives and born-digital objects (content pulled from floppy disks, web pages, Tweets, and on) but I lack practical, professional experience working with these materials. But after my time interning with the Web Archiving Team at the Library of Congress, I am confident in my exposure to a subset of digital materials and to the professional world of web archives: its relationships, its openness, its complexities.

The Library’s Web Archiving Team works to manage and preserve at-risk digital content born from the web – web pages, and yes, social media included and more. The team considers the task of archiving the web from every angle: by working with software, like Openwayback, and developing tools to assist with crawls; considering copyright issues; and building collections that help paint a comprehensive picture of the web as it stands today (or, as it stood yesterday).

Abrams’ “RAD!” notes from a web archiving meeting. Credit: Samantha Abrams

In four weeks, I have learned about the ins and outs of what web archiving really is (and what it can be). At a recent meeting, we discussed the look, and feel, and design of the collections: how can we keep users focused as they interact with the massive collection, yet allow them to discover both related and unrelated content while introducing them to the web of the past? I have spent time cleaning up data in preparation for migration to a new curator tool. And, in what will be my final project with the Library, I have helped lay the groundwork for a Business in America Web Archive. It has been a process of learning and asking questions: web archiving is an emerging and changing field, and the way professionals consider its quirks and processes requires constant readjustment and creative thinking. To be on a team so interested in following those changes as they occur has been as challenging as it has been rewarding.

I have also spent time at the Library getting to know the archival profession on an individual level: person to person, process to process, idea to idea. Early on in my time here, I reached out to archivist Kathleen O’Neill, and asked her if she would be willing to explain the way the Manuscript Division handles the acquisition and processing of born-digital materials. She introduced me to software the Division uses to access content on tangible media, and spoke about the ethical questions this processes often raises. For instance: how do archivists handle uncovering once-deleted files stored on tangible media? I’ve also spoken with Andrew Cassidy-Amstutz, an archivist with the Veteran’s History Project, and he spoke openly about the Project’s goals: reaching out to veterans, and seeking very specific content, which, in turn, leads to a workflow focused on processing digital items in bulk, and pulling as much content as possible, as quickly as possible, from the media donated to the Project. All of my questions have been answered eagerly, with thoughtful recommendations including: You know who you should talk to next about this? You know what I once read about this exact question? Have you heard of this archivist, with this institution? You should reach out to them. And on.

And this, I have realized, has been the most rewarding experience of my time with the Library. I have been introduced to an institution filled with connected, passionate individuals, eager to share their knowledge with those interested in asking about it. The people I have met here have helped introduce me to the archival world as a whole: the way we stand connected, bound by our interest in the same field, in its materials, and in its people. And just like the rest of the Library, the Web Archiving Team is composed of talented individuals, interested in sharing what they know. And these individuals, in turn, contribute to an archival profession that is vast, far-reaching, and eager to share.

LITA: Organizing Library Workflows with Asana

planet code4lib - Mon, 2015-07-13 13:00

As coordinator for non-Roman language cataloging at my library, I have to keep track of several workflows simultaneously without actual fluency in any of the 10+ languages that my section deals with. As a librarian it goes without saying that I’m a big fan of organization and efficiency. So I’ve implemented a free task-based program called Asana in order to keep track of my section’s productivity, statistics, and progress.

Asana was created with the objective of eliminating dependability on email in order to manage projects. Tasks and conversations are all in one place to promote transparency and accessibility, which is extremely valuable when you are on a team of five or more people with multiple established workflows. I’m certain I’m not alone when I say that email can often seem like a void that creates more confusion than clarity when it comes to communicating important work updates. Not everyone that I have to correspond with is well-versed in the proper use and etiquette involved with emailing, which often inspires me to do this:

Ron Swanson, Parks & Recreation.

With Asana, I have the ability as a project manager to create a timeline with due dates, assign particular tasks to people as needed, organize initiatives & meetings, and keep track of progress all in one interface. This also cuts down on the necessity for constant meetings and prevents things from falling by unnoticed in an email thread where there are already twenty-some responses and everyone is using the Reply All button.

I have been primarily using Asana to organize cooperative cataloging projects in my section. My library is a member of several initiatives to connect with other academic institutions (e.g. the CIC) in order to catalog materials on behalf of a fellow library that may not have staff who can create bibliographic records in a particular language or format.

An example of Asana’s interface.

Here, a team member is able to log their progress on tasks assigned to them, keep track of the established timeline, and upload documents like title inventories. Having all this information in one (free!) place makes it easier for a project manager to create reports and to aggregate statistics. I’ve successfully implemented Asana for two cooperative cataloging projects thus far.

Have you used Asana in your library? Do you have a favorite task managing program?


LibUX: 024: Anticipatory Design

planet code4lib - Mon, 2015-07-13 06:57

In this episode, we — Amanda and Michael — are talking about The next design trend is one that eliminates all choices by Anne Quito. Anticipatory design describes design decisions that anticipate what the user is looking for and through which lens, but we are interested in extreme “anticipatory design” through personalization.

Can personal data and context craft a user experience that eliminates choice?

We use the term “interaction cost” to similarly describe what Quinto and Aaron Shapiro call “decision fatigue”.

The irony of creating so much choice for ourselves is that—from our health and diet to finances and fitness—people make bad decisions every day. Little ones that add up over time and, sometimes, big ones that ruin their lives. And even more importantly, people can suffer real consequences from the well-documented phenomenon of decision fatigue.

When there is too much going on, whether on the page or in the totally unrelated context the user is working from, if the cost of dealing with the interface is too great then the user will move on. Improving usability often involves reducing the interaction cost.

The next big breakthrough in design and technology will be the creation of products, services, and experiences that eliminate the needless choices from our lives and make ones on our behalf, freeing us up for the ones we really care about: Anticipatory design.

Tune-in in other ways

Listen to this and other episodes on Stitcher, find us on iTunes, subscribe through RSS, or download the MP3.

In addition to weekly podcasts and articles, I write the Web for Libraries — a newsletter chock-full of data-informed commentary about user experience design, including the bleeding-edge trends and web news I think user-oriented thinkers should know.

Email Address

The post 024: Anticipatory Design appeared first on LibUX.


Subscribe to code4lib aggregator