Thanks, Tim-- I appreciate the help, but yeah, even our locked items still show the Anonymous group still having read access. I'll see whether I can hone in on the error with troubleshooting.
Paige --------------------- *Meeting/regular work hours: Monday - Thursday, 9am-5pm; limited email on Friday mornings.* Dr. Paige C. Morgan (she/her/they) Digital Publishing and Copyright Librarian, Head of Digital Initiatives & Preservation University of Delaware Library, Museums and Press (on Lenape land <https://native-land.ca/maps/territories/lenape/>) Morris 118 ORCID: https://orcid.org/0000-0001-8076-7356 paig...@udel.edu 302.831.7153 Make an appointment to meet with me: https://calendly.com/paigecm/ (Meetings available via Zoom, phone, etc.) *** I observe email-free evenings and weekends. *** On Tue, Jun 13, 2023 at 3:25 PM Tim Donohue <tim.dono...@lyrasis.org> wrote: > Hi Paige, > > I've not been able to reproduce that "locked bitstreams" issue...but can > reproduce that deleting multiple bitstreams will only delete one bitsteam. > > I suspect though that the "locked bitstreams" issue is simply a > permissions issue. That should be fixable if you Edit the Item and go to > "Status -> Authorizations". If you look at the policies of those locked > bitstreams (in the ORIGINAL bundle), it's possible that their "READ" policy > is wrong. If you want them available anonymously then READ must use the > "Anonymous" group. > > For more info on managing policies on that page, see the docs at > https://wiki.lyrasis.org/pages/viewpage.action?pageId=249135668 > > If that's not the issue you are seeing, then it's possible there's an > underlying error. In which case you may need to use the Troubleshooting > guide to look for errors: > https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove) > > Tim > ------------------------------ > *From:* dspace-tech@googlegroups.com <dspace-tech@googlegroups.com> on > behalf of Paige Morgan <paig...@udel.edu> > *Sent:* Tuesday, June 13, 2023 1:47 PM > *To:* Tim Donohue <tim.dono...@lyrasis.org> > *Cc:* DSpace Technical Support <dspace-tech@googlegroups.com> > *Subject:* Re: [dspace-tech] deleting multiple bitstreams results in > locked bitstreams > > Thanks, Tim -- out of curiosity, is there anyway to unlock items once > they've been locked? I didn't see anything in the regular documentation > about doing that; clicking on the padlock just gets a "this item is > forbidden" error message. > > Paige > > --------------------- > *Meeting/regular work hours: Monday - Thursday, 9am-5pm; limited email on > Friday mornings.* > > Dr. Paige C. Morgan > (she/her/they) > Digital Publishing and Copyright Librarian, > Head of Digital Initiatives & Preservation > University of Delaware Library, Museums and Press (on Lenape land > <https://native-land.ca/maps/territories/lenape/>) > Morris 118 > ORCID: https://orcid.org/0000-0001-8076-7356 > paig...@udel.edu > 302.831.7153 > > Make an appointment to meet with me: https://calendly.com/paigecm/ (Meetings > available via Zoom, phone, etc.) > *** I observe email-free evenings and weekends. *** > > > On Fri, Jun 2, 2023 at 5:45 PM Tim Donohue <tim.dono...@lyrasis.org> > wrote: > > Hi Paige, > > This sounds like this bug: https://github.com/DSpace/DSpace/issues/8029 > > We are working on a fix that is coming in 7.6 (which is due later this > month). The fix is in the final stages of review, so I'm sure it will be > included in 7.6. > > Tim > ------------------------------ > *From:* dspace-tech@googlegroups.com <dspace-tech@googlegroups.com> on > behalf of Paige Morgan <paig...@udel.edu> > *Sent:* Friday, June 2, 2023 8:54 AM > *To:* DSpace Technical Support <dspace-tech@googlegroups.com> > *Subject:* [dspace-tech] deleting multiple bitstreams results in locked > bitstreams > > Hi all-- > > We've uncovered an unusual behavior in both our production repository and > our sandbox (both running DSpace 7.4). A colleague and I can mostly > reliably reproduce it in our instances -- it doesn't happen every single > time, but it does happen repeatedly. I have not yet been able to reproduce > this in the demo version, so it may well be something in our local config > -- but it's a weird phenomenon. > > We use DSpace both for our institutional repository, and for our digitized > collection materials from Special Collections. For that latter set of > material, occasionally, we need to wholly replace a bitstream -- versioning > isn't appropriate. When we go in, and try to delete more than one bitstream > (by clicking on the trashcan icon for the selected bitstreams, and then > hitting the save button), *one *of the bitstreams is deleted -- but the > other ones selected for deletion become locked (previously they were > publicly available.) No one can delete them, and trying to access them > prompts users to log in, but eventually results in a 404 page, even though > the bitstream is still present, and the bitstream access policies all > suggest that it's functioning normally. > > It's pretty rare for us to delete bitstreams entirely, which is why we're > just discovering this now, 7 months into running DSpace 7.4. But I'd still > like to get it sorted out, especially because it's making a couple of items > in our production instance inaccurate. > > Has anyone else encountered anything like this? Thanks in advance-- > > Paige > > --------------------- > *Meeting/regular work hours: Monday - Thursday, 9am-5pm; limited email on > Friday mornings.* > > Dr. Paige C. Morgan > (she/her/they) > Digital Publishing and Copyright Librarian, > Head of Digital Initiatives & Preservation > University of Delaware Library, Museums and Press (on Lenape land > <https://native-land.ca/maps/territories/lenape/>) > Morris 118 > ORCID: https://orcid.org/0000-0001-8076-7356 > paig...@udel.edu > 302.831.7153 > > Make an appointment to meet with me: https://calendly.com/paigecm/ (Meetings > available via Zoom, phone, etc.) > *** I observe email-free evenings and weekends. *** > > -- > All messages to this mailing list should adhere to the Code of Conduct: > https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx > --- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to dspace-tech+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-tech/CA%2BzEVd%3D2%2BohO%3D-djtPpWsDE7B7oyA4ZG2Qd9iTTWY6Zonxt2nQ%40mail.gmail.com > <https://groups.google.com/d/msgid/dspace-tech/CA%2BzEVd%3D2%2BohO%3D-djtPpWsDE7B7oyA4ZG2Qd9iTTWY6Zonxt2nQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > -- > All messages to this mailing list should adhere to the Code of Conduct: > https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx > --- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to dspace-tech+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-tech/CA%2BzEVd%3DbDHL_by_gX9gmJoBPgv0mtWKkw7tR42BJ0b6TqCy1cA%40mail.gmail.com > <https://groups.google.com/d/msgid/dspace-tech/CA%2BzEVd%3DbDHL_by_gX9gmJoBPgv0mtWKkw7tR42BJ0b6TqCy1cA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CA%2BzEVdktdoPC1ZUCNMaM2_PGKT50gteSccNUoNMJN9DHLVYtEw%40mail.gmail.com.
