I very much like this infographic from COAR. I've been working with COAR on the Next Generation Repositories Working Group and we have been gradually building a picture of a technological future for repository systems. As this work has progressed over the last year or so, it has gradually become clear that there is an opportunity to describe a sustainable knowledge commons. While the Next Generation Repository group is gradually assembling a picture of the technical components and protocols which can make this work, this infographic covers some other, non-technical aspects which will also be required.
(This is the second of two posts forming my contribution to Open Access Week 2015.) The following proposal was written as a thought-experiment to test, in a recognisable problem-space, the idea outlined in my previous post, The Active Repository Pattern. I was able to call on the the advice of colleagues at EDINA who have world-class expertise in the area of 'routing' open-access metadata and content. The United Kingdom Council of Research Repositories (UKCoRR) was invited to comment, and many members of that organisation provided some very valuable feedback, for which I am very grateful!
(This is the first of two posts forming my contribution to Open Access Week 2015.) Context Institutional repositories It is easy to overlook, or take for granted, the way in which the drive towards open-access (over the last decade or more) has succeeded not only in creating several viable "institutional-repository" software packages, but also in encouraging libraries and IT departments in universities to deploy them. It should be recognised that individual universities have shown, and continue to show commitment to maintaining their repositories in spite of shrinking budgets.
A brief comment, as I hop across the North Sea back to Bristol. With the news that arXiv will now accept deposits from institutional repositories, Dorothea Salo continues her theme about a deposit flow which goes from author, to institutional repository, to subject/discipline repository. Dorothea offers some scenarios, including: Achaea University adopts a Harvard-style open-access mandate. If she wants her articles in arXiv as well, Dr. Troia must rather annoyingly dual-deposit… unless Achaea’s IR implements a deposit pipeline to arXiv, in which case the most she has to do is tick a ticky-box (and I can imagine ways to abstract away the ticky-box).
At a JISC workshop last Thursday I was invited to present some ideas around an architecture to support and exploit repositories in the UK. I gave the presentation the title Repository Architecture #83 ;-) My intention was to suggest some starting principles and then explore how they held up in the face of real-world issues. Here is the slide where I outlined these principles: I also asked the question: "do we actually need a new architecture?
In Repositories thru the looking glass over on the eFoundations blog, Andy Powell gives a summary of a keynote he gave to the Vala Conference last week. It's interesting stuff, and I will take the time to look at the presentation slides as well. I mostly agree (vehemently in some instances) with Andy's points, though I do find myself questioning some parts of this, so I'll quote some snippets and make a few comments here.
Having attended the CRIG Unconference last week, I think that it delivered much that was interesting and valuable. I look forward to the results of the synthesis of the many contributions from the delegates. Although there was just one formal presentation, the volume of content was still considerable, as just about everyone actively contributed something. The final analysis will have to demonstrate whether or not the quality of the content has been good enough to be useful.