[
https://jira.duraspace.org/browse/DS-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25180#comment-25180
]
DSpace @ LyNcode edited comment on DS-1195 at 6/18/12 6:17 PM:
---------------------------------------------------------------
Hi Ivan Masár,
allow me to comment on your post.
-- OAICAT
I think the correct way of solving this problem is changing the OAICat
behavior, using tweaks as solutions isn't a good method. Theoretically (based
on the OAI-PMH protocol) OAICAT behavior it is not correct. That is, assuming
from=0001-01-01 and/or until=9999-12-31 on the absence of from/until parameters
is not correct. If not defined, they should be considered as it: undefined.
This behavior could generate two useless SQL WHERE clauses that, in practice,
only adds more complexity (lower performance) to the OAI implementation.
-- ORACLE
The Oracle problem, in fact, is related with the defined timezone.
Look at here:
http://grepcode.com/file/repo1.maven.org/maven2/org.dspace/dspace-api/1.8.2/org/dspace/search/Harvest.java#Harvest.toTimestamp%28java.lang.String%2Cboolean%29
Oracle database should be defined with UTC timezone.
-- Conclusion
OAICAT is working wrong.
There are some ORACLE issues that must be documented in the DSpace manual.
The patch (only) solves the OAICAT problem.
was (Author: lyncode):
Hi Ivan Masár,
allow me to comment on your post.
-- OAICAT
I think the correct way of solving this problem is changing the OAICat
behaviour, using tweaks as solutions isn't a good method. Theoretically (based
on the OAI-PMH protocol) OAICAT behaviour it is not correct. That is, assuming
from=0001-01-01 and/or until=9999-12-31 on the absence of from/until parameters
is not correct. If not defined, they should be considered as it: undefined.
-- ORACLE
The Oracle problem, in fact, is related with the defined timezone.
Look at here:
http://grepcode.com/file/repo1.maven.org/maven2/org.dspace/dspace-api/1.8.2/org/dspace/search/Harvest.java#Harvest.toTimestamp%28java.lang.String%2Cboolean%29
Oracle database should be defined with UTC timezone.
-- Conclusion
OAICAT is working wrong.
There are some ORACLE issues that must be documented in the DSpace manual.
The patch (only) solves the OAICAT problem.
> DSpace OAI with Oracle
> ----------------------
>
> Key: DS-1195
> URL: https://jira.duraspace.org/browse/DS-1195
> Project: DSpace
> Issue Type: Bug
> Components: OAI-PMH
> Affects Versions: 1.8.2
> Environment: Oracle Database
> Reporter: DSpace @ LyNcode
> Priority: Critical
> Attachments: patch-dspace-oai-oracle-db.diff
>
>
> Patch to solve this problem:
> http://sourceforge.net/mailarchive/message.php?msg_id=29421592
> The new OAICAT version does not solve this problem.
> In attachment, you could see a patch to apply over the dspace-oai source:
> $ cd [DSPACE-SOURCE]
> $ patch -p0 < [PATH-TO]/patch-dspace-oai-oracle-db.diff
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
