This thread is old, but I've just realized a benefit to already having a
lot of unix experience under my belt.
I'm taking some online courses and the first week of each course is
essentially bringing the Windows and Mac users up to speed. This is a
working directory, this is the command line,
Chocolatey suite.)
Josh Welker
-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
Siobhain Rivera
Sent: Monday, October 27, 2014 9:02 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: [CODE4LIB] Why learn Unix?
Hi everyone,
I'm part of the ASIST Student Chapter
Hi Everyone,
Thanks for the friendly and helpful comments. I really appreciate the
information, and I will check out the linked articles. If you come up with
anything else, I'd love to hear about it.
Siobhain Rivera
Indiana University Bloomington
Library Science, Digital Libraries Specialization
On Oct 28, 2014, at 10:07 AM, Joshua Welker wrote:
There are 2 reasons I have learned/am learning Linux:
1. It is cheaper as a web hosting platform. Not substantially, but enough to
make a difference. This is a big deal when you are a library with a
barebones budget or an indie developer (I
I would recommend learning Linux because it is the key platform for open
source software in general, and librarians need to embrace open source in
order to take control over their library systems, in order to deliver to
their users what they actually need, rather than what can be delivered
within
On 10/27/2014 10:02 AM, Siobhain Rivera wrote:
Hi everyone,
I'm part of the ASIST Student Chapter and Indiana University, and we're
putting together a series of workshops on Unix. We've noticed that a lot of
people don't seem to have a good idea of why they should learn Unix,
particularly the
On Mon, Oct 27, 2014 at 10:02:18AM -0400, Siobhain Rivera wrote:
I'm part of the ASIST Student Chapter and Indiana University, and we're
putting together a series of workshops on Unix. We've noticed that a lot of
people don't seem to have a good idea of why they should learn Unix,
particularly
Hello,
Well said Conal. I can't believe that an army of over 100,000 librarians
continue to purchase closed ILSs and other software that limits how we
serve our patrons yet have the nerve to complain about dwindling library
budgets and even the nerve to refer to ourselves as information
Hi everyone,
I'm part of the ASIST Student Chapter and Indiana University, and we're
putting together a series of workshops on Unix. We've noticed that a lot of
people don't seem to have a good idea of why they should learn Unix,
particularly the reference/non technology types. We're going to do
Learning Unix is not necessarily the problem to solve. Instead it is means to
an end.
To my mind, there are number of skills and technologies a person needs to know
in order to provide (digital) library service. Some of those
skills/technologies include: indexing, content management
Couldn't agree more with Eric. Additionally if you are going to be doing
any web work at all you will need to know the back end environment which
will likely be Linux.
Edward Iglesias
On Mon, Oct 27, 2014 at 10:09 AM, Eric Lease Morgan emor...@nd.edu wrote:
Learning Unix is not necessarily
Eric hit the nail on the head, Unix is not inherently needed for many
libraries, but it can be useful for more technically inclined librarians to
know Linux. I am a digital content librarian at my institution and I
actually know neither system, though I wish I had a better understanding of
Linux.
On 27/10/2014, Matthew Sherman matt.r.sher...@gmail.com wrote:
Eric hit the nail on the head, Unix is not inherently needed for many
libraries, but it can be useful for more technically inclined librarians to
know Linux. I am a digital content librarian at my institution and I
actually know
oops, ignore the accidental blank
but anyway, Linux/unix have a nicer idea of permissions and security
so often you get better uptimes, less need for reboots.
You can serve apache etc on other OSs but often not all modules are
ported to the less popular serving platforms.
Dave Caroline
On
Hello,
I think that all library jobs are and ought to be techy. If they aren't is
because the person's working those jobs aren't practicing modern librarianship.
In think the culture of librarianship is at fault as opposed to the individual
librarians.
When it comes to Unix, I'm assuming
It really depends on what you mean by learn Unix.
I agree with Eric that many tools, particularly open source tools, are more
robust on l
Linux. This is because most of their development communities are building
on Linux, so new features and bug fixes show up their first.
I live in the open
There is something of a natural symbiosis between *NIX and libraries. If you
have not already found it, read Unix as Literature for some background on why
those who like the written word are drawn to *NIX naturally.
--
Andrew Anderson, Director of Development, Library and Information
There’s also something to be said for the Unix pipeline/filter model of
processing. That way of breaking down a task into small steps, wiring little
programs to filter the data for each step, building up the solution
iteratively, essentially a form of function composition. Immedidately, you can
Siobhan,
I teach a course on digital curation tools and applications for the
University of North Texas, and one of the motivational pieces I use is the
Digital Curation Centre's chapter on Open Source and Digital Curation by
Andrew McHugh in the Digital Curation Manual (2005):
for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Cornel
Darden Jr.
Sent: Monday, October 27, 2014 10:51 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Why learn Unix?
Hello,
I think that all library jobs are and ought to be techy. If they aren't is
because the person's
Hello,
A reference librarian solves information problems. If I ask an average
librarian how to rip a video, how to convert file formats and videos, or why my
files and videos aren't playing; should they be able to help? That's the real
question. Should reference librarians know how to create
A few other readings I use on *nix:
- Powers, E. (2012). Why I learned to love the command line. Hack
Library School: By, For, and About Library School Students.
http://hacklibschool.wordpress.com/2012/02/20/why-i-learned-to-love-the-command-line/
- Stephenson, Neal. (1999). In the
Learning UNIX is fine. However, I do think learning SQL might be a better
investment. So many of our resources are in databases. Understanding indexing,
sorting and relevancy ranking of our databases is also crucial. With linked
data being all the rage knowing about sparql endpoints is
On Oct 27, 2014, at 10:02 AM, Siobhain Rivera siori...@indiana.edu wrote:
what do you think are reasons
librarians need to know Unix, even if they aren't in particularly tech
heavy jobs?
The best reason is so that you can understand the problems you're working with
as well as
Hi Siobhain,
I have a discussion of why learn UNIX in this Code4Lib journal article I
wrote a few months back:
Unix Commands and Batch Processing for the Reluctant Librarian or Archivist
http://journal.code4lib.org/articles/9158
Best,
Anthony Cocciolo
--
Anthony Cocciolo, Ed.D.
Associate
On Oct 27, 2014, at 12:38 PM, Bigwood, David wrote:
Learning UNIX is fine. However, I do think learning SQL might be a better
investment. So many of our resources are in databases. Understanding
indexing, sorting and relevancy ranking of our databases is also crucial.
With linked data
for Libraries CODE4LIB@LISTSERV.ND.EDU on behalf of Siobhain
Rivera siori...@indiana.edu
Sent: Tuesday, 28 October 2014 3:02 a.m.
To: CODE4LIB@LISTSERV.ND.EDU
Subject: [CODE4LIB] Why learn Unix?
Hi everyone,
I'm part of the ASIST Student Chapter and Indiana University, and we're
putting together a series
27 matches
Mail list logo