On Tue, Jun 18, 2013 at 12:06 PM, "M. Àngels Pulido" <[email protected]> wrote: > Yes Helix, to us this approach works because we want to hide the bitstream > that is a .pdf where the user put the permission to publish their work: > article, book, etc. in our repository and therefore, this document contains > personal data. So we are interested that are not indexed in the search > engines and is a document that can only access the administrators. > I'm not sure if this is what Jessica hopes ...
That's a good approach for your use case - storing permissions in the repository. But let me give you a suggestion. If you create a new bundle, it will be listed in the METS file and unless you restrict the bitstrean access rights, it will be accessible (if you know how to find out its URL from the METS file). A better way would be to use the LICENSE bundle for storing permissions, because it' not shown in the list of bundles by defaut. In either case, you should still make sure to remove Anonymous READ access from the file. You probably do that, I'm just making sure. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ 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
