Another consideration for the entry of date information includes the exact format or sequence with which it is entered into a record. For example, today's date can be described:
February 23, 2014
February 23, '14
Feb 23, 2014
23 February, 2014
2/23/14
2/23/2014
23/2/14
23/2/2014
2-23-14
2.23.14
And that just scratches the surface of variations possible, not to mention factoring in foreign languages. So which format does a metadata creator use to ensure that the date is adequately understood by potential users? Accounting for regional differences in date presentation, and the fact that computers can't even interpret some of the variations, there is no perfect solution. The W3CDTF encoding scheme is one possible solution, and prescribes the use of the YYYY-MM-DD format for single dates. Whichever method is settled upon by the metadata creator, however, the importance of consistency in date entry can not be overstated.
This is why I am so fascinated with the date element. Who would have thought it would be this complicated. What about date ranges? I picked date as my first choice for DC elements.
ReplyDeleteI imagine this will be even more complicated when dealing with objects that are 3-4 years old having been reated near the end of each respective year. You get things like 11-12-10, which could mean that something was created on December 11, 2010. Or is it November 12, 2010? Or perhaps December 10, 2010? I hope that there are clear rules for disambiguating this stuff further.
ReplyDelete"date" is my favorite DC element because of eye-popping complexities underneath the surface!
ReplyDelete--Dr. MacCall