Giters

saa-ts-dacs / dacs

Describing Archives: A Content Standard

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

What activities does Principle 6 require to be documented?

regineheberlein opened this issue · comments

commented

Links to related tickets

I expect that this will require a

  • Minor change to DACS
  • Major change to DACS

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

Principle 6

commented

This ticket is currently blocking #69, #70, #72, #73, #92

commented

Summary of viewpoints:

  • general agreement that this encompasses major / substantive actions, not e.g. fixing typos
  • general agreement that this is applies equally to initial processing and description as well as changes to either over time
  • general agreement that more guidance is needed to define "major" or "substantive"
commented

What needs to happen to move this ticket forward:

  • consensus on what rises to the level of needing to be documented, in particular with respect to changes

A proposal from #70 focuses on changes that affect meaning and reads in part:

Substantive changes may be understood as those edits that affect the identity of resources or re-contextualize or otherwise significantly affect the information as it was previously presented.

Examples of edits that affect the identity of resources include changes to title, call number, or any other identifying information.

Examples of edits that re-contextualize information include the addition or removal of or to notes, dates, or controlled access terms; intellectual re-arrangement; wording changes to remove harmful language or change the description reparatively; or any edits however minor that alter the meaning of what was previously recorded.