Library Studies in the UK

17/09/2013 § 4 Comments

Editor’s note:  This is a guest post by Natasha S. Chowdory

Hi! I’m Natasha. At the moment I’m working as an assistant librarian in a small technical library in the UK. I’ve been in the role for a little over a year and loved it so much that I decided to become a librarian. Today I wanted to share information about what it’s like to be a library student in the UK.

First and foremost, in order to become a librarian or rather ‘information management professional’ in the UK you have to make sure that you choose a course that has been accredited by CILIP (Chartered Institute of Library and Information Professionals). CILIP has branches for each region of England as well as hosting conferences and serving as a platform for new ideas related to information management (the most current being the issues surrounding metadata and the crisis of libraries closing across the UK). If your course is accredited by CILIP you increase your employability – not just in the UK but also all over the world. So that’s step 1. They have reduced membership rates for students which include incredible benefits – magazines, job notifications, etc.

« Read the rest of this entry »

How You Too Can Transition from a Librarian to a Doctoral Student

03/09/2013 § 11 Comments

Editor’s note: This is a guest post by Abigail Phillips.

I often get, quite naturally, the question, “So, what made you decide to get your PhD?” I always feel a bit sheepish when I offer my response, “Well, I’ve always known I would.” I should have an intelligent and eloquent explanation for such a major, life-altering decision. But I don’t. However, what I do have is a somewhat intelligent and kinda eloquent explanation for my decision to leave my job as a public librarian and become a doctoral student in Information Studies.

After working in public library for six years, two as a library assistant and four as a professional librarian, I left the practitioner world behind last fall to join the PhD program in Information Studies at Florida State University (FSU). I have yet to regret this decision. My experiences in researching, writing, and teaching over the past year have erased any doubts I may have had during those first few months of my doctoral studies. This feeling of rightness and certainty is a rare experience for me.

So, how do you, dear reader, know if you really want to get a PhD? If you are working as a public librarian or school media specialist, how do you know if academia is a good fit for you? What follows are some suggestions, tips, and advice from an ex-librarian turned academic for those thinking about entering a PhD program. Although my focus in this post is on potential doctoral students in Information Studies, this advice can be applied to any doctoral program.

« Read the rest of this entry »

Basic Tips for Working with Patrons with Disabilities

22/08/2013 § 2 Comments

Editor’s note: This is a guest post by Ruth Kitchin Tillman

Although I’ve been interested in making libraries and archives more accessible to persons with disabilities for a while now, I’ve been spending this summer specifically working on learning more about laws, programs, and first-person perspectives on disability. While it’s a challenge to learn about what’s out there, working with patrons with disabilities doesn’t have to be complex. There are just two things to remember:

1) People with disabilities are people first.

Talk to THEM first. Talk to them just like you would anyone else unless they indicate otherwise (such as people with hearing loss who ask you to speak up or indicate a pad/paper). If they need interpretation or assistance from a person who is with them, that person will volunteer when needed. If the person serves as an interpreter, direct your conversation to the patron, not the interpreter. I recently wrote up about my first experience with a relay (TTY) call. My problem was thinking of it as some complicated interaction, instead of a simple communication between two people.

« Read the rest of this entry »

Web Development 101 – Beyond the Basics

30/07/2013 § 2 Comments

Editor’s note: This is part 2 of a guest post by Bryan J. Brown. You can read part 1, The Basics, here.

After learning HTML and CSS, the next steps on your path to web development greatness depend largely on what you want to do. Depending on your personal and/or professional interests, you should decide whether you want to dive into server-side or client-side scripting (or if you are even interested in going further, HTML and CSS may be all you want). To understand the difference between server-side and client-side code, it’s helpful to know just what happens when you go to a web page.  When you type a URL, you are requesting a specific page from a specific server on the web, and that URL contains that page’s exact location. Let’s use “example.com/index.php”. This URL points to the file “index.php” sitting on the “example.com” server. When the “example.com” server recieves this request, it processes it and responds by sending the requested page’s source code (along with any CSS or JavaScript code associated with it) back to your browser. When there are server-side scripts associated with a web page, the server runs these scripts as part of it’s processing of the request. The script tells the server to do something, and this can be anything from outputting the current date and time to pulling information from a database and outputting it as HTML. This new, dynamically created web page is then sent as the response. If the page has client-side scripts in it, these are sent as part of the server’s response (the server does not process the client side code at all, this is the key difference). When your browser receives the response from the server, it starts building a visual representation from the HTML and CSS (this is what you see in your window) in a process called rendering. Any client-side code is then processed by the browser and applied to the rendering or behavior the page. If you have ever seen moving parts of a web page, such as  buttons that expand or contract, this is client-side code being run directly in the browser.

HTTP Request & Response

Image made available by the author under a CC0 1.0 license.

« Read the rest of this entry »

Web Development 101 – The Basics

23/07/2013 § 18 Comments

Editor’s note: This is part 1 of a guest post by Bryan J. Brown. Part 2 will be posted on July 30.

If you’ve been paying attention to the librarian blog scene at all, you’re probably familiar with the infamous “Should librarians learn to code?” debate. Maybe “debate” isn’t the best way to describe it; it’s more like a dead horse that bloggers give a few extra whacks to every couple of months. Well, now it’s my turn. It’s 2013, y’all. Of course you should learn to code. In case you haven’t noticed, pretty much every aspect of librarianship has been completely revolutionized by the web and that’s not a trend that will lose steam anytime soon. The web isn’t the future anymore, it’s already the present. The role of the digital librarian is to leverage all available technology to enhance access to information worldwide, and I don’t care whether you work in reference, collection development, or tech services, we are all digital librarians now simply by virtue of being librarians in a digital age. If you choose not learn to code, you are choosing to limit your competency with technology, and that’s not something anyone should choose to do (especially if you are a grad student looking for a job). Choose to play an active role in the exciting world of digital librarianship. Choose to be unlimited. Choose to code.

I can certainly understand why some people wouldn’t want to learn to code, it looks pretty scary from the outside. Programming is one of the most intimidating subjects around, but the thing you have to realize about it is that it’s only as difficult as you want it to be. Let’s compare it with learning to fix your car. That’s a scary prospect because cars are really complex, but no mechanic ever started out by rebuilding a carburetor. They probably learned to deal with the easier problems first, like changing the oil or replacing a dead spark plug. These problems don’t require much mechanical skill or knowledge, yet they end up being the most common issues that auto owners have to deal with. For some people, that’s all they are interested in learning, and that’s totally fine. At least they are now that much more knowledgeable and capable than the person who decided that working on cars AT ALL was too scary and avoided the subject altogether. Some knowledge is always better than none. Similarly, nobody is saying you to become an expert programmer, but everyone should be able to fix simple errors on a web page, and these are the most common coding problems of all. The more you know about coding, the more opportunities open up for you. Every new thing you learn is another thing that you don’t have to rely on someone else to do for you, and the ability to do things yourself is truly powerful (and truly impressive to folks who can’t do it). With this in mind, realize that how much programming you learn is entirely up to you, but it is always in your best interest to learn all that you can.

Baby Steps

Enough already with this propaganda, you get my point: code good, fear bad. You want to start, but you don’t know where. What’s the best point of entry into the awesome world of web development? The answer is HTML and CSS. HTML and CSS are the most important things to know for any librarian (or anyone interested in coding in general) because they are the foundational elements of the web and surprisingly simple. To go back to the mechanic analogy, HTML and CSS are they oil changes and spark plug replacement skills of the web development world; they are easy enough for anyone to pick up quickly, but they do require a bit of courage to get your hands dirty. No matter what area of the library you work in, there is a very good chance that you will have to create or fix a web page at some point in your career, and HTML and CSS are the languages you will use. If you have no clue what these crazy acronyms mean, just think of HTML as the text that appears on a web page and CSS as the “rules” that determine it’s appearance.

Writing HTML and CSS is definitely “coding”, but it doesn’t have the complex logical skills of true “programming” (although it will teach you some basic skills that will come in handy later if you end up doing some real “programming”, like how to use a text editor or connect to a server). A basic knowledge of HTML and CSS will give you the skills to create a simple static web page from scratch, and even though there are a lot of other things you can learn that will supplement these simple web pages to make them do some really cool stuff, they are pretty useless if you don’t know HTML and CSS first. Some top notch places to learn HTML and CSS are (in order of my personal preference): Codecademy, HTML Dog, and W3Schools, but the web is overflowing with other resources as well (YouTube videos are also great if you are more of a visual learner). Fire up your text editor (you even can use the default text editors on your system, like Notepad on Windows or TextEdit on a Mac), copy the examples from tutorials and play around with them until you feel like you understand them, and then try to create some new pages from scratch. You don’t even need a server, just save the files to your desktop and open them in a browser. If you want to show off your shiny new code babies to your family and friends, you can even put them up on the web using Dropbox.

Be sure to read part 2 of this post, Beyond the Basics, next Tuesday, July 30.

Bryan Brown is a second year MLS/MIS student at Indiana University’s School of Informatics and Computing in Bloomington, IN with a focus on digital libraries. He works as a Web Development Assistant at the Lilly Library, and as a Scanning Technician for IUL Digital Collections Services. His professional interests include library metadata, web development and digital preservation, but he also plays a mean banjo. Find out more about him on Twitter (@bryjbrown) or from his blog (www.bryanjbrown.com).

Follow

Get every new post delivered to your Inbox.

Join 736 other followers

%d bloggers like this: