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

Update Admin UI for moving item to a different collection #483

Open
astridu opened this issue Jan 14, 2025 · 1 comment
Open

Update Admin UI for moving item to a different collection #483

astridu opened this issue Jan 14, 2025 · 1 comment

Comments

@astridu
Copy link

astridu commented Jan 14, 2025

Here are the new designs for updating the Admin UI for moving an item to a different collection. This is the original ticket from H2 for reference: sul-dlss/happy-heron#2685
Screenshot 2025-01-13 at 4 25 08 PM
Screenshot 2025-01-13 at 4 25 37 PM

@amyehodge
Copy link
Collaborator

Here are the requirements we should have now (from #).

  • Items can only be moved to collections that have been deposited (so, not anything in a "first draft" state, but later draft states are fine)
  • Items can't be moved if certain conflicts exist:
    -- the item is embargoed but the collection is set for immediate release only
    -- the depositor of the item chose not to get a DOI but the collection requires DOI assignment
    -- the item has a license that is not allowed by the collection setting
    -- the item is set for Stanford visibility but the collection requires world visibility
  • This move needs to trigger a versioning of the item so that the new collection information is sent to SDR
    -- I think we need to create a new system version in this case still. We do not want to trigger a new user version.

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

No branches or pull requests

2 participants