All 3 entries tagged Sherpa Romeo
No other Warwick Blogs use the tag Sherpa Romeo on entries | View entries tagged Sherpa Romeo at Technorati | There are no images tagged Sherpa Romeo on this blog
August 09, 2011
Writing about web page http://www.rsp.ac.uk/events/romeo-for-publishers/
Thankfully I'm new enough to the whole repository busy that I've never had to try to manage or populate an open access repository without the help of SHERPA's RoMEO service and I hope I'll never have to try! So an event presenting a number of new developments and the chance to engage with Publishers representatives was too good to miss out on!
The event itself gave two really clear messages: we are all on the same side and clarity is everything. The clarity message was raised again and again, all the various players in this community need clarity and consistency in who says what, what means what and what we can do with what (to badly paraphrase Bill Hubbard). Another message that came from both RoMEO and representatives of the Repository community (Enlighten Team Leader Marie Cairney) was that at the end of the day, as much as we care about Open Access, we don't mind being told 'no' as long as it's clear that that is what you are saying.
Some highlights from the sessions:
- "Change is coming" was the title of the latter part of Bill Hubbard's (Centre for Research Communication) presentation and highlighted the many areas (peer-review, end of the Big-Deal (?), social research tools (Mendeley etc.), demands for free access, cross-discipline research, possibility of institutions taking more control of the intellectual property produced by the institution and more) where we might be seeing change that affect the way we work in the next ten years. No doubt there will be others we haven't thought of yet.
- Azhar Hussain (SHERPA Services) continued the theme of opportunity by highlighting some interesting statistics for RoMEO. The service currently stands at 998 publishers covering 18,000+ journals and bringing in nearly 20,000 visits a month. Also highlighted was the growth of usage from within CRIS systems, something RoMEO is tracking closely.
- Mark Simon from Maney Publishing spoke about the reasons behind the companies decision to 'go green' as well as highlighting the fact that for Maney, as they broadly publish for learned societies, the copyright of published work often does not rest with Maney itself, but with the Society. Mark also highlighted the cost of their 'Gold OA' options (STM journals $2000, Humanities journals $800, Some tropical medicine journals $500) stating that the cost disparity was due to the cost of STM journals to produce and the fact that more people want to publish in STM journals.
- Marie Cairney (Enlighten, Glasgow University) spoke about some of the recent developments to Enlighten, including using the 'Supportworks' software to better track enquiries and embargoes. She also highlighted the changes to publisher policies over the years that have caused problems for her team, most of us can guess which ones she mentioned! Marie's final message was that the more clarity we can get on policy matters, the more deposits we can get.
- Jane Smith (SHERPA Services) spoke on a similar subject and touched on many of the common pitfalls that can occur when contacting Publishers to clarify policy. These included, no online policy, no single point of contact, two contradictory responses from different parts of the company and more. Jane ended with a plea for the publishers to let RoMEO know when their policy changes so they can get the information out as quickly as possible and for copyright agreements/policies to be written in clear English.
- Emily Hall from Emerald was up next. One point clearly highlighted from the outset was that Emerald was a 'green' publisher (it couldn't really have been any other colour!). Emily also spoke about the decision not to offer 'Gold OA' options (not felt to be good for the publisher or work for the discipline they mostly publish) and touched on issues with filesharing. (Trivia: Emerald's most pirated book 'Airport Design and Control 2nd Ed.') Emily did mention that Emerald haven't been able to 'see' the content in Mendeley (as of this morning listing more than 100 million papers) yet but they are looking for a way to do this. One thing that came out of the discussion at the end of the talk was an idea for publishers to return versions to authors with coversheets clearly indicating what they can and can't do with that version.
- Peter Millington (SHERPA Services) finished the presentations with a demonstration of a new policy creator tool developed to be used with RoMEO. This tool, based on the repositories policy tool created as part of the OpenDOAR suite of tools, would allow publishers to codify their policies into standardised language as a way of helping people to read and understand the policy of their publisher/journal. I for one hope publisher's start using this tool as standard. The prototype version of the tool is available now and can be found here.
The breakout session that followed the presentations asked us to consider four questions (and some of our answers):
- How can RoMEO help Publishers? (Track changes to policy, Visual flag for publishers to use on their websites to indicate the 'colour' of the journal, act as a central broker for enquiries so one service has a direct contact to the publisher that can be accessed by all creating a RoMEO Knowledge Base of all the enquiries for all repositories to use)
- How can Publishers help RoMEO? (Nominate a single point of contact, create a page for Repository Staff similar to their pages for 'Librarians', ways to identify academics (see previous blog post), clarity of policy)
- What message do Publishers have for Repository Administrators? (Thank you for the work done checking copyrights, don't be scared to talk to us, always reference and link back to the published item.)
- What message do Repository Administrators have for Publishers? (Clarity (please!), make it clear what is OA content on your website, educate individuals on copyright, communicate with us!)
A full run down of the answers to those four questions can be found at the link above.
The final panel discussion raised interesting questions that we didn't really find answers for! Issues on multimedia items in the repository; including datasets in the repository or finding ways to link the dataset repository to an outputs repository - DOI's for datasets (see the British Library's project on this topic); and the matter of what to do in the case of corrects and/or retractions being issued by publishers. The last one at least gave me some food for thought!
The event was another valuable day from the RSP featuring lively discussions on current situations and challenges facing the repository community and an invaluable opportunity to meet and have frank discussion with the Publishing Industry representatives. I think both groups got a lot out of the day along with the realisation that we have a lot more in common than might seem obvious at first glance.
February 23, 2010
Last Friday I was at the UKCoRR members' meeting. As their Chair, I reported on my activities and announced speakers. As a repository manager, I learnt a lot from the other participants.
Louise Jones introduced the day, as the University of Leicester library were our hosts. They have recently appointed a Bibliometrician at Leicester and they're acquiring a CRIS to work alongside their repository. They have a mandate for deposit and Gareth Johnson's presentation later in the day about the repository at Leicester mentioned that they have more than enough work coming in, without the need for advocacy work to drum up deposits. I guess that the CRIS will come in handy for measuring compliance with the mandate!
Gareth's presentation also included some nice pie charts showing what's in their repository by type, and what's most used from the repository, by type and then again by "college" (their college is like a faculty). Apparently he had to hand-count the statistics for the graphs... well done Gareth!
Nicky Cashman spoke about her work at Aberystwyth and I found it interesting that one of their departments' research projects on genealogy has hundreds of scanned images of paper family trees that they are looking for a home for, at the end of their project. They don't require a database to be built around their data as they already built one, and they want to link from it to the scanned images. This sounds like a great example of the kind of work that the library/repository can do to support researchers with their research data. The problem is, though, that in order to host that kind of material in a repository there will be substantial costs, (cataloguing each item, storing it and preserving it) and these costs perhaps ought to have been included in the original research bid. Researchers ought to be thinking about such homes for their data at the beginning of their projects, rather than at the end.
Nick Sheppard spoke about his work on Bibliosight and using the data provided through Web of Science's Web Services. There was some discussion about the fact that you can't get the abstract out of WoS because they don't own the copyright in it in order to grant that we might use it...
Jane Smith of Sherpa demostrated some of the newer and more advanced features of RoMEO. I think that the list of publishers who comply with each funders' mandate is something that might be of use to researchers looking to get published. Also, the FAQs might be useful for new users of RoMEO.
I would like to see the Sherpa list of publishers who allow final version deposit enhanced to include which of them will allow author affiliation searching as well, so that we can find our authors' articles in final versions and put them into the repository. And another column to say whether the final versions are already available on open access or not, because I'd prioritise those not already available on open access.
One development that has been considered for SherpaRoMEO is that it should list the repository deposit policy at journal title level, because publishers often have different terms for different titles. However, in trying to develop such a tool, it has transpired that one journal might appear to have many copyright rights owners, when looking at the different sources of information about journal publishers. For instance, the society or the publisher who acts on their behalf might each claim the rights and each have different policies. Which rights owner's policy ought SherpaRoMEO to display?
Hannah Payne spoke about the Welsh Repository Network who have a Google custom search for all the welsh repositories which I like but would wish to see a more powerful cross-searching interface, and in the afternoon we did a copyright workshop that had also been run at one of the WRN events.
So there is plenty I can take away from the day.
March 06, 2009
The SherpaRomeo tool is great and I know that there are some development plans in the offing. Here are my thoughts on what would make a real difference!
1) Publishers don't keep Sherpa up to date about changes in their policies... or even their policy in the first place. Wouldn't it be great if all publishers kept us all informed through Sherpa? Some publishers are better than others, of course!
2) Sherpa don't attempt to include detailed publisher statement texts. These vary more often than the policies themselves, so it is sensible of Sherpa to link us to publisher websites. I don't think there's much that Sherpa can do on this score.
3) Data at the level of each journal title: this is even more complex to manage and maintain than the publishers' policies, so its entirely understandable why Sherpa haven't attempted to do this. It is irritating to find out the publishers' policy on Sherpa and then have to double check which collection the journal title is a part of, to see how long the embargo period is. It is doubly irritating to find the general policy on SherpaRomeo which allows repository deposit, but when you check the publisher's website and then finally find the actual journal's copyright information page, you find that this title is an exception to the general policy!
Policy variations at individual journal title level mean that we have to do checks anyway. Again, I think that this is not so much a weakness of SherpaRomeo as of the data they are presenting to us...
4) It would be great if Sherpa could track previous publisher policies for each journal title: titles change hands between publishers and publishers change policies. Being able to check the policy at journal title level, and for a specific year/date would be a real benefit if we are trying to be as accurate as possible in what we allow into the repository.
Of course, none of this would be quite as necessary if our authors kept copies of the agreements that they signed and submitted those along with their articles. Then we could refer to the actual source, and at the same time drive home the importance of the copyright agreement to our authors. But it's hard enough to get them to submit even the paper, never mind the copyright agreement as well... :-)