Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem: Docs suggest name (creator) access points are automatically added to the list in the Access points information area of an archival description when they actually need to be manually selected + added for the name to appear in the list #197

Open
currmie opened this issue Oct 5, 2022 · 0 comments
Assignees
Labels
minor fix The change requested by the issue will be minor in scope user manual The issue affects content in the User manual

Comments

@currmie
Copy link

currmie commented Oct 5, 2022

User reports confusion around help topic that describes how name (creator) access points are created and automatically added to the list in the 'Access points information' for a description. Example provided from linked topic:

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. Doing so conforms to the recommendations found in ISAAR-CPF 1.5 and 1.6, and 1.8....

From the above statement, user assumes the name (creator) access points are automatically added to the access points list in the archival description as in previous versions when in reality they still need to be manually selected from the drop-down menu and manually added in order to appear in the list.

@currmie currmie added user manual The issue affects content in the User manual minor fix The change requested by the issue will be minor in scope labels Oct 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
minor fix The change requested by the issue will be minor in scope user manual The issue affects content in the User manual
Projects
None yet
Development

No branches or pull requests

2 participants