Skip to content

[E] Depositing Improvements, Phase 3#206

Merged
scryptmouse merged 1 commit into
mainfrom
ag/depositing-3
May 11, 2026
Merged

[E] Depositing Improvements, Phase 3#206
scryptmouse merged 1 commit into
mainfrom
ag/depositing-3

Conversation

@scryptmouse
Copy link
Copy Markdown
Contributor

  • Add a new section to GlobalConfiguration for contributors with two new boolean properties (both default to true for MVP):
    • claimable: Contributor claiming is enabled. Details below.
    • ownerUpdatable: Controls whether a contributor that is linked to a user can be updated by that user.
  • Greatly improve the handling of updating contributors and linking them with user records:
    • Add a new mutation, contributorClaim that can be used on any contributor that does not have an attached user record. It requires claiming to enabled (currently true by default) and for the user to have a role that grants contributors.claim. This will be true for depositors, reviewers, and any higher-tier roles.
    • Depositors will now auto-create a contributor if they don't have a primary contributor assigned to them yet, whether through claiming or an admin assigning beforehand.
    • A submission's user's primary contributor will be assigned as the author on the generated entity at creation time. It can be edited afterwards if need be.
    • The aforementioned user will also be granted a new system role, Author, that ensures that they have update access to the entity. This facilitates being able to specify access: UPDATE on the items resolver in order to see which record(s) a depositor can access. When the submission is published, this role will be removed (for now). This prevents authors from being able to make post-publication changes outside of the submission workflow. We can surface an option to allow this in the future.
    • Users who are attached to a contributor can manage that contributor record themselves. As with claiming, this is also controlled by the new setting: contributors.ownerUpdatable.
  • Add the ability to merge contributors. Merging happens in the BG, but can be kicked off by the contributorMerge mutation.
  • Port over a number of VOG improvements to be able to test filters as well as make further improvements to extract framework code out of app and into lib/support.

* Add a new section to `GlobalConfiguration` for `contributors` with
  two new boolean properties (both default to `true` for MVP):
  * `claimable`: Contributor claiming is enabled. Details below.
  * `ownerUpdatable`: Controls whether a contributor that is linked to
    a user can be updated by that user.
* Greatly improve the handling of updating contributors and linking
  them with user records:
  * Add a new mutation, `contributorClaim` that can be used on any
    contributor that does not have an attached user record. It
    requires claiming to enabled (currently true by default) and
    for the user to have a role that grants contributors.claim.
    This will be true for depositors, reviewers, and any higher-tier
    roles.
  * Depositors will now auto-create a contributor if they don't have
    a primary contributor assigned to them yet, whether through
    claiming or an admin assigning beforehand.
  * A submission's user's primary contributor will be assigned as the
    author on the generated entity at creation time. It can be edited
    afterwards if need be.
  * The aforementioned user will also be granted a new system role,
    Author, that ensures that they have update access to the entity.
    This facilitates being able to specify `access: UPDATE` on
    the `items` resolver in order to see which record(s) a depositor
    can access. When the submission is published, this role will be
    removed (for now). This prevents authors from being able to make
    post-publication changes outside of the submission workflow. We
    can surface an option to allow this in the future.
  * Users who are attached to a contributor can manage that
    contributor record themselves. As with claiming, this is also
    controlled by the new setting: `contributors.ownerUpdatable`.
* Add the ability to merge contributors. Merging happens in the BG,
  but can be kicked off by the `contributorMerge` mutation.
* Port over a number of VOG improvements to be able to test filters
  as well as make further improvements to extract framework code out
  of app and into `lib/support`.
@scryptmouse scryptmouse merged commit 7fe1259 into main May 11, 2026
2 checks passed
@scryptmouse scryptmouse deleted the ag/depositing-3 branch May 11, 2026 15:23
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.

1 participant