Community decisions and responsibilities
Consider who should take part in archive work, how decisions are made, and how material should be cared for.
An archive brings together material, knowledge and responsibilities. Describing a recording, acknowledging contributions or choosing who can read a record may involve different people and different kinds of knowledge.
Each community decides how to organize its archive work. People, families and communities connected with particular material may also have responsibilities that guide how it is described and used.
Kiskemisowin supports this work through permissions, review and access settings. The people responsible for the archive give those controls their purpose.
Agree how the work is shared
Archive work can include:
- Gathering information and preparing descriptions.
- Acknowledging the people and communities involved.
- Checking names, dates, sources and uncertain details.
- Reviewing proposed changes and seeking relevant guidance.
- Maintaining information reused across records, such as names, languages and places.
- Reviewing access and responding to requests for correction or removal.
These responsibilities can be shared in different ways. One person may carry several, and the people involved may change depending on the material.
When these guides refer to contributors, reviewers or people maintaining the archive, they describe work being done. They do not prescribe community positions or a fixed way of organizing responsibilities.
Decide whose guidance is needed
Before describing or sharing material, consider who has relevant knowledge, authority or responsibility.
The person entering information may need guidance from others about names, meaning, attribution, access or appropriate use. Permission to work in the application does not settle those questions.
Useful questions to discuss include:
- Who should guide how this material is described and whose contributions are acknowledged?
- Who can authorize access or reuse, and what should happen when that authority is unclear?
- What needs to be checked before publication, and how will differing interpretations or disagreements be handled?
- Who should respond when someone requests a correction, restriction or removal?
Use these questions in a way that fits the relevant community’s decision-making practices and the responsibilities connected with the material.
Connect decisions with application controls
Once responsibilities are agreed, application access can support the work.
| Decision | How Kiskemisowin supports it |
|---|---|
| Who can prepare and correct records? | Working permissions allow people to create records and edit drafts. |
| Who can submit and review changes? | Separate permissions allow people to submit, approve or reject changes. |
| Who can read published material? | Visibility settings and audience membership control published reading access. |
| Who can maintain information used across records? | Catalog permissions allow people to manage entries such as Directory names, languages and places. |
A person with Root access—the application’s special system administration authority—manages permission groups and their membership.
An account’s permissions determine what it can do in the software. They do not establish expertise, cultural authority or permission to use material.
Contributor credits serve a different purpose again: they acknowledge contributions without granting application access.
See Understanding access and sharing for how working permissions, reading access and guidance about using material differ.
Understand what approval records
Review allows someone with the required permission to approve or reject a submitted change.
The current workflow accepts one authorized approval. It also allows someone with the necessary permissions to approve their own submission.
If your process requires several people to agree, or a reviewer who did not prepare the record, arrange that consultation and division of work before the application decision.
Approval records a decision in Kiskemisowin. It does not automatically record the conversations behind it or establish that consent, rights ownership or cultural responsibilities have been confirmed.
Rights information and cultural guidance can help communicate how material should be treated. The people responsible for the work still need to consider and follow that guidance.
Keep responsibilities current
An archive’s needs can change as people contribute knowledge, take on responsibilities or leave the work.
Agree who will:
- Maintain shared names and other descriptive information.
- Review working permissions and audience memberships.
- Respond to corrections, concerns and requests to change access.
- Maintain the installation and help people when something goes wrong.
Keeping material available over time also needs practical arrangements for ongoing care and responding to loss or interruption. Make those arrangements—and their limits—clear to the people relying on the archive.
Using Kiskemisowin supports parts of this work. The responsibilities and agreements around it need continuing attention.
Next: understanding archive records
Continue with Understanding archive records to see how descriptions, files, people and surrounding information come together in a record.