Tuesday, 3 April 2012
UKCoRR Responds to RCUK's Revised Policy on Open Access
----
UKCoRR, on behalf of its membership, wishes to respond to the RCUK’s proposed policy on access to research outputs, given that it is an area that directly impacts on the activities of our 250+ members across the UK’s research establishments.
At the outset, UKCoRR would like to commend the RCUK for a very clear, positive and explicit statement. In particular the restriction of support for embargoes longer than 6 months post-publication (12 for AHRC and ESRC funded work). UKCoRR are also delighted to note the tone of the policy in favouring more Open Access friendly journals and publishers for RCUK funded research outputs.
There are, however, several issues, concerns and clarifications that our membership would like us to flag up for your attention and consideration.
Definition of Open Access
UKCoRR would query the definition of Open Access to scholarly publications as digital journal articles. "The Research Councils define Open Access to mean unrestricted, on-line access to peer reviewed and published scholarly research papers." [p2] and likewise your classification of books or monographs as “grey’ literature” [p3]. There are many other types of authoritative research output besides pdfs of journal articles, especially in arts and humanities research. It is our belief that the OA movement needs to lobby for access to all research outputs, and that there is a need to ensure that RCUK’s policy does not exclude this significant portion of the scholarly literature. The contents of our members’ Open Access repositories clearly demonstrate the richness, value and readership of such scholarly works.
Creative Commons
The CC licence is a potentially contentious issue [p2] and one that UKCoRR believes may create more problems than it solves.
The current model of Green OA (i.e. self-archiving in an IR) as opposed to Gold (i.e. author-institution pays), is predicated on a pragmatic negotiation of copyright with academic publishers and, along with high profile initiatives like SHERPA RoMEO, has encouraged growth of the number of RoMEO green journals which allow self archiving, and therefore in the potential number of OA papers that can be self-archived in repositories. UKCoRR is concerned that the new policy will potentially impact on this strategy, and on repositories which will have to assert CC-BY on relevant papers after a maximum embargo period of 6 months.
It is not clear what effect the policy may have on journals defined as ‘green’ by SHERPA RoMEO and on the application of embargoes. Journals may choose to become RCUK-compliant, to remain RoMEO green but not compliant, or to reject green and compliance altogether with individual publishers’ policy likely to be informed by the potential loss of revenue resulting from a universal 6 month embargo and by the extent to which other funders will follow RCUK's lead on CC-BY.
HE institutions are increasingly adopting policies on OA and self-archiving in their repositories and UKCoRR has some concerns that the policy should more explicitly consider implications to this Green route to Open Access
Limitation on Publication Destination
While UKCoRR acknowledges the value of this part of the policy, we note that it is likely to cause anxiety among academic stakeholders unless backed up by clear support mechanisms. If our members’ author stakeholders are made to feel more constrained on their choice of where to publish [p3] it could generate an adverse perception and consequent resistance towards the implementation of Open Access policies within their organisation; already an issue that many of our members encounter in the course of their work. However, we look forward with interest to the impact this may have on those publishers who to date have been reluctant to embrace more Open Access compliant author copyright licence agreements.
Impact on Publisher Policy
The policy would require a significant change in many publishers’ policies, and would limit the choice of journals to those that are recognised as compliant. Sources of funding for Open Access compliance will therefore become a more pressing issue across many institutions, where few currently have resources set aside to cope with such moves [p5]. We would encourage RCUK to be more proactive in ensuring that all researchers, especially PIs, and research administrators are made fully aware that this is part of the indirect costs allocated within the grant application and award. Clarity on RCUK’s stance in this regard would be especially welcomed by our membership.
Access to Data Outputs
The final paragraph in section 8 says "The underlying research materials do not necessarily have to be made Open Access" [p6]. While UKCoRR understands that mandating open data publication is out of the scope of this policy, we would welcome an approach that encourages this. There is an opportunity here to get more open data for use and reuse by the research community while respecting the normal provisos about commercial sensitivity, patient confidentiality etc.
Compliance Mechanisms
Our membership would also be interested in knowing more about how the “mechanisms to help ensure compliance” will operate [p6]. Given the time scales and workloads already placed upon our members, greater clarity in this regard and at the earliest opportunity will make such mechanisms more practicable for us to implement.
OA Fields and ROS
Given the timing of this, we would also query the lack of proper OA fields built in to the recently launched Research Outcomes System (ROS). There are fields for SHERPA/RoMEO data and preprint/postprint, but nothing to clarify if an OA version actually exists. While we are aware of discussions ongoing with the JISC that UKCoRR has also been party to, we would welcome this being highlighted in the policy.
Final Comments
Overall, as strong advocates of the cultural, economic and intellectual benefits of Open Access to the UK’s unique research outputs UKCoRR keenly supports this bold policy.
We welcome any opportunity to enter into a dialogue with the RCUK as to how this could be cascaded, both to our membership and our academic stakeholders.
Thursday, 22 March 2012
Are your repository policies worth the HTML they are written in?
Not to put too fine a point on it, I think Owen has identified issues that are fundamental to the potential value of our repository infrastructure in UK HE, at least in terms of responsible 3rd parties building services on top of that infrastructure - though Owen also asks in the title of his post "What does Google do?" for which the short answer is that it indexes (harvests) metadata and full text for (arguably) commercial re-use unless asked not to by robot.txt. This is not necessarily to suggest that Google is irresponsible, it may well be but that is a rather bigger discussion!
For CORE, by comparison, it has understandably been important to establish individual repository policy on re-use of metadata and full text content; where such policies exist at all they are invariably designed to be human readable rather than machine readable which is obviously is not conducive to automated harvest, in spite of guidance being available on how to handle both record, set and repository level rights statements in OAI-PMH from http://www.openarchives.org/OAI/2.0/guidelines-rights.htm.
To quote Owen in his review of policies listed in OpenDOAR he found that "Looking at the 'metadata' policy summaries that OpenDOAR has recorded for these 125 repositories the majority (57) say "Metadata re-use policy explicitly undefined" which seems to sometimes mean OpenDOAR doesn't have a record of a metadata re-use policy, and sometimes seems to mean that OpenDOAR knows that there is no explicit metadata re-use policy defined by the repository. Of the remaining repositories, for a large proportion (47) OpenDOAR records "Metadata re-use permitted for not-for-profit purposes", and for a further 18 "Commercial metadata re-use permitted"."
It might be suggested that machine-readability is actually secondary to what is potentially misconceived policy in the first place - or which hasn't perhaps been fully thought through and at the very least is fatally fragmented across the sector - and that arguably is the result of lip-service rather than based on what actually happens in the real (virtual) world.
For my own part, in my institutional role, I was very, er, green (no pun intended) when I defined our repository policies back in 2008 using the OpenDOAR policy creation toolkit - http://www.opendoar.org/tools/en/policies.php - and to be frank I haven't really revisited them since. I suspect I'm not terribly unusual. To quote Owen once more, "the situation is even less clear for fulltext content than it is for metadata. OpenDOAR lists 54 repositories with the policy summary "Full data item policies explicitly undefined", but after that the next most common (29 repositories) policy summary (as recorded by OpenDOAR) is "Rights vary for the re-use of full data items" - more on this in a moment. OpenDOAR records "Re-use of full data items permitted for not-for-profit purposes" for a further 20 repositories, and then (of particularly interest for CORE) 16 repositories as "Harvesting full data items by robots prohibited".
The (reasonably unrestrictive) metadata and full-text policies I chose at Leeds Metropolitan University state that "the metadata may be re-used in any medium without prior permission for not-for-profit purposes and re-sold commercially provided the OAI Identifier or a link to the original metadata record are given" and "copies of full items generally can be reproduced, displayed or performed, and given to third parties in any format or medium for personal research or study, educational, or not-for-profit purposes without prior permission or charge". Even this, with the word "generally" implicitly recognises the fact that there may be different restrictions that apply to different items which to some extent reflects the complexity of negotiating copyright for green OA, not to mention the other types of records that repositories may hold (e.g. our repository also comprises a collection of Open Educational Resources [OER] which are in fact licensed at the record level with a Creative Commons URI in dc:rights as in this example - http://repository-intralibrary.leedsmet.ac.uk/IntraLibrary-OAI?verb=GetRecord&identifier=oai:com.intralibrary.leedsmet:2711&metadataPrefix=oai_dc)
Nor are my policies available in a machine readable form (which as we've established is typical across the sector) and I'm not actually sure how this could even be achieved without applying a standard license like Creative Commons?
Owen goes on to consider "What does Google do?", if you haven't already it's certainly worth reading the post in full but he concludes that "Google, Google Scholar, and other web search engines do not rely on the repository specific mechanisms to index their content, and do not take any notice of repository policies". Indeed, I think in common with many repository managers, I devote a lot of time and effort on SEO to ensure my repository is effectively indexed by Google et al and that full-text content can be discovered by these global search engines...which seems somewhat perverse when our own parochial mechanisms and fragmented institutional policies make it so difficult to build effective services of our own.
Tuesday, 6 March 2012
The Unfulfilled Promise of Aggregating Institutional Repository Content (Guest Post)
----
Monday, 27 February 2012
The COAR Question
There are a number of obstacles to membership in our way - not least of which is the question of how as a lightweight unfunded organisation we would afford to pay the annual membership fee. There are also broader policy questions about whether membership of COAR would be in the best interests of UKCoRR's long term Independence of action, policy and governance. You only have to glance at the recent announcements from us both on the Elsevier question to see that while the two groups have for the most part allied goals that we are likely to come from two different angles on some issues.
COAR is an organisational membership body funded by subscriptions pushing ahead the interests of open access and repositories. UKCoRR is a individual membership organisation unfunded and independent that pushes forward the representation and development of its members, as well as the role of repositories in the UK. There are other differences but I encourage you all to study the goals of both COAR and UKCoRR and come to your own conclusion on the compatibility or otherwise of the two organisations.
As I said in Portsmouth, as Chair while I can see a certain simpatico in establishing strong lines of communication and liaison with COAR (or indeed any other similar body) I do have a number of concerns over formal membership for UKCoRR.
Not least among these are these questions:
- What does UKCoRR the organisation really get out of membership?
- What do UKCoRR members get out of our membership?
- How closely does membership tie us to COAR's agenda and policy?
- Is it better to maintain our independence rather than interdependence?
Rather than UKCoRR becoming a member, would it not perhaps be a better idea for our host institutions to become members of COAR (UK membership is currently negligible)? Would this better suit the aims of both organisations, and our employers to boot?
As such I am looking to you the membership to give the Committee a steer on this. Leaving aside the fee question, the core question is: Should UKCoRR explore routes to becoming a formal member of COAR?
Najla Rettberg of COAR has helpfully provided a bit more information from their perspective that I'd encourage you all to read before responding.
I await your thoughts with considerable interest - please feel free to comment here or if you prefer contact myself or any of the Committee offline.
[Update 2/April/2012: As UKCoRR members will know already; following the discussions on the list and inside the Committee it has been decided that membership within COAR is not something that will be pursued. As Chair I've written to COAR to inform them of our decision, and warmly welcomed them to consider entering into a memorandum of understanding and support with us; in much the same way as we have with the RSP and the DRF.]
Wednesday, 1 February 2012
It was the Year of Fire...
| New look for Repository Managers? |
- Who are you?
- What do you want?
- Why are you here?
- Do you have anything worth living for?**
- Who do you serve?
- Who do you trust?
- Where are you going?
Some of these questions I believe are easier to answer than others. Some though need continued and protracted thought and consideration. I can say, for example, the question of funding vs Independence is one that has vexed the Committee for some considerable time; and I suspect will continue to. As Chair I'm personally ethically opposed to the introduction of any fee for membership structure, but at the same time conflicted as there are opportunities that would be far easier for UKCoRR if we had some form of funding stream.
Naturally there are those organisations out there whom might wish to provide us with an alternate funding stream - but with great funding comes great responsibilities (apologies, mixing my genres there) - to whit to accept a quid means there may a pro quo around the corner.
Likewise there is the prospect of UKCoRR entering into arrangements of mutual benefit with external bodies that may well serve the interests of our members well; but at the same time once again these come with strings attached. Is it better to simply be in formal liaison with key players rather than partnership, or is loss of our Independence a small price to pay for advancing the cause of professional repository management and administration? I remain to be convinced but over 2012 we will continue to talk to a variety of other organisations that do overlap with our concerns to explore where mutual benefits do exist, whilst not giving away the home world at the same time. I'll be talking more about one of these in particular where I want you the membership's views in my next post!
There are two major reasons why I raised all these questions in this post and the talk. Firstly because I believe that UKCoRR as an organisation, like open access and repositories, is a field that continues to evolve at a relatively cracking pace. As the professional membership body for repository practitioners we too must evolve likewise. And secondly because as part of the annual cycle which begins anew in April the Committee will be charged with drawing up a strategic and operational plan of action for the next year - and this is your opportunity to feed directly into the process.
So contact us, comment on this or catch us at the various repository events around the Country over the coming couple of months because, as I never tire of saying, UKCoRR is the membership - we the Committee simply try and run it according to your desires and needs; not to mention enlightened best interests!
Because if we don't, it may all end in fire but this could also be the year of rebirth just as easily.
--
* Don't get me into who the Shadows, Vorlons and First Ones are in the repository world - that's a whole other talk!
** I think this one is a bit beyond us!
Monday, 21 November 2011
We Are the Winners...
Those of you who are at the Online Exhibition and conference in December may well get the chance to see the award being presented in person to the External Liasion Officer (exact date and time TBC)
Tuesday, 21 June 2011
CRIS -> Repository...full-text only...or metadata records too?
From the RSP publicity: "With the REF taking place in 2014 (http://www.hefce.ac.uk/research/ref/) CRIS systems and repositories are becoming a higher priority and their functionality more visible. Smooth interaction between the two will be vital for a smooth and painless submission in 2014. Now is the perfect time to find out how others have managed this process! This event will look at how repositories and CRISs can work together to meet this goal. Findings of the RePosit project, which has developed case studies around the integration of Symplectic Ltd and repositories in 5 institutions, will be shared."
I've had several conversations recently with repository managers from different institutions in the process of or planning soon to implement CRIS and integrate with their repositories with many reporting a driver to transfer not only full-text to an institutional repository (the current functionality supported by Symplectic for example) but also metadata-only records - presumably to ensure their repositories remain the locus for research management. However, does it perhaps make more sense to separate our research database in a CRIS from full-text only in a repository?
Arguably, one of the limitations of Open Access repositories from an original conception (in the arXiv mould) of holding, disseminating and preserving full-text research outputs is that they have, in effect, become "diluted" by metadata records for which it has not been possible to procure full-text or copyright does not permit deposit. Developing a "hybrid" model that separates full-text from bibliographic records in this way rather than pushing everything into a repository might enable repositories to return to an antedeluvian world where they are focused once again on preservation of full-text material rather than also including bibliographic data.
The very term "CRIS" is perhaps problematic and probably better conceived of as an infrastructure derived from a set of software and services - HR systems, Finance systems, repository etc as well as 3rd party commercial software like Symplectic Elements, Atira Pure and Converis (Avedas). Moreover, leading repository software providers like EPrints are looking to extend the functionality of repositories themselves (see: Carr, L. (2010) EPrints: A Hybrid CRIS/Repository. In: Workshop on CRIS, CERIF and Institutional Repositories, 10-11th May 2010, Rome, Italy.); I have no idea whether such a "hybrid" approach would necessarily be achievable in every - or even most - institutions; as emphasised at "Learning how to play nicely: Repositories and CRIS", institutions are all different and there is no one-size-fits-all solution. The availability of human and other resources, in-house expertise and the existing infrastructure will all have an impact on the most appropriate course of action. The tentative conclusion from that event was that if starting with a blank slate, it probably makes sense for a CRIS to be the central system with the repository as a linked peripheral component; but, of course, very few are actually starting from this point and different models can be just as effective.
Thursday, 9 June 2011
What do you want? Membership Survey 2011
We continue to live in interesting times as repository managers and workers. The advent of CRISes and the REF have seen us go up the visibility flagpole in many institutions, but at the same time this visibility often seems to bring with it a restriction of movement; and it's always been the flexibility and adaptability of repositories that has been one of their strongest points.
I'll be nagging/reminding you all over the coming weeks to have your say!
Friday, 27 May 2011
Survey: Annual metrics collection for SCONUL & UK Repositories
As it happens my boss is chair of the SCONUL Chair of Performance Measures group and we've been talking about the SCONUL annual stats return. As many of you remember last year this tried to include repository download numbers for full-text items. I know from conversations I had with various people in the community that what they asked for wasn't realistically collectible, or at least wasn't last year.
However, SCONUL remains keen to be able to demonstrate what the UK repository community is delivering in their findings for 2011. She wanted to know if it was possible to isolate full-text downloads/accesses as discrete from total accesses, as she thinks the former is a more valuable figure.
For my own part I'm still not certain that I can create these figures for my local repository, or at least not without a lot of tech time investigating (something that with all the CRIS work we've got going on isn't really going to be an option). But what about the rest of the community?
Yes, that's right - this is a plea for information!
If you could take a minute or two to complete the following survey it would be very much appreciated and may help shape SCONUL's requests for this year into a more realistic metric! Which I'm sure we could all agree would be a positive move for the community.
The survey is here: http://www.surveymonkey.com/s/PKQH6RC
If you're unable to access the Survey Monkey site please get in touch with me and I'll I'll email you a copy of the questions. I'll blog about the results this time next week - so get clicking and thanks
Tuesday, 21 December 2010
OAI-PMH aggregation?
The protocol dates back to the earliest days of the open access and institutional repository movements when there was considerable investment by the community, in software specification for example, and has never really, I don't think, been as widely used as it could be. I can offer only anecdotal evidence but I’m pretty sure that your average academic will tend towards Google/Google Scholar* - who withdrew support for OAI-PMH back in April 2008 - to source research on the open web. Google, however, arguably has inherent limitations for academic purposes and I would argue that OAI-PMH still has considerable potential for (OA) research dissemination (though possibly watered down by so many repositories also carrying metadata only records rather than exclusively full text - one of the draw-backs of OAI-PMH harvest is that there was no easy way of filtering on full text from the major repository software.)
Friday, 22 May 2009
The results are in!
Approximately a quarter (24%) of members responded to the survey and it is really encouraging to see this level of response given that this is a particularly busy time of the academic calendar with many people away at conferences.
The committee will be meeting to review the results next week and in particular to make plans for the next UKCoRR meeting where we will take advantage of the various venues and speakers offered by respondents to the survey.