Current Behavior
Steps to reproduce the behaviour - Part 1
- Link authority record to a description as creator
- Link the same authority record to the same description as a name access point
- View authority record to see the description only listed in the 'Creator of' cards on the left side
Steps to reproduce the behaviour - Part 2
- Continuing from Part 1, link the same authority record to a different description as a name access point.
- View authority record to see the newly linked description linsted in the 'Subject of' card on the left side, with the 'Browse 1 results' button underneath.
- Click 'Browse 1 results'.
- Browse will say "Showing 2 results"
Expected Behavior
Expected behaviour - Part 1:
The related resource used to show up in both 'Subject of' and 'Creator of' cards.
Expected behaviour - Part 2:
The results shown should match the browse results counter.
Possible Solution
Solution 1:
Include all related resources in the 'Subject of' list where the authority is a name access point, regardless of whether that authority is also a creator of the same resource. The counter should align correctly with this approach. This is a return to previously observed behaviour.
Solution 2:
Implement automatic assignment of creators as name access points as documented.
In digging into this issue, I came accross this part of the documentation:
On Name vs. Subject Access Points
First, name (creator) access points are automatically derived from ISAAR authority records in AtoM. Whenever a creator is added to an archival description, the creator name is also added as a name access point in the Access points information area of the archival description.
Are creators supposed to automatically be added as name access points in the access points area? I don't recall this being the case, but this could have been how things worked before I became a user quite some time ago.
If creators are supposed to be automatically added as name access points, then I follow the logic of removing them from the 'Subject of' list for the sake of eliminating redundacy. However, properly implementing the automatic assignment of name access points as part of assigning creators has a number of moving parts and is not a simple solution. I think this is worth discussing, or if not, then at the very least remove reference to this behaviour in the documentation.
Context and Notes
No response
Version used
2.10.1
Operating System and version
Ubuntu 24.04.4 LTS
Default installation culture
No response
PHP version
PHP 8.3.6
Contact details
No response
Current Behavior
Steps to reproduce the behaviour - Part 1
Steps to reproduce the behaviour - Part 2
Expected Behavior
Expected behaviour - Part 1:
The related resource used to show up in both 'Subject of' and 'Creator of' cards.
Expected behaviour - Part 2:
The results shown should match the browse results counter.
Possible Solution
Solution 1:
Include all related resources in the 'Subject of' list where the authority is a name access point, regardless of whether that authority is also a creator of the same resource. The counter should align correctly with this approach. This is a return to previously observed behaviour.
Solution 2:
Implement automatic assignment of creators as name access points as documented.
In digging into this issue, I came accross this part of the documentation:
On Name vs. Subject Access Points
Are creators supposed to automatically be added as name access points in the access points area? I don't recall this being the case, but this could have been how things worked before I became a user quite some time ago.
If creators are supposed to be automatically added as name access points, then I follow the logic of removing them from the 'Subject of' list for the sake of eliminating redundacy. However, properly implementing the automatic assignment of name access points as part of assigning creators has a number of moving parts and is not a simple solution. I think this is worth discussing, or if not, then at the very least remove reference to this behaviour in the documentation.
Context and Notes
No response
Version used
2.10.1
Operating System and version
Ubuntu 24.04.4 LTS
Default installation culture
No response
PHP version
PHP 8.3.6
Contact details
No response