Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow preprints to be withdrawn or removed #6271

Open
NateWr opened this issue Oct 8, 2020 · 18 comments
Open

Allow preprints to be withdrawn or removed #6271

NateWr opened this issue Oct 8, 2020 · 18 comments
Assignees
Labels
Enhancement:3:Major A new feature or improvement that will take a month or more to complete.

Comments

@NateWr
Copy link
Contributor

NateWr commented Oct 8, 2020

Describe the problem you would like to solve
A preprint may need to be withdrawn, removed or unpublished. Although similar to retracted publications, preprints are withdrawn for a wider variety of reasons, and may need to be fully removed or unpublished if they contain harmful information or are the result of an unintentional posting.

Describe the solution you'd like
This paper, which @alexxxmendonca brought to my attention, puts forward clear recommendations for withdrawn and removed preprints (see "Defining preprint withdrawal & removal"). In particular, it provides a table with examples of how existing preprint servers are handling this.

OPS should support these two actions and should aim to follow the conventions of existing preprint servers. I recommend reading the guidance in full, but here is a short summary:

  • Withdrawal is similar to retractions. A new version is created. The preprint (all versions) is marked "withdrawn" and the new version's abstract is changed to a description of the withdrawal. The original post remains as an old version, so the withdrawn content is still available to the public record.
  • Removal is a rare event when a preprint contains harmful information, such as disclosing personal information or containing research without ethical approval. The item is marked "removed" and all existing versions are modified so that the abstract is changed to a description of the removal. Existing galley files are replaced with files that describe the removal.

In both cases, distribution services (like Crossref) should receive updated metadata.

Who is asking for this feature?
Preprint server administrators

Additional information
This is split off from a discussion about withdrawing submissions before publication in OJS/OMP. See #1813.

@NateWr NateWr added the Enhancement:3:Major A new feature or improvement that will take a month or more to complete. label Oct 8, 2020
@ajnyga
Copy link
Collaborator

ajnyga commented Oct 8, 2020

@alexxxmendonca can you comment here if the issue Nate created covers your use cases?

@alexxxmendonca
Copy link
Contributor

@ajnyga yes, this is perfect.

@alexxxmendonca
Copy link
Contributor

I would also add that "Distribution services (like Crossref) should receive updated information" in the event of a Removal as well.

@NateWr
Copy link
Contributor Author

NateWr commented Oct 8, 2020

Thanks @alexxxmendonca. I've updated the original description to make that clear.

@willinsky
Copy link

willinsky commented Oct 8, 2020

Screen Shot 2020-10-08 at 12 31 18 PM

To jump right in were I'm most comfortable around words and buttons, I'd propose the following two buttons in the Publication tab for OJS.OMP and for OPS.

Status: Published [Minor Revisions] [New Version]

I also find "This version has been published and can not be edited." in far too an alarming shade of red, as if to bar the way to disaster. It is a little confusing, as this version can be edited, using "Minor Revisions." What we appear to need is only a slight reminder without much color to the effect that "The metadata and published version can revised by clicking Minor Revisions."

Again, I know it is inconvenient, but I still want to put in a plug for OPS being differentiated along the following lines, if only by this key distinction

Status: Posted [Minor Revisions] [New Version]

@asmecher
Copy link
Member

asmecher commented Oct 9, 2020

@willinsky, the design work around "minor revisions" vs. unpublish / modify / republish (also leading to the big red version banner) was captured on #2072 -- I'd suggest reviewing that first, and proposing changes related to it in another issue that links back to both your comment above and that original design work.

@willinsky
Copy link

Alec, I did my best in reviewing #2072, as suggested, and couldn’t see a way to make the suggestions there, so entered changes here on this point of renaming buttons on Publication page "minor revisions" and "new version."

Also, I'm convinced that Nate has it right in #1813 with placing Withdrawal and Retraction under discrete "More" button, given the extreme rarity of these two (which I have exploded into two options in my suggestions.

@alexxxmendonca
Copy link
Contributor

We are currently facing a situation where an author has systematically submitted the same made-up manuscript even after we rejected it. The manuscript is clearly made-up (it's made of mostly nonsense) and the author has submitted 8 times the same manuscript, 5 of which we rejected.

Right now, these submissions are clogging our submission queue. We don't have any other choice but to reject and this is affecting our rejection rate.

Having a way to withdrawn the papers would allow us to deal with these cases without affecting our editorial statistics.

@alexxxmendonca
Copy link
Contributor

Related to #1813

@asmecher
Copy link
Member

asmecher commented Nov 3, 2021

@alexxxmendonca, in cases where you're effectively being spammed and want to keep the entries off the record, why not send the submission to the archive and then delete it entirely from there? Deleted submissions don't affect the statistics.

@alexxxmendonca
Copy link
Contributor

alexxxmendonca commented Nov 3, 2021

@asmecher How do you archive a preprint without recording an "Accept" or "Reject" decision?

How do you delete a submission from the Archives? It doesn't seem to be a way to do that.

@asmecher
Copy link
Member

asmecher commented Nov 3, 2021

@alexxxmendonca, record a Decline decision, then go to the "Archives" listing and click the down arrow beside the submission to expand its view. You should see a Delete button there:
image

@alexxxmendonca
Copy link
Contributor

@asmecher we don't have that option:

image

OPS 3.3.0.6

@NateWr
Copy link
Contributor Author

NateWr commented Nov 4, 2021

I just checked and the delete button appears in the test drive install of OPS 3.3.0-8. Looks like you need to be ROLE_ID_MANAGER or ROLE_ID_SITE_ADMIN.

@alexxxmendonca
Copy link
Contributor

Hi @NateWr I am logged in as the Site Administrator and I still don't see the button.

Am I doing something wrong?

@alexxxmendonca
Copy link
Contributor

After running some tests, I noticed that you need not only to have the Editor role enrolled to your user. That alone won't suffice. You also need to be assigned as an Editor to the submission in order to be able to delete a preprint.

However, with the current issue of #6875, it's getting a little tricky. You can't be an Editor for posting preprints, but you have to be one in order to delete a preprint.

I also found this issue, which could be related: #4348

@NateWr
Copy link
Contributor Author

NateWr commented Nov 11, 2021

@alexxxmendonca can you file a separate issue or add on to one of the other issues you identified? It's a separate problem from the question of withdrawals in this issue.

@ajnyga ajnyga self-assigned this Feb 27, 2022
@felixhelix
Copy link

Can anyone comment on the status of this issue? I can see that here as well as in the related issue pkp/ojs#3669 nothing has happend for over a year. Is there some help needed?
We are planning to host OPS with the additional feature of open peer review, and the option to withdraw preprints in a defined way would be welcome :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement:3:Major A new feature or improvement that will take a month or more to complete.
Projects
Status: Backlog
Status: Under Development
Development

No branches or pull requests

6 participants