<div>Hi Richard,</div> <div> </div> <div>Dublin core suggests the encoding rules to be applied to data values.</div> <div> </div> <div>For any element that has dates it suggests the W3C-DTF - <A href="http://www.w3.org/TR/NOTE-datetime">http://www.w3.org/TR/NOTE-datetime</A> </div> <div> </div> <div>there are many values in the w3c scheme.</div> <div> </div> <div>We at NLB have tried to implement it based on information available during cataloging.</div> <div> </div> <div>for example - </div> <div> </div> <div>YYYY format if the complete date of the resource is not available, but only the year</div> <div> </div> <div>YYYY-MM if the exact day of the resource is not available</div> <div> </div> <div>YYYY-MM-DD if the exact date is known</div> <div> </div> <div>So I agree with Mr Scott, DSpace might not validate the value, unless you have strict validation rule for the data values that have been
input.</div> <div> </div> <div>to summarise, any format that falls in the w3c-dtf scheme should be good.</div> <div> </div> <div>regards,</div> <div>Ganesh Yanamandra</div> <div>Project Manager, Digital Resources & Services,</div> <div>National Library Board, Singapore</div> <div><BR><BR><B><I>Scott Yeadon <scott.yeadon@anu.edu.au></I></B> wrote:</div> <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Hi Richard,<BR><BR>It's up to you how you represent your values, you could use the DCMI <BR>Period or something simple such as "1930-1940". We tend to have the <BR>latter since that's what our users typically enter. The batch import <BR>process won't parse the values, as long as the document is valid XML the <BR>values will be accepted.<BR><BR>Scott.<BR>> Message: 3<BR>> Date: Fri, 08 Jun 2007 12:08:16 +1200<BR>> From: Richard MAHONEY <R.MAHONEY@ICONZ.CO.NZ><BR>> Subject:
[Dspace-general] DSpace `Dublin Core' | Date Issued | Date<BR>> Range | How to represent<BR>> To: DSpace Tech <DSPACE-TECH@LISTS.SOURCEFORGE.NET>, DSpace General<BR>> <DSPACE-GENERAL@MIT.EDU><BR>> Message-ID: <1181261296.8680.21.camel@proliant><BR>> Content-Type: text/plain<BR>><BR>> Dear List Members,<BR>><BR>> I am in the process or preparing material for bulk import and have<BR>> again encountered and issue that I was inclined to gloss over last time<BR>> it arose: the format of the DSpace Dublin Core Date Elements,<BR>> Qualifiers, and particularly, the Values.<BR>><BR>> What exactly is the required Value format and is it configurable?<BR>> Simple date Values such as the following present no difficulty:<BR>><BR>> <DCVALUE qualifier="issued" element="date">1970</DCVALUE><BR>><BR>> The trouble for me -- and this situation would arise often for many<BR>> projects -- is how to correctly represent date
ranges, for e.g., date<BR>> issued, 1964 to 1970. Which Value format should should be used to<BR>> represent a date range in DSpace DC? Some DSpace version of the<BR>> W3C-DTF/ISO 8601 scheme?<BR>><BR>> http://dublincore.org/documents/2000/07/28/dcmi-period/<BR>><BR>><BR>> Best regards,<BR>><BR>> Richard Mahoney<BR>><BR>><BR>> <BR><BR>_______________________________________________<BR>Dspace-general mailing list<BR>Dspace-general@mit.edu<BR>http://mailman.mit.edu/mailman/listinfo/dspace-general<BR></BLOCKQUOTE><BR><BR><BR><DIV>
<DIV>
<DIV>
<DIV>
<DIV>
<DIV>
<DIV>
<DIV>
<DIV>
<DIV>
<DIV>
<DIV>
<DIV><EM>
<DIV class=Section1>
<P class=MsoNormal><FONT color=#9966cc><FONT face="Comic Sans MS">"I haven't lost my mind ~ it's backed up on disk somewhere!"</FONT> </FONT></P>
<P class=MsoNormal><STRONG></STRONG> </P></DIV></EM></DIV></DIV></DIV></DIV></DIV></DIV></DIV></DIV></DIV></DIV></DIV></DIV></DIV><p> 
<hr size=1></hr> Download prohibited? No problem! <a href="http://us.rd.yahoo.com/mail/in/ywebmessenger/*http://in.messenger.yahoo.com/webmessengerpromo.php">CHAT</a> from any browser, without download.