Am 22.02.2013 10:30, schrieb helix84: > Actually, it was an attempted fix to another issue reported by > Christos here: > https://jira.duraspace.org/browse/DS-1311 > https://jira.duraspace.org/browse/DS-1445 > > but it was never merged, as you can see in the later comments. I'm > not > sure how to help you, maybe João will chime in. > > Meanwhile, you can try 3.1, there have been a few fixes to OAI there, > but I'm not sure if anything was timezone-related.
Hi Helix, sorry i forgot i update to 3.1 a few days ago, so dspace 3.1 is already running. I downloaded the src now too. I modified the code to include the attempted "fix" from https://github.com/lyncode/DSpace/commit/8415c4b41dc7d725a0b39d33bc50f4ada4bc5de9 After mvn package the files DateUntilFilter.class DateUtils.class dont't differ to the installed one tested vie md5sum. I copied over the two files, restarted tomcat, imported all items with creating new index and cleaning up the oai cache. After that the item requesting the item over the OAI i recognized that nothing had changed. I saw that the item it self has the right time value in the field dc.date.accessioned maybe i can use that value in the XSL? Next question, which XSL is building the header? Best regards, Marco ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
