arXiv team conference call with publishers and societies

August 9, 2013

Attending: 

Agenda item 1: UPDATES

From 2010-2013, arXiv was planning financial and governance changes in order to make the program a community-supported, sustainable initiative. 2013 is the first year of implementation and it is still a work in progress. See sustainability initiative and pledge list for more information. 

Agenda Item 2: IOP-arXiv pilot to develop a process to deposit an author-final version of a journal article to arXiv

IOP is currently working on a pilot project with arXiv to deposit an author final version of journal articles to arXiv after a 12-mo. embargo period. The purpose of the pilot is to address funding and government mandates to provide OA to research. The functionality will be a link in arXiv back to the version of record at IOP website. IOP plans to provide alerts to authors at point of deposit. One of the goals in developing this process is to ensure it fairly generic and replicable in order for other publishers to adopt it. IOP will be relying on the SWORD standards and protocol.

Questions:
1. Robert/AMS: How do you expect usage to change over time, if at all?
A (Graham): Expect to cover a majority of papers via the deposit process.
2. Gunther: How do you find out if article is already in arXiv?
A (Graham): Will ask for arXiv record # from author and have an editor do a manual check as required. IOP plans to ask author if they would like IOP to update arXiv record – will need author's permission to do this.
3. Mark (APS): Expressed as a concern that APS provided information on bilateral linking to arXiv over a year ago and still no progress. Says other publishers are taking a different approach to make article available from publisher's website – does not need author permission. APS not sure they would go IOP direction on this.
A: Graham: IOP considers itself a "trusted partner" with arXiv. They are also considering to make the author's final version available on IOP website – waiting on CHORUS outcome to decide.
4. Robert: Does not see CHORUS and arXiv as oppositional. arXiv is different from, for example, PubMedCentral. Both can work in unison.
5. Eleanora/Elsevier: Elsevier wants to stress the idea of recognizing papers already in arXiv and that it is hard to get this information from authors. Is there a solution in place?
A:Graham: IOP is willing to do the same if it had author permission. Completely automated system would be great.

Agenda Item 3: Updates from publishers/societies related to open access repositories and arXiv

Agenda Item 4: September 2011 collaboration agenda

1) Cross- linking and persistent identifiers – no comments from group. arXiv API was created about a year ago.
2) Lifecycle of research materials and version control – to be discussed at SAB.
3) Supplementary material support
Oya - exploring position on data. For last 3 years arXiv has accepted dataset files – about 200 data submissions to date (these have not been large datasets). Interesting experiment – received 40 different file extensions. Raised questions about how to provide maintenance and support. Highlighted importance of provenance. arXiv decided to continue to accept submission of small datasets using EZID DOIs. Data Conservancy pilot data will be pulled back to arXiv – no action yet.
Eleanora – does anyone have a definition of raw data? No problem to release the data, but the definition and issue is not so clear.
Chris – this is a big can of worms. Astronomy data is analyzed over and over. Suggest that final data used in the article is the data for submission, but difficult question.
Robert – do not care about definition.
4) Statistics
Oya – plan to engage with SAB on this issue. arXiv as a source of compliance reporting makes arXiv a bit nervous and represents a change in mission.
Mark – Altmetrics (the company) interested in identifying articles as eprint and as final version to integrate into a single coherent view of the work.
Robert – AMS is launching with Altmetrics for their journals – want to associate comments made via media with their articles.

Summary

Bidirectional linking is important to all. Would like to create a generalized automated workflow for this process.
CHORUS and arXiv are complementary, and we will continue to listen for news about this initiative. 
CC license issues exist and arXiv: the team will continue to explore. 

-end of call--