Bulk access management doesn't remove access conditions

[Maruan Sahyoun]

I've a question regarding bulk access management and maybe a misconception from my side.

Currentl I have an item with READ permission for Anonymous. Now using Bulk access management I'd like to change that to Administrator using "Replace Access Conditions" and selecting "administrator" from the drop down.

After that I have READ permission for Administrator but still READ permission for Anonymous.

I'm using DSpace 7.6.0 - am I doing something wrong?

BR

Maruan

[Andrew K]

Has the bulk-access-control process finished successfully? (in the Processes tab)

середу, 13 грудня 2023 р. о 18:20:51 UTC+2 Maruan Sahyoun пише:

[Maruan Sahyoun]

Yes - that's of course something I've checked. It reports that it sets the items access

[DSpace Technical Support]

Hi Maruan,

Assuming you selected to change the "Item's Metadata" and selected the "Replace access conditions" mode, then the Item should only have one policy (which matches with the new access condition type).  It's not exactly clear to me why this wouldn't be working based on the details you provided.

If this isn't working, then we may need more details about the steps you are taking, or you might want to submit a bug ticket to https://github.com/DSpace/dspace-angular/issues (with the step by step process you took). You also are welcome to test this process out on the demo site (https://demo.dspace.org), which is running 7.6.1, to see if you can reproduce the issue there.

Tim

[Maruan Sahyoun]

Hi Tim,

thank you for your response. I've tried on the demo site where it works. Will investigate further.

BR

Maruan

[Maruan Sahyoun]

Hi Tim,

I'm attaching a screenshot of the items policy setting before and after having run bulk access together with the json and log. As there is already a cusom setting for read and write maybe that's where it's getting confused as you can see from the after screenshot that instead of replacing it's adding also the control json is specifying replace.

BR

Maruan

[Maruan Sahyoun]

Hi Tim,

I think I've found the reason. In the source there is

        if (REPLACE_MODE.equals(acItem.getMode())) {
            removeReadPolicies(item, TYPE_CUSTOM);
            removeReadPolicies(item, TYPE_INHERITED);
        }

so READ is only removed for TYPE_CUSTOM or TYPE_INHERITED and not any of the other types or if the type hasn't been set at all (which is the case with our data).

Do you consider this to be a bug?

BR

Maruan