You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes we have an issue date like 2015, which is a valid ISO 8601 date, yet I noticed that when I export results from OpenRXV the date appears as 2015-01-01. There is no way to know whether the item was actually issued on that date, or if the date was converted.
In DSpace, issue dates are always formatted as YYYY, or YYYY-MM, or YYYY-MM-DD. It may be possible to adjust the date format in the Elasticsearch field.
The text was updated successfully, but these errors were encountered:
Sometimes we have an issue date like
2015
, which is a valid ISO 8601 date, yet I noticed that when I export results from OpenRXV the date appears as2015-01-01
. There is no way to know whether the item was actually issued on that date, or if the date was converted.In DSpace, issue dates are always formatted as
YYYY
, orYYYY-MM
, orYYYY-MM-DD
. It may be possible to adjust the date format in the Elasticsearch field.The text was updated successfully, but these errors were encountered: