[
http://jira.dspace.org/jira/browse/DS-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11539#action_11539
]
Claudia Jürgen commented on DS-568:
-----------------------------------
Hi Kim,
ah haven't delved into it, thanx for the explanation.
Maybe indicating the time used in display will at least clear make clear that
there might be a difference to the time zone one is in. Wonder how this is
treated in other places where metadata is exposed, e. g. OAI.
Have a nice weekend
Claudia
> Time Stamps for metadatavalues (date accessioned/available) differ from last
> modified time stamp in item table
> --------------------------------------------------------------------------------------------------------------
>
> Key: DS-568
> URL: http://jira.dspace.org/jira/browse/DS-568
> Project: DSpace 1.x
> Issue Type: Bug
> Components: DSpace API
> Affects Versions: 1.5.1, 1.6.0
> Reporter: Claudia Jürgen
>
> Another date issue:
> During submission (both via UI and as import) time stamps are created
> differently:
> item table last_modified got "real" time
> whereas metadatavalues like dc.date.accessioned and dc.date.available got
> real time -2 hours
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
