[Open Source 2.0] Create dedicated source files section for publication to foster open source article

[Proposal related to my citizen research on the meaning of “open source” and associated preprint « Open Source 2.0: From Open Source Software to Open Source Resources? »]

Many open resources provide the right to modify through licenses without the ability to do so because of the lack of source files. Similarly to arXiv, I suggest to create a dedicated section to handle source files of final document(s)/galleys. You already distinguish editable/non-editable format, this would be about providing these editable elements.

Why a dedicated section ?

While wondering how you handle these source files, I found the production section in the workflow.

As I’m not a user of OJS and with my understanding, it seems that source files can be already provided, “OJS allows users to upload almost any kind of file”. The problem in providing source files is therefore not technical but cultural one, as open access is not really about the ability to edit collaboratively research.

A dedicated section would create the affordance to incitate user to provide them.

How useful it would be ?

For now I don’t know. It’s still not part of the culture to manipulate sources files post-publication by external people to improve resources, which are usually in a kind of final state.

But, versioning is slowly taking shape, where we may progressively move towards more evolutive article. With increasingly more collaboration through new practices in open science. I also believe we may move beyond research article, a format inherited from traditional printing practices which is probably not all that remarkable given the capabilities of digital technology, but that’s another discussion.

This access to source files could support emerging practices in open science. OJS would then become more fully an open source tool!

Complementary information

Hi @jun,

Thanks for your post. Could you please edit your first post following this template? You have much of the correct information for following our feature request format, it just needs to be adjusted to match this structure:

Describe the problem you would like to solve
Example: Our editors need a way to […]

Describe the solution you’d like
Tell us how you would like this problem to be solved.

Who is asking for this feature?
Tell us what kind of users are requesting this feature. Example: Journal Editors, Journal Administrators, Technical Support, Authors, Reviewers, etc.

Additional information
Add any other information or screenshots about the feature request here.

You can use this post as a reference.

Thank you,

Roger
PKP Team

Hum… I do not see any edit button (anymore?) :sweat_smile: But it’s quite your structure, just different title. I would have just add them.

Edit: I definitely see and can use the edit button for this message, not for the old one.