RMA System filePlanUnique ensures that within and RMA system, each file plan is given a unique identifier. RMA system type. DoD 5015.2 6-19-2002 C2.T1 DoD 5015.2 6-19-2002 C2.T1 DoD 5015.2 6-19-2002 C2.T1.5 DoD 5015.2 6-19-2002 C2.T1.4 DoD 5015.2 6-19-2002 C2.T1 recordeFolderUnique ensures that within each record category, record folders are given unique identifiers. recordUnique ensures that within each record category, records are given unique identifiers. DoD 5015.2 6-19-2002 C2.T1.9 DoD 5015.2 6-19-2002 C2.T1 DoD 5015.2 6-19-2002 C2.T1.1 DoD 5015.2 6-19-2002 C2.T1.3 DoD 5015.2 6-19-2002 C2.2.2.1. dispositionPhaseUnique ensures that within a disposition schedule, each disposition phase is assigned a unique identifier. Disposition phases, should, in addition, be assigned sequential identifiers. Disposition phases should be executed in the order indicated by their identifiers starting with the phase with the smallest value for its identifier. Assignment of sequential identifiers, and ordered execution of phases are not currently enforced by this schema. DoD 5015.2 6-19-2002 C2.T1.6 DoD 5015.2 6-19-2002 C2.T1.7 DoD 5015.2 6-19-2002 C2.T1.8 Note that this field should be mandatory when vitalRecordIndicator = 1 and null otherwise. This is currently not enforced in the schema. DoD 5015.2 6-19-2002 C2.2.6.7.2 This field should be null unless vitalRecordIndicator = 1. DoD 5015.2 6-19-2002 C2.T2.1 DoD 5015.2 6-19-2002 C2.T2.1 DoD 5015.2 6-19-2002 C2.T1.2 DoD 5015.2 6-19-2002 C2.T2 DoD 5015.2 6-19-2002 C2.T2.1.1 DoD 5015.2 6-19-2002 C2.T1.1.3 If the record is stored in the RMA repository, then this field shall contain the full path to the record within the RMA system. DoD 5015.2 6-19-2002 C2.T1.1.4 DoD 5015.2 6-19-2002 C2.T2.1.5 Note that this field should be mandatory when vitalRecordIndicator = 1 and null otherwise. This is currently not enforced in the schema. DoD 5015.2 6-19-2002 C2.2.6.7.2 This field should be null unless vitalRecordIndicator = 1. DoD 5015.2 6-19-2002 C2.2.6.2.1 DoD 5015.2 6-19-2002 C2.2.6.4.1 DoD 5015.2 6-19-2002 C2.T2.1.6 DoD 5015.2 6-19-2002 DL1.1.68 DoD 5015.2 6-19-2002 C2.T2.1.7 DoD 5015.2 6-19-2002 C2.T2.1.2 DoD 5015.2 6-19-2002 C2.T3 Record versioning as described in DoD 5015.2 6-19-2002 C2.2.3.20 can be accomplished using the successor, alternateRendition, version, and alternateVersion fields. Future work on this schema should include an investigation of alternatives for improved versioning support. DoD 5015.2 6-19-2002 C2.T3.3 This field shall be used to contain the subject line from email and other correspondance or to contain a subject description for other untitled documents. This field shall be used to contain the title of any document with a defined title. DoD 5015.2 6-19-2002 Ct.T3.9 This field may contain either the name of the author (document creator) or originator (document issuer). The originator shall be identified by the name of a person, an official title, an office symbol or a code. DoD 5015.2 6-19-2002 C2.T3.12 DoD 5015.2 6-19-2002 Ct.T3.6 This field shall be automatically completed by the RMA system at the time the record is entered into the system. This field shall not be editable by the user. DoD 5015.2 6-19-2002 Ct.T3.7 DoD 5015.2 6-19-2002 Ct.T3.8 DoD 5015.2 6-19-2002 C2.2.6 DoD 5015.2 6-19-2002 C2.2.6.4.1 DoD 5015.2 6-19-2002 C2.T3.13 DoD 5015.2 6-19-2002 C2.T3.5 This field shall be used to contain a description of the format in which the record is stored. Examples of formats include: paper (may specify a particular if format e.g. Form 3120, v.2.2), MS Word 2000, VHS NTSC, Dobly Digital Audio, MS Excel v 3.2, etc. DoD 5015.2 6-19-2002 C2.T3.4 This field shall be used to contain a description of the media on which the record is stored. Examples of media types include: paper, CD-ROM, microfiche, permanent magnetic disk (hard drive), video cassette, magnetic tape, removable magentic disk (floppy disk), etc. Although this schema allows this field to contain an arbitrary string, implementers of RMA systems based on this schema may wish to limit the media choices available to the system's users. DoD 5015.2 6-19-2002 C3.T3.10 This field shall be mandatory for all email and other correspondence records. DoD 5015.2 6-19-2002 C2.T3.11 This field shall be mandatory for email and other correspondence which contain secondary addressees. DoD 5015.2 6-19-2002 C2.T3.14 DoD 5015.2 6-19-2002 C2.T3.15 Note that this field should be mandatory when vitalRecordIndicator = 1 and null otherwise. This is currently not enforced in the schema. DoD 5015.2 6-19-2002 C2.2.6.7.2 This field should be null unless vitalRecordIndicator = 1. DoD 5015.2 6-19-2002 C2.2.3.20 DoD 5015.2 6-19-2002 C2.2.3.18 The RMA system shall ensure that this field contains the ID of a record which exists in the RMA system. DoD 5015.2 6-19-2002 C2.2.3.20 The RMA system shall ensure that this field contains the ID of a record which exists in the system DoD 5015.2 6-19-2002 C2.2.3.19 The RMA system shall ensure that this field contains the ID of a record which exists in the system. DoD 5015.2 6-19-2002 C2.2.3.17 The RMA system shall ensure that this field contains the ID of a record which exists in the RMA system. DoD 5015.2 6-19-2002 C2.2.3.17 This field shall contain text data consisting of actual supporting data or a description of the location of the supporting data (e.g. a URL). DoD 5015.2 6-19-2002 C2.T3.2 DoD 5015.2 6-19-2002 C2.T3.16 DoD 5015.2 6-19-2002 C2.T3.1 DoD 5015.2 6-19-2002 DL1.1.95 Selection of this field indicates that the record or records with which this field is associated should next be reviewed and updated on the date contained in this field. Selection of this field indicates that the record or records with which this field is associated should be reviewed on a periodic basis as defined by this field. DoD 5015.2 6-19-2002 DL1.1.33 It is unlcear from DoD 5015.2 6-19-2002 whether disposition instructions serve any purpose other than to associate disposition schedules with record categories. If disposition instructions contain no other data, then it not necessary to have a specific field for disposition instructions. A list of record categories and their associated disposition schedules can be easily generated from the record categories themselves. Each instance of this element identifies a record category, and the disposition schedule which applies to that record category. DoD 5015.2 6-19-2002 C2.2.2.1 This field should contain the ID of a record category which exists in the file plan to which this categorySchedulePair belongs. Currently this requirement is not enforced by this schema. This field should contain the ID of the dispositionSchedule which belongs to the record category identified by the recordCategory field in this categorySchedulePair. Currently this requirements is not enforced by this schema. DoD 5015.2 6-19-2002 C2.2.2.1 DoD 5015.2 6-19-2002 C2.2.2.2 This attribute is used to identify the order in which the disposition phases within a particular disposition schedule occur. DoD 5015.2 6-19-2002 C2.2.2.2 DoD 5015.2 6-19-2002 C2.2.2.4 This choice identifies the type of cutoff and disposition instruction, and the information required for compliance with each. DoD 5015.2 6-19-2002 C2.2.2.3.2 DoD 5015.2 6-19-2002 C2.2.2.3.3 Note that this field should be mandatory when dispositionAction = Interime Transfer or dispositionAction = Accession and null otherwise. This is currently not enforced in the schema. DoD 5015.2 6-19-2002 C2.2.2.4.1 DoD 5015.2 6-19-2002 C2.2.2.4.2 DoD 5015.2 6-19-2002 C2.2.2.4.3 DoD 5015.2 6-19-2002 C2.2.2.3 Selection of this field indicates that the records in this category shall be cutoff on a particular day defined by the content of this field. For example, if this field contains 'end of month', then records in this category shall be cutoff on the last day of the current month, and on the last day of each following month. Selection of this field indicates that the records in this category shall be cutoff on a periodic basis as defined by the content of this field. For example, if this field contains '7 weeks' then records in this category shall be cutoff seven weeks from the start date and every seven weeks thereafter. DoD 5015.2 6-19-2002 C2.2.2.3.1 Selection of this field indicates that the record is to be retained until the next occurrence of the date indicated by the content of this field. For example, if this field indicates 'end of calendar year' then the record is eligible for disposition on December 31 of the current year. Selection of this field indicates that the record is to be retained for the duration specified by the content of this field. The start date is assumed to be the cutoff date. For example, if this field contains '3 months' then the record is eligible for disposition 3 months from the cutoff date. This type allows cutoff or retention periods to be defined to occur on particular days, such as end of month, end of of fiscal year, etc. This choice allows the user to select between the end of an identifiable period (e.g. end of month), a described day within the month (e.g. first Monday), a particular date within the month (e.g. 15th of the month), a particular day within the year (e.g. March 12), or a single, fixed date. Date of month fixed dates are permitted to include day 1 to day 31. For months which contain fewer than 31 days, the RMA system shall treat this date as the latest possible day which remains in the month, and which has a date less than or equal to the date contained in this field. for example, if this field contains the value '30', then in February of a non-leap-year, the RMA system must treat this field as if it contains '28'. This type allows cutoff or retention periods to be defined to occur on a periodic basis such as every 3 months, every year, or every 10 years. When this field is a component of a retention period, the RMA shall automatically set this date to the date of cutoff for the record folder. This type allows fixed days to specified by describing a day of the month (e.g. first Monday, second Thursday, or last Friday). DoD 5015.2 6-19-2002 C2.2.6.4.1 This type allows users to specify that a folder or record has been extended or frozen, and why. Identifies that a record or folder is frozen and identifies the reason. DoD 5015.2 6-19-2002 C2.2.6.4.2 Identifies that a record or folder is extended, may indicate reason, or extension date. This field is not specified in DoD 5015.2 6-19-2002. This field is not specified in DoD 5015.2 6-19-2002. DoD 5015.2 6-19-2002 DL1.1.92 This schema implements DoD5015.2, 6/19/2002. Except where noted, it includes all mandatory requirements which can be enforced through the XML schema; it does not address non-mandatory features such as support for metadata related to classified material.