Hi Evgeni, I *think* that's why DS-3979 exists...cause it's a bug. I admit, though, I haven't had a chance to review that ticket or the PR associated myself. So, I'd recommend commenting directly on the ticket or PR and ask how to reproduce this problem. It might clarify to you (and me) what the actual bug is.
- Tim On Wed, Aug 22, 2018 at 9:24 AM Evgeni Dimitrov <dimitrove....@gmail.com> wrote: > Thank you Tim, > > I really did not know this. But still I don't see why change of the > filename or the format should affect the authorization policy of the > bitstream. > > Best regards > Evgeni > > On Wednesday, August 22, 2018 at 5:09:04 PM UTC+3, Tim Donohue wrote: > >> Hi Evgeni, >> >> This DS-3979 issue is referring to editing a bitstream's *metadata* (not >> the actual file associated with the bitstream). A bitstream's metadata is >> editable from the UI, but the file itself is not editable (you can only >> upload a new file). >> >> Here's how you get to the edit a bitstream's metadata in XMLUI: >> * Login, and browse to the Item >> * Edit the Item >> * Click on "Item Bitstreams" tab >> * Click on the Bitstream name. You'll then be on the "Edit Bitstream" page >> >> - Tim >> >> On Wed, Aug 22, 2018 at 4:01 AM Evgeni Dimitrov <dimitr...@gmail.com> >> wrote: >> > In issue DS-3979 I noticed a comment: >>> >>> Chris Herron (Atmire) added a comment - 10/Aug/18 11:52 AM >>> >>> Without this in place, if DEFAULT_ITEM_READ is Anonymous and >>> DEFAULT_BITSTREAM_READ is Administrator, then any edit to a bitstream will >>> add an Anonymous READ policy, making the bitstream public again. >>> >>> I don't know how to "edit a bitstream" and how editing can add a policy >>> to it. Can somebody shed some light on this? >>> >>> >>> -- >>> All messages to this mailing list should adhere to the DuraSpace Code of >>> Conduct: https://duraspace.org/about/policies/code-of-conduct/ >>> --- >>> 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...@googlegroups.com. >>> To post to this group, send email to dspac...@googlegroups.com. >> >> >>> Visit this group at https://groups.google.com/group/dspace-tech. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> Tim Donohue >> Technical Lead for DSpace & DSpaceDirect >> DuraSpace.org | DSpace.org | DSpaceDirect.org >> > -- > All messages to this mailing list should adhere to the DuraSpace Code of > Conduct: https://duraspace.org/about/policies/code-of-conduct/ > --- > 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 post to this group, send email to dspace-tech@googlegroups.com. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > -- Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
