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

Include information about considering a plurality of users when assigning access points. #63

Open
1 task done
sreller opened this issue Dec 10, 2021 · 1 comment
Open
1 task done
Labels
Inclusive description Principle 2 Users are the fundamental reason for archival description. Principle 10 Archivists must have a user-driven reason to enhance existing archival description. Principles Project TS-DACS has begun a systematic review of how to better reflect the new principles.

Comments

@sreller
Copy link

sreller commented Dec 10, 2021

Link to Relevant DACS Principle

Principle 2. Users are the Fundamental Reason for Archival Description.
Principle 10. Archivists must have a user-driven reason to enhance existing archival description.

Describe how DACS does not currently meet this principle

DACS should include information about considering a plurality of users when assigning access points and when encoding creators. 2.6 states that "Repositories are encouraged to employ recognized standardized vocabularies (e.g. Library of Congress). Language should suggest alternative thesauri.

Additional guidance could be added to the Overview of Archival Description and Access Points. Language should focus on inclusivity and state that inclusive description is created with care and thoughtfulness. Likewise, language should suggest that archivists do not rely on Library of Congress Subject Headings (LCSH) exclusively (and especially problematic LCSH subject headings) when creating subject access points.

I expect that this will require a

  • [] Minor change to DACS
  • Major change to DACS

Link(s) to any relevant part(s) of DACS

[Overview of Archival Description: Access Points] (https://saa-ts-dacs.github.io/dacs/05_overview_of_archival_description.html#access-tools)
2.6 Name of Creators

@sreller sreller added the Principles Project TS-DACS has begun a systematic review of how to better reflect the new principles. label Dec 10, 2021
@gwiedeman gwiedeman added Principle 10 Archivists must have a user-driven reason to enhance existing archival description. Principle 2 Users are the fundamental reason for archival description. labels Dec 10, 2021
@regineheberlein
Copy link
Contributor

I agree with this in principle. The question I have is how we avoid falling from one set of bias into another when naming examples of other thesauri to use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Inclusive description Principle 2 Users are the fundamental reason for archival description. Principle 10 Archivists must have a user-driven reason to enhance existing archival description. Principles Project TS-DACS has begun a systematic review of how to better reflect the new principles.
Projects
Status: Open Issues
Status: No status
Development

No branches or pull requests

3 participants