Status: Accepted
Owner: [email protected]
Labels: Type-Defect Priority-Medium

New issue 1984 by [email protected]: Remove system enforcement of custodial history as mandatory (RAD template)
http://code.google.com/p/qubit-toolkit/issues/detail?id=1984

Currently, a warning message appears in the RAD template if custodial history is not populated, although there is no asterisk in the template.

While it is understandable why things were implemented this way, RAD actually indicates that custodial history should *not* be populated when the material is received directly from the creator. Indeed, this is a source of common confusion, so including this error message may prompt users to incorrectly use custodial history instead of immediate source of acquisition.

The excruciating details... The closest RAD comes to identifying mandatory elements is through the "levels of detail in the description." Custodial history is indeed included here, but this needs to be read in the context of the more general instruction "Include this minimum set of elements for all materials described at the chosen level **when the elements are applicable** to the unit being described ..." (emphasis added). In the case of custodial history, the applicable rule is "When the unit being described is acquired directly from the creator, record this information in the Note Area (see 1.8B12)." (referring to Immediate Source of Acquisition) This is made somewhat clearer in RAD Revealed: "If the unit being described has been acquired directly from the creator, do not include a custodial history in the description."

There are more general issues relating to mandatory fields in RAD, but the custodial history case should be changed in the meantime. See meeting notes: http://qubit-toolkit.org/wiki/index.php?title=Meeting_20110504

--
You received this message because you are subscribed to the Google Groups "Qubit 
Toolkit Issues" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/qubit-issues?hl=en.

Reply via email to