On Mon, Jun 29, 2020 at 02:27:37PM +0200, Bram Luyten wrote: ... > *dc.date.issued *is the most commonly used field for a "publication" date. > For content that doesn't exist elsewhere, dc.date.issued can coincide with > dc.date.available. But very often, the date of publication in another > medium, website, or journal is used there. > The submission form user interface date format allows: > YYYY > YYYY-MM > YYYY-MM-DD > > But I'm pretty sure (not tested though!) that if you would fill it out with > a timestamp, like 2018-01-07T08:55:55Z, it would work as well. > > You generally don't want to fill it out with "circa YYYY", or "195X" > > The main areas that you are risking to break are the Browse by Issue Date > pages, cfr http://demo.dspace.org/xmlui/browse?type=dateissued > Or you may have items not showing up in your Discovery date facets. (see > screenshot)
Allow me to underscore the fact that, in this field, there are not just established guidelines to consider; this field will be interpreted by software and must use a syntax that is recognized by the software if you want to avoid unfortunate and mysterious behavior. -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 www.ulib.iupui.edu -- 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/20200629142953.GD14455%40IUPUI.Edu.
signature.asc
Description: PGP signature
