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

Visibility bug #243

Open
2 tasks
jillpe opened this issue Feb 14, 2025 · 2 comments
Open
2 tasks

Visibility bug #243

jillpe opened this issue Feb 14, 2025 · 2 comments

Comments

@jillpe
Copy link

jillpe commented Feb 14, 2025

Summary

When I upload a work as private, it changes to Institutional visibility. When I edit that work and change it back to private, it remains private upon saving.

Editing visibility of works does not seem to work

Acceptance Criteria

  • The visibility specified through the visibility selection in the create a work, create an importer, or importer sheet is what saves for the record
  • Editing a work's visibility updates the visibility to what is selected and saves correctly
@jillpe jillpe converted this from a draft issue Feb 14, 2025
@jillpe jillpe changed the title Works uploaded as private changes visibility to Institutional Visibility bug Feb 14, 2025
@laritakr laritakr self-assigned this Feb 17, 2025
@laritakr laritakr removed the status in PalsKnapsack Feb 17, 2025
@laritakr laritakr moved this to In Development in PalsKnapsack Feb 17, 2025
@sjproctor
Copy link
Contributor

sjproctor commented Feb 17, 2025

Replicating the Problem

  • On production
  • Creating a work as private
  • Logged out users are only able to see public works
Photo: Works are maintaining their visibility

Image

Photo: Work created as private Image
Photo: Works with edited visibility Image

❌ Unable to replicate the problem

@laritakr
Copy link
Contributor

This could have been due to the collections/admin sets which failed to migrate. Please add details if issue recurs - tenant, link to specific work, etc.

@laritakr laritakr moved this from In Development to Client QA in PalsKnapsack Feb 18, 2025
@ndroark ndroark moved this from Client QA to Deploy to Production in PalsKnapsack Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Deploy to Production
Development

No branches or pull requests

4 participants