Include information on availability of data and computation model (for IJM)

[chris-huggins]

IJM need to include the following information in the article and author information section within an article. If possible it may even be preferable to include as a new section within an article:

From IJM's current author guide:

"Authors are required to report, for any data they use, which is the source and whether the data is:

• publicly available (specifying how the data can be accessed);
• available for scientific research only upon registration;
• proprietary (specifying the nature of the data and the user agreement which they benefited from).

If the paper is model-based, authors are also required to specify whether the code is:

• open-source;
• proprietary, with executable available;
• proprietary, with executable also not available."

I will aim to follow up with specific examples from IJM of content needed for each option

[chris-huggins]

Copied from google doc for reference:

I've looked into this a little and there aren't clear examples of it being included as a dedicated section of a manuscript (similar to eLife's data availability statement), so I might have misunderstood. It might just be general advice to authors to include in the text somewhere, which we cannot include in a dedicated section, and therefore should not worry about.

@m.plaine@elifesciences.org perhaps we should clarify with Matteo?

[Melissa37]

I think we need to look at current content not the archive.

We can show you Kriya if that helps?eLife is proposing tagging it semantically going forward.

Cheers Melissa

On Mon, 2 Dec 2019 at 17:27, Chris Huggins notifications@github.com wrote:

Copied from google doc for reference:

I've looked into this a little and there aren't clear examples of it being included as a dedicated section of a manuscript (similar to eLife's data availability statement), so I might have misunderstood. It might just be general advice to authors to include in the text somewhere, which we cannot include in a dedicated section, and therefore should not worry about.

@m.plaine@elifesciences.org perhaps we should clarify with Matteo?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/libero/publisher/issues/101?email_source=notifications&email_token=ABOFQJCGGNZFYMEU3RHCJQDQWVAOHA5CNFSM4GSZVUU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFUHX2Q#issuecomment-560495594, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABOFQJEAF7CXOLZY6ZAX2PTQWVAOHANCNFSM4GSZVUUQ .

--

Melissa Harrison Head of Production Operations

Tel: +44 1223 855340

http://elifesciences.org

-- eLife Sciences Publications, Ltd is a limited liability non-profit non-stock corporation incorporated in the State of Delaware, USA, with company number 5030732, and is registered in the UK with company number FC030576 and branch number BR015634 at the address Westbrook Centre, Milton Road, Cambridge, CB4 1YG.

[chris-huggins]

Thanks @Melissa37. That would be really useful if anybody in your team has time this afternoon?

[Melissa37]

Hi @chugginselifesciences it's IJM's instance of Kriya that needs to be looked at and only @FAtherden-eLife and I have access to that.

Please feel free to ask @FAtherden-eLife :-)

[chris-huggins]

For reference following conversation with Fred and Melissa: the Data availability and Software availability information will be handled much like eLife's data availability statement - i.e. in the Figures and Data of the article view. For archived articles where this content doesn't exist this will not be shown on the article view. Therefore IJM's MVP prototype will not include this content as it is an archived article, but the Production team have already worked with IJM to ensure this will be included in new articles in future.