Hi Filippos,since 1.5.2 it is possible to exclude restricted item metadata from being exposed, see the following section in dspace.cfg:
#### Restricted item visibilty settings #### By default RSS feeds, OAI-PMH and subscription emails will include ALL items
# regardless of permissions set on them. ## If you wish to only expose items through these channels where the ANONYMOUS
# user is granted READ permission, then set the following options to false #harvest.includerestricted.rss = true #harvest.includerestricted.oai = true #harvest.includerestricted.subscription = true Hope that helps Claudia Jürgen Filippos Kolovos schrieb:
Dear Sir/Madam, We currently have two dspace installations, version 1.4.1 One is open access and the other one is used separately for "sesnitive" documents. At first we had included these documents in one repository together with the "open access" documents. In order to restrict them from public view we had given permission only to the system administrator to see the whole collection(s) they were in. However, since Dspace runs an OAI server as well, their metadata could not be restricted from public view, since the OAI server could not stop sending these metadata. The documents per se could not be retrieved by the users but the metadata were being disseminated through OAI, which in some cases was a problem. In order to solve that problem we had to install a second instance of Dspace, in a separate server, with the OAI server deactivated and the server being behind a firewall. It is entirely closed from public view. I hope that we may have helped you. Kind Regards, -Fk ------------------------------------------------------------------------ _______________________________________________ Dspace-general mailing list [email protected] http://mailman.mit.edu/mailman/listinfo/dspace-general
<<attachment: Claudia_Juergen.vcf>>
_______________________________________________ Dspace-general mailing list [email protected] http://mailman.mit.edu/mailman/listinfo/dspace-general
