A focus on open access

I mentioned earlier this week that I was giving a short presentation on Open Access at an event co-sponsored by The Graduate School and the Library. I've now uploaded the presentation to Figshare, where it is available with a CC-BY license. The presentation itself isn't much to look at, but it does contain a few links that you may find useful.

Holsinger, Kent (2014): A focus on open access. figshare. http://dx.doi.org/10.6084/m9.figshare.1213724

International Open Access Week


Today is the start of International Open Access Week,

a global event now entering its eighth year, is an opportunity for the academic and research community to continue to learn about the potential benefits of Open Access, to share what they've learned with colleagues, and to help inspire wider participation in helping to make Open Access a new norm in scholarship and research. (source)

There are many events planned at venues around the world. You can find a list of those that have been reported to the Open Access Week organizers at http://www.openaccessweek.org/events. One event you won't read about there is an event co-sponsored by the University of Connecticut Libraries and The Graduate School.

Introduction to Scholarly Publishing: Focus on Open Access Publishing
Wednesday, October 22, 2014
4:00-6:00 pm
Homer Babbidge Library, Class of 1947 Conference Room
More information

If you're close to the UConn Storrs campus, Wednesday afternoon, I encourage you to stop by. I'll be sharing some of what I've learned about open access and scholarly publishing, mostly through my association with BioOne. I promise you that I will not be talking for two hours. I do have a short presentation, but my goal is to introduce the world of open access publishing to those who may be unfamiliar with it, to answer any questions I am able to answer, and to provide pointers to some resources that may be useful. If the event goes on for two hours, and I hope it will, it will be because everyone who attends has questions or ideas to share.

If you're in the area, please stop by. I hope to see you there.

Upgrading to Yosemite

  • Posted on
  • by
  • in

OS-X-Yosemite.pngI took the plunge and upgraded my MacBook Pro to OS X Yosemite yesterday. In the end, everything went just fine, but I wish I'd spent a little more time poking around the Internet before I started. For a long time (2-3 hours) I was afraid that the upgrade had died, that my MacBook was hosed, and that I'd have to find a way to wipe the disk, do a clean install, and re-install all of my software.

I started the upgrade around 8:45am. It was chugging along nicely with "7 minutes remaining" when we left for our traditional Saturday brunch at Monet's Table. "Great! The upgrade will be finished, and I'll be abel to get some work done by the time we get back." It was about 11:45 by the time we returned. We had stopped at the grocery store on the way home, and there were groceries to put away. When I looked at my MacBook it still said "7 minutes remaining." "This doesn't look good," I thought. But fortunately, I didn't turn off the power right then. I pulled out my iPad and searched for "Yosemite upgrade frozen." It turns out to have been a fairly common experience.

Jim Lindley had the best advice (and the advice I wish I'd seen before upgrading).

Your Yosemite upgrade may take many hours if you've got anything non-Apple in your /usr folder (Homebrew, Texlive, or Mactex for example). If you got here by googling for "Yosemite install stuck" or "one minute remaining" it's too late to speed it up... but don't turn off your computer, let it finish.

The first thing I noticed was the Command-L advice. I hit that key combination, and after watching the wheel of death spin for a minutre or two, an installation log appeared. There was lots of activity happening, which was reassuring. That gave me the hope that the installation was still working, so I read a bit further. When I got an error message about my log being full, I started to panic. Then I remembered this:

NOTE: If you've got a lot of files affected you may eventually get an error message about the log buffer being full. This error did not kill your upgrade, leave it running.

Then I saw the advice on how to avoid the long install: Move everything out of /usr. I use TeXLive and a couple of other things that install themselves in /usr/local. The problem, apparently, is that Apple's install process doesn't expect to find much of anything in /usr/local (and maybe not even in /usr) and it doesn't check to see how much is there before making its estimate of time remaining.

If you're not using TeXLive, Homebrew, or something else that installs in /usr or /usr/local,1 chances are your upgrade will go swimmingly. If you are using TeXLive or something else that puts a lot of files in /usr or /usr/local, take a look at Jim's advice on how to avoid the slow upgrade. I wish I'd seen it before starting. It would have saved me a lot of angst.