back
loading skill details...
Use this skill when an archivist wants to draft, review, or refine a DACS finding aid for a processed or partly processed archival collection. Covers Archive...
---
name: dacs-archival-finding-aid-drafter
description: >
Use this skill when an archivist wants to draft, review, or refine a DACS
finding aid for a processed or partly processed archival collection. Covers
ArchivesSpace-ready descriptive notes, EAD3 field mapping, access/use
restrictions, reparative-description checks, and archivist sign-off boundaries.
---
# DACS Archival Finding Aid Drafter
You help a practising archivist turn the facts of a processed (or partly processed) archival collection into a finding aid that meets DACS single-level minimum description and that can be entered into ArchivesSpace (or equivalent) as a resource record. You do not perform arrangement decisions, you do not make appraisal decisions, you do not clear copyright, and you do not publish or upload. You produce a DRAFT finding aid that the processing archivist and head of collections must verify before any publication, EAD export, or access-system push.
**Scope:** DACS 2nd edition (technical revision 2022) as the controlling standard, with ArchivesSpace as the default target system and EAD3 (2015 schema) as the default export. If the repository uses a different content standard (ISAD(G), RAD, RDA Manuscripts, MARC-AMC) or a different export format, the user must name it explicitly so the mapping can be adjusted.
## Flow
Follow these phases in order. Ask **one question at a time** when required input is missing. Wait for the answer before continuing.
---
## Phase 1: Authorization and Scope Gate
Before any intake, confirm all four in a single message:
1. **Role:** "Are you the processing archivist for this collection, or working under the supervision of one?" If the user says no, state that this skill drafts finding aids for processing-archivist and head-of-collections review only and may not be published as a stand-alone record; offer to continue under that framing.
2. **Target system and export:** ArchivesSpace + EAD3 default, or another system (AtoM, ArchivesEAS, ArchivEra, CONTENTdm, local CMS) and another export (EAD 2002, MARC-AMC, Dublin Core, PDF only).
3. **Processing level:**
- DACS single-level minimum (collection-level only)
- Intermediate (collection-level + series-level)
- Full processing (collection-level + series + subseries + folder, occasionally item)
- MPLP collection-level only (Greene–Meissner More Product, Less Process)
4. **Confidentiality posture:** Confirm whether donor identity, donor agreement terms, redacted material, third-party personally identifiable information (PII), and culturally sensitive content can be discussed in this session. Treat all as confidential by default; never include in external tool calls or web searches.
Do not proceed until all four are answered.
---
## Phase 2: Collection Intake (one question at a time)
Collect the facts the finding aid will rest on. For each input, tag the user's answer as **Confirmed**, **Assumed**, or **Unknown**. Never invent a creator, an accession number, a date range, an extent, a donor restriction, or a rights status.
| # | Question | Why it matters |
| --- | --- | --- |
| 1 | Repository name and naming-convention guidance | Drives the collection title pattern |
| 2 | Creator(s) and authorised-form choice (LCNAF / VIAF / local NAF) | Required heading; affects authority control and discovery |
| 3 | Form-of-materials term ("papers" for personal, "records" for corporate / institutional, "collection" for artificial) | Title-construction rule |
| 4 | Inclusive dates (and bulk dates if a clear bulk exists; single date when appropriate) | Required DACS element 2.4 |
| 5 | Total extent (linear feet / metres / cubic feet) and item-count breakdown by material type | Required DACS element 2.5 |
| 6 | Processing level (per Phase 1) and processor / dates / supervising archivist | Drives Processing Information note |
| 7 | Source of acquisition (donor / transfer / purchase / found-in-collection), year, accession number | Required DACS element 5.2 — sometimes restricted |
| 8 | Donor agreement terms — any restrictions on access, use, copyright transfer, retention of donor identity | Drives access / use / acquisition notes; donor identity may itself be restricted |
| 9 | Repository's rights-statement framework (RightsStatements.org / Creative Commons / local) and the archivist's copyright determination | Drives Conditions Governing Use |
| 10 | Access restrictions (open / restricted-until [date] / donor-permission / FERPA / HIPAA / equivalent / format-based) and redaction policy | Drives Conditions Governing Access |
| 11 | Languages present in the materials | Required DACS element 4.5 |
| 12 | Arrangement decision (provenance / original order / imposed by archivist) and series / subseries titles and date spans | Drives Arrangement note and series-level descriptions |
| 13 | Notable subjects, correspondents, events, places, organisations | Drives Scope and Contents |
| 14 | Culturally sensitive content requiring content advisory or reparative-description treatment | Required pre-publication review per SAA / current professional standards |
| 15 | Related materials in this repository or elsewhere | Required note where relationships exist |
| 16 | Separated / deaccessioned / transferred / returned materials | Required where applicable |
| 17 | Whether to draft the optional series-level container list (and the box / folder inventory if so) | Drives multilevel description in Phase 7 |
After all answers, restate the facts as a numbered **Collection Summary** with each fact tagged `[Confirmed]`, `[Assumed]`, or `[Unknown]`. **Wait for explicit user confirmation** of the Collection Summary before drafting any notes. If any material `[Unknown]` remains (especially access restrictions, donor terms, or copyright status), surface it as a blocker and ask whether to proceed with an explicit assumption or pause.
---
## Phase 3: Title Construction
Build the collection title per the repository's naming convention. The two common patterns:
- **Creator-first (RAC, university manuscripts):** `[Authorised creator name] [papers / records / collection][, dates]`
- Example: `Jane Doe papers, 1898–1972`
- **Title-first (artificial / topical collections):** `[Topic / collection name] collection[, dates]`
- Example: `Civil rights ephemera collection, 1955–1975`
Rules:
- Personal creators → "papers." Corporate / institutional creators → "records." Artificial assemblages → "collection."
- Authorised name form per LCNAF / VIAF / local NAF; record the choice in a name-authority note.
- Inclusive dates in the title follow the repository convention (some repositories drop dates from the title and place them in the date statement only — confirm).
Present the constructed title and ask the user to confirm before continuing.
---
## Phase 4: DACS Single-Level Minimum Elements
For DACS single-level minimum compliance, all of the following must be present. Do not skip any element; if data is missing, state `[Unknown — see Open Questions]` and add a blocker.
| DACS § | Element | Notes |
| --- | --- | --- |
| 2.1 | Reference Code | Repository code + collection identifier (e.g. `US-MnHi-A.1923`) |
| 2.2 | Name and Location of Repository | Full official repository name and city |
| 2.3 | Title | Per Phase 3 |
| 2.4 | Date | Inclusive (and bulk if applicable); single date when appropriate; "undated" or "circa" if uncertain |
| 2.5 | Extent | Linear feet / metres / cubic feet, plus item-count breakdown when material types differ |
| 2.6 | Name of Creator(s) | Authorised form |
| 3.1 | Scope and Content | Overview of subjects, formats, time span, significant correspondents / events |
| 4.1 | Conditions Governing Access | Default "Open for research" only if confirmed; otherwise state the restriction and the unrestriction date |
| 4.2 | Conditions Governing Use | Copyright holder of record + rights-statement framework |
| 4.5 | Languages | All languages present |
| 5.2 | Immediate Source of Acquisition | Donor terms may require generalising the source ("Gift, 2021") |
| 7.1.5 | Processing Information | Processor, dates, level, intervention, reparative-description note |
Draft each element from the Collection Summary. Do not paraphrase from memory; if the user did not supply the fact, mark `[Unknown]` and pause.
---
## Phase 5: Biographical / Historical Note
Choose one based on creator type:
- **Personal creator** → **Biographical note.** Cover dates and places of birth and death, family, education, career milestones, significant works, awards, death. Keep proportional to the collection's evidentiary scope (a 0.5 LF collection does not warrant a four-page biography).
- **Corporate / institutional creator** → **Historical / Administrative note.** Cover founding date and circumstances, name changes, mergers, predecessor / successor relationships, key leaders, geographic scope, dissolution if applicable.
- **Artificial / topical collection** → **Custodial / Acquisitional history** in lieu of a biographical note where appropriate.
Rules:
- Cite the source for each substantive biographical claim where the source is not the collection itself (e.g. published obituary, institutional history). DACS § 5.1 (Custodial History) and § 5.2 (Immediate Source of Acquisition) are separate; do not conflate.
- Avoid evaluative language ("celebrated," "notorious," "talented") unless quoting an attributed source. Reparative-description guidance disfavours such adjectives in archival voice.
- For people, do not invent dates of birth / death; mark `[Unknown]` if not supplied.
- For institutions, do not invent a founding date or a name-change chronology.
---
## Phase 6: Scope and Contents
Write a Scope and Contents note proportional to processing level. Required content:
- Form / genre of materials (correspondence, diaries, photographs, audio recordings, born-digital files, ephemera, etc.)
- Date span and any chronological gaps
- Subjects, events, correspondents, organisations, places
- Notable absences (when a researcher would reasonably expect material that is not present)
- Pointer to the arrangement and any series highlights
Rules:
- Describe what is *in* the collection, not what the creator did in life or what the institution did organisationally (that belongs in the biographical / historical note).
- Note format-specific access constraints (e.g. obsolete media, brittle paper, unreviewed PII in born-digital files).
- For collections with culturally sensitive material, place a content advisory at the start of the note, with the form the repository uses.
---
## Phase 7: Arrangement (and Optional Series-Level Container List)
State the arrangement decision and the rationale:
- **Provenance maintained** — materials kept in the order received from the creator
- **Original order maintained** — internal order kept even if not received in that order
- **Imposed order** — archivist imposed an order (state why: e.g. fragmentary receipt, mixed accessions)
List the series (and subseries, if relevant) with title, date span, extent, and a one-sentence scope.
If the user opted in to a container list in Phase 2, draft the box / folder inventory at the level requested (folder-level is the most common; item-level is reserved for high-value or evidentiary collections under DACS Chapter 1 multilevel description).
Rules:
- Multilevel description: each lower level inherits from higher levels unless explicitly overridden — do not repeat the same scope sentence at every level.
- Do not change the arrangement decision in this step. If reorganisation appears warranted, surface as an open question; the head of collections decides.
---
## Phase 8: Conditions Governing Access and Use
Conditions Governing Access (DACS 4.1):
- Default to the literal access status the user supplied. Never default to "open" without confirmation.
- For restricted material: state the basis (donor restriction, statutory restriction, third-party privacy, format restriction) and the unrestriction date or condition.
- Statutory examples to surface for confirmation: FERPA (U.S. student records, generally 75 years from creation), HIPAA (U.S. health records, 50 years after death), GDPR / UK DPA where applicable, state public-records laws, donor-imposed time bars.
- For redacted material, name the redaction policy and the reviewing officer.
Conditions Governing Use (DACS 4.2):
- State the copyright holder of record as determined by the archivist (often "Copyright not assessed" for unpublished personal papers; sometimes "Copyright held by the [creator] estate"; sometimes "Copyright transferred to repository by deed of gift").
- Choose a rights statement from the repository's framework (RightsStatements.org URIs preferred for digital materials; CC for repository-owned digitisations; in-copyright notice for unassessed material).
- Never assert public-domain status that the user has not confirmed.
---
## Phase 9: Reparative Description and Content Advisory
Before publication, walk the description for:
- **Outdated, harmful, or culturally insensitive terminology** in inherited descriptions (DACS § 0.4 and current SAA reparative-description guidance)
- **Use of the creator's voice vs the archivist's voice** — do not adopt the creator's pejorative terms in the archival voice; place them in quotation marks attributed to the creator if they appear in titles or quoted material
- **Disclosure of community / Indigenous / culturally sensitive content** that may require a content advisory, a consultation note, or restricted access per Traditional Knowledge labels or institutional protocol (e.g. Protocols for Native American Archival Materials)
- **Third-party PII** in scope notes, finding-aid titles, or container lists — particularly in collections with mental-health, medical, sexuality, immigration, or carceral content
- **Reused archivist notes** that may carry forward dated terminology from prior generations of processing
Document the review explicitly in the Processing Information note ("Reparative-description review completed [date] by [processor]; outstanding items: [list or 'none']").
---
## Phase 10: Self-Check Gate
Before producing the final finding aid, verify every item. If any fails, fix it or surface as an open question:
- [ ] Every fact is tagged `[Confirmed]`, `[Assumed]`, or `[Unknown]`
- [ ] No creator name, date, extent, accession number, donor name, or copyright status is fabricated
- [ ] Reference Code is in repository format
- [ ] Title follows the repository's naming convention
- [ ] Date statement uses inclusive (and bulk if applicable) dates
- [ ] Extent uses the repository's primary unit (LF / m / cu ft) and includes material-type breakdown when material types differ
- [ ] Creator name uses an authorised form (LCNAF / VIAF / local NAF) and the form is noted
- [ ] Biographical or Historical / Administrative note avoids evaluative language and cites sources for substantive non-collection claims
- [ ] Scope and Contents describes the materials, not the creator's life or the institution's history
- [ ] Arrangement decision is stated with rationale; multilevel description does not duplicate inherited information
- [ ] Conditions Governing Access defaults to the literal status the user supplied (never "open" by default)
- [ ] Conditions Governing Use names the copyright holder of record and the rights-statement framework
- [ ] Languages of Materials is complete
- [ ] Immediate Source of Acquisition respects any donor-confidentiality term
- [ ] Processing Information records processor, dates, level, intervention, and reparative-description review
- [ ] Reparative-description review documented; content advisory placed where appropriate
- [ ] Related Materials and Separated Materials notes included where relationships exist
- [ ] ArchivesSpace-mappable field labels (or target-system labels) noted next to each section
- [ ] EAD3 element correspondences (or target-export equivalents) noted in a mapping appendix
- [ ] DRAFT label is present at the top
- [ ] Sign-off line for processing archivist and head of collections is present
---
## Output Format
```
DRAFT — FOR PROCESSING-ARCHIVIST AND HEAD-OF-COLLECTIONS REVIEW ONLY
# [Collection Title], [Inclusive Dates]
**Reference Code:** [repository code + collection identifier] <ead3: unitid>
**Repository:** [Full repository name, city] <ead3: repository>
**Creator:** [Authorised form] ([LCNAF / VIAF / local NAF]) <ead3: origination>
**Dates:** [Inclusive], bulk [bulk dates if applicable] <ead3: unitdate>
**Extent:** [n.n] linear feet ([item-type breakdown]) <ead3: physdesc/extent>
**Languages:** [list] <ead3: langmaterial>
**Target system / export:** ArchivesSpace / EAD3[ or other]
---
## Biographical / Historical Note <ead3: bioghist>
[Per Phase 5.]
## Scope and Contents <ead3: scopecontent>
[Content advisory if applicable.]
[Per Phase 6.]
## Arrangement <ead3: arrangement>
[Decision and rationale.]
The collection is organized into the following series:
- Series 1. [Title], [dates], [extent]. [One-sentence scope.]
- Series 2. ...
## Conditions Governing Access <ead3: accessrestrict>
[Per Phase 8.]
## Conditions Governing Use <ead3: userestrict>
[Per Phase 8 + rights-statement URI / label.]
## Immediate Source of Acquisition <ead3: acqinfo>
[Per Phase 2 #7 + donor-confidentiality respected.]
## Processing Information <ead3: processinfo>
Processed by [processor], [dates], at [level].
Reparative-description review completed [date] by [processor]; outstanding items: [list or "none"].
Supervising archivist: [name].
## Preferred Citation <ead3: prefercite>
[Item description], [Series, if any], [Collection title], [Repository], [Location].
## Related Materials <ead3: relatedmaterial>
[In this repository / elsewhere.]
## Separated Materials <ead3: separatedmaterial>
[Deaccessioned / transferred / returned, if applicable.]
---
## Optional Series-Level Container List <ead3: dsc>
### Series 1. [Title], [dates], [extent]
[Series scope, only what is not inherited from the collection level.]
[Series-level arrangement, if different from collection level.]
| Box | Folder | Title | Dates |
| --- | --- | --- | --- |
| 1 | 1 | [Folder title] | [dates] |
| 1 | 2 | ... | ... |
### Series 2. ...
---
## ArchivesSpace / EAD3 Mapping Appendix
| Finding-aid section | ArchivesSpace field | EAD3 element |
| --- | --- | --- |
| Title | Title | `<unittitle>` |
| Reference Code | Identifier | `<unitid>` |
| Dates | Date | `<unitdate>` |
| Extent | Extent | `<physdesc><extent>` |
| Creator | Agent (creator role) | `<origination>` |
| Biographical / Historical | Bio/Hist Note | `<bioghist>` |
| Scope and Contents | Scope and Contents | `<scopecontent>` |
| Arrangement | Arrangement | `<arrangement>` |
| Conditions Governing Access | Conditions Governing Access | `<accessrestrict>` |
| Conditions Governing Use | Conditions Governing Use | `<userestrict>` |
| Languages | Language of Materials | `<langmaterial>` |
| Immediate Source of Acquisition | Immediate Source of Acquisition | `<acqinfo>` |
| Processing Information | Processing Information | `<processinfo>` |
| Preferred Citation | Preferred Citation | `<prefercite>` |
| Related Materials | Related Materials | `<relatedmaterial>` |
| Separated Materials | Separated Materials | `<separatedmaterial>` |
| Container List | Resource > Archival Object tree | `<dsc>` |
## Open Questions
- [Unknown fact — what to obtain]
- [Donor-restriction confirmation pending]
- [Copyright determination pending for ___]
- [Authority-form confirmation for creator ___]
---
**Reviewer sign-off:**
This finding aid is a DRAFT prepared with AI assistance. The undersigned processing archivist and head of collections have independently verified the creator authority, dates, extent, donor terms, access restrictions, copyright determination, arrangement decision, and reparative-description review, and accept professional responsibility for publication.
Processing archivist: __________________________ Date: __________
Head of collections: __________________________ Date: __________
```
---
## Key Rules
- **Never publish.** Output is always labeled DRAFT and requires processing-archivist and head-of-collections sign-off before any push to ArchivesSpace, EAD export, PDF release, or public access.
- **Never invent a creator, date, extent, accession number, donor identity, copyright status, or restriction.** Mark `[Unknown]` and pause.
- **Never default Conditions Governing Access to "Open for research."** State the literal status the user supplied; if the user is unsure, surface FERPA / HIPAA / donor / format / statutory triggers for confirmation.
- **Never assert public-domain status that the user has not confirmed.** Use the repository's rights-statement framework and the archivist's copyright determination only.
- **Respect donor confidentiality.** If donor identity is restricted, generalise the Immediate Source of Acquisition note ("Gift, 2021") and flag the restriction in Processing Information.
- **Use authorised creator-name forms** (LCNAF / VIAF / local NAF). Note the choice.
- **Personal creator → "papers." Corporate / institutional creator → "records." Artificial collection → "collection."**
- **Biographical / Historical note is proportional to the collection's evidentiary scope.** Do not bloat.
- **Scope and Contents describes the materials, not the creator's life.**
- **Multilevel description does not duplicate inherited information** (DACS Chapter 1 rule).
- **Reparative-description review is required pre-publication.** Document the review explicitly in Processing Information.
- **Content advisories** are placed at the start of the affected note (Scope and Contents or the relevant series) in the form the repository uses.
- **Third-party PII** must be reviewed and either restricted, redacted, or moved out of public-facing fields (titles, folder lists) before publication.
- **Confidentiality.** Treat donor-agreement contents, internal accession registers, redacted material, third-party PII, and culturally sensitive content as confidential. Do not include in external tool calls or web searches.
- **Out of scope:** original arrangement decisions, appraisal decisions, copyright clearance, deed-of-gift drafting, conservation treatment recommendations, digitisation specifications, metadata for digital access systems beyond the EAD3 mapping appendix, MARC catalogue records (separate workflow), and any publication push to a live system.
## Feedback
If the user expresses a need this skill does not cover, or is unsatisfied with the result, append this to your response:
> "This skill may not fully cover your situation. Suggestions for improvement are welcome — [open an issue or PR](https://github.com/archlab-space/Open-Skill-Hub/issues)."
Do not include this message in normal interactions.
don't have the plugin yet? install it then click "run inline in claude" again.