You are here

Feed aggregator

FOSS4Lib Upcoming Events: KohaCon 2016

planet code4lib - Sun, 2016-02-07 11:06
Date: Monday, May 30, 2016 - 08:00 to Saturday, June 4, 2016 - 17:00Supports: Koha

Last updated February 7, 2016. Created by David Nind on February 7, 2016.
Log in to edit this page.

Join Koha community members for their annual conference from 30 May to 4 June 2016 in Thessaloniki, Greece.

Whether you're just curious about Koha, or have been using it for many years to manage your library, come along and learn more about Koha, the world's first free and open source integrated library management system.

FOSS4Lib Recent Releases: CollectiveAccess - 1.6

planet code4lib - Sun, 2016-02-07 04:37
Package: CollectiveAccessRelease Date: Friday, January 29, 2016

Last updated February 6, 2016. Created by David Nind on February 6, 2016.
Log in to edit this page.

Version 1.6 of Providence, the CollectiveAccess cataloguing tool, includes many changes including completely rebuilt support for ElasticSearch, a brand new display template parser (faster! better!), lots of bug fixes and many new user-requested features.

You can learn more by reading the release notes for version 1.6.

NOTE: The 1.4 version of Pawtucket (the public web-access application) is NOT compatible with version 1.6 of Providence. A 1.6-compatible release will be available soon.

FOSS4Lib Recent Releases: Piwik - 2.16.0

planet code4lib - Sun, 2016-02-07 03:48

Last updated February 6, 2016. Created by David Nind on February 6, 2016.
Log in to edit this page.

Package: PiwikRelease Date: Thursday, February 4, 2016

FOSS4Lib Recent Releases: Koha - 3.22.2, 3.20.8

planet code4lib - Sun, 2016-02-07 03:44
Package: KohaRelease Date: Thursday, January 28, 2016

Last updated February 6, 2016. Created by David Nind on February 6, 2016.
Log in to edit this page.

Monthly maintenance releases for Koha.

See the release announcements for the details:

Terry Reese: MarcEdit In-Process Work

planet code4lib - Sat, 2016-02-06 13:09

Would this be the super bowl edition? Super-duper update? I don’t know – but I am planning an update. Here’s what I’m hoping to accomplish for this update (2/7/2016):

MarcEdit (Windows/Linux)

· Z39.50/SRU Enhancement: Enable user defined profiles and schemas within the SRU configuration. Status: Complete

· Z39.50/SRU Enhancement: Allow SRU searches to be completed as part of the batch tool. Status: ToDo

· Build Links: Updating rules file and updating components to remove the last hardcode elements. Status: Complete

· MarcValidators: Updating rules file Status: Complete

· RDA Bug Fix: 260 conversion – rare occasions when {} are present, you may lose a character Status: Complete

· RDA Enhancement: 260 conversion – cleaned up the code Status: Complete

· Jump List Enhancement: Selections in the jump list remain highlighted Status: Complete

· Script Wizard Bug Fix: Corrected error in the generator that was adding an extra “=” when using the conditional arguments. Status: Complete

MarcEdit Linux

· MarcEdit expects the /home/[username] to be present…when it’s not, the application data is being lost causing problems with the program. Updating this so allow the program to drop back to the application directory/shadow directory. Status: Testing

MarcEdit OSX

· RDA Fix [crash error when encountering invalid data] Status: Testing

· Z39.50 Bug: Raw Queries failing Status: Complete

· Command-line MarcEdit: Porting the Command line version of marcedit (cmarcedit). Status: Testing

· Installer – Installer needs to be changed to allow individual installation of the GUI MarcEdit and the Command-line version of MarcEdit. These two version share the same configuration data Status: ToDo


Mark E. Phillips: Identify outliers to use for a user interface feature.

planet code4lib - Sat, 2016-02-06 05:07

At work we are deep in the process of redesigning the user interface of The Portal to Texas History.  We have a great team in our User Interfaces Unit that I get to work with on this project,  they do the majority of the work and I have been a data gatherer to identify problems that come up in our data.

As we are getting closer to our beta release we had a new feature we wanted to add to the collection and partner detail pages.  Below is the current mockup of this detail page.

Collection Detail Mockup

Quite long isn’t it.  We are trying something out (more on that later)

The feature that we are wanting more data for is the “At a Glance” feature. This feature displays the number of unique values (cardinality) of a specific field for the collection or partner.

At A Glance Detail

So in the example above we show that there are 132 items, 1 type, 3 titles, 1 contributing partner, 3 decades and so on.

All this is pretty straight forward so far.

The next thing we want to do is to highlight a box in a different color if it is a value that is different from the normal.  For example if the average collection has three different languages present then we might want to highlight the language box for a collection that had ten languages represented.

There are several ways that we can do this, first off we just made some guesses and coded in values that we felt would be good thresholds.  I wanted to see if we could figure out a way to identify these thresholds based on the data in the collection itself.  That’s what this blog post is going to try to do.

Getting the data:

First of all I need to pull out my “I couldn’t even play an extra who stands around befuddled on a show about statistics, let alone play a stats person on TV” card (wow I really tried with that one) so if you notice horribly incorrect assumptions or processes here, 1. you are probably right, and 2. please contact me so I can figure out what I’m doing wrong.

That being said here we go.

We currently have 453 unique collections in The Portal to Texas History.  For each of these collections we are interested in calculating the cardinality of the following fields

  • Number of items
  • Number of languages
  • Number of series titles
  • Number of resource types
  • Number of countries
  • Number of counties
  • Number of states
  • Number of decades
  • Number of partner institutions

To calculate these numbers I pulled data from our trusty Solr index making use of the stats component and the stats.calcdistinct=true option.  Using this I am able to get the number of unique values for each of the fields listed above.

Now that I have the numbers from Solr I can format them into lists of the unique values and start figuring out how I want to define a threshold.

Defining a threshold:

For this first attempt I decided to try and define the threshold using the Tukey Method that uses the Interquartile Range (IQR).  If you never took any statistics courses (I was a music major so not much math for me) I found this post Highlighting Outliers in your Data with the Tukey Method extremely helpful.

First off I used the handy st program to get an overview of the data that I was going to be working with.

Field N min q1 median q3 max sum mean stddev stderr items 453 1 98 303 1,873 315,227 1,229,840 2,714.87 16,270.90 764.47 language 453 1 1 1 2 17 802 1.77 1.77 0.08 titles 453 0 1 1 3 955 5,082 11.22 65.12 3.06 type 453 1 1 1 2 22 1,152 2.54 3.77 0.18 country 453 0 1 1 1 73 1,047 2.31 5.59 0.26 county 453 0 1 1 7 445 8,901 19.65 53.98 2.54 states 453 0 1 1 2 50 1,902 4.20 8.43 0.40 decade 453 0 2 5 9 49 2,759 6.09 5.20 0.24 partner 453 1 1 1 1 103 1,007 2.22 7.22 0.34

With the q1 and q3 values we can calculate the IQR for the field and then using the standard 1.5 multiplier or the extreme multiplier of 3 we can add this value back to the q3 value and find our upper threshold.

So for the county field

7 - 1 = 6 6 * 1.5 = 9 7 + 9 = 16

This gives us the threshold values in the table below.

Field Threshold – 1.5 Threshold – 3 items 4,536 7,198 language 4 5 titles 6 9 type 4 5 country 1 1 county 16 25 states 4 5 decade 20 30 partner 1 1

Moving forward we can use these thresholds as a way of saying “this field stands out in this collection from other collections”  and make the box in the “At a Glance” feature a different color.

If you have questions or comments about this post,  please let me know via Twitter.

Equinox Software: On The Road Again

planet code4lib - Fri, 2016-02-05 18:08

It’s a new year, which means it’s time for the Equinox team to hit the road and attend some Spring conferences!  Here’s where we’ll be for the next few months:

  • Code4Lib Conference in Philadelphia, Pennsylvania March 7-10, 2016
    • We love Pennsylvania, this much is true.  Equinox is proud to be co-sponsoring childcare for this event.  Mike Rylander and Mary Jinglewski will be attending the Code4Lib Conference and they’re excited to learn some new things and mingle with the library tech folk.  If you’d like to meet up with either of them, please let us know!
  • Public Library Association (PLA) Conference in Denver, Colorado April 5-9, 2016
    • Equinox is looking forward to exhibiting at PLA this year in beautiful Denver, Colorado.  The team will be ready and waiting in Booth #408.  We can’t wait to meet with you to talk about Open Source solutions for your library!  
  • Evergreen Conference in Raleigh, North Carolina April 20-23, 2016
    • Our very favorite conference of the year!  We love getting together with Evergreen users and sharing our experience and knowledge.  Equinox is not only a Platinum Sponsor for this event; we are also sponsoring the Development Hackfest. The Equinox team will be involved in fourteen separate talks throughout the conference spanning a wide variety of topics.

There are a lot of exciting things in store for 2016 and we can’t wait to share them with you.  Whether in an exhibit booth or over a beer, we love to talk.  Hope to see you all soon!

LITA: Quid Pro Quo: Librarians and Vendors

planet code4lib - Fri, 2016-02-05 13:00

I joked with a colleague recently that I need to get over my issue with vendors giving me sales pitches during phone calls and meetings. We had a good laugh since a major responsibility of my job as Assistant Director is to meet with vendors and learn about products that will enhance the patron experience at my library. As the point of contact I’m going to be the person the vendor calls and I’m going to be the person to whom the vendor pitches stuff.

The point was that sometimes it would be nice to have a quiet day so you could get back to the other vendors who have contacted you or maybe actually implement some of the tech you acquired from a vendor—he says as he looks wistfully at a pile of equipment in his office that should out in the public’s hands.

Just last month my fellow blogger Bill Dueber talked about the importance of negotiating with vendors in his post “There’s a Reason There’s a Specialized Degree.” Because I work hand in hand with vendors on an almost daily basis there’s a number of things I try to do to hold up my end of the bargain. There’s an article from 2010 on LIS Careers that talks about the Librarian/Vendor relationship. While not everything is relevant, it does have some good information in it (some of which I’ve pulled into this post).

  • Pay bills on time
  • Reply to calls/emails in a timely manner
  • Be clear about timelines
  • Say no if the answer’s no
  • Be congenial

I find it helps if I think of the vendors as my patrons. How would I treat a member of the public? Would I wait weeks before answering a reference question that came in via email? We’re all busy so not responding the same day to a vendor is probably ok but going more than a day or two is not a good idea. If I don’t want the vendor emailing me every other day I need to communicate. And if things are really busy or something’s come up I need to be clear with the vendor that I won’t be able to look at a new product until next week or second quarter, whichever the case may be.

I can’t speak for other libraries, but our board approves bills so we basically do a big swath of payments once a month. The more time it takes me to sign off on a bill and hand it over to finance, the longer it’ll take for that bill to get processed. Trust me, the last thing you want is for your computer reservation license to expire so you end up scrambling fifteen minutes before you open the doors trying to get a new license installed.

If I’m doing my part, then there are some things I expect in return from vendors (this list will look similar):

  • Send bills in a timely manner
  • Don’t send email/call every other day
  • Take no for an answer
  • Don’t trash competitors

It’s very frustrating to me when a vendor keeps pushing a product after I’ve said no. I know the vendor’s job is to find customers but sometimes it can be beneficial to lay off the sales pitch and save it for another visit. Only once have I actually had to interrupt a vendor several times during a phone call to tell them that I no longer will be doing business with them and do not want them to call me any more.

It’s one thing to say that your product does something no one else’s does or to claim that your product works better than a competitor. That’s business. But I’ve sat in vendor demos where the person spent so much time trashing another company that I had no idea what their product did. Also, sometimes I use similar products from different companies because they’re different and I can reach more patrons with a wider variety of services. This is particularly true with technology. We provide desktops, laptops, and WiFi for our customers because different people like to use different types of computers. It’s not always economically feasible to provide such a variety for every service, but we try to do it when we can.

I also have a number of things I’ll put on a wish list for vendors.

  • Look over meeting agendas and minutes
  • Check our website for services we’re offering
  • Provide a demo that you can leave behind
  • Try to not show up unannounced; at least call first

It shocks me when vendors ask what our budget is on a project, especially something for which we’ve done an RFP. This might pertain more to public libraries, but everything we do is public record. You can find the budget meetings on the city website and see exactly how much was approved. That attention to detail goes a long way towards showing me how you’ll handle our relationship.

Maybe we use iPads in our programming. Maybe we just replaced our selfchecks. Perhaps we already have a 3D printer. Maybe the head of our children’s department took part in an iLead program with the focus on helping parents pick early literacy apps for their children. Our website is, for all intents and purposes, an ever-changing document. As such, we make every effort to keep our services up to date and tout what our staff is doing. This can help you frame your sales pitch to us. You might not want to downplay iPads when we’ve been having success with them.

Where technology’s concerned, being able to leave a demo device with me is huge. It’s not always possible, but any amount of time I get where I can see how it would fit into our workflow helps us say yes or no. Sometimes I have a question that only comes up because I’ve spent some time using a device.

If you’re seeing a customer in Milwaukee, my library is not that far away and it makes sense that you can drop in and see how things are going. Totally fine. If you can, call first. The number of times I’ve missed a vendor because I didn’t know they were coming are more numerous than I’d like. But I can’t be available if I don’t know I should.

I get it. Companies are getting bigger through acquisitions, people’s sales areas are changing, the volume of customers goes up and up, and there’s still the same number of hours in the day. But there are vendors who do the things I mention above, and they’ll get my attention first.

What are some of the things you would like to see vendors do?

Patrick Hochstenbach: Studies in crosshatching

planet code4lib - Fri, 2016-02-05 08:15
Filed under: portaits, Sketchbook Tagged: art, crosshatching, hatching, illustration, ink, pen, rotring, sketch, sketchbook

OCLC Dev Network: Update to WorldCat Metadata API

planet code4lib - Thu, 2016-02-04 20:30

The latest release of the WorldCat Metadata API includes new operations for validating records.

OCLC Dev Network: Update to WorldCat Metadata API

planet code4lib - Thu, 2016-02-04 20:30

The latest release of the WorldCat Metadata API includes new operations for validating records.

LITA: 2016 Election Slate

planet code4lib - Thu, 2016-02-04 20:06

The LITA Board is pleased to announce the following slate of candidates for the 2016 spring election:

Candidates for Vice-President/President-Elect Candidates for Director-at-Large, 2 elected for a 3-year term Candidates for LITA Councilor, 1 elected for a 3-year term

View bios and statements for more information about the candidates. Voting in the 2016 ALA election will begin on March 25 and close on April 22. Election results will be announced on April 29. Note that eligible members will be sent their voting credentials via email over a three-day period, March 15-18. Check the main ALA website for information about the general ALA election.

The slate was recommended by the LITA Nominating Committee: Michelle Frisque (Chair), Galen Charlton, and Dale Poulter. The Board thanks the Nominating Committee for all of their work. Be sure to thank the candidates for agreeing to serve and the Nominating Committee for developing the slate. Best wishes to all.

SearchHub: Fusion plus Solr Suggesters for More Search, Less Typing

planet code4lib - Thu, 2016-02-04 18:05

The Solr suggester search component was previously discussed on this blog in the post Solr Suggester by Solr committer Erick Erickson. This post shows how to add a Solr suggester component to a Fusion query pipeline in order to provide the kind of auto-complete functionality expected from a modern search app.

By auto-complete we mean the familiar set of drop-downs under a search box which suggest likely words or phrases as you type. This is easy to do using Solr’s FST-based suggesters. FST stands for “Finite-State Transducer”. The underlying mechanics of an FST allow for near-matches on the input, which means that auto-suggest will work even when the inputs contain typos or misspellings. Solr’s suggesters return the entire field for a match, making it possible to suggest whole titles or phrases based on just the first few letters.

The data in this example is derived from data collected by the Movie Tweetings project between 2013 and 2016. A subset of that data has been processed into a CSV file consisting of a row per film, with columns for a unique id, the title, release year, number of tweets found, and average rating across tweets:

id,title,year,ct,rating ... 0076759,Star Wars: Episode IV - A New Hope,1977,252,8.61111111111111 0080684,Star Wars: Episode V - The Empire Strikes Back,1980,197,8.82233502538071 0086190,Star Wars: Episode VI - Return of the Jedi,1983,178,8.404494382022472 1185834,Star Wars: The Clone Wars,2008,11,6.090909090909091 2488496,Star Wars: The Force Awakens,2015,1281,8.555815768930524 ...

After loading this data into Fusion, I have a collection named “movies”. The following screenshot shows the result of a search on the term “Star Wars”.

The search results panel shows the results for the search query “Star Wars”, sorted by relevancy (i.e. best-match). Although all of the movie titles contain the words “Star Wars”, they don’t all begin with it. If you’re trying to add auto-complete to a search box, the results should complete the initial query. In the above example, the second best-match isn’t a match at all in an auto-complete scenario. Instead of using the default Solr “select” handler to do the search, we can plug in an FST suggester, which will give us not just auto-complete, but fuzzy autocomplete, through the magic of FSTs.

Fusion collections are Solr collections which are managed by Fusion. To add a Lucene/Solr suggester to the “movies” collection requires editing the Solr config files according to the procedure outlined in the “Solr Suggester” blogpost:

  • define a field with the correct analyzer in file schema.xml
  • define a request handler for auto-complete in file solrConfig.xml

Fusion sends search requests to Solr via the Fusion query pipeline Solr query stage, therefore it’s also necessary to configure a Solr query stage to access the newly configured suggest request handler.

The Fusion UI provides tools for editing Solr configuration files. These are available from the “Configuration” section on the collection “Home” panel, seen on the left-hand side column in the above screenshot. Clicking on the “Solr Config” option shows the set of available configuration files for collection “movies”:

Clicking on file schema.xml opens an edit window. I need to define a field type and specify how the contents of this field will be analyzed when creating the FSTs used by the suggester component. To do this, I copy in the field definition from the very end of the “Solr Suggester” blogpost:

<!-- text field for suggestions, taken from: --> <fieldType name="suggestTypeLc" class="solr.TextField" positionIncrementGap="100"> <analyzer> <charFilter class="solr.PatternReplaceCharFilterFactory" pattern="[^a-zA-Z0-9]" replacement=" " /> <tokenizer class="solr.WhitespaceTokenizerFactory"/> <filter class="solr.LowerCaseFilterFactory"/> </analyzer> </fieldType>

After clicking the “Save” button, the Fusion UI displays the notification message: “File contents saved and collection reloaded.”

Next I edit the solrConfig.xml file to add in definition for the suggester search component and corresponding request handler:

This configuration is based on Solr’s “techproducts” example, based on the Suggester configuration docs in the Solr Reference Guide. The suggest search component is configured with parameters for the name, and implementation type of the suggester, the field to be analyzed, the analyzer used. We also specify the optional parameter weightField which, if present, returns an additional document field that can be used for sorting.

For this example, the field parameter is movie_title_txt. The suggestAnalyzerFieldType specifies that the movie title text will be analyzed using the analyzer defined for field type suggestTypeLc, (added to the schema.xml file for the “movies” collection in the previous step). Each movie has two kinds of ratings information: average rating and count (total number of ratings from tweets). Here, the average rating value is specified:

<searchComponent name="suggest" class="solr.SuggestComponent"> <lst name="suggester"> <str name="name">mySuggester</str> <str name="lookupImpl">FuzzyLookupFactory</str> <str name="dictionaryImpl">DocumentDictionaryFactory</str> <str name="storeDir">suggester_fuzzy_dir</str> <str name="field">movie_title_txt</str> <str name="weightField">rating_tf</str> <str name="suggestAnalyzerFieldType">suggestTypeLc</str> </lst> </searchComponent>

For details, see Solr wiki Suggester seachComponent section.

The request handler configuration specifies the request path and the search component:

<requestHandler name="/suggest" class="solr.SearchHandler"> <lst name="defaults"> <str name="suggest">true</str> <str name="suggest.count">10</str> <str name="suggest.dictionary">mySuggester</str> </lst> <arr name="components"> <str>suggest</str> </arr> </requestHandler>

For details, see Solr wiki Suggester requestHandler section.

After each file edit, the collection configs are saved and the collection is reloaded so that changes take effect immediately.

Finally, I configure a pipeline with a Solr query stage which permits access to the suggest request handler:

Lacking a UI with the proper JS magic to show autocomplete in action, we’ll just send a request to the endpoint, to see how the suggest request handler differs from the default select request handler. Since I’m already logged into the Fusion UI, from the browser location bar, I request the URL:


The power of the FST suggester lies in its robustness. Misspelled and/or incomplete queries still produce good results. This search also returns the same results as the above search:


Under the hood, Lucidworks Fusion is Solr-powered, and under the Solr hood, Solr is Lucene-powered. That’s a lot of power. The autocompletion for “Solr-fu” is “Solr-Fusion”!

The post Fusion plus Solr Suggesters for More Search, Less Typing appeared first on

Islandora: Lobstometre Rising

planet code4lib - Thu, 2016-02-04 16:51

Our friendly fundraising lobster, the Lobstometre (r before e because we are Canadian like that) has gotten another bump this week, thanks to new Collaborator Florida Virtual Campus, a renewed partnership with LYRASIS, and support from Individual Members totalling more than $1500. We are more than halfway to our minimum fundraising goal and would like to say a very big 'THANK YOU!" to the supporters who have gotten us here. 

Andromeda Yelton: what I’ve been up to

planet code4lib - Thu, 2016-02-04 14:15

Wow, it turns out if you have a ton of clients materialize over the fall, you have no time to tell the internet about them!

So here’s what I’m up to:

  1. Running for LITA president! Yup. If you’re a member in good standing of LITA, you’ll get your ballot in March, and I’d really appreciate your vote. Stay tuned for my campaign page and official LITA candidate profile.
  2. Coding for Measure the Future! This consists largely in arguing with Griffey about privacy. And also being, as far as I can tell, the first person on the internet to have gotten a Django app running on an Intel Edison, a tiny adorable computer that fits in the palm of my hand.
  3. Coding for Wikimedia! So…that happened. I’m doing an internal project for The Wikipedia Library, improving the usability of their journal access application system (and creating the kernel of a system that, over time, might be able to open up lots more possibilities for them).
  4. Coding for CustomFit! We’ve debuted straight-shaped sweaters along with our original hourglass (a coding process which was not unlike rebuilding an airplane in flight), so now you can make sweaters for people who may not want normatively-feminine garments. Yay! Also I implemented a complete site redesign last fall (if you’re wondering, “can Andromeda take a 12-page PDF exported from Photoshop, translate it into CSS, and rewrite several hundred templates accordingly”, the answer turns out to be yes). Anyway, if you’d been thinking of taking the CustomFit plunge but not gotten around to it yet, please go check that out – there’s a ton of great new stuff, and more on the way.
  5. Keynoting LibTechConf! My talk will be called “The Architecture of Values”, and it’ll be about how our code does (or, spoiler alert, doesn’t) implement our library values. Also the other keynoter is Safiya Noble and I am fangirling pretty hard about that.

FOSS4Lib Recent Releases: pycounter - 0.11.1

planet code4lib - Thu, 2016-02-04 13:23
Package: pycounterRelease Date: Monday, January 25, 2016

Last updated February 4, 2016. Created by wooble on February 4, 2016.
Log in to edit this page.

Now includes a bare-bones SUSHI client executable, better support for DB1, BR1, BR2 reports, and the ability to output COUNTER 4 TSV reports (from either programatically-built reports, reports parsed from other formats, or reports fetched with SUSHI)

LITA: Call for Proposals, LITA education webinars and web courses

planet code4lib - Wed, 2016-02-03 21:28

What library technology topic are you passionate about?
Have something to teach?

The Library Information Technology Association (LITA) Education Committee invites you to share your expertise with a national audience! For years, LITA has offered online learning programs on technology-related topics of interest to LITA Members and wider American Library Association audience.

Submit a proposal by February 29th to teach a webinar, webinar series, or online course for Summer/Fall 2016.

All topics related to the intersection of technology and libraries are welcomed. Possible topics include:

  • Research Data ManagementCC by
  • Supporting Digital Scholarship
  • Technology and Kids or Teens
  • Managing Technical Projects
  • Creating/Supporting Library Makerspaces, or other Creative/Production Spaces
  • Data-Informed Librarianship
  • Diversity and Technology
  • Accessibility Issues and Library Technology
  • Technology in Special Libraries
  • Ethics of Library Technology (e.g., Privacy Concerns, Social Justice Implications)
  • Library/Learning Management System Integrations
  • Technocentric Library Spaces
  • Social Media Engagement
  • Intro to… GitHub, Productivity Tools, Visualization/Data Analysis, etc.

Instructors receive a $500 honorarium for an online course or $100-150 for webinars, split among instructors. For more information, access the online submission form. Check out our list of current and past course offerings to see what topics have been covered recently. We’re looking forward to a slate of compelling and useful online education programs this year!

LITA Education Committee.

Questions or Comments?

For questions or comments related to teaching for LITA, contact LITA at (312) 280-4268 or Mark Beatty,

LITA: Jobs in Information Technology: February 3, 2016

planet code4lib - Wed, 2016-02-03 20:48

New vacancy listings are posted weekly on Wednesday at approximately 12 noon Central Time. They appear under New This Week and under the appropriate regional listing. Postings remain on the LITA Job Site for a minimum of four weeks.

New This Week:

City of Sierra Madre, Library Services Director, Sierra Madre, CA

Concordia College, Systems and Web Services Librarian, Moorhead, MN

Depaul University Library, Digital Services Coordinator, Chicago, IL

Loyola / Notre Dame Library, Digital Services Coordinator, Baltimore, MD

The National Academies of Sciences, Engineering, and Medicine, Metadata Librarian, Washington, DC

Visit the LITA Job Site for more available jobs and for information on submitting a job posting.

District Dispatch: Federal Dollars on the Line for State Library Programs

planet code4lib - Wed, 2016-02-03 20:41

Ask Your Members of Congress to Help Bring the Bucks Home while They’re at Home

It’s “appropriations” season again in Washington. That time every year when the President submits a budget to Congress and, in theory at least, Congress drafts and votes on bills to federally fund everything from llama farming to, well, libraries. Nevermind where llamas get their cash, but libraries in every state in the nation benefit from funds allocated by Congress for the Library Services and Technology Act (LSTA), the only federally funded program specifically dedicated to supporting libraries. Last year, libraries received just under $183 million in LSTA funding, about $156 million of which flowed to states as matching grants.


Neither llama farmers nor libraries, however, benefit from federal funding without considerable convincing. That’s where you and your Members of Congress come in.

Starting in mid-February, individual Members of Congress will start signing letters addressed to their influential colleagues who sit on the powerful Appropriations Committees in both chambers of Congress. Those letters will ask the Committee to provide specific dollar amounts for specific programs, LSTA included. The math is easy: the more Members of Congress who sign the “Dear Appropriator” letter asking for significant LSTA funding, the better the odds of that money actually being awarded by the Appropriations Committee and eventually flowing to your state. Similarly, the more librarians and library supporters who ask their Members of Congress to sign that LSTA Dear Appropriator letter, the better the odds that LSTA will be funded and funded well.

So, how can you help? That’s easy, too.

We are asking library supporters to reach out and request a meeting with their Representatives and Senators while Members of Congress are home for the Presidents’ Day recess from February 15 – 20. The message to deliver at these meetings couldn’t be more simple or straightforward: “Please add your name to the LSTA Dear Appropriator letter.”

Members of Congress may be considering signing letters in support of other programs, but they will most likely sign the LSTA letter if they hear from constituents back home … or better yet, if they can visit your library and see the positive impact LSTA-funded programs are having on their constituents.

Please take a moment this week to reach out to your Member of Congress’ and Senators’ offices and request a meeting with the Member or his or her “District Director” anytime during the week of February 15 to discuss LSTA and the Dear Appropriator letters. Once you’ve met, please let the Washington Office know how it went and we will follow up on your great work.

Your Representative and Senators work for you and will love hearing about all of the great things that LSTA money does for their constituents. They’ll be happy to hear from you! Please, set that Presidents’ Week meeting today.

The post Federal Dollars on the Line for State Library Programs appeared first on District Dispatch.

FOSS4Lib Recent Releases: VuFind - 2.5.2

planet code4lib - Wed, 2016-02-03 16:21
Package: VuFindRelease Date: Wednesday, February 3, 2016

Last updated February 3, 2016. Created by Demian Katz on February 3, 2016.
Log in to edit this page.

Minor security release.


Subscribe to code4lib aggregator