Description
DSpace allows changing the group that a Bitstream's Resource Policy applies to. However, when only the policy group is changed, the updated group name is not immediately reflected in the Bitstream Policies table after saving.
The UI continues to display the stale group name until the page is manually reloaded.
There is also a slightly different behavior when the policy name is changed at the same time as the group. In that case, the updated data is eventually displayed, although stale data may still be visible briefly after the redirect.
To reproduce
recorded jam
Changed only bitstream policy group
-
Create an Item with a Bitstream.
-
On the Item page, go to:
Administer → Bitstreams → Edit any Bitstream.
-
Select Edit bitstream's Policies.
The Resource Policy table contains information such as Name and Group.
-
Click Edit policy.
-
Scroll to the bottom of the page and change the policy to a different group.
-
Save the policy.
-
After saving, DSpace redirects back to the Bitstream Policies page.
The table still displays the previous group name, even though the policy was successfully changed:
-
Reload the page.
After reloading, the table displays the correct, updated group:
Alternative behavior
There is a second case where the behavior is slightly different.
If, while editing the policy, we change both the policy name and the policy group, the updated values are reflected in the UI after saving.
For example:
-
Edit the policy.
-
Change the policy name.
-
Select a different policy group.
-
Save the policy.
-
After being redirected back to the Bitstream Policies page, the updated group is displayed in the UI:
However, stale data may still be displayed briefly before the current state is shown.
Expected behavior
After changing a Bitstream policy's group and being redirected back to the Bitstream Policies page, the table should immediately display the updated group without requiring a manual page reload.
The UI should consistently reflect the current state of the Resource Policy after saving, regardless of whether only the group was changed or other policy properties were changed as well.
Description
DSpace allows changing the group that a Bitstream's Resource Policy applies to. However, when only the policy group is changed, the updated group name is not immediately reflected in the Bitstream Policies table after saving.
The UI continues to display the stale group name until the page is manually reloaded.
There is also a slightly different behavior when the policy name is changed at the same time as the group. In that case, the updated data is eventually displayed, although stale data may still be visible briefly after the redirect.
To reproduce
recorded jam
Changed only bitstream policy group
Create an Item with a Bitstream.
On the Item page, go to:
Administer → Bitstreams → Edit any Bitstream.
Select Edit bitstream's Policies.
The Resource Policy table contains information such as Name and Group.
Click Edit policy.
Scroll to the bottom of the page and change the policy to a different group.
Save the policy.
After saving, DSpace redirects back to the Bitstream Policies page.
The table still displays the previous group name, even though the policy was successfully changed:
Reload the page.
After reloading, the table displays the correct, updated group:
Alternative behavior
There is a second case where the behavior is slightly different.
If, while editing the policy, we change both the policy name and the policy group, the updated values are reflected in the UI after saving.
For example:
Edit the policy.
Change the policy name.
Select a different policy group.
Save the policy.
After being redirected back to the Bitstream Policies page, the updated group is displayed in the UI:
However, stale data may still be displayed briefly before the current state is shown.
Expected behavior
After changing a Bitstream policy's group and being redirected back to the Bitstream Policies page, the table should immediately display the updated group without requiring a manual page reload.
The UI should consistently reflect the current state of the Resource Policy after saving, regardless of whether only the group was changed or other policy properties were changed as well.