Go to content Go to menu

I recently was convinced that I need to look into Node.js to build simple webapps or tools, the sort of thing a programmer in a library is asked to do pretty much every day of the week. Yesterday, my friend Kevin Clarke from UCLA reminded me that he had mentioned Vert.x in the past, and that it is “like Node.js for Java.” He’s right. I do think Vert.x is at the top of my “things to play with more” stack. Thanks, Kevin!


OR2016 Dublin Recap

34 days ago

My friend Adam Field tweeted this series of word clouds based on the tweets mentioning OR2016 Dublin. Whatever your feelings about word clouds might be, these are pretty spot-on as far as simple summaries of the experience, so I’m going to start off with these images:


Surprises

This year, I have been struck several times by the fact that I managed to make it through the conference without experiencing the feeling that my brain was mush. This year… I don’t know, maybe I’ve finally settled into this mental space… I suppose part of it is that I participated as a reviewer for OR16, and I ended up attending most everything I reviewed. So, I had longer to digest what it was that was being covered, and there were fewer real surprises for me.

There will be screencasts

But, that’s not to say there were no surprises. Here’s one big one: I’ve now been utterly convinced that recording and making public screencasts is no big deal. The important thing is to just start, and to provide an index to each video, and collect them all in a wiki (including the index with links to sections of the video). Just start, and make useful videos, and keep doing it. Thanks, Adam.

Robots are seriously bad news for usage stats, and there are easy things we can do about that right now

The paper title was I Can Haz Robot and was about robot detection/filtering from usage stats… my initial reaction before even skimming the abstract was, “I think we’ve solved this problem?” Boy was I wrong. The evidence is pretty damning, and was very thoroughly presented by Joseph W. Greene, from University College, Dublin. There is lots of work to do here, but I should at least give an occasional look for the obvious robots (the top users/downloads reports are a great place to start) and then filter those out using the mechanisms provided by DSpace (or whatever platform you might use). It’s not enough, but it’s work that is worth doing. Joseph has an article in the works that will cover this topic in depth, scheduled for publication in July 2016, in the journal Library Hi Tech (deposited but currently under embargo, in Research Repository UCD — the embargo lifts on 8/1/2016 ). Slides for this talk will likely be posted on the OR2016 site .

Node.js is worth exploring (especially for simple tasks)

Jared Watts from the University of Auckland, New Zealand, co-presented a “Daring Demo” about Microservices with my friend and fellow DSpace committer Kim Shepherd, and we sat together at the conference dinner. During dinner, Jared made the case for using Node.js for simple one-off tasks and projects, which is a task space for which I have been using Ruby the past few years, with the idea of “It’ll be good for me to know Ruby better.” I’m convinced, I think Node.js may help deliver on simple projects much faster than Ruby, especially after watching their discovery service demo.

Automated code review will make you look less dumb, and is worth checking out

I kept running into Jeremy Prevost from MIT, including at the Dublin airport on the way out of town. Our last chat was the most memorable, we talked about collaboration and technical debt, and then Jeremy advised that I look into CodeClimate which is an automated code review tool, it’ll check your commits before you push them, and give you the chance to deal with a mistake before someone calls you on it. Sounds great to me, I’m just bumbling my way along here. :-) But, alas, Codeclimate doesn’t work with Java. However, Codacy does, and I intend to play with it.

Speaking of collaborators, here are a few of my favorites: a group photo of some of the DSpace committers

Pictured above, from left to right: Graham Triggs, Hardy Pottinger, Tim Donohue, Andrea Schweer, Pascal Nicolas Becker, Ivan Mas├ír (aka Helix84), Andrea Bollini, Terry Brady, Kim Shepherd, and Richard Rodgers. Unfortunately the committers from @mire had left the room when we decided to take this picture, which makes me a little sad. Next year we’ll get them in the picture, I promise.

DSpace 6 is a little late and people don’t mind; DSpace 7 is going to be awesome

Tim Donohue, the Technical Lead for DSpace, brought this bit of news: several people had expressed relief that DSpace 6 has not yet been released. This counts as a minor surprise. Tim also demonstrated what will likely be the new UI in DSpace 7: ngUI (I think Richard Rodgers coined the name, but it fits, ng is what Angular 2 calls itself), the Angular2-based extended prototype is a work in progress. It’s being built in an agile way, using a Waffle.io board to manage work. I’m hearing a lot about Angular2 (and Angular) from other developers (not just DSpace devs), I think basing the out-of-the-box UI for DSpace 7 on Angular2 is a fantastic choice, and will lead to some really fun repository experiences down the road. I’m looking forward to working with it. Here are the slides from Tim’s presentation on the new UI prototype video recording of one of these sessions should be available soon.

Vagrant Up!

We had a room change and I don’t think the recording equipment made it into the room, so there’s no recording of the Vagrant Up session I volunteered to chair. I blew past the 8 minutes slotted for my demo, which is part of why I’m so enamored with the idea of doing some screencasts… I want a do-over! Luckily, there were four other people in the room to take up my slack: Alicia Cozine from Curation Experts, Nick Ruest from York University, Liz Krznarich from ORCID, and Francis Kayiwa from Virginia Tech. I think between us all we covered all aspects of Vagrant, and a good bit of general provisioning concerns. I’m honored to have been able to present with these fine folks.

On the horizon: mix and match: annotations, IIF integrations, re-usability and related services, machine interfaces to data

It’s pretty clear from the presentations this year that repositories have moved past the “Data is coming! get ready for the data!” stage to the “Let’s do something interesting with all this data!” stage. Stanford is blazing the trail, which does not count as a surprise to anyone, and I found their paper, Value-added services to garner repository adoption to be way more thrilling than the title. Honestly, they are doing amazing stuff, and I want to swipe all their code. They have presented on Spotlight , their exhibit-building service, at past ORs. New to me is their Embed Service which lets them turn over the exhibit building to other sites/services, and focus on just delivering bitstreams with an embedded viewer. It’s really slick, and I intend to play with it. This presentation wasn’t the only place I heard the Rufus Pollock quote ‘The best thing to do with your data will be thought of by someone else.’ but it was the first place I heard it this year. Jack Reed, from Stanford, added “Don’t just create an open repository, let’s build open services around it.” One of the coolest things I saw in this presentation is how the data set in their repository was feeding into all kinds of related projects. And the derivative visualizations had the capability of rebuilding if a new version of the data was loaded. That’s the sort of thing that makes my head tingle a bit.

Speaking of head tingling, Dr. Peter Sefton from University of Technology, Sydney, Australia, presented on this amazing Data Arena they built, which is a platform for storing and displaying data visualizations. It’s a really cool mash-up of version control, data science, repositories and Hollywood.

Peter also presented on Ozmeka which is a fork of Omeka, re-tooled to function more like a repository platform. In a quick demo, he showed off a really slick way to import data into this repository via a CSV, which is pretty standard. What was really interesting was that he included in this CSV file an outline of the data model (collections, etc.) to fit the Portland Common Data Model, and then showed how this same CSV file could also feed into a Fedora 4 repository. It’s a useful concept, and one DSpace users might be able to borrow, since the PCDM is roughly the same as the DSpace data model.

OK, that’s a quick first draft of my thoughts. I reserve the right to make additions and changes, and I plan to add more links to presentations as time goes by. If video recordings are posted, I’ll link them here, too.

I’m especially interested in re-watching the opening and closing keynotes again. I have notes, but I want to re-watch them before I try to say anything about them.

Hmmm… maybe my brain really is mushy, I just haven’t noticed yet?

Ideas Challenge

I almost completely forgot, Adam Field was relentless in recruiting entrants for the Ideas Challenge, and I did join a team, with Grant Denkinson, from University of Leicester, UK, and Roeland Dillen, from Atmire. We didn’t win, but I think our idea, which includes the notion of a post-ingest workflow, will end up being part of DSpace (see DS-3247 ), because it’s a pretty great idea… Getting stuff into the repository is most definitely not the end of the process.

Other recaps

As I find them, I’ll add links to other recaps of OR2016 here. First up is George Macgregor’s ‘EPIC’ blog post … George went to a few of the same sessions I did, and he has written a very detailed analysis, backed up with lots of links.

Videos!

Videos from OR2016 are now getting posted, I’ll link to a few sessions I attended which I think are worth checking out.

  • Ozmeka, a repository before breakfast I mentioned this one above as well… it’s a cool little “scratch pad” repository application, and a nice demo of how to transform a simple CSV file into something far more complex with linked data.