acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ...

ANSI/NIST-ITL 1-2011 - UPDATE 2013 DRAFT VERSIONooDeletedCorrupted• event reason / EVR is the second information item. It states the rationale behind theEvent that occurred. This information item is optional and should be populated withalphanumeric text with special characters up to 200 characters.• information identifier / IID is the third information item. It is mandatory andidentifies the field/subfield/information item that has been affected by the Event. It isdefined as the concatenation of the IDC, a comma, the Field Number in the standard, acomma, the repeat count of the subfield (default = NA), a comma, and the informationitem mnemonic (if it exists).If a repeating subfield or information item does not exist, enter a “NA”. Examples:ooo17,10.014,NA,BBC3,9.373,4,NA8,10.024,2,QVUFor the case when a repeated subfield is removed, the entry for the repeat fieldnumber is the original repeat set count, preceded by a negative; theinformation item mnemonic is entered as “NA”. When an information item isremoved, the mnemonic is preceded by a negative. When an optional field isremoved, the field number is preceded by a minus. Even though subfields andinformation items may have been in the field, the field number is followed by“NA,NA” so that the subfields and information items do not have to beindividually listed.ooo12,10.024,-2,NA6,18.016,NA,-AL35,-14.024,NA,NA• agent / AGT is the fourth information item. It is mandatory and shall containinformation describing the entity (Agent) responsible for the EVT that affected theobject identified by the IID. It is an alphanumeric entry of up to 200 characters withspecial characters allowed.• old value / OLD is the fifth information item. It is optional. When used, it shallcontain the original value of the location in the transaction referenced in IID before itwas affected by the event (EVT).8.23.9 Field 98.901 Audit revision number / ARNThis field is mandatory if Field 98.900: Audit log / ALF appears in the record. Itcontains a unique reference to the revision within the revision history. It is numeric,with up to 3 digits. For example, Revision 1 shall be encoded as 1; Revision 88 as 88.Revision “x” may contain multiple events, each of which is recorded as a discreteMay, 2013 DRAFT VERSION UPDATE 2013 Page 427