Hi Juan, At the database level, DSpace will only save dates in UTC format (this is true for any version of DSpace, including 7.x). So, all dates are formatted to UTC before they are saved in the database as metadata. This is necessary to make things like time-base access restrictions (e.g. embargoes) and other date comparisons easier in the codebase.
It's currently not possible to change this behavior (at least not easily, and it could have side effects for embargoes and similar if you change it). That said, you might be able to customize how those dates are displayed in the User Interface, if you want them to appear in local timezone (you'd just need to translate them back form UTC to local time). But, just be aware that if you change/save a date in the User Interface, it'll always be converted to UTC before it's saved to the database. Tim On Tuesday, February 8, 2022 at 7:35:14 AM UTC-6 [email protected] wrote: > Hi all! > > I'm seeing an odd behaviour on my Dspace 6.3. Whenever there is a new item > submission, the dc.date.accessioned and dc.date.available are saved with > UTC time but it should be with the local time that my server and database > have: > > [image: imagen_2022-02-08_083220.png] > > Do you guys know if DSpace uses only UTC time to create this metadata? > > Is there a way to make DSpace use America/Bogota timezone? > > > Regards, > > Juan > -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" 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-tech/9962375c-49f3-479f-9985-2017fd6501b3n%40googlegroups.com.
