Follow Up to Repository Fringe 2014

It has now been about a month since Repository Fringe 2014 and we wanted to bring you a somewhat belated follow up post to share presentations and other resources with you. Firstly though a huge thank you to all who joined us at the end of July for two days of all things repository. It was brilliant to have our biggest ever turn out this year! We had a great time and we hope you did too!

Image of Round Table Discussions at RepoFringe 2014

Round Table Discussions at RepoFringe 2014

 

Throughout the event we endeavored to blog as many sessions as possible. You can find these in our LiveBlog Day One and LiveBlog Day Two. You can also find links to specific sessions within the Programme page – where you will also find links to most of the Slides and, where available, Owen Stephen’s blog posts on the event (thanks Owen!).

Image of Participants talking at Repository Fringe 2014

Participants talk at Repository Fringe 2014

During RepoFringe 2014 we were also out and about taking pictures. You can find all of these – and add your own if you would like – in our Flickr Group. If you are/have written a post or article on your own travels to Repository fringe you are more than welcome to use any of the images uploaded by our RepoFringe account as they are all shared under Creative Commons licenses.

Your Blogs and Tweets

You were brilliant throughout Repository Fringe 2014 contributing to the event, tweeting magnificently and, in some cases, also blogging your own experiences. You can view all of the key tweets and updates in the Storify we have created, tracking discussion and articles about the event. You can also see Adam Field‘s excellent tag cloud by clicking on the image below.

Adam Field / @Godbfrey tweets his World of the #rfringe14 tweets

Stephanie Taylor, ULCC, wrote about her trip to Repository Fringe, and highlighted her colleague Rory McNicholl’s participation in the winning Developer Challenge entry from the Repository Linter Team in this blog post on the ULCC Digital Archives Blog.

The full team for Repository Linter was Richard Wincewicz, Paul Mucur and Rory McNicholl and you can access their code here on GitHub. They did a great job but did have stiff competition in the Challenge from Are We There Yetttt?, a team composed of Miggie Picton, Marta Riberiro and Adam Field. Our Developer Challenge was sponsored by the lovely people at the Software Sustainability Institute who are running their AGM and Hackday in London this week. For more details on what they do and upcoming events take a look at the SSI website.

Image of The Developer Challenge Teams at RepoFringe 2014

The Developer Challenge Teams at RepoFringe 2014

Sarah Fahmy at the Jisc Open Access Good Practice project blogged about the team’s time at RepoFringe on their project blog. Meanwhile David Young at the Jisc-ARMA OA Good Practice Pathfinder Project wrote about his own, and his colleague Ellen Cole’s adventures at the event on the project blog and on the Northumbria Research Support blog.

Clair Waller blogged about Repository Fringe 2014 – sharing a “Part 3″ post on the Jisc End-to-End Open Access Process Review and Improvements project blog, to compliment our Live Blog posts. And Jackie Proven, from the Open Access support team at St Andrews, blogged about her team’s experience at the Fringe in “Open Access at the Fringe“.

Other Useful Resources

A number of useful URLs were circulated on Twitter around the event.We’ve captured a few of our favourites, and added additional access to our Twitter archives for Repository Fringe 2014.

Thank You!

We’ve have tried to collect up all of the relevant blog posts, slides and resources for this post but if we’d missed yours out just let us know and we’ll be happy to update this post! We would also be happy to share your own reflections or follow up posts to this year’s event, just get in touch to let us know.

Huge thanks again to all who came along to Repository Fringe 2014, and to all of you who completed our feedback survey which we will use to help us shape future events. If you have any other feedback do leave a comment here on the blog or drop us an email, we’d love to hear your comments and ideas!

Image of Repository Fringe participants networking

Lovely Repository Fringe participants networking at coffee on Day One

Repository Fringe 2014 LiveBlog – Day One

It’s finally here! Repository Fringe 2014 is live, with two busy days of talks, discussions and our Developer Challenge. We will be tweeting – follow #rfringe14 for all updates – as well as liveblogging the event. We are also taking images and videoing some of our talks, and these will be uploaded and made available here on the website shortly after the event.

This is a liveblog and that means there will be a few spelling errors and may be a few corrections required. We welcome your comments and, if you do have any corrections or additional links, we encourage you to post them here. 

Welcome to Edinburgh, Kevin Ashley, DCC, Informatics Forum, G.07

Welcome to Edinburgh! I’m Kevin Ashley, Director of the Digital Curation Centre, one of three organisations – along with EDINA and the University of Edinburgh – that fund and make Repository Fringe possible. I know this is our biggest Repository Fringe ever! This is something of an unconference event, we try to adapt the event to the needs of the participants – and I’ll say a bit more about that shortly.

Coming back to the origins of the event. Back when I first got involved in repositories, back when I was at the University of London, we heard about this project at MIT called DSpace… as it happens our university moved away from DSpace and into EPrints. But for a long time we spent a lot of time looking at managing papers and collections of papers. And whilst that is part of what we focus on at Repository Fringe, we also like to think about what else we need to store – collections of tweets, multimedia… and we think about what changes need to happen to move things forward, and what barriers need to be overcome to do that.

One way to do that is the Developer Challenge. You have until lunchtime today to register for that. You’ll have 24 hours to solve a particular repository problem. Even if you are not a repository you can contribute by feeding in ideas, also by lunchtime.

Of course we know there is also the Edinburgh Fringe taking place – and just like the Fringe, Repository Fringe takes place across several venues this year! We are mainly here in Informatics, in Appleton Tower, and some events are in the Main Library just across George Square.

One further thing about the Repository Fringe – we really want to open up the discussion about what the Repository Fringe should look like in the future. Do come and chat with us, let us know your feedback and ideas.

And now, to introduce our opening keynote speaker Yvonne Budden, who has worked in libraries since she graduated in 2002. She has worked on the WRAPed project and currently works at the University of Warwick spanning repositories, scholarly communications, data metrics around repositories, etc. She is also chair of UKCoRR and sits on the Jisc Scholarly Communications Advisory Group. So, over to Yvonne.

The revolution has been cancelled: the current state of UK open access,Yvonne Budden, University of Warwick, Informatics Forum, G.07

When I was asked to speak I was told to be controversial, to get things off to a rousing start. Now, I may not be as rousing as my picture of Lenin here but I do hope to trigger a revolution by the end of my talk! By which I mean a radical change.

I was reading an article by Richard Poynder (2014) the other day, answering questions on where we are with repositories and what still needs to be done. He said

“For their part, publishers tend to assume that OA advocates are freeloaders or – as ACS’s Rudy Baum appeared to imply in 2004 – dangerous socialists”

Now, when I was reading that I was chasing and paying invoices to publishers, awaiting a new HEFCE REF, but nonetheless I liked the idea of being a dangerous socialists! Are we getting a stall in the way we are thinking? So I got to thinking about revolutions, about movements. I looked up some definitions and have picked three…

1. A wide reaching change in affairs

So, this year we had another significant anniversary. The 25th anniversary of the invention of the internet. The internet has been a huge change for people but it has also become synonimous with the idea of freedom of knowledge, and the freedom of knowledge – also associated with Gutenburg’s press and the history of publication. Communication is speedy and international, information is readily available – good and bad. And people’s expectations have become to change in this environment. People expect to be able to get this information. People expect to be able to Google something and find an answer. So are we, in scholarly communications, making the most of that opportunity, those advantages, and those expectations? I think this will be vital for researchers who are time poor, but also these tools will help us to do our job and support researchers better, to automate part of our work.

We had Stefan ?’s call to arms in 1994. We saw huge amounts of action and advocacy around open access. But it has been about fixing our problems – about overcoming access issues. Is it really a people’s revolution? When we get a collective group of people talking about something, you can do anything. People power is important. But an issue we have in the open access world is that… is what I think of as open access the same thing that you think of as open access? What is green open access? What is gold open access? I heard “diamond” open access the other day! If we don’t understand how can we expect our researchers to do that. These are complex and difficult definitions. It is an international movement and yet everyone looks at the issue from their own environments, their own local context. That makes sense, we can’t change things beyond our immediate area, but we are also activists, we are part of bigger movements. We need to start thinking with one voice, in one specific direction, to make things that little bit clearer. There has never been a single international body that has pushed for open access. Why haven’t we got an IFLA or Libre… international movements. Are we giving bodies that do exist, like SPARC, enough power and support for them? Are some forms of open access more equal than others?

2. Revolution is a cyclical recurrance

The oldest definition here. We have an interesting survey from Taylor and Francis – attitudes are up across the board, except for the speed of open access. I think that’s to do with people engaged in hybrid open access. Almost half of T&F authors plan to choose green open accces in the future, a third plan to choose gold open access. 66% of those asked found articles useful to their research in repositories. And 45% of these international authors found the repository version just as useful as the “version of record”. Nothing in this report is likely to be a surprise, but there are more people talking about open access. Responses feel more informed all the time. Open access is no longer the preserve of “that crazy repository manager”. We no longer hear people asking what open access is. Now it is “I’ve heard of it, but how do I do it?”.

I also wanted to contrast that T&F survey with some research did with our Warwick researchers. We did two surveys – one in 2011 and one in 2014. Both are based on Huddersfield’s Repository Support Project survey. We haven’t seen a big change in attitude (in favour) to OA. But we have seen increasing numbers making work open access (and happily for us 67.1% used WRAP). And interestingly 70.4% believe copyright of articles should remain with the authors. That’s interesting and tells us that the status quo is kind of broken. And 93.5% keep a copy of the authors manuscript – although I can tell you now that not all of them are sending them to me. And finally 48.6% are happy with CC-BY licenses for their work.

Just a quote from one respondent, who notes that the model for open access means the university pays to make work OA, and also for licenses to journals, so pay twice when it would be better spent on research. And another respondent raised the issues of the bounds of plaguerism – an issue we will all increasingly need to grapple with.

In terms of attitudes to the RCUK policy from Warwick researchers, a good 20% are strongly in favour, others are also (less strongly) in favour. Contrast that with attitudes to the HEFCE policy. They are completely different approaches, with very different priorities. The key areas and mechanisms are very different. But reactions of the researchers are very similar. Those in favour of the RCUK policy, also seemed to be in favour of the HEFCE policy. It will be interesting to see how those strongly not in favour get on.

I think it was my very first Repositories Support Project meeting that I heard the phrase “Carrot and Stick” – important for compliance for all of us. But I think one of the things we have to be very careful about as we engage with publishers on an article by article basis for gold OA, is that the carrot for the researcher in funding does not become the stick for the library in terms of work and admin. Anyone working with publishers will be aware of just how much work it takes to get OA working. Some of us still aren’t getting what we paid for – the licenses, the speed of publishing. And the irritating practice of having an article under a different license when “in press” than when published? Should in press articles get that same CC-BY license in that crucial 4 month window when the research is new and live.

And issue of ownership, and a brief quote from Leo Tolstoy on the taking of labour by force… I have had the experience of explaining how publishing work to someone totally outside of that world. You explain the process, from author handing over copyright, then reviewing for free, then buying articles back for the researcher to borrow. I have a friend in banking who I explained this to who couldn’t understand this model. Our whole model is based around publishers certifying the research. Except it isn’t the publisher that is certifying that research. Isn’t it time that we do it ourselves. The SPARC agenda – the license to publish rather than a license to make open access – is becoming really useful and interesting here. When I undertook my librarianship degree the phrase “knowledge economy” was being bandied about, but I think we are only just seeing universities and researchers thinking about how best to exploit their knowledge, to be part of this knowledge economy.

At this point we are 16 months into the RCUK 5 year policy. We are having issues with pubishers, with getting what we’ve paid for. And there is that perception of OA taking money away from research. The RCUK policy is well intentioned. It makes researchers think about journal selection, about where to publish. Or at least it should. We don’t quite see that… instead they submit, they get the article accepted, and only then is it a hurdle they have to cross… and they want money to publish in a journal and we have to point out when that is not a compliant journal, and not an article we can pay for. There is still much to do to ensure this checking, this OA process, begins much earlier in the process, at the point of selection and submission.

Now, many of you will be familiar with Swan and Houghton’s 2012 work on the cost of implementing OA. It’s very clear from that work that OA will cost this country money. And how do we go forward in a mixed ecology where some countries support OA, some do not. Are we creating two classes of research and researchers? Are all articles and is all OA equal?

One of the existing tenants of scholarly publishing has been the idea of free markets. But if you can only buy a journal from a single publisher, that isn’t a functional market. That doesn’t encourage prices to even out. It’s the situation we’ve had with journal articles, and it’s an issue we will see with APCs. We will create another monopoly within the publishing market. We are already seeing that costs of subscriptions and APCs are continuing to rise. Are we creating a market by paying for OA? Going forward we need to make sure that we don’t do with research, what we did with journals. Now with journals we did a classic library thing… we made life for researchers easy and seamless… but the costs and work in that were hidden. We’ve now had to switch off IP access to electronic resources because of the number of conferences etc. held at Warwick. This is something that helped raise awareness with researchers that the library is paying for this stuff. They don’t get this stuff automatically. The library puts a lot of budget in. And with APCs we need to do similarly. We should develop seamless processes all through the environment and process so that those who want to pay for OA can do so easily. BUT we have to make the cost, and who is paying that cost, clear to our researchers. That’s essential for us going forward. That sense of researchers understanding that there is a cost here. And that’s the only way to focus attention on the cost of journals.

3. Overthrowing of an established government or social order by those previously subject to it

Now this something we need to be part of. We need to inform researchers so they can change their own environment and process. But change won’t come quickly. One area we are subject to change in… there has been a certain amount of vocal government support of OA approaches. I don’t know if the new universities minister, Greg Clark, may do anything. I don’t think things are looking hugely promising for the current government – and that may not even apply to colleagues in Scotland after September! – but what will things look like for the UK in May 2015? Will there be another shift? Can we do anything about it to push forward a wholesale change in the environment, in scholarly communications?

Now, when we talk to a researcher about OA, which hat is he wearing? How much of our message gets across depending on whether he’s wearing a research, a dissemination, a supervisor, a teaching hat. And we need to be aware of all those hats – and the needs they have under each of the many roles they combine. Can we think in a more joined up fashion and get people to engage in all parts of that process. This gets back to the issue of research data management. It’s been interesting for me to take on the role of Academic Support Manager at Warwick, to engage researchers at other points in the process – not just when they have this product, this neat journal article. I find being a contact for researchers around their research, their research data… if we can engage when they wear all of their different hats – and if we can change our repository manager hats to suit – then that will make a real difference. At Warwick I’m known as the “open access person”, that’s fine but I don’t think we can afford to just be. Open Access doesn’t just happen in isolation – it’s part of the full research life cycle.

I’ve spoken a lot about open access in the research community. So what is the future of scholarly communications? Is electronic publishing and OA about replicating print materials. There has been a revolution in OA Journals. Can we think differently. Can we have a conversation about what “dissemination of research” really mean? What do researchers want it to mean? For a researcher to fulfill open access, public engagement, widening access, REF, requirements all at once and differently? When preparing Warwick’s REF materials I was sad to see an awful lot of interesting and innovative types of outputs disappear from the outputs section as everything became a homogenous series of books and journal articles. Some of that stuff went into case studies but for many researchers REF meant that type of materials. It didn’t matter what REF said – it had wide requirements – our researchers were totally focused on their traditional outputs. But there is so much more taking place, so many other forms of output. Is there not something to do there. In that T&F survey 11% of researchers said that the current scholarly articles will no longer be relevant in 10 years time. That’s depressing. We need to think outside of the box now. We need to encourage researchers to think beyond packaging research as journal articles. I think it’s time to start having these conversations, particularly as we move publishing activity into the institution, where we can make a real difference. So if a researcher wants to set up a new journal can we start talking about research outputs that enable interaction, that are conversations, that get more people involved. We can think of researchers in a different way, outputs in a different way, and scholarly communications in a different way. Changing researchers attitudes in a way that moves forward the whole.

Q&A

Q1: You mentioned switching off IP access. How did you do that?

A1: There are a few journals we have had to leave IP access on because there wasn’t another way to do it. We had backlash to that change otherwise – and all from one department. We have enabled the switching off of IP access using a proxy that forces login.

Q2: Given how things have played out over the last 10-15 years… there have been lots of missteps around whether Institutional or Subject repositories are better. Open vs Libre access. Should you change the whole scholarly communications structure… if you had been in charge, if you had been in power, what do you think should have been done differently?

A2: I think in a lot of cases the biggest issue is that open access, as a movement, has been split. And there have been skirmishes around which type of open access is better. I would have bashed some heads together, to seek a way to agree on open access, to enable all routes to open access no matter what sort of repository. So if we speak to researchers the library talks about one sort of open access, the publisher talks to them about a different sort of open access. Open access means 30 or 40 different things and you can’t get concensus in that environment.

Q3: I wanted to clarify – who do you consider to be the revolutionaries? To me it’s no longer the libraries’ problem, it’s an academic problem. Doesn’t that shift emphasis from repositories towards solutions for them.

A3: Absolutely. But I think we still have a role here. It is an academic problem, our role is to find solutions. There is a lot of work in the OA community – options, ways to get systems to talk to each other. But we may no longer be on the forefront anymore. To be honest I’m not sure we ever should have been.

Q4: I was really interested in your last point – about broadening what we do in terms of research dissemination. There is no rule against that. Publishers don’t neccassarily stop that. And open access articles are not the only way of doing that. Would it be a good idea to encourage researchers to put data in data repositories, to disseminate their researchers in parallel to scholarly articles. To breaking out of the loop.

A4: yes, this is the time to start thinking about this. We need to think of data as a product – not just the by product of an article. The point I was trying to make was that when researchers think about what they need for promotion or for the REF, is that they tend to fall back on the traditional. I think it would be nice to think about not having that article in that top flight journal isn’t neccassarily bad if you are disseminating elsewhere – the data, the research methods, etc.

Q4: I think we are not ever going to be at a place where repositories or institutional websites will ever have the same impact factor that researchers need for the REF and for promotion. I just think that we need both in parallel. Making data available for reuse, for text mining etc.

A4: Yes, but personally I would prefer not to need to have that traditional model always there.

Q5: I was really pleased to see you talking about rights, about licensing. I came into repositories having done work selling writing. I was sure that model wouldn’t survive.. but it has. This has been a real brick wall. We now have the means to publish… I can’t seem to get over the hurdles, to make researchers aware that THEY are the value of the journal – their reviews, their input. It’s not the publisher. This has really inspired me though – do you have any tips?

A5: I have helped researchers retain their own copyright, but often thats researchers coming to me and wanting to find out how to avoid signing a publishing contract having seen colleagues retain copyright of their work. Oddly I think we will have more traction with established academics, young researchers tend to be more conservative. But the new impact factors from Thomson Reuters, and discussion about those, have been encouraging. Thomson Reuters took away impact factors from 39 journals, the most ever, because of academic misconduct. That idea that the current landscape cannot (always) be trusted can create some real opportunities.

Meeting Research Funder Requirements: RIOXX Application Profile and Guidelines, Paul Walk, EDINA & Balviar Notay, Jisc, Informatics Forum, G.07

Balviar: I wanted to start by giving you an update on RIOXX 2.0. We were hoping it would be released by June but we are awaiting NISO approval of the free-to-read and licence-ref. We now expect their recommendations towards the end of August or beginning of September. We don’t expect big changes but we want to wait until their recommendations are received. However we don’t want to wait to develop our plugin so we will be working on that – consulting with the DSpace and EPrints communities – and, after that approval, we will be testing with early adopters in October/November 2014. Just get in touch or respond to my post on the Jisc Scholarly Communications blog if you would like to be in that early adopter test group.

We will then, in December 2014 through to April 2015 we will be implementing RIOXX, and there will also be support around that implementation process. And that will allow data collection with the appropriate RIOXX fields to effectively support RCUK evidence-based reviews of the effectiveness and impact of their Open Access policy. Jisc Monitor will also benefit from this consistency of data. Unless you have consistency, it’s hard to build services on top. And this will also support institutions in early planning for REF OA compliance starting 1st April 2016.

If you Google “Jisc Scholarly Comms” you’ll find more on this and on the timeline for this work. And with that it’s over to Paul.

Paul: So I came in late to Yvonne’s talk, just in time to hear that it’s not just about compliance! Anyway…

As most of you have already heard something of RIOXX I’ll just summarise… it’s a metadata application profile intended to allow repositories to report on open access publications in a way which satisfies reporting requirements from RCUK and HEFCE. It’s a set of guidelines for repository implementation. And it has been developed by UKOLN and is now with myself and colleagues at EDINA. And this work has been funded by Jisc.

The original concerns of RIOXX was how to represent the funder for research. How to represent the project or grant. But also how to represent the persistent identifier of the item described, the provision of identifiers pointing to related dataset(s), and how to represent the rights of use of the item. And those concerns haven’t really changed.

We also had some original principles for RIOXX: that it be purpose driven – and focused on satisfying RCUK reporting requirements; Simple – relatively easy to implement; generic in scope – so not just about traditional publications; transient – a year or two ago there was a lot of interest in CERIF etc; interoperable – respecting other related standards that apply; developed openly – not just in closed mailing list, developed as much as possible with public consultation. So, what’s changed? Well it’s still about being purpose driven – for RCUK and also serves HEFCE requirements without deviation form the original remit; simple – slightly more complex than version 1 but still pretty simple; generic in scope – now gone, it needed to be specific, but that doesn’t mean we can’t conceive of parallel or more generic versions; transient – kind of gone as we talk about preparations for REF 2020; interoperable – still working with OpenAIRE, currently mapping the profiles to enable a crosswalk (in one direction); developed openly – yes, you can look on the RIOXX website, on my own blog, public discussions.

The other major change from version 1 to version 2 of RIOXX has been about implementing recommendations from the V4OA process. So, we have released a beta for public consultation in June 2014 – we had a great response including many of you in the room so thank you for that! Now version 2.0 RC 1 has been compiled, we are writing accompanying guidelines, and XSD schema has been developed.

So I just wanted to go through some of the elements of RIOXX. Firstly

dc:identifier

One of the things I’ve had to explain is that the profile, when it is expressed in an XML record, within that record the identifier identifies the OA item being described by the RIOXX metadata record (regardless of where it is). Recommended that it is the item itself – not the splash page. Whatever it is it must be an HTTP URI (a URL).

dc:relation and rioxxterms:version_of_record

rioxxterms:version_of_record is an HTTP URI which is a persistent identifier to the published version. Meanwhile dc:relation is a way to capture related items, to enable discovery of those.

dcterms:dateAccepted

This must be provided – it is one of the clearer defined dates and it acts as a trigger in a work flow. It’s much more precise than the date “published”. This is the most important date in RIOXX – we almost took out publication date but it’s still there, date of acceptance is the important one though.

rioxxterms:author and rioxxterms:contributors

Both of these accept an optional ID attribute, this must be an HTTP URI. Use of ORCID is strongly recommended. All authors should be represented as individual rioxxterms:author properties. The “first names author” can be indicated with another optional attribute: “first-named-author”. In a perfect world we’d have it work like a citation – possible – but data transfer in XML records can be rearranged hence the explicit attribute.

rioxxterms:contributors – is for all other contributors to the item.

rioxxterms:project

This now joins funder and project_id in one, slightly more complex, property. The use of funder IDs (DOIs in their HTTP URI form) from FundRef is recommended but other options are possible. For institutionally funded work you can use your institution’s ID, this is a free text field though so use the ID you have been given, or select something sensible. For multiple funders you simply repeat this element as many times as needed.

license_ref

This is from the NISO “Open Access Metadata and Indicators”. It is a simple element taking an HTTP URI and a start date. The URI should identify a license – there is work underway to create a “white list” of acceptable licenses. That will be a simple way to make data consistent – discussion going on with SHERPA and Jisc and HEFCE at the moment. The start date enables an expression of embargoes, with the date on which the license takes effect captured. All the business of interpreting licenses is out of scope – you just capture the information here.

So, in summary, we are close to release. Detailed guidelines are being drafted right now. The white list is being worked on. Jisc is funding work to develop plugins. And RIOXX has been taken up by HEFCE and RCUK so we have their support and engagement here.

Q&A

Q1: A quick question on implementation of RIOXX for CRIS systems. You mentioned DSpace and EPrints, but what about CRIS systems?

A1: I’ll leave the plugin question for Balvier. I did some work with the technical lead for CERIF, and she wrote up that discussion of how RIOXX could work for CERIF there. And the technical description for RIOXX allows you express it however you want to. My colleague Ian has created a schema for repositories but there is no reason it could not be used or developed for CRIS systems.

Balvier: We haven’t yet talked to CRIS vendors. But we know we do need to consider CRIS systems, to engage with the community. We are starting to have those conversations and looking at what needs to happen.

Q2: I did have one of those conversations with Balvier about RIOXX for CRIS systems, we’ve started the process with PURE here at Edinburgh and you can already harvest some data. But I had two questions: firstly about the corresponding author versus first named author.

A2: It’s my understanding is that it’s usually the same.

Q2: No, not always.

Comment: In biology it’s normally the last named author.

Comment: If you mean “lead author” then call it.

A: It was RCUK’s preference that it be “first named author” but the synonyms will be in the guidance.

Q2: So, my second question…why are items other than publications now out of scope?

A2: It’s to reflect RCUK needs, it has harmonised vocabularies. HEFCE are aware of that work…

Comment: We decided to focus on publications as we wanted this to be useful for the REF and many other types of items wouldn’t make sense in that RIOXX profile.

Q3: We have trouble tracking accepted or published dates sometimes so how can we go back and create RIOXX records for our publications?

A3: Another important element of RIOXX is that it isn’t in any sense retrospective – it’s not designed to do that. It’s designed to facilitate open access outputs for RCUK. It’s deliberately not a generic bibliographic record for open access publications

Q3: We can’t convert it?

A3: It’s open access, you’d be welcome too! But that wouldn’t be RIOXX, it would be something else.

Comment: I think this about taking RIOXX in the way it has been intended.

Paul: Yes, that’s a good point. RIOXX isn’t intended to be a standalone record – your repositories will have much richer metadata available. And it doesn’t make sense to subvert RIOXX to do that. By all means use the prior work in your own context. Only really useful if you are reporting back to RCUK or HEFCE – if that retrospective aspect becomes important then we need to consult again. But right now mandates don’t apply retrospectively.

Q4: Have you got the capability for more than one author ID?

A4: Not really. It’s not our problem in this thing to solve. We need a unique identifier for the author. If you have to map between multiple IDs thats a different problem.

Q4: So pick one based on funder requirements and prioritise?

A4: Yes.

Q5: I wonder about the issue of identifying publications. What motivates people and influences change. Impact and impact case studies have been important. How far do you have to focus your future spectacles to understand that we need a way to indicate impact in RIOXX? Is that in the future? Is it something RCUK have started to ask you about?

A5: I’ll give an answer but RCUK might have their own response. We have had these conversations but no focused piece of work in that record.

Comment: Right now our biggest problem is monitoring compliance with our open access policy, RIOXX will enable that in a significant way, but we also have other ways to monitor impact of research too.

Comment: That impact problem is being solved elsewhere. Taking a linked data view of that multiple ID issue, that idea of “sameAs” is doable elsewhere. So I think that we let that be solved elsewhere.

Paul: Yes, we ask for one ID, we let someone else make those decisions about which one.

Comment: Institutions are now minting ORCID IDs… if you are associated with more than one institution then you may have multiple ORCIDs and I guess that means it is up to the individual to resolve that – although it perhaps has all the makings of a potential car crash!

Comment: A similar issue to FigShare minting DOIs – can have two DOIs for the same publication.

Q6: You said that you would be interoperable with OpenAIRE, so if they adopt RIOXX will they be able to comply with OpenAIRE?

A6: Yes, that’s the intention. At the beginning of RIOXX we looked at OpenAIRE as an option for meeting funder requirements. But where funding is from the European Commission the use of OpenAIRE matters. It’s important. What we worked out is that if you produce a RIOXX record for an OA publication, funded by EU funding, then you can create an OpenAIRE record from your RIOXX record in a lossless way. I hestitate to say that you can forget about OpenAIRE BUT you can use RIOXX as a route to create OpenAIRE records. Jisc are talking to the Open University about doing this. But we are being careful that we haven’t put anything in RIOXX that might prevent us from doing this. But it won’t work the other way round – you can’t create a RIOXX record from an OpenAIRE record.

And now we return, after a lovely lunch, with two parallel sessions. In the library we have “Optimising resources to develop a strategic approach to Open Access (an OA Good Practice Pathfinder Project), Ellen Cole, Northumbria University”, whilst in the Informatics Forum – and on the blog – we have:

SHERPA Services Update (RoMEO, JULIET, FACT, Open DOAR), Bill Hubbard, University of Nottingham, Informatics Forum, G.07

My name is Bill Hubbard and I am based at the Centre for Research Communications, based at the University of Nottingham. And we have been running those for some 10 years now. And I will be talking about SHERPA services. Looking at the attendee list it’s great to see that a lot of you are practitioners with a really practical focus which will be great as we want to hear your views, your opinion.

To start things off, SHERPA services are currently majority funded by Jisc although we also have funding from others. And I’m going to start by showing some slides illustrating how what we do fits into the wider Jisc Repositories Shared Services Project – they are part of an integrated service within the UK, a cohesive support structure for the sector from Jisc.

So I will be talking a bit about what we do at the moment, the value proposition and benefits that we offer, and an example use case. We have three fundamental services and a service on top using our APIs – and others may be able to use those, I’ll suggest, for other innovative services.

RoMEO is the global service of authors’ rights for using repositories giving details journal by journal. It’s used by other services and some institutional repositories to embed permissions checking into the deposit process.

JULIET is a registry of policies on Open Access from research funders worldwide. Funders are actually trying to make policies clear and concise. JULIET lets you see the differences, to compare policies.

So if we combine RoMEO and JULIET we perhaps have a third thing…

OpenDOAR is the world’s authoritative and quality-assured directory of open access repositories. That is manually checked, thoroughy quality assured. And that’s work used by Jisc, at EDINA for the Jisc Publications Router. It’s useful for anyone trying to establish which repositories are where.

FACT is an end user service – advice to UK authors on compliance with funder’s policies in their journal of choice. It has been put together for academic projects. We inherited green and yellow colours to indicate publisher policies… Les asked our opening keynote what she would have done… If I’d known then… I would never have gone for green and gold! Until now I wouldn’t have given our other services for an author to look at… but it is designed for end users to be a simple system to use.

So, across these, we see our value proposition as being about these being services, and these are services with truly global reach. And I would thank you all for the feedback and suggestions and contributions that you have made. So we are global… but our funding is not global. Bit of tension there. For each of the three services we simplify information on repositories. We standardise. We put information into a standard set of descriptors. Thats a functional standard that we created and use. And we also summarise, to make it useful to you. We see that as having particular value. And each of our services have APIs – so that information is available to use on an open access basis, to be used in your institutional service or in other services.

So, we offer efficiency gains at sector level, we have single points of information, we provide quick access to policies and information, and we allow quick comparison of policies and information, and we are taking some of the pressure off the OA community – because these questions would be there anyway. And the feedback we get seems to back that up. But if you feel different, we’d love to hear your views.

At an operational level we maintain central datasets. We can compare between records. We can extract statistics. And we talk to publishers, to funders, to the OA community. And we can therefore see some of the places where tensions can arise, or where challenges or problem may be occurring. At a strategic level we see that we have a role in developing future OA support services. SHERPA services data used to prime systems.

We used the data from RoMEO and JULIET APIs to create the new SHERPA FACT in response to the RCUK requirements for open access. Those APIs made swift development of that possible. And you can also use our APIs to build things with our tools and data. Do let us know – we like to hear how they are being used – but they are there for you to use.

So these four services have four distinct groups of users. For FACT it’s for end users to check for compliance. For RoMEO and JULIET is can be used by repository managers. And we see OpenDOAR being used to understand the wider landscape. But that’s what we think… we know in the real world the users may be different, or the use cases may be different. For instance some RoMEO users use results as a starting point – heading off to look at the publishers own website for instance. So that’s a valid but different use case to what we initially envision.

But what about in the future? The world is changing. We have real momentum and it’s getting faster. To pick up on Yvonne’s point about revolution, I already see the tug of real change, a real people’s revolution. And certainly what I truly do believe is that this stuff has to be embedded in academic culture. It takes time, but it also takes official acceptance. Those revolutions that don’t get embedded, don’t become part of policy, through fudging and compromise, don’t actually take effect. You end up with idealogically messy situations. I’m really pleased with progress to date. I’m pleased with where we are and delighted with the RCUK and HEFCE policies as that’s real change and embedding. But we’ve always tried and wanted more people to engage. In some ways you could say that we’ve tried to engage with academics around OA on our terms, arguably we now have to engage with academics on OA on their terms. Funders are engaged, institutions are engaged, publishers are engaging… and that means changing working practices and processes.

So, how do our services respond?

It’s down to you. You have to use them and feed back on them in order for them to stay useful, relevant, and to prove their work. We’ve had lots of surveys, focus groups, a technical review, and our day to day feedback. But in this ever changing world we want to ask you whether what we do is what you want?

So, over to you. For instance likes and dislikes… take RoMEO…. and don’t be afraid to be critical! We’ll happily take criticism on board.

Comment 1: I find it very useful – along with all of the SHERPA services – are about the colours but also about the granularity… if between 12 and 18 months then I might need to go to the publishers website. And with SHERPA FACT you can see what kind of OA but not whether you need to pay for publication or not. There’s no way of seeing if it’s a green option.

A 1: So it tells you you can archive it, but not that you would have to pay for it. Perhaps you could send that comment to us too as my colleague has an encyclopedic knowedge

Comment 1: In general they are great though, not having to get to the publishers website is great.

A 1: Yes, finding information on publishers website is raised and we have raised it with them

Comment 2: I encourage my researchers to use RoMEO, and I use RoMEO all the time. But the colours are really confusing – they associate green RoMEO with green open access. I don’t look at colours, I read the terms, but the colours cause so much confusion.

Comment 3: With my funders hat on… if a journal is not compliant, is there usefulness in seeing what similar journals are compliant? Would that be good? Would that be an issue in terms of competition? Would that be too much?

A3:Really interesting. Lets see by show of hands… would that be useful? That looks like about a third of us think it would be, many fewer think it would not be.

Comment 4: As a librarian I’d find that useful. Academics probably do know the alternatives… may just be a frustration that their preferred journal isn’t compliant.

A4: What if alternatives were ranked by impact factors?

Comment 4: Depends on the credence you place in impact factors… ! I also had a question about how information is gathered for RoMEO… that sort of crowdsourcing model… do you think that works for maintaining accuracy and information? And as a corollary… there is a risk that combining information from different sources… are publishers likely/can they be interested in providing more information directly to RoMEO.

A4: Are publishers interested in making their terms and conditions clear? I’m not sure… BUT they would if there were commercial incentives. There is QA on RoMEO but it can be tough to get information back from publishers. And on your other question… we like that it’s a sort of quality controlled crowd sourcing. We do a lot of the work. If suggestions come in with a pointer to the right information, that’s fine, but sometimes a lot of work is involved. But I don’t see full QA and central updating as being realistic and scalable – another 3FTEs worth of work I suspect – so I don’t see that being workable.

Comment 5: I don’t use directly your services, so take this with a pinch of salt, but picking up on the compliance cycle… presumably the issue of related journals… the problem of understanding which journals are in which space would be useful to solve. That could almost be a key way in, especially into the publications process… with the other data an add on. And the other side of that… what happens if I publish in an non-compliant journal? Might be helpful to think about.

Comment 6: Speaking as a researcher… I’m aware that what I, and people like me, want from you is omniscient god-like-ness to make a judgement “yes” or “no”. But the real world is many levels of judgement, and confusion… and not helped by multiple conflicting statements from publishers and journals. And my local team making judgements… that may conflict with my judgement… And you said that magic word “crowd sourcing”… I would want to interpret statements multiple ways – that I can do X – and my librarian may disagree. There is a role for the community to filter up their decisions and their practice… that crowdsourcing element… rather than imposing a perception. Does that have any value?

A6: Yes, we can think of different ways about crowdsourcing, and it’s accuracy. RoMEO is about consistent interpretation… so we’d have to shift it to a different service so people understood where that information is coming from… that might take work away from us, which would be great. But it’s about a crowdsourced solution that the crowd thinks is right.

Another way to do this is to ask “why use RoMEO”? I think it’s because we don’t want to do something against copyright. If we can be assured that no-one will take action against us, if we knew publishers wouldn’t sue us…. would we need RoMEO? It seems important… but is it a defensive manoeuver. Are we driven by fear? By uncertainty?

Now we’ve talked about what you like, what you do. But how does it fit with what you need? Would you prefer all four services in one interface, say?

Comment 7: I tend to have a list in the repository in one window, the service in another, and copy and paste between. So if there was a way to give a list and say “check this”, that would be great. But yes, we do use RoMEO to check compliance. If we could do this all automatically in the repository that would be great…

A7: That may be an opportunity for using the API.

Comment 8: Picking up on the idea of a list of compliant journals, the publication lifecycle and workflow, in persuading academics to think about OA at the point of publication… That list is something I am asked for by academics. Often I have to get a list of relevant journals… and then I look them up. So a real time subject based system for decision making, that list of compliant journals, would be really useful. I did attend a SHERPA workshop and there was some support for that sort of idea there.

A8: We have thought about it, but it’s about implementation. But we will consider it.

Thank you to all of you for coming along. You can contact us with your feedback – we are on email and on Twitter – and we are at a crucial moment. We have support from key research players and we need to ensure we continue to meet your requirements.

And now we break into three strands: DSpace 4.0 Update from Claire Knowles, University of Edinburgh, in Appleton Tower M2B; Latest developments in Hydra-land from Chris Awre, University of Hull, in Appleton Tower M2C; and here in the Informatics Forum:

EPrints  Update, Les Carr, University of Southampton

Now, I wanted to start with this slide of how the web is changing things… an image of people in Somalia trying to get a phone signal. And here we see people viewing the world cup on a mac, in the middle of the desert. That is a huge impact on life. And I think we get frustrated that that impact doesn’t magically happen in academia… and those systems we have built in academia over the last 600 years have survived so solidly, through so many changes of government and culture… so changing them is really hard work. And the innovation we see elsewhere therefore isn’t so easy!

So, EPrints… we have been going for over ten years… we will be hitting the difficult teenage years soon! We used to talk about EPrints at Southampton, the Jisc Innovation projects, and the EPrints services. But everything is changing. Fewer Jisc projects. We are less connected to IT support. So now the focus is on EPrints Services, about providing services and hosting to repositories across the UK and across the world. And we’ve seen all sorts of mandates, policies, reporting coming in. And we see big data coming in, CRIS systems, innovation as key business. So how do we manage those as “insurmountable opportunities”.

So, if we look at a timeline here, from that call to action in 1994, we move on to open access, the projects, all the things we have been involved with at EPrints. So, in case you are wondering, here is the office where EPrints is based. We exist within the context of Southampton University. I’m academic lead for EPrints, part of the Web and Internet Science research group. And it falls within lots of areas of the university – it was one of the impact case studies in our REF return in fact.

Over the years we’ve had a lot of changes in the team. At the moment we are myself, John Darlington, Sheridan Brown, Adam Field – the business and community relations manager, Kelly Terrell, Justin Bradley, Jiadi Yao, Will Fyson, Nawar Halabi. Lots of change. Our technical lead Seb is about to join Tate Digital as their chief information architect.

So, what are we doing? We host 70 repositories. We support open access repositories for about 100 institutions. We are not for profit and much more about the impact of our work, about our belief in open access.

In terms of recent and future developments.. IRStats 2 v1.0 is released. We have EPrints4 developments. And we are trying to think about what the repository will be in 2016. And, basically, we’ve hear you. We are looking at scalabilty issues (browse pages in particular); search is not always accurate; limited UI interactions; E{rints3 built from many blocks – so it’s time to refactor and improve it, and really improve the engineering; and lots of new domains.

So we are trying to find the path to the actual repositories, the business requirements, of their repositories. Whether to report on open access, to improve marketing and knowledge presence on the web. So how do we take what we have, and make sure it’s what people want. So, what is EPrints for? Well it’s for research content – publication, educational resources, scientific data; research business – research management, research processes, research impact; and the research activity – data collection, and data analysis. It is NOT a graveyard for the end of projects, it is part of living activity. It’s to support researchers, research data, research outputs, research outcomes and impact, and your librarians.

So, what is EPrints 4?

Well it’s for open access, publications repositories, research reporting. There is a bigger agenda for librarians, information management and for curation. It’s not about creating a fantastic shiny new repository. We believe there is a lot in EPrints. We need to tune it for speed, efficiency, scale and flexibility. We had EPrints analysed… and printed on a 3D printer… enables you to see where the software is not optimised, where it’s too blocky. We had lots of help from those visiting colleagues.

So, over the last 9 months we’ve written some 11,000 lines of code. Search is essential as is reporting. We’ve improved integration with Xapian, DB transactions, memcached, fine-grained ACLs. So we’ve been doing lots of improvement work here. You can use EPrints with a UI, but we think its much better with one.

Thinking towards Repository ’16. All the issues of trying to report to funders, to government, in order to share services, SHERPA etc. This is all really important to us. We’ve been working with a number of institutions and with Jisc – so we want to ensure that these (e.g. Gateway to Research) are in place for everyone in EPrints in the UK. IRUS-UK is on Bazaar, Publications Router is native to EPrints (SWORD) and importers on Bazaar, ORCID – proof of concept on Bazaar, etc. And we’ve been breaking down some of that division between repositories and CRIS systems.

As a piece of technology repositories are not a thing, but a performance… it’s librarians and developers and researchers hand-in-hand changing the environment in which they work. And becoming more sophisticated. We hope the environment has improved in the last 10-12 years. It’s not just about enforcing historic norms but also stimulating new practices to emerge – around copyright and openness and intellectual property, and privacy, and creativity, and Science 2.0. Helping academics adapt to a changing world around them.

So, where do we see ourselves in that… we want to be in the big bright shiny future. We want to support you in all the things that your institution is trying to do.

Q&A

Q1: An easy question: what is the easiest way to tell EPrints about questions or concerns?

A1: We’ve been trying to answer that question… part of our answer is Adam’s new role. But we also try to talk to people, to ask them what they think and want whenever we are out and about. What would you want to ask me?

Q1: Nothing right now but historically really… is there somewhere central to log this stuff?

A1: That is where Adam’s role to sit. But we need to know what businesses, what institutions need.

Comment 2: Surely user groups are the way to do that?

A2: There is a UK EPrints user group and the last meeting was in Leeds. Maybe ULCC next. We will support that and come along whenever we can. We wanted that to be community led, but we want to come along, taking notes etc.

Comment 2: But Adam will be there for that.

Comment 3: But user groups or user support in particular really important for reporting issues and requesting developments. I’d like a case number and details when I submit a question. Everyone is lovely but I want more organisation and strategic support there.

A3: In the university this stuff just grew up. Kelly has come from the NHS and she will be doing this project management stuff, ensuring we are being more organised and structured.

Comment 4: EPrints is on GitHub, can track issues there.

A4: Great for developers… but only that part of the community. We need other routes for other parts of the community.

COmment 5: You need a helpdesk, a way for ordinary stuff to be resolved quickly, to track queries.

A5: Adam’s role is going to be about this. We haven’t had an organised way to do that before. That’s part of reorganising our team at the moment.

Comment 6: Can you offer training for someone like me – I’ve worked on 5 repositories before but there is still basic stuff I can’t do on EPrints.

A6: We do have regular training activities. I’d have to check what’s happening and get back to you but you’d be welcome to attend those.

Comment 6: It’s tiny things. I feel silly emailing about them, I’d like to learn to do it myself.

A6: I’ll take your details and we can work on that.

Q7: When will EPrints 4 coming out?

A7: We don’t have a date, but probably about a year away.

And, after a lovely coffee and cake break…

Implementing Open Access at University of Bournemouth and University College London, Jean Harris, Informatics Forum, G.07

I work in both University of Bournemouth and University College London – hence the two hats! So I’m going to talk to you about my experience at these two hugely different university. UCL is a Russell Group universiy, it has 28,000+ students, about half UG, half PG. And total research funding is £871m (2011/12). Meanwhile Bournemouth has 17000+ students, many more UG than PG with teaching as central as research.

Both universities undertake publications management. Both use Symplectic Elements to manage publications and EPrints for IR. At UCL library manages OA funding and publications through the Research Publications Service (RPS) and Discovery (EPrints). At Bouremouth the Research and Knowledge Exchange Office managed OA funding and BRIAN (Bournemouth Research Information And Networking), but also BURO (EPrints) is managed by the library. UCL Discovery (EPrints) is supported inhouse (which means we are not always at the head of the queue) vs. BURO which is a hosted service with support from the EPrints Service.

For those without Publications Managerment it’s sold as a one stop shop – connecting up repository and public facing profile pages. Bournemouth is a full text only service. In UCL it’s a mixed picture with very mixed quality metadata. Both have very patchy metadata on individuals and their profiles.

UCL is metadata only and full text outputs, There are over 317,000 total outputs. In terms of open access there are over 16,000 Full text (green and gold) items. Live gold without full text are around 6327 items. And includes Theses – 2814 live full text plus 230 embargoed out of 5111. Bournemouth is full text but not all open access – some items stored there for the REF only.

At UCL there is a virtual open access team – gold has a manager and three staff, green has a manager plus 3.27 staff (I’m the 0.27!) – they mainly work on Theses work, and we have 1 member of UCL press – they have just taken the imprint back and aim to make everything available through UCL Discovery and publishers for eBooks. At BU there is OA funding – RKE 1 Manager and admin support for processing. We have no full time repository staff. There is a rota of 3 editorial staff working one work in three on outputs, a 0.2 manager, and me (0.2).

Funding for OA is also quite different, UCL are funded by RCUK, UCL and Wellcome. UCL’s funded OA compliance for RCUK is 115%. UCL have pre payment agreements with a great number of journals – an agreement with Elsevier has saved a huge amount of time and money. BU funded OA statistics – the budget is what researchers bring in plus 100,000 from BU. There are far fewer articles here. But both BU and UCL have had some challenges spending their money – UCL has done some retro conversion for instance.

In terms of challenges for engagement… UCL Discovery includes metadata only outputs – and only full texts get checked by staff, academic engagement has been a challenge – many staff were used to having things done for them so it took a lot of training and coaching to get them through even with the large stick of the REF, and there can be difficulty sending large files – they have to use dropbox and/or break up files, they are furious about how h index is calculated in RPS, they don’t understand searching and filtering for RPS – crashed whole system with a common name and single common keyword searching of PubMed for instance. BU-Buro moved in 2013 to full text only. We have some mapping data issues. Incorrect publications no longer appear in staff profiles, and there is some confusion about where the repository is located – because it has moved.

In terms of challenges for OA. A new statement has reiterated UCL’s commitment to OA, but it will be hard to move academics to this place. We need them to understand versioning, to understand that they have academic freedom in terms of where to publish – but they still have to comply with OA requirements. And we have to get them to deal with multiple entries. And there is an issue of sheer volume – UCL staff can be overwhelmed as there is such a drive there. For BU there is advocacy. Academic freedom is less of an issue… plus academics are more used to manual entry of metadata but there remain concerns about being scooped! And publishing timelines can be an issue.

For both organisations there are challenges  of deposit on acceptance, the range of OA options, establishing new workflows, moving goalposts, flexible support – workshops aren’t enough so you really need one-to-one support sessions, encouraging champions in faculties – to get them to engage with the repository. And we want to use REF2020 as a stick, but also as a carrot for their research. UCL is one of the new Jisc Pathfinder projects too.

But what happens when the money runs out?

At UCL the university as a whole supports Green OA but assists academics to meet their requirements through the gold route.

Q1: How do you comply 115%?

A1: By publishing more articles than they are required to. They are very proud of it.

Q2: In terms of dealing with Symplectic – how is deduplication of different data from different platforms dealt with?

A2: They don’t yet, we’ve called for it – through suggesting corrections etc. Sometimes there can be four matching/correct entries. You can join these in Symplectic but most people don’t notice or care about that. People don’t notice that duplication. So that’s a user workflow thing. The feed goes into the pending file… you get a message from IT services… and you then go and approve (or not) those items. It’s not really engaging them. You get a choice of options, if a manual entry from library staff that takes priority in the repository itself. You want to bring it all together, and validate that, giving the best record. Symplectic gives you best choice but that’s not ideal. But new version is coming out which will help with deduplication. But we’ve yet to see how that is decided. But it will help us – we’ll be able to see the full text attached.

Glasgow Led Jisc Open Access Project – End-to-End Open Access Process Review and Improvements, Valerie McCutcheon, University of Glasgow, Informatics Forum, G.07

I’ve worked at Glasgow University for the last 12 years, and for the last few years I’ve been working on research and open access. Two years ago we linked the repository to the research system so funders could see the outputs. I had been working in research outcomes, so really interesting to work with the repositories. But I’m here to talk about the Glasgow led Jisc Open Access Project which is a collaborative project with a number of partners including EPrints. We are a really varied group. From big organisations (with lots of publications) – Glasgow and Southampton – to wee ones like Lancaster or Kent. Some are in the north, some in the south. Some have EPrints out of the box, some have complex set ups with loads of customisations.

So, who else is involved? Well the Association for Research Managers and Administrators – we try to engage and join up with them. We don’t want to reinvent the wheel. We work with the EPrints User Group as well as other appropriate user groups. We speak to SCONUL, RLUK, and UK Council of Research Repositories. Really everyone. We want you to be involved, to engage, to collaborate and share!

So, what are we doing that is “special”? Well we are manifesting standard new open access metadata profile – an EPrints case study (generic, just happens to be EPrints), Hydra case study; EPrings OA reporting functionality; EPrints improved award linkage functionality. Some organisations have awards in their systems, others doing it manually or looking at how to do it soon. So we have proposed a number of generic workshops. An early stage workshop on issue identification and solution sharing – of use to our project but also to other Pathfinder projects. We also want to do a workshop, probably in November or December, on embedding future REF requirements – and we’ll collaborate and reuse (not repeat) with other Pathfinder workshops. We may also run a workshop on advocacy and as we reach the end of the project we will run a workshop to disseminate and share.

Are we duplicating standards? Well there is a Consortia Advancing Standards in Research Information Management (CASRAI-UK) bringing together standards and ideas, bringing them together and sharing. We will use output from RIOXX to feed into what we do, to implement it. We will use the V4OA work. And there is also NISO which is also looking at standards, and will take some of the appropriate standards from there. So we will be using one big spec that enables everything institutions need for research information management.

Right now we have a big spreadsheet of metadata – looking for concensus on what’s required for that basic specification for the EPrints software community. What I should mention is that we are very much focusing on what we want, not how it is delivered – that’s for the developers to think about. So that spreadsheet includes comments from the community, questions for us to answer. Things to be clarified from RIOXX, from HEFCE, etc. So, for instance, we have entries on date of article acceptance, on information on EU funding, etc.

We also have the APC finance workflow here – we are looking across workflows, to see what happens, why, to understand how our work can fit into those workflows and processes.

So, we have a workshop on 4th September on current initiatives on Open Access, and particularly on the Metadata. etc. Come along!

And we are part of these Pathfinder projects – there are a number of us and, to borrow a statement in a non-political way, we are “better together” – we need to work together, to collaborate, to share experience.

Q&A

Q1: You mentioned V4OA and CASRAI – do you have a sense of how they will work together?

A1: My impression is that we are synthesising these with RIOXX, to make sense of them all…

Comment from Balvier: In terms of V4OA, specific elements of vocabularies we all work on… APCs, embargoes, etc. are those types of terms. They were intended to be part of other information systems, including RIOXX. In terms of CASRAI it was about agreeing particular vocabularies – e.g. “organisational identifiers”. There isn’t overlap, they are distinct areas.

A1: So it can be synthesised and made coherent.

Lessons in Open Access Compliance in Higher Education (LOCH), Dominic Tate, University of Edinburgh, Informatics Forum, G.07

I’m aware that we are on the last leg of the day, so I will move through this quite swiftly. This project, LOCH, is another Pathfinder project. It is led by University of Edinburgh – a large research led Russell Group university – with Heriot Watt University (research led but business and industry focused), and with St Andrews University – the oldest university in Scotland, much smaller size. We all work together through the Scottish Digital Library Consortium (SDLC) and use PURE and some other common systems.

So, we are looking at managing open access payments – including a review of current reporting methods and creation of sharable spreadsheet templates for reporting to funders. The second strand is about using PURE as a tool to manage Open Access compliance, verification and reporting – we are all very active members of the PURE UK user group and are feeding in new requirements. Finally we will be adapting institutional workflows to pre-empt Open Access requirements and make compliance as seamless as possible for academics.

We are already working on a functional specification for PURE, we will then be looking at publishing workflows, and we have 6 case studies expected, three webinars, three workshop events, minimum of 24 blog posts, pilot services and workflows. And we will be disseminating through conferences, journal articles, etc.

Q1: Will you be working to current or forthcoming policies? They are putting RDM etc. for REF 2016… is that realistic?

A1: We are concentrating on existing policies and requirements. The “extra credit” bit isn’t known yet so not appropriate to focus on that yet. We have someone working with the project, from Elsevier, who really understands those upcoming changes. In terms of those additional requirements it will happen, the user group is an important part of that. If you look at the last REF Elsevier did develop stuff to meet the requirements.

The Mechanical Curator, Ben O’Steen, British Library, Informatics Forum, G.07

World Premiere: Open Access in Scotland

Dominic: Unfortunately Ben O’Steen is ill and cannot be here, however any questions about his project, The Mechanical Curator, can be asked of Steph Taylor who is here. Anyway, Like a rubbish substitute teacher, I’m going to show you a video. This is a world premiere. This was put together by my colleagues and some outside filmmakers, and this has been funded by Jisc. We wanted a video for use in advocacy. We went to universities across the UK, spoke to repository managers and maybe didn’t get the views we expected. We didn’t want this to be some sort of North Korean propaganda movie so there is a mixture of views.

And now we are watching Open Access in Scotland (which was super).

An A-Z of RDM (Song), Robin Burgess, Glasgow School of Art, Informatics Forum Atrium

Robin has based this song on two projects – one focused on capturing research data, one working with early career researchers on research data management. And I dedicate this to my manager Nicola Simonson.

And with that, a lovely a capella version of Robin’s A-Z of RDM, we conclude for the day with drinks, networking, and – if participants have read Edinburgh’s weather report for the next few days – a rare opportunity to enjoy a beautiful sunny evening! We will be back on the live blog tomorrow morning, see you then!