|
|
|
|
|||||||||
|
VERS STORY | STANDARD | ASSESSMENT | PROJECTS | DIGITAL ARCHIVE | TRAINING | TOOLKIT | PUBLICATIONS | |
|
|||||||||
|
|||||
|
3.10 Date A Date (M54) element contains three dates of relevance to the record: Date/Time Transacted (M56); Date/Time Created (M55); and Date/Time Registered (M57). Experience has shown that the purpose of these three elements is not clear. The Date/Time Transacted (M56) is the date and time the event documented by the record occurred. Consider a meeting as an example. The Date/Time Transacted is the time the meeting occurred. The Date/Time Created (M55) is the date and time the record was created. The record of the meeting is the minutes, and the Date/Time Created of the meeting record is the time the minutes were prepared. This would normally be some time after the Date/Time Transacted (M56). The Date/Time Registered (M57) is the date and time the record was registered with the recordkeeping system. The Date/Time Registered of the meeting record is the time the minutes were registered into the recordkeeping system. The Date element is equivalent to the AGLS Date element.
Figure 11. Subelements of the Date element. The subelements of Date are:
All three dates are mandatory and must appear in every VERS record. Often, the only definitely known date is the Date/Time Registered (M57), which is normally recorded automatically by the recordkeeping system. The Date/Time Transacted (M56) and Date/Time Created (M55) are normally entered by the user at the time of registration and may not be known. In this case they normally default to be the same as Date/Time Registered (M57). The recordkeeping system should not over-specify the time. If only the date of the event is known the time should not be entered (see the Date/Time Transacted in the following example). An example of the XML representation of a Date follows: <naa:Date> | |||||
 |
 |
|
