Showing posts with label information access. Show all posts
Showing posts with label information access. Show all posts

Thursday, March 28, 2013

Open Access is easier than you think

I recently attended a talk by Jill Cirasella, a librarian at Brooklyn College, on open access publishing (check out the slides here: http://www.slideshare.net/cirasella/cuny-oa-ir-york). I kind of went as a professional courtesy to my colleague who set up the talk, because I honestly thought I was pretty well-informed on the topic. Turns out I was sadly mistaken on that count. I figured the talk would be about seeking out and publishing in open access journals, but what I didn't realize was that there are actually two types of open access publishing: gold and green.

Gold open access journals are ones that make their articles freely available to the public, and sometimes (often?) require their authors to pay a publishing fee. This funding model puts payment for access to scholarship at the beginning of the publishing process, or the time of submission, not at the end, or time of access. This is also what most of us think about when people talk about open access publishing. 

But it turns out this talk was focused on green open access publishing, or traditional journals that allow their authors to self-archive some version of their work, and make it openly available on the web. Some restrictions can include an enforced embargo period, or only allowing authors to make available the pre-print (article before any editor or peer review comments) or post-print (final version of the article, but not in the format published by the journal.)

Jill gave us some tools to easily find out the copyright rules for specific journals, including the SHERPA/RoMEO website, which allows you to search for a journal title, and view a summary of authors' rights. Turns out, the publisher of the two journals I've written articles for, Taylor & Francis, have a very lenient open access policy for library science journals. They allow you to self-archive the post-print of your article, with no embargo period. (Oh how I wish I knew that earlier! My articles have been languishing behind paywalls all this time!)

Once you find out if you can self-archive your article, (it turns out that 94% of the journals covered in RoMEO allow some form of it. Wow!) you need to find a repository to deposit your article in. You can, of course, self-archive on your own site, but large repositories are far more stable and vastly increase find-ability. (You do want to be cited, don't you?!) If your institution has an institutional repository, that's the best place to start. If it doesn't (as my school does not) you can check out this list of discipline-specific digital repositories: http://oad.simmons.edu/oadwiki/Disciplinary_repositories.

It turns out there are 2 pretty prominent library science repositories, E-LIS and DLIST. I plan on submitting my papers to both, but have only gotten around to submitting to E-LIS so far. 

submitted!

and... accepted!
So now you can access the final, peer-reviewed, full-text of my articles here: http://bit.ly/Y1uQZd. I'll keep you all posted on whether my citations go noticeably up or not, now that they are out from behind a paywall.

A pro-tip for you, so you can learn from my fail: KEEP SEPARATE COPIES OF ALL VERSIONS OF YOUR PAPER. I cannot stress this enough. When the editors sent me the first round of comments, I opened up the Microsoft Word document and made the changes (without enabling the track changes function.) So when I was told I was free to make my pre-print publicly available, I didn't HAVE a pre-print to make available. 

THEN, because I'm an IDIOT, I had the opposite problem with the post-print. The final round of edits are usually made directly in the publisher's online system, and I didn't bother going back to my word document to mirror the changes I had made in the system. So when they told me I could make the post-print freely available (but not their version of it) I didn't HAVE a post-print to make available. ::headdesk:: For you fine people, I actually went through the final pdf version of the document, copied and pasted it page by page into a text file to remove formatting, and then transferred the whole thing, plus images, back into a Word document. This was monotonous and cumbersome and I DON'T recommend you do it.

So, make sure you have a copy of the article that you originally submit, BEFORE you receive any comments from the editors or peer-reviewers, and make sure you have your own copy of the final version, with all the edits, and make sure they're clearly labelled _preprint and _postprint. You'll thank me later.

PS- Thanks, Jill, for a really enlightening presentation!!! :)
PPS- You can find a list of all the links from the talk (including a link to the slides) here: http://bitly.com/bundles/scwlibrary/5

Tuesday, October 5, 2010

Bridging the gap from Wikipedia to scholarly sources: a simple library bookmarklet

So I know I have been alluding to a fancy-shmancy "project" for awhile now, and it's finally at a point that I can show it off! Barbara Arnett and I (mostly Barbara, but I set the project in motion, so that counts for something I guess) have created a javascript bookmarklet that can be used in any browser to execute a search in Ebsco Discovery Service from any web page.

The impetus for this project was a tendency for novice researchers to rely on internet sources that may not be up to the standards required by their professors for college-level research (read: Google & Wikipedia). Unfortunately, those users were not only beginning, but ending their search with those websites, without ever trying the library’s subscription databases, or even making it to the library’s website.

Stevens is currently undergoing a trial of Ebsco Discovery Service (EDS), a federated search tool which includes the library catalog data. To make it easier for students to search the library resources, we decided to create a bookmarket that eliminates the step of having to go to the library website first before searching library resources.

The bookmarket provides an important bridge between common search behaviors (especially among undergraduates), and the "deep web" content located in library-funded, proprietary databases, thus easing their transition into scholarly research. You just drag-and-drop it into any browser, after which a search can then be initiated from any webpage the user visits. When the bookmarklet is clicked, the search terms default to the title of the page (so it works especially well with Wikipedia articles), and a prompt is displayed that allows the user to edit the terms, if so desired. When they press the OK button, the search is automatically executed in the Discovery tool and the results are displayed in a new browser window.

The bookmarklet is written in simple Javascript code, which resides on the library’s server, so it can be edited or updated without the user having to reinstall it. It works on all major browsers, and can also be edited to work with various search tools, such as specific databases, library catalogs or competing federated search tools (such as Serial Solutions’ Summon.)

A short demo:



Barbara and I will be participating in a webinar for the Metro New York Library Council in December, demonstrating various tech tools for libraries. See here for details: http://bit.ly/aYud4Q

11/19/10 - NOTE:

Ken Varnum at the University of Michigan has used our code to create an ArticlesPlus bookmarklet for their users. To make it easier for other developers to adapt our code for their projects, here it is, in its entirety. You'll have to edit it to use whatever search tool you want it to run, and change it to link to your own Google Analytics account (or just take that part out if you're not using GA), and we ask that you keep the attribution statement in there.

Thanks!

~val

Monday, August 13, 2007

Panic, Setting In...

Well, it's already two weeks into August, and I'm officially starting to freak out. I can't believe the fall semester starts in two weeks! On top of planning our library instruction sessions for the term, as well as our outreach and promotion, we just found out that we are a go on the new website, but the person who will be designing the CMS template (and so basically, the site) will be leaving at the end of September, so we need to be ready to launch by the end of August.

Wait, what?!!! You'd think with all my complaining and scheming and daydreaming that I would be ready for this by now, but when you actually start to put your ideas in motion, all sorts of problems and issues arise. Suddenly we are getting very critical of our planned navigation, and how will we deal with third and fourth-level nav, and what about server stuff, and what are our online forms coded in?! Oh, and we want to overhaul the content too, so new pages have to be created for all the first and second-level links. Yikes!!!

Some issues we've already encountered:
  • What to call that pesky database page? People obviously get confused by the term (and rightly so, in my eyes.) So far we've settled on Online Resources.
  • What links should go down the left-hand side of the page? These will be our main navigation, and will stay consistent on all pages, so they need to be helpful and fairly self-explanatory. (Right now we're thinking of using Research Tools, Library Services, Special Collections, About the Library, FAQ, and Contact Us.
  • What size screen/resolution to design for? Too big and there will be side-scrolling, too small and there's way too much white space. We're thinking 1024x768 might be a good middle ground...

The homepage will also feature a box that gets populated from our blog, and a MeeboMe widget for IM reference.

So, yeah, I'm definitely freaking out a bit here. But alas, my dream of a site redesign is finally being realized, so the scary deadline is also a sign that we will actually get the new site we were hoping for in the foreseeable future.

If anyone has any insight on good library website design, or sites they think are particularly well-done, please send them this way, I know for a fact that I am in over my head, and would be so thankful for any tips!

Wednesday, May 23, 2007

Why My Library Should Invest in Overhauling Its Online Presence

How is it that, in today's technological atmosphere, where users expect to be able to access virtually everything online (no pun intended, but a good one nonetheless, haha...) it is such a struggle to get the administration to realize the importance of our website? Why am I practically begging for them to at least provide me some support in my effort to streamline and enhance our digital presence, and to see our website as a branch of the library, offering all services the physical branch offers?

My justification to them for such an expense? Here goes...

First and foremost, the library’s website is long overdue for an update, ideally including a redesign. Although the redesign of any website inherently carries some risks, probably the most notable of which is making major changes to a resource that is already familiar to its users, the ever-evolving nature of the internet and the emergence of web 2.0[1] concepts makes an update desirable, if not necessary. Website success can often be traced back to several important concepts, including simplicity in design, logical organization and navigation, media richness, and interactivity[2]. In that vein, the new site should be more intuitive to navigate, and organized to facilitate ease of finding information for all levels of user experience. There should be a focus on technologies enabling communication and interactivity throughout the site, and access to resources and services should be seamless[3].

The chief goals of the new site would be:

- Optimize space on homepage
- Improve navigation
- Integrate web 2.0 technology (interactability)
- Clean up content
- Improve access to resources and services

These changes would make the site more intuitive to navigate, and support users of varying levels of expertise:

- Guided navigation for new users (on homepage only)
- Logical hierarchical navigation for normal users (on left-hand side of each page)
- Quicklinks – direct to resources – for expert users (on top right of every page)

The site would also make better use of web 2.0 technology, featuring a news blog to relay important information about the library and information resources in general. The blog would be updated regularly and be featured on the library’s homepage.

A library blog can be a very useful tool for reaching all of the academic community, not just regular library users. It can be used to draw attention to information about library services and resources that might otherwise be buried in the library’s regular website content. It will also act as a witness to how active and necessary the library is, and can promote the role of the library as an information source and guide even to those not currently using “traditional” library services, by also focusing on general web resources, services and applications. In other words, the blog will seek to make the library visible to faculty and students who have “forgotten” about it.

To better reach the students, care must be taken to keep current on what technologies they are currently using, and to integrate those technologies into library services. For example, instant messaging (IM) could be for reference, and social networking software (such as Facebook and Myspace) can be used for outreach and promotion.

Some guiding questions for integrating technology into library services:

- What technologies are the students and professors already using? Let’s bring the library to them (without investing in new technology just because it’s “new and cool”)…
- Can we find a way for professors to create course/subject pages with important links, or a way for professors to contribute to our “resources by discipline” (since they are the subject-specialists)
- Is there some way to allow users in general to identify relevant resources?

Another important issue is online access to library resources and services. The library currently uses a proxy server to authenticate off-campus users, and users also have to register with the library (with their student ID number) to receive a PIN to access certain services. Ideally, they could log in with their username and password and that would provide seamless access to all library resources and services.

[1] McFedries, P. (2006). The Web, Take Two. IEEE Spectrum, 43(6), 68-68. Retrieved April 2007 from the IEEE database.

[2] Palmer, J. (2002). Web Site Usability, Design, and Performance Metrics. Information Systems Research, 13(2), 151-167. Retrieved April 2007 from the Business Source Premier database.

[3] See ACRLog: Formula for Academic Library Success (http://acrlblog.org/2007/05/14/formula-for-academic-library-success/academic-library-success/academic-library-success/)

For my super-awesome powerpoint presentation for this proposal click here.

Monday, May 14, 2007

If You Build It, Maybe They Will Come...

http://acrlblog.org/2007/05/14/formula-for-academic-library-success/

My library has heretofore been focusing on outreach, but my position is this, we need a user-friendly, intuitive product to promote, or all the awareness in the world is not going to help us. Users have been known to simply ignore software and apps that they find difficult to use. And facing such popular rivals as Google and Wikipedia, we can't afford to send our students elsewhere for their information.

Wednesday, May 9, 2007

I Dreamed a Dream...

My coworker and I were discussing online services the other day, and we decided to get all wacky, and describe the attributes of our dream academic library website. So, here goes...

1.) Authentication through username and password, NOT a proxy server that requires you to configure your browser or a VPN. I know this is not a crazy wish, just a little beyond our over-worked IT department right now (and by that I mean the university's IT dept., we don't have our own, so you can see why they're so over-worked). Once logged in, the users would not only have accesses to all online resources, but also all features of the OPAC, instead of needing a separate PIN number, like they do now.

2.) One interface. Uno. Un. Solamente. Dream big, right? The interface would be Ebscohost-like, for no other reason than I like that particular interface. Through this interface, students can access our books, books elsewhere, e-books, journals, journal articles, newspapers/articles, etc. etc. They would be able to customize their search through a series of checkboxes that allowed them to choose which databases they wanted to search, and/or what kind of results they wanted (what format/media, that is).

The results would be sorted not by database (unless they wanted them that way), but by format (I'm sure most users don't care what database the journal article is contained in, so why not put all the journal articles together in the results, thereby allowing for sorting across all of them, and eliminating duplication?)

This interface would also contain links or buttons that allowed students to immediately request an item through ILL/DDS directly from the record (like in WorldCat). For requests that require a fee, students would be given an option to immediately charge their student account (or credit card or whatever...) In the case of requested articles, once the fee is paid, the PDF is immediately e-mailed to the user (one of the complaints we get most often is from users wanting immediate access to articles... No big surprise there.)

You'll note here that I am not a propronent of a simple, Google-like interface that searches everything. I know that such an interface as I propose would be very complicated, and have a steep learning curve, but it would be so much easier to teach only one interface in our library instruction sessions than 5, or 12, or 20... and it would be so much more useful if the user had control over what they were searching in, what they were searching for, and how they wanted their results displayed/sorted.

I'm definitely not techie enough to know just how much of this is currently possible, but I am internet-obsessed enough to know that this is what users will come to expect, and hopefully the direction we are going in.