Hifor a historic repository we manage an extended list of dates as in http://liburutegibiltegi.bizkaia.eus/browse?type=dateissued . Library & archives managers needed some more (or maybe less) ¿precision? when describing the dates. The original records in the catalogues showed some very special dates:
[c.1488] , 1901-19-?] , 1494/1495, (1217?-1274), [ca. 1515-1517]The order of items in browse -by-date seems to behave quite well (i.e 1480-1562 before 1492...etc)
Also, the DC schema was extended to deal some additional characteristics (see 139 & 128 in this list-->
11 dc.date.accessioned Date DSpace takes possession of item.12 dc.date.available Date or date range item became available to the public.
13 dc.date.copyright Date of copyright.14 dc.date.created Date of creation or manufacture of intellectual content if different from date.issued.
139 dc.date.description 15 dc.date.issued Date of publication or distribution. 16 dc.date.submitted Recommend for theses/dissertations.128 dc.date.updated The last time the item was updated via the SWORD interface
10 dc.date Use qualified form if possible. best Emilio El 27/06/2020 a las 17:26, Chris Clawson escribió:
My project is a mostly a historic repository of images from my home area. In some cases, we know the exact date a picture was taken. In the worst case, a date would only be a guess made from a historian ("circa 1895"). Of course, many other date related fields are defined. There are international standards and guidelines issued from Google and others.We wish to identify and curate everything added. How shall we deal with imperfect information, and keep compatible with established guidelines? In DSpace, where, when and how are the 'date' metadata fields important in this case?--All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/---You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-community/2599252f-fa1b-40fe-b8e5-56ceb4d3df15o%40googlegroups.com <https://groups.google.com/d/msgid/dspace-community/2599252f-fa1b-40fe-b8e5-56ceb4d3df15o%40googlegroups.com?utm_medium=email&utm_source=footer>.
-- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/--- You received this message because you are subscribed to the Google Groups "DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-community/546681a4-7f45-1096-8751-f974c55b5a62%40arvo.es.
<<attachment: elorenzo.vcf>>
