You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most of our collections have multiple conditions governing access notes. Only one of these (the last one) is displaying in the "parent terms of access" field for the collection's items.
Here is an example of a collection level access restriction:
And this is the access restriction and parent access restriction for a series in that collection:
We would like all of these notes to display. (This behavior is also true for parent conditions governing use, though we don't repeat that field often.) Based on the comment here, I think the current behavior is unexpected.
The text was updated successfully, but these errors were encountered:
bonniegee
changed the title
For parent conditions governing access and parent conditions governing use, only one is displaying when nearest ancestor has multiple access or multiple use notes
If an ancestor has both multiple access or use notes, only one note displays in parent access/use restrictions
Jul 15, 2024
bonniegee
changed the title
If an ancestor has both multiple access or use notes, only one note displays in parent access/use restrictions
If an ancestor has multiple access/use notes, only one note displays in parent access/use restrictions
Jul 15, 2024
Most of our collections have multiple conditions governing access notes. Only one of these (the last one) is displaying in the "parent terms of access" field for the collection's items.
Here is an example of a collection level access restriction:
And this is the access restriction and parent access restriction for a series in that collection:
We would like all of these notes to display. (This behavior is also true for parent conditions governing use, though we don't repeat that field often.) Based on the comment here, I think the current behavior is unexpected.
The text was updated successfully, but these errors were encountered: