Re: [CODE4LIB] Getting started with Ruby and library-ish data (was RE: [CODE4LIB] You *are* a coder. So what am I?)
On Mon, Feb 18, 2013 at 6:00 AM, Ethan Gruber ewg4x...@gmail.com wrote: The language you choose is somewhat dependent on the data you're working with. I don't find that Ruby or PHP are particularly good at dealing with XML. They're passable for data manipulation and migration, but I wouldn't use them to render large collections of structured XML data, like EAD or TEI collections, or whatever. It's also dependent on your environment. You may or may not have a say in this, and chances are you'll have to work with code that others wrote. If you mess with systems, it's hard to avoid working with perl. Ruby is popular here, but relatively few jobs call for it, it's slow, and the support community is way smaller than it is for some of the other languages. PHP is decent for web stuff, but it's not a good all purpose language. Yes, you *can* do just about anything with it (presuming you don't need something it just doesn't do like multithreading), but if you're not root, you could easily find it wasn't allocated nearly enough memory or time to do what you want. It's also not fast even if it is considerably faster than ruby. Speed's no biggie if your program is calling something else that does the real work or if you don't have that much processing to do. But it could be a big deal if you have to cut through lots of data regularly. Even if you don't intend to do much coding, it's impossible to avoid working with a number of languages. Learn what you need, as you need it. If you're trying to figure out what to start with, use whatever the people you're most likely to turn to help use. The best resource (if you have access) is a willing local person who you can ask questions. kyle
Re: [CODE4LIB] In chicago - Residents tickets
+1 to Residents, although I can't make the show. I vouch for them wholeheartedly... On Thu, Feb 14, 2013 at 8:30 PM, Paul Fogel paul.fo...@ucop.edu wrote: I should have sent this message earlier, but if you are in Chicago on Friday evening, the Residents are playing at Schuba's at 9pm ( http://www.songkick.com/concerts/14839734-residents-at-schubas). I have an extra pair of tickets that I don't need. The show isn't sold out, but I'm happy to strike a deal (ticket face value = $25). Why do I think code4libbers would be interested? The tour is named Wonder of Weird tour. If interested, email or text me at: 510.289.2661. Paul
[CODE4LIB] A Responsibility to Encourage Better Browsers ( ? )
Hi everyone, I'm having a change of heart. It is kind of sacrilegious, especially if you-like me-evangelize mobile-first, progressively enhanced web design, to throw alerts when users hit your site using IE7 / IE8 that encourage upgrading or changing browsers. Especially in libraries which are legally and morally mandated to be the pinnacle of accessibility, your website should - er, ideally - be functional in every browser. That's certainly what I say when I give a talk. But you know what? I'm kind of starting to not care. I understand that patrons blah blah might not blah blah have access to anything but IE7 or IE8 - but, you know, if they're on anything other than Windows 95 that isn't true. * Using Old IE makes you REALLY vulnerable to malicious software. * Spriting IEs that don't support gradients, background size, CSS shapes, etc. and spinning-up IE friendly stylesheets (which, admittedly, is REALLY easy to do with Modernizr and SASS) can be a time-sink, which I am starting to think is more of a disservice to the tax- and tuition-payers that pad my wallet. I ensure that web services are 100% functional for deprecated browsers, and there is lingering pressure-especially from the public wing of our institution (which I totally understand and, in the past, sympathized with) to present identical experiences across browsers. But you know what I did today? I sinned. From our global script, if modernizr detects that the browser is lt-ie9, it appends just below the navbar a subtle notice: Did you know that your version of Internet Explorer is several years old? Why not give Firefox, Google Chrome, or Safari a try?* In most circles this is considered the most heinous practice. But, you know, I can no longer passively stand by and see IE8 rank above the others when I give the analytics report to our web committee. Nope. The first step in this process was dropping all support for IE7 / Compatibility Mode a few months ago. Now that Google, jQuery, and others will soon drop support for IE8 - its time to politely join-in and make luddite patrons aware. IMHO, anyway. Already, old IE users get the raw end of the bargain because just viewing our website makes several additional server requests to pull additional CSS and JS bloat, not to mention all the images graphics they don't support. Thankfully, IE8 is cool with icon fonts, otherwise I'd be weeping at my desk. Now, why haven't I extended this behavior to browsers with limited support for, say, css gradients? That's trickier. A user might have the latest HTC phone but opt to surf in Opera Mini. There are too many variables and too many webkits (etc.). With old IE you can infer that a.) the user has a lap- or desktop, and [more importantly] b.) that old IE will never be a phone. Anyway, This is a really small-potatoes rant / action, but in a culture of all accessibility / never pressuring the user / whatever, it feels momentous. I kind of feel stupid getting all high and mighty about it. What do you think? Michael | Front End Librarian | www.ns4lib.com * Why, you may ask, did I not suggest IE9? Well, IE9 isn't exactly the experience we'd prefer them to have, but also according to our analytics the huge majority of old IE users are on Windows XP - where 9 isn't an option anyway. Eventually, down the road, we'll encourage IE9ers to upgrade too (once things like flexbox become standard), and at least they should have the option to try IE10.
Re: [CODE4LIB] Follow-up to my c4l13 lightning talk (emotion, interactive fiction, and linked data)
I was tempted to open my response with anarchivist++, partly as an allusion to your point about protological control, and partly to point out that in our own community here we have a form of that as well, though unlike facebook's like, it is both owned by beholden to _us_... I'm not sure why I think that makes a difference, but I do. It does make a difference. There are certainly use cases for supporting an idea with a like or +1 response if one has nothing more to add or could not say it any better. Like is not necessarily the problem. I think the problem is that Facebook tries to use that like data to jump to all sorts of conclusions about us and our relationship to others. These oversimplified definitions are then reinforced in the algorithms and software design, creating some kind of dissonance with our mental models. I can see how that could contribute to depression and feelings of isolation for Facebook users. -Shaun
Re: [CODE4LIB] A Responsibility to Encourage Better Browsers ( ? )
On 2/19/2013 10:22 AM, Michael Schofield wrote: Now that Google, jQuery, and others will soon drop support for IE8 - its time to politely join-in and make luddite patrons aware. IMHO, anyway. I would like a cite for this. I think you are mis-informed. It is a misconception that JQuery is dropping support for IE8 anytime soon. And I'm not sure what you mean about 'Google' dropping support for IE8. [The mis-conception comes from the fact that JQuery 1.9 will not support IE 9, HOWEVER, JQuery 1.8 will be supported indefinitely as feature-complete-compatible with JQuery 1.9, and supporting IE 9. JQuery 1.9 is just an alternate smaller JQuery without IE 8 support, yeah, but JQuery 1.8 has no EOL and will be supported indefinitey feature-complete with 1.9]. Anyway, I think it's clear that the web developer with our level of resources can not afford to support every browser that may possibly exist. We have to decide on our list of browsers we will actually spend time ensuring work with our code. (You can also, like JQuery-mobile, have a list that's supported as 'first class', and another list that is supported with graceful degredation -- and then others which you don't look at at all, and may fail miserably/unusably). That decision is generally based on a combination of popularity of browsers among your users as well as difficulty (expense) to support. If you can politically get away with no longer supporting IE8 even though it's popular among your users, I guess that could be legit. It depends on your 'business needs', right? Once you've decided to stop supporting a browser, especially one that may be popular anyway, a secondary question is whether to let it just silently potentially fail (you generally aren't spending time analyzing whether it will in fact fail, work as intended, or degrade gracefully -- that's part of the point), or actually sniff user agents and give the user some sort of warning that your site may not work with your browser. If you are going to give a warning, I'd recommend it be a relatively unobtrusive warning that still lets them proceed to use your site anyway if they want to ignore your warning, rather than one that locks them out.
Re: [CODE4LIB] A Responsibility to Encourage Better Browsers ( ? )
Keep in mind that many old-IE users are there because their corporate/gov entity requires it. Our entire univeristy health/hospital complex, for example, was on IE6 until...last year, maybe?... because they had several critical pieces of software written as active-x components that only ran in IE6. Which, sure, you can say that's dumb (because it is), but at the same time we couldn't have a setup that made it hard for the doctors and researchers use the library. On Tue, Feb 19, 2013 at 10:22 AM, Michael Schofield mschofi...@nova.eduwrote: Hi everyone, I'm having a change of heart. It is kind of sacrilegious, especially if you-like me-evangelize mobile-first, progressively enhanced web design, to throw alerts when users hit your site using IE7 / IE8 that encourage upgrading or changing browsers. Especially in libraries which are legally and morally mandated to be the pinnacle of accessibility, your website should - er, ideally - be functional in every browser. That's certainly what I say when I give a talk. But you know what? I'm kind of starting to not care. I understand that patrons blah blah might not blah blah have access to anything but IE7 or IE8 - but, you know, if they're on anything other than Windows 95 that isn't true. * Using Old IE makes you REALLY vulnerable to malicious software. * Spriting IEs that don't support gradients, background size, CSS shapes, etc. and spinning-up IE friendly stylesheets (which, admittedly, is REALLY easy to do with Modernizr and SASS) can be a time-sink, which I am starting to think is more of a disservice to the tax- and tuition-payers that pad my wallet. I ensure that web services are 100% functional for deprecated browsers, and there is lingering pressure-especially from the public wing of our institution (which I totally understand and, in the past, sympathized with) to present identical experiences across browsers. But you know what I did today? I sinned. From our global script, if modernizr detects that the browser is lt-ie9, it appends just below the navbar a subtle notice: Did you know that your version of Internet Explorer is several years old? Why not give Firefox, Google Chrome, or Safari a try?* In most circles this is considered the most heinous practice. But, you know, I can no longer passively stand by and see IE8 rank above the others when I give the analytics report to our web committee. Nope. The first step in this process was dropping all support for IE7 / Compatibility Mode a few months ago. Now that Google, jQuery, and others will soon drop support for IE8 - its time to politely join-in and make luddite patrons aware. IMHO, anyway. Already, old IE users get the raw end of the bargain because just viewing our website makes several additional server requests to pull additional CSS and JS bloat, not to mention all the images graphics they don't support. Thankfully, IE8 is cool with icon fonts, otherwise I'd be weeping at my desk. Now, why haven't I extended this behavior to browsers with limited support for, say, css gradients? That's trickier. A user might have the latest HTC phone but opt to surf in Opera Mini. There are too many variables and too many webkits (etc.). With old IE you can infer that a.) the user has a lap- or desktop, and [more importantly] b.) that old IE will never be a phone. Anyway, This is a really small-potatoes rant / action, but in a culture of all accessibility / never pressuring the user / whatever, it feels momentous. I kind of feel stupid getting all high and mighty about it. What do you think? Michael | Front End Librarian | www.ns4lib.com * Why, you may ask, did I not suggest IE9? Well, IE9 isn't exactly the experience we'd prefer them to have, but also according to our analytics the huge majority of old IE users are on Windows XP - where 9 isn't an option anyway. Eventually, down the road, we'll encourage IE9ers to upgrade too (once things like flexbox become standard), and at least they should have the option to try IE10. -- Bill Dueber Library Systems Programmer University of Michigan Library
Re: [CODE4LIB] A Responsibility to Encourage Better Browsers ( ? )
Hey world, I suppose I could start appending footnotes to my ranty emails. Johnathan is definitely right regarding jQuery while I was generalizing. Yes, jq1.8 will be supported - but, if you wanted to, you could still run a site using jq1.4. The jQuery team is moving beyond LT IE9 because losing the bloat is certainly more performant, especially as the web scurries further away from high-speed connections. Even now, many of us are supporting old IE by pulling in additional stylesheets or scripts. The practice doesn't change if on detection you choose to load jq1.8 instead of 2+. As the web moves forward, the experience for old browser users will increasingly suck - polyfills bust performance budget. Google Apps / Play pulled support for IE8 on November 15. Link to Techcrunch below. It's not fatal, but it's the same premise - IE8 users will get the you should consider upgrading message. It's the beginning of the trend, but it's definitely a trend. I just browserstacked my dusty G+ profile and there is a polite message. I didn't see it on Calendar or Gmail. It more in-your-face on Play. It's there and it's not. It works, it's gradual, but it's goading. John's right, too, when he makes the point that the decision has a lot to do with the difficulty / expense to support. The question to me is if a library website is built by taxes and tuition, is there a point where the redundant work for backward compatibility becomes a disservice? Michael // ns4lib.com http://techcrunch.com/2012/09/14/google-apps-says-goodbye-to-internet-explorer-pulls-support-for-the-browser/ -Original Message- From: Jonathan Rochkind [mailto:rochk...@jhu.edu] Sent: Tuesday, February 19, 2013 11:57 AM To: Code for Libraries Cc: Michael Schofield Subject: Re: [CODE4LIB] A Responsibility to Encourage Better Browsers ( ? ) On 2/19/2013 10:22 AM, Michael Schofield wrote: Now that Google, jQuery, and others will soon drop support for IE8 - its time to politely join-in and make luddite patrons aware. IMHO, anyway. I would like a cite for this. I think you are mis-informed. It is a misconception that JQuery is dropping support for IE8 anytime soon. And I'm not sure what you mean about 'Google' dropping support for IE8. [The mis-conception comes from the fact that JQuery 1.9 will not support IE 9, HOWEVER, JQuery 1.8 will be supported indefinitely as feature-complete-compatible with JQuery 1.9, and supporting IE 9. JQuery 1.9 is just an alternate smaller JQuery without IE 8 support, yeah, but JQuery 1.8 has no EOL and will be supported indefinitey feature-complete with 1.9]. Anyway, I think it's clear that the web developer with our level of resources can not afford to support every browser that may possibly exist. We have to decide on our list of browsers we will actually spend time ensuring work with our code. (You can also, like JQuery-mobile, have a list that's supported as 'first class', and another list that is supported with graceful degredation -- and then others which you don't look at at all, and may fail miserably/unusably). That decision is generally based on a combination of popularity of browsers among your users as well as difficulty (expense) to support. If you can politically get away with no longer supporting IE8 even though it's popular among your users, I guess that could be legit. It depends on your 'business needs', right? Once you've decided to stop supporting a browser, especially one that may be popular anyway, a secondary question is whether to let it just silently potentially fail (you generally aren't spending time analyzing whether it will in fact fail, work as intended, or degrade gracefully -- that's part of the point), or actually sniff user agents and give the user some sort of warning that your site may not work with your browser. If you are going to give a warning, I'd recommend it be a relatively unobtrusive warning that still lets them proceed to use your site anyway if they want to ignore your warning, rather than one that locks them out.
Re: [CODE4LIB] A Responsibility to Encourage Better Browsers ( ? )
jQuery 2.x will support IE 9+ . Jonathan is correct that 1.x will continue to support IE 6+ and there are techniques to deliver the older version of jQuery to older browsers if the developer deems it necessary. http://jquery.com/browser-support/ However, I think Michael is in good company in thinking the time has come to cut (or at least reduce) support for older versions of IE. I've heard several top notch web developers talking on various podcasts (no, I'm not going to cite them) about starting with responsive web approach that that delivers what would essentially be the mobile view of the page, albeit with less functionality, to these browsers. The full desktop view goes only to modern browsers. It doesn't cut off those communities that are bound for whatever reason to use IE 6 or 7. It just gives them a different experience. My 2c. Tom On Tue, Feb 19, 2013 at 11:57 AM, Jonathan Rochkind rochk...@jhu.eduwrote: On 2/19/2013 10:22 AM, Michael Schofield wrote: Now that Google, jQuery, and others will soon drop support for IE8 - its time to politely join-in and make luddite patrons aware. IMHO, anyway. I would like a cite for this. I think you are mis-informed. It is a misconception that JQuery is dropping support for IE8 anytime soon. And I'm not sure what you mean about 'Google' dropping support for IE8.
Re: [CODE4LIB] A Responsibility to Encourage Better Browsers ( ? )
I guess my general philosophy is that, for any browser with a decent market share (1% ish), it's my responsibility that the website *works*. It is not my responsibility to make it look the same or run as fast in every browser, which means IE 8 can get flat colors instead of gradients or a fallback if it's not too time-intensive to write. Google's web apps are dropping IE 8 support; visit Google Docs in IE 8 or even an older Firefox and you'll see a warning. AFAIK, Google Search works fine in almost any browser. And the jQuery thing is true but the versions are off; 2.0 will drop oldIE support, 1.9 will be the maintained branch that keeps IE support. See their announcement: http://blog.jquery.com/2013/01/15/jquery-1-9-final-jquery-2-0-beta-migrate-final-released/ Best, Eric On Tue, Feb 19, 2013 at 12:14 PM, Bill Dueber b...@dueber.com wrote: Keep in mind that many old-IE users are there because their corporate/gov entity requires it. Our entire univeristy health/hospital complex, for example, was on IE6 until...last year, maybe?... because they had several critical pieces of software written as active-x components that only ran in IE6. Which, sure, you can say that's dumb (because it is), but at the same time we couldn't have a setup that made it hard for the doctors and researchers use the library. On Tue, Feb 19, 2013 at 10:22 AM, Michael Schofield mschofi...@nova.edu wrote: Hi everyone, I'm having a change of heart. It is kind of sacrilegious, especially if you-like me-evangelize mobile-first, progressively enhanced web design, to throw alerts when users hit your site using IE7 / IE8 that encourage upgrading or changing browsers. Especially in libraries which are legally and morally mandated to be the pinnacle of accessibility, your website should - er, ideally - be functional in every browser. That's certainly what I say when I give a talk. But you know what? I'm kind of starting to not care. I understand that patrons blah blah might not blah blah have access to anything but IE7 or IE8 - but, you know, if they're on anything other than Windows 95 that isn't true. * Using Old IE makes you REALLY vulnerable to malicious software. * Spriting IEs that don't support gradients, background size, CSS shapes, etc. and spinning-up IE friendly stylesheets (which, admittedly, is REALLY easy to do with Modernizr and SASS) can be a time-sink, which I am starting to think is more of a disservice to the tax- and tuition-payers that pad my wallet. I ensure that web services are 100% functional for deprecated browsers, and there is lingering pressure-especially from the public wing of our institution (which I totally understand and, in the past, sympathized with) to present identical experiences across browsers. But you know what I did today? I sinned. From our global script, if modernizr detects that the browser is lt-ie9, it appends just below the navbar a subtle notice: Did you know that your version of Internet Explorer is several years old? Why not give Firefox, Google Chrome, or Safari a try?* In most circles this is considered the most heinous practice. But, you know, I can no longer passively stand by and see IE8 rank above the others when I give the analytics report to our web committee. Nope. The first step in this process was dropping all support for IE7 / Compatibility Mode a few months ago. Now that Google, jQuery, and others will soon drop support for IE8 - its time to politely join-in and make luddite patrons aware. IMHO, anyway. Already, old IE users get the raw end of the bargain because just viewing our website makes several additional server requests to pull additional CSS and JS bloat, not to mention all the images graphics they don't support. Thankfully, IE8 is cool with icon fonts, otherwise I'd be weeping at my desk. Now, why haven't I extended this behavior to browsers with limited support for, say, css gradients? That's trickier. A user might have the latest HTC phone but opt to surf in Opera Mini. There are too many variables and too many webkits (etc.). With old IE you can infer that a.) the user has a lap- or desktop, and [more importantly] b.) that old IE will never be a phone. Anyway, This is a really small-potatoes rant / action, but in a culture of all accessibility / never pressuring the user / whatever, it feels momentous. I kind of feel stupid getting all high and mighty about it. What do you think? Michael | Front End Librarian | www.ns4lib.com * Why, you may ask, did I not suggest IE9? Well, IE9 isn't exactly the experience we'd prefer them to have, but also according to our analytics the huge majority of old IE users are on Windows XP - where 9 isn't an option anyway. Eventually, down the road, we'll encourage IE9ers to upgrade too (once things like flexbox become standard), and at least they should
Re: [CODE4LIB] A Responsibility to Encourage Better Browsers ( ? )
Let's not forget that Google has a business case for dropping IE8 support. Alerting folks to their old browser could (in SEO terms) turn into Chrome conversions. -Sean On 2/19/13 12:22 PM, Eric Phetteplace phett...@gmail.com wrote: I guess my general philosophy is that, for any browser with a decent market share (1% ish), it's my responsibility that the website *works*. It is not my responsibility to make it look the same or run as fast in every browser, which means IE 8 can get flat colors instead of gradients or a fallback if it's not too time-intensive to write. Google's web apps are dropping IE 8 support; visit Google Docs in IE 8 or even an older Firefox and you'll see a warning. AFAIK, Google Search works fine in almost any browser. And the jQuery thing is true but the versions are off; 2.0 will drop oldIE support, 1.9 will be the maintained branch that keeps IE support. See their announcement: http://blog.jquery.com/2013/01/15/jquery-1-9-final-jquery-2-0-beta-migrate-fin al-released/ Best, Eric On Tue, Feb 19, 2013 at 12:14 PM, Bill Dueber b...@dueber.com wrote: Keep in mind that many old-IE users are there because their corporate/gov entity requires it. Our entire univeristy health/hospital complex, for example, was on IE6 until...last year, maybe?... because they had several critical pieces of software written as active-x components that only ran in IE6. Which, sure, you can say that's dumb (because it is), but at the same time we couldn't have a setup that made it hard for the doctors and researchers use the library. On Tue, Feb 19, 2013 at 10:22 AM, Michael Schofield mschofi...@nova.edu wrote: Hi everyone, I'm having a change of heart. It is kind of sacrilegious, especially if you-like me-evangelize mobile-first, progressively enhanced web design, to throw alerts when users hit your site using IE7 / IE8 that encourage upgrading or changing browsers. Especially in libraries which are legally and morally mandated to be the pinnacle of accessibility, your website should - er, ideally - be functional in every browser. That's certainly what I say when I give a talk. But you know what? I'm kind of starting to not care. I understand that patrons blah blah might not blah blah have access to anything but IE7 or IE8 - but, you know, if they're on anything other than Windows 95 that isn't true. * Using Old IE makes you REALLY vulnerable to malicious software. * Spriting IEs that don't support gradients, background size, CSS shapes, etc. and spinning-up IE friendly stylesheets (which, admittedly, is REALLY easy to do with Modernizr and SASS) can be a time-sink, which I am starting to think is more of a disservice to the tax- and tuition-payers that pad my wallet. I ensure that web services are 100% functional for deprecated browsers, and there is lingering pressure-especially from the public wing of our institution (which I totally understand and, in the past, sympathized with) to present identical experiences across browsers. But you know what I did today? I sinned. From our global script, if modernizr detects that the browser is lt-ie9, it appends just below the navbar a subtle notice: Did you know that your version of Internet Explorer is several years old? Why not give Firefox, Google Chrome, or Safari a try?* In most circles this is considered the most heinous practice. But, you know, I can no longer passively stand by and see IE8 rank above the others when I give the analytics report to our web committee. Nope. The first step in this process was dropping all support for IE7 / Compatibility Mode a few months ago. Now that Google, jQuery, and others will soon drop support for IE8 - its time to politely join-in and make luddite patrons aware. IMHO, anyway. Already, old IE users get the raw end of the bargain because just viewing our website makes several additional server requests to pull additional CSS and JS bloat, not to mention all the images graphics they don't support. Thankfully, IE8 is cool with icon fonts, otherwise I'd be weeping at my desk. Now, why haven't I extended this behavior to browsers with limited support for, say, css gradients? That's trickier. A user might have the latest HTC phone but opt to surf in Opera Mini. There are too many variables and too many webkits (etc.). With old IE you can infer that a.) the user has a lap- or desktop, and [more importantly] b.) that old IE will never be a phone. Anyway, This is a really small-potatoes rant / action, but in a culture of all accessibility / never pressuring the user / whatever, it feels momentous. I kind of feel stupid getting all high and mighty about it. What do you think? Michael | Front End Librarian | www.ns4lib.com * Why, you may ask, did I not suggest IE9? Well, IE9 isn't exactly the experience we'd prefer them to have, but also according to our analytics the huge
[CODE4LIB] Immediate Opening for Paid Intern: CableU.TV Research Company - Data Management Marketing Intern (NYC)
*CableU.TV Research Company - Data Management Marketing Intern - Paid (NYC)* -- CableU.tv is seeking a college-aged data intern to work in the company's New York office with the director of digital media on various data maintenance and data-based marketing tasks. CableU is an innovative, small research company that analyzes Nielsen television ratings data and publishes monthly reports on television network performance on its website, CableU.tv. The main site is also home to an innovative wiki database on television people, programs and networks. Candidates should: -Be enthusiastic, organized -Be excellent writers / communicators -Be highly analytical -Be detail-oriented -Have experience with MS-Office Suite of products -Be available between 15-30 hours a week on a consistent schedule -- some potential for flexibility or work from home possible Would be nice to have: -Experience using *WordPress *blogging and content management system -Interested in a career in television / media -Capable of transferring time to actual school credit in addition to pay and other benefits of working with our team of researchers, sales staff and engineers - it's NOT ok to contact this poster with services or other commercial interests - Compensation: $13 / hour *Send Cover Letter and Resume to j...@cableu.tv*
[CODE4LIB] Code 4 Lib attendees, Help please
I attended last week's Code 4 Lib conference. Unfortunately, while I was having a late lunch on Thursday in China Town, my friend's car was vandalized and my laptop stolen. I had all of my conference notes on that laptop. Would anyone be willing to share their conference notes with me? I would be particularly interested in notes from an academic librarian, but I'll take whatever I can get my hands on. I really enjoyed the conference, but I'm reduced to trying to piece things together from memory-and that's spotty at best. Ian Barba Research Development Librarian Texas Tech University Libraries
Re: [CODE4LIB] Code 4 Lib attendees, Help please
On Tue, Feb 19, 2013 at 09:54:53PM +, Barba, Ian wrote: I attended last week's Code 4 Lib conference. Unfortunately, while I was having a late lunch on Thursday in China Town, my friend's car was vandalized and my laptop stolen. I had all of my conference notes on that laptop. Would anyone be willing to share their conference notes with me? I would be particularly interested in notes from an academic librarian, but I'll take whatever I can get my hands on. I really enjoyed the conference, but I'm reduced to trying to piece things together from memory-and that's spotty at best. I hope this doesn't spoil your experience of the conference otherwise. Thanks to jronallo@ you should be able to watch all (except Tuesday AM before Tara paid for video) the conference proceedings. Example below http://code4lib.org/conference/2013/burton-west Ian Barba Research Development Librarian Texas Tech University Libraries -- Our policy is, when in doubt, do the right thing. -- Roy L. Ash, ex-president Litton Industries
Re: [CODE4LIB] thanks and poetry
At Sat, 16 Feb 2013 06:42:04 -0800, Karen Coyle wrote: gitHub may have excellent startup documentation, but that startup documentation describes git in programming terms mainly using *nx commands. If you have never had to use a version control system (e.g. if you do not write code, especially in a shared environment), clone push pull are very poorly described. The documentation is all in terms of *nx commands. Honestly, anything where this is in the documentation: On Windows systems, Git looks for the |.gitconfig| file in the |$HOME| directory (|%USERPROFILE%| in Windows’ environment), which is |C:\Documents and Settings\$USER| or |C:\Users\$USER| for most people, depending on version (|$USER| is |%USERNAME%| in Windows’ environment). is not going to work for anyone who doesn't work in Windows at the command line. No, git is NOT for non-coders. For what it’s worth, this programmer finds git’s interface pretty terrible. I prefer mercurial (hg), but I don’t know if it’s any better for people who aren’t familar with a command line. http://mercurial.selenic.com/guide/ (As a general rule, for every programmer who prefers tool A, and says that everybody should use it, there’s a programmer who disparages tool A, and advocates tool B. So take what we say with a grain of salt!) (And as a further aside, there’s plenty to dislike about github as well, from it’s person-centric view of projects (rather than team-centric) to its unfortunate centralizing of so much free/open source software on one platform.) best, Erik Sent from my free software system http://fsf.org/. pgpKhLEacXDgb.pgp Description: PGP signature
[CODE4LIB] Job: Assistant University Librarian for Resource Services and Technology at Portland State University
Position # D98558 Job Title Assistant University Librarian for Resource Services and Technology Department Library FTE 1.0 FTE, 12-month, benefits eligible Posted February 12, 2013 Portland State University, a thriving public university based in downtown Portland, Oregon, seeks a dynamic, experienced library professional to serve as Assistant University Librarian for Resource Services and Technology (AULRST). Comprising eight schools and colleges, Portland State is the largest academic institution in the Oregon University System and is one of the 100 largest public universities in the nation, enrolling 29,818 students in 99 bachelors, 89 masters, and 38 doctoral programs. Occupying an attractive central location on the PSU campus, the Branford Price Millar Library is an exceptional resource to support students and faculty and also an active and influential member of the Orbis Cascade Alliance, a library consortium of 37 higher education institutions in Oregon and Washington. The Assistant University Librarian for Resource Services and Technology (AULRST) position is a full-time, unclassified, unrepresented faculty position reporting to the Dean of the University Library. The AULRST provides leadership, vision, planning, budgeting, assessment, and management for resource services and technology functions within the scope of the Portland State and Library policies, procedures, and strategic plans. Resource Services includes six faculty and thirteen additional employees within the Acquisitions, Cataloging, Preservation, Collection Development, and Electronic Continuing Resources units. Library Technologies includes a Manager and five employees and provides technical support for the Library's staff and to users of existing systems, plans and implements new and upgraded applications and digital services, and partners with the Office of Information Technology to strengthen the Library and campus information technology infrastructure and access. The AULRST will be responsible for active collaboration, within the Library and at the campus and consortial level. The AULRST reports to the Dean, University Library and is a member of the Library's Administrative Leadership Team, and the AULRST must contribute to the profession through outstanding professional service and scholarly activities, as well as supporting library faculty in the promotion and tenure process. Responsibilities: * Supervises and mentors the Resource Services faculty librarians and the Library Technologies Manager, contributing to the evaluation of their performance; * Plans, justifies, and monitors budgets related to Resource Services and Technologies (RST); * Continually evaluates and assesses the quality of RST, making suggestions for greater efficiency, cost containment, or service enhancements to meet goals related to educational impact and strategic plans; * Contributes to the Library's long-range strategic planning, establishing short- and long-range RST goals and objectives, and positioning RST to anticipate and meet the changing needs of library users; * Participates in broad oversight, decision making, policy development, and alignment of resources for the Library as a member of the Administrative Leadership Team; * Works positively and productively in a changing environment, providing a supportive work environment for colleagues and a positive role model that demonstrates professionalism, a strong public services commitment, and a willingness to adapt to changes; * Develops and documents effective policies, procedures, and standards of service; * Oversees activities related to the assessment and selection of information resources, the management of resources, and operations pertaining to acquisitions, cataloging, preservation, and electronic continuing resources; * Collaborates with librarians to build and provide access to collections that are responsive to newly developing technologies and supportive of student learning and research; * Continually evaluates the cost effectiveness and quality of workflows and systems, making suggestions for greater efficiency, cost containment, or service enhancements; * Collaborates with members of the Orbis Cascade Alliance, leveraging the shared integrated library system to create innovative workflows; * Oversees the Library's various information systems operations, including the integrated library system, ILLiad, network wired and wireless infrastructure, servers, and public and staff workstation hardware and software configurations in cooperation with the University's Office of Information Technology and in anticipation of the changing needs of users; * Oversees upgrades and implementation of new system features; * Coordinates Library website design and enhancement; * Represents the Library in coordinating resources services and systems support with the University's Office of Information Technology and other campus
[CODE4LIB] Job: Film/Media Archivist at Oddball Film+Video
Oddball Film+Video, a unique San Francisco stock footage company is seeking a project-base, part-time Film+Media Archivist. We are searching for someone who is focused on archiving, database management and historical research with strong tech skills. Our company specializes in providing offbeat and unusual footage for feature films, documentaries and web related projects around the world. We have extensive 35mm, 16mm and small gauge film, analog tape and digital media archives. Responsibilities Include Archiving, database management and research of multi format media materials. Technical and logistical support of analog and digital media, media migration, data storage and backup. Technical systems configuation and troubleshooting. Requirements A working knowledge Filemaker Pro and other relevant database software. Familiarity with multiple analog and digital file formats and non linear editing systems such as Final Cut Pro. Configuration and troubleshooting experience. An understanding of 16mm film and analog video equipment, digital software and editing tools. A working knowledge of office-oriented software like Word and Excel. Knowledge of Mac OSX operating systems and data backup procedures. Applicant should be articulate, outgoing and proactive with excellent analytical, organizational, communication and verbal skills Useful Skills Knowledge of historical events and use of stock footage in documentary, commercial broadcast and web based programming. Library science background. Hands on experience with 16mm and small gauge film. Photoshop and other related media programs. Your Future Possibility of part time or full time employment with a small and growing creative company. Note to Applicants We're looking for an eager, forward-thinking person interested in media and archival footage to assist in growing this into a part or full time position. While we're open to people with a variety of skill sets from diverse backgrounds please either have the qualifications above or specifically stated transferable skills necessary for this position. Note this is not a production or editing position. How to Apply Please send a brief letter of inquiry and a resume focusing on your skills and previous experience relevant to this position. Brought to you by code4lib jobs: http://jobs.code4lib.org/job/6356/
[CODE4LIB] Job: Digital Archive Cataloging Librarian at Academy of Motion Picture Arts and Sciences
The Margaret Herrick Library of the Academy of Motion Picture Arts and Sciences is hiring a full-time Digital Archive Cataloging librarian: The Digital Archive Cataloging Librarian will work under the direction of the Digital Archivist. Primary duties will include data cleanup of existing records in the Library's Digital Asset Management system and other image databases and cataloging digital images as they are ingested into the Digital Asset Management system. Duties and Responsibilities * Review work of others and correct cataloging errors and conflicts within the digital asset management system. * Perform online original descriptive and subject cataloging for photographs and digital images in consultation with Digital Archivist as appropriate, according to in-house guidelines. * Describe visual content of images and assign controlled vocabulary terms, maintaining accuracy and consistency. * Update catalog records as necessary. * Provide digital delivery of images from the Digital Image Gallery to internal and external library users as needed. * Research and verify name, subject, and other subject headings to conform to appropriate authority files and in-house conventions. * Handle photographic and archival materials with care, according to in-house guidelines. Qualifications and Requirements * A Master's degree in library or information science from a program accredited by the American Library Association. * Minimum of one year relevant cataloging experience. * Experience cataloging using an online bibliographic utility applying AACR2 standards and LC classification system subject headings as well as experience cataloging using one or more non-MARC metadata formats * Experience cataloging in a digital asset management system highly desirable * Knowledge of film history * Ability to identify a variety of photographic processes and media * Understanding of proper handling of photographic and archival materials * Attention to detail and accuracy with organized and orderly work habits * Strong communication and problem-solving skills * Self-motivation and a willingness to work both independently and as a team member To Apply: Please send a cover letter and resume to: jobs(at)oscars.org Brought to you by code4lib jobs: http://jobs.code4lib.org/job/6357/
[CODE4LIB] Job: Electronic Resources Librarian, Data Projects and Partnerships at North Carolina State University
NORTH CAROLINA STATE UNIVERSITY LIBRARIES VACANCY ANNOUNCEMENT ELECTRONIC RESOURCES LIBRARIAN, DATA PROJECTS AND PARTNERSHIPS Entry-Level The NCSU Libraries has a well-earned reputation for creating adventurous library spaces and innovative services that delight today's students and researchers. The D. H. Hill Library combines the best of tradition and innovation, housing special collections and a beautiful gallery alongside vibrant, experiential spaces such as the Learning Commons and Technology Sandbox. The new James B. Hunt Jr. Library, located on NC State's Centennial Campus, is an iconic building, a place where people gather to explore new ways to research, learn, experiment, and collaborate. Designed as a working incubator for educational technology, with dynamic video walls, computing and visualization spaces, gaming and media labs, and group collaboration rooms, the Hunt Library provides focused services for the Colleges of Engineering and Textiles, while serving as a second main library for the NC State community. If you are a person who would like to provide a new generation of library users with everything they can imagine and more, consider applying for the following position. The NCSU Libraries invites applications and nominations for the position of Electronic Resources Librarian, Data Projects and Partnerships in the Acquisitions and Discovery department. Established in 2012 through a merger of acquisitions and cataloging, staff in this department collaborate across the library and with the publishing community to support the collections life- cycle including budget management, acquisitions, licensing, e-resource management (ERM), and discovery for materials in all formats. The department creates, transforms, and maintains data, in both MARC and non-MARC schema, to facilitate discovery of high-value library resources. This position reports to the Principal Cataloger. Responsibilities The Electronic Resources Librarian, Data Projects and Partnerships: * Takes a lead role in describing and providing access to print, electronic, and manuscript resources, with a specialization in the Libraries' digital repository and userdiscovery systems. * Oversees data operations across the Libraries' systems. * As a member of the Data Projects Partnerships Unit, manages projects, develops workflows, and trains staff * Maintains close working relationships with content providers, vendors, and consortium partners * Develops and analyzes statistical and management reports for the department and the Libraries * Consults on metadata schema and workflows with staff engaged in repository and digital collections projects across the Libraries * Identifies emerging trends and technologies in metadata management that have the potential for new and improved library services * Participates in library planning, serves on library-wide committees, task forces, and teams NCSU librarians are expected to be active professionally and to contribute to developments in the field. Required qualifications: * ALA-accredited MLS or equivalent advanced degree in library or information science * Knowledge of trends and practices in metadata creation and library discovery systems. * Knowledge of applications of current and emerging technologies as they relate to metadata creation, manipulation, and use * Strong analytical and problem-solving skills * Outstanding oral and written communication skills and interpersonal skills * Ability to work creatively and collaboratively in a team environment * Evidence of ability for ongoing professional development and contribution Preferred qualifications: * Familiarity with trends and practices in serials and electronic resources cataloging * Data analytics experience * Experience working with non-MARC metadata, including XML-based schemas, especially Dublin Core, EAD/EAC, VRA Core * Experience with institutional repository software environments, such as dSpace, DuraCloud, Fedora The Libraries, the University, and the Area The NCSU Libraries and its staff have won numerous awards, including the first Association of College and Research Libraries' Excellence in Academic Libraries Award, Library Journal's Librarian of the Year, Paraprofessional of the Year, and six Movers and Shakers awards. The library system currently consists of the D. H. Hill Library and branch libraries for design, natural resources, textiles, and veterinary medicine, with the James B. Hunt Jr. Library opening soon. With a staff of 260+ FTE, the Libraries has more than 4.5 million volumes in its collection, acquires more than 66,000 print and electronic serials, and has a total annual budget of over $27 million, with approximately $10 million allocated to collections. The Libraries is the host site for NC LIVE, a multi-type library initiative making digital resources
