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

Arrangement note changes #81

Open
wants to merge 22 commits into
base: master
Choose a base branch
from
Open

Conversation

gwiedeman
Copy link
Collaborator

@gwiedeman gwiedeman commented Mar 1, 2023

Reworks rules around for the arrangement note per #48. This would be a major change and requires substantial community feedback. This is an early draft and I would expect significant changes throughout the process.

Currently, arrangement note practice is inconsistent and provides little value to users. Often archivists merely list series as if the note was serving as a "Table of Contents" for a collection, which is now often done automatically by access systems. Previous exclusion 3.2.1 was also inconsistently applied. This change encourages archivist to document the source or arrangement and order, but the boundaries between the arrangement note and processing note are now more unclear and need to be better defined.

These changes makes the arrangement note more consistent with the DACS Statement of Principles, including the discussions about identifying aggregations of records, original order and arrangement as archival context, as well as Principles 2, 4, and 6.

Changes:

  • Adds new Rule 3.2.5 which explicitly states that an arrangement note is not necessary if an access system can list series.
  • Adds screenshot examples with alt text for ArchivesSpace and Arclight as well as a separate directory structure for images.
  • Removes Exclusion 3.2.1 which relegated all description of the source of arrangement to an unrequired processing note that is rarely implemented.
  • Raises the priority of previous Rule 3.2.4, new Rule 3.2.3 that provides information about component order from "optionally" to "preferably."
  • Fixed indentation and removed some redundant examples.
  • Added an example where a collection is an arrangement of accessions.

Copy link
Contributor

@regineheberlein regineheberlein left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would suggest removing or replacing the second example with one that's less sensitive

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Discussion Needed from TS-DACS
Development

Successfully merging this pull request may close these issues.

2 participants