[Koha-devel] Suggestions requested for a feature / enhancement based around opac-retrieve-file.pl

[Marcel de Rooy]

Sounds as an acceptable improvement.
Could be handled with a syspref of course. Would be the easiest solution to implement. 
But we could also extend the meaning of Public here. And make a division between Private, Restricted and Public. Restricted could be handled by allowing patron types, as Marc suggested ? Or patron lists ? Or ... More flexible than just a true/false flag. 

Marcel

-----Oorspronkelijk bericht-----
Van: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] Namens Indranil Das Gupta
Verzonden: maandag 26 juni 2017 00:15
Aan: koha-devel at lists.koha-community.org
Onderwerp: [Koha-devel] Suggestions requested for a feature / enhancement based around opac-retrieve-file.pl

Hi all,

the current Koha::Upload.pm and opac-retrieve-file.pl allows for a uploaded file (e.g. PDF) to be displayed on the OPAC as long as the flag is set to public.

I know how many librarians feel about reader history privacy and they are protective about it for good reason. In this context, I'm faced with the following two use-cases:

In India, e-books with archival rights are gaining ground over hardcopy. As it happens the buyer (institutional library) has to give an undertaking that it will implement reasonable safeguards to ensure that while all their bonafide users should have access to the books, these shall not be presented to the users in such as way as to permit un-monitored access / downloads by un-authenticated users etc along with maintenance of any access log for any necessary compliance.

Or for example PhD theses where many institutions across India have an embargo on the full-text online access for non-members for a period upto 2 years from the date of publication, but no such restriction exist for bonafide authorised users.

I am working on an early stage prototype to support this sort of functionality. My question here to  you all is that how far are we open as devs and librarians to accept such an extension into Koha? Of course, there would be a syspref that will have to be set for the functionality to  kick in.

Suggestions? Comments?

regards
indranil

--
Indranil Das Gupta
L2C2 Technologies

Phone : +91-98300-20971
WWW  : http://www.l2c2.co.in
Blog    : http://blog.l2c2.co.in
IRC     : indradg on irc://irc.freenode.net
Twitter : indradg
_______________________________________________
Koha-devel mailing list
Koha-devel at lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/