Skip to content

[Reference PR] PB&S 26-22 - #12023

Draft
cslzchen wants to merge 25 commits into
developfrom
feature/pbs-26-22
Draft

cslzchen wants to merge 25 commits into
developfrom
feature/pbs-26-22

Conversation

@cslzchen

Copy link
Copy Markdown
Collaborator

Ticket

  • TBD

Purpose

  • TBD

Changes

  • TBD

Side Effects

  • TBD

QE Notes

  • TBD

CE Notes

  • TBD

Documentation

  • TBD

bodintsov and others added 25 commits November 4, 2026 14:34
## Ticket
https://openscience.atlassian.net/browse/ENG-10338

## Purpose
Fix registrations not becoming public once the embargo ends
## Ticket
https://openscience.atlassian.net/browse/ENG-12575

## Purpose
Remove unauthorized users from test environments
## Ticket
https://openscience.atlassian.net/browse/ENG-12564

## Purpose
Problem statement
The system requires a Primary Preprint File to exist any time a preprint is in draft state. This blocks users from clearing and replacing a wrong file — there’s no way to do it without either deleting the entire draft or triggering unwanted file versions. The file should only be required when the preprint tries to transition out of Initial or Rejected state into moderation.

Acceptance criteria
A preprint in Initial or Rejected state can exist without a Primary Preprint File

A Primary Preprint File is still required to transition out of those states into moderation

Provide an explanation on what changes were made/needed.


## Changes
allow removing Primary Preprint File from draft state
… direct fetch (#11991)

## Ticket
https://openscience.atlassian.net/browse/ENG-12508

## Purpose
User can access node preprints when uses AVOL

## Changes
Hide `preprints` relationship on node data fetch when AVOL is used. `v2/nodes/<guid>/`
Raise 403 on `v2/nodes/<guid>/preprints/` when AVOL is used
…admin (#12002)

## Ticket
https://openscience.atlassian.net/browse/ENG-12443

## Purpose
Support needs a way to withdraw registrations from admin and to undo a withdrawal made by mistake. Preprints already have this, registrations didn't.

## Changes
- Withdraw button on the registration admin page, enabled only for accepted registrations, with an optional justification. The withdrawal is applied right away without contributor or moderator approval, and no emails are sent since Support handles that by email.
- Unwithdraw button, enabled only for withdrawn registrations. It restores the registration and its components to accepted, so a new withdrawal can be requested later.
- Both actions add a project log attributed to the OSF Support label and an admin log entry.
- Registration withdrawal metadata skips the creator when the withdrawal has no initiator.

## QA Notes
- Withdraw is enabled only for accepted registrations, Unwithdraw only for withdrawn ones.
- After unwithdraw the registration is accepted and public, and contributors can request a new withdrawal.
…llow admin to remove them (#11972)

* List user's connected identities in admin interface
* Abort removal and show an error if the ORCiD revoke fails
* Fail admin ORCiD identity removal when token is missing
* Update identities table, rename revoke helper, TODO on ConfirmEmailView
* Fix migration

---------

Co-authored-by: Longze Chen <cslzchen@gmail.com>
…12005)

## Ticket
https://openscience.atlassian.net/browse/ENG-12558

## Purpose
Prevent automated spam processes from banning or flagging users who are HAM, assumed HAM (safe-listed email domain), or own HAM-marked content. Staff can still mark them spam manually. 

## Changes
Added OSFUser.is_protected_from_auto_spam and a force= override. 

Spam checks, domain reclassification and check_resource_with_spam_services now respect it, including for the author's other public content. Added find_assumed_ham_spammy_users (report by default, --fix resets). --fix skips staff-confirmed spam, service-flagged and user-reported accounts, only reactivates accounts the ban disabled, and lists still-spammed nodes and preprints in the CSV. 

## Side effects
Contributors on a HAM project are also protected, which Product confirmed. 

## QE notes
Check that an assumed-HAM or HAM user isn't banned by domain reclassification or Akismet/OOPSpam. Check that admin "Confirm spam" still works for them. 

## CE notes
No migration. Run python manage.py find_assumed_ham_spammy_users --output report.csv first, then --fix.
## Ticket
https://openscience.atlassian.net/browse/ENG-12613

## Purpose
Fix issue: can't add moderator/admin to preprint provider, registration provider, etc.
## Ticket
https://openscience.atlassian.net/browse/ENG-12664

## Purpose
PsyArXiv is moving off OSF. After the move, an author who opens My Preprints could find their list empty or their work marked as withdrawn. That looks like something broke, even when the migration went fine.

The frontend is adding a “Migrated” label so authors know their preprint moved. This ticket covers the backend piece: a field that marks a preprint as migrated, exposed through the API, plus a way to set it for a whole provider at once.

This applies to preprints only. It needs to ship within a couple of weeks for PsyArXiv, so it’s separate from the redirect links project.

## Changes
implement command to set preprints migrated

`python manage.py set_preprints_migrated --provider-id psyarxiv --unset`
## Ticket
https://openscience.atlassian.net/browse/ENG-12580

## Purpose
Make a series of improvements to the Admin app’s management of admin users:

Fix the account/register page to properly add groups to a user (there is currently a bug preventing that from working)

On the account/register page, do not show groups starting with osfgroup_or institution_

Add an admin_user_management permissions class, and require it for using the account/register page. That being said, there may already be a permissions class for this, and if so, just keep using that, but if it’s only usable by superusers, then add this class. If this class already exists, anywhere below that references the admin_user_management permissions class just use that class.

Create an “Admin users” section on the left of the admin app that shows for users who have the admin_user_management permissions class

Include “Register admin” link in that section, which takes the user to account/register

Create an “Admin audit” link in the “Admin users” section (for users with the admin_user_management permissions class), which will generate a paginated list of all users who are marked as staff or who have superuser status. The report will show:

User guid with link to their admin user page

Primary email address

If they have is_staff (editable)

If they are superuser (can be disabled, but not enabled)

A list of groups they belong to
…nection (#11907)

* Revoke access and remove token when user remove ORCID connection
* Fail ORCiD disconnect when token revocation fails
* Fix conflicts for `requests_retry_session()`, update how it is called
* Rename methods to avoid confusion, add comments/docstring
* Only retry 500s for ORCiD revoke request
* Update error check for ORCiD removal and GDPR delete

---------

Co-authored-by: Longze Chen <cslzchen@gmail.com>
* 0062_post_enter_p2_update
* 0063_alter_adminprofile_options
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants