[
https://jira.duraspace.org/browse/DS-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20368#action_20368
]
Robin Taylor commented on DS-829:
---------------------------------
Another wee comment. The existing code in Harvest.harvest(..) takes the stance
that withdrawn items should always be included in the result set flagged as
withdrawn even if they had restricted visibility. I guess the logic is that
they may in the past have been harvested therefore we need to tell harvesters
that they have now been withdrawn. this means that all the OAI-extended filters
would need to check that the item was not flagged as withdrawn before filtering
it. Another argument for doing the filtering in Harvest. The pseudo logic would
be amended to be...
Read database
If not withdrawn
{
then apply filters
If not required then go back and read another item
}
add to result set
> OAI Extended Addon : Adding filter and modifying capacities to the OAI
> interface
> --------------------------------------------------------------------------------
>
> Key: DS-829
> URL: https://jira.duraspace.org/browse/DS-829
> Project: DSpace
> Issue Type: New Feature
> Components: OAI-PMH
> Reporter: João Melo
> Assignee: Robin Taylor
> Fix For: 1.8.0
>
> Attachments: OAIExtended-v2.2.tar.gz,
> OAIExtended_v2.1_with_documentation.tar.gz
>
>
> Purpose
> The OAI Extended Addon was initially developed to allow DSpace to be
> compliant with the Driver project guidelines
> (http://www.driver-repository.eu).
> How it works?
> When an OAI-PMH request is received, the DSpace database is queried through
> the standard OAI Interface included in DSpace. After that, the OAI Extended
> Addon starts to work. First, the list of items retrieved from the database is
> filtered by a Filter Mechanism, after that, each item associated metadata is
> modified by a Modifier Mechanism. The results of both actions are returned to
> the harvester that performed the request.
> Because of the initial purpose, most of the filters and modifiers implemented
> are specific to the Driver compliance issue. But there is an easy way to
> develop your own filters and/or modifiers, just by extending the abstract
> class Filter and/or Modifier. More information is included in the attachment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
