Bug 21412

Summary: Optionally limit OPAC access to files attached to bib records via upload to only logged in users
Product: Koha Reporter: Cihan D <scdogan>
Component: OPACAssignee: Bugs List <koha-bugs>
Status: NEW --- QA Contact: Testopia <testopia>
Severity: enhancement    
Priority: P5 - low CC: 2178216511, andrew, dcook, martin.renvoize
Version: Main   
Hardware: All   
OS: All   
See Also: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38655
GIT URL: Change sponsored?: ---
Patch complexity: --- Documentation contact:
Documentation submission: Text to go in the release notes:
Version(s) released in:
Circulation function:
Attachments: step1
step3
step6

Description Cihan D 2018-09-26 12:34:52 UTC
Created attachment 79410 [details]
step1

I want to restrict access to the files I upload in the Koha automation system. What steps can I use? Thank you.

1. 1. Opac Display - Disable  ( This collection will be private)
2. https://www.youtube.com/watch?v=mbYgsodcPaU (How to attach a file to a MARC Record in Koha)
3. Cataloging step
4.Copy upload file link ( For Example : http://193.140.223.100/cgi-bin/koha/opac-retrieve-file.pl?id=eca42072bd9eb83f28260e9c9e7f0e2f )
5. Log out Koha
6. Paste link any browser than file is open. I want to system asked username and password
Comment 1 Cihan D 2018-09-26 12:35:23 UTC
Created attachment 79411 [details]
step3
Comment 2 Cihan D 2018-09-26 12:35:57 UTC
Created attachment 79412 [details]
step6
Comment 3 David Cook 2023-12-13 05:42:43 UTC
I figured there would be a lot of duplicate bug reports for this enhancement request, but this is the only one I've seen...
Comment 4 e 2024-08-14 12:23:11 UTC
Comment on attachment 79411 [details]
step3

ffff
Comment 5 Andrew Fuerste-Henry 2025-03-20 16:26:48 UTC
Renaming this a bit in hopes of getting more attention, as this does seem like a useful feature.
Comment 6 David Cook 2025-03-20 23:28:06 UTC
It should be easy enough to add another column to uploaded_files. Something like "access_level" or "anonymous_access". 

The column will only make sense relative to the "public" column, which makes the additional column feel weird. 

So another idea would be to change the logic of the "public" column. NULL can be non-public, 1 can be public anonymous access, and 2 can be public authenticated access. 

Using integers instead of codes makes things less maintainable in the long-term though, as it's not clear at a glance what it means. I think this is a problem we've often ran into Koha.

So... maybe "1" means public anonymous access, and "auth" means public authenticated access. Of course, that would require a DB schema change which changes "public" from tinyint(4) to something like char(4). And at that point maybe it's worth rewriting "1" to "anon" as well. 

--

Anyway, just some thoughts. I haven't had any customers asking for this, so it's not a priority for me, but that's how I'd do it.
Comment 7 David Cook 2025-03-20 23:32:49 UTC
(In reply to David Cook from comment #6)
> Anyway, just some thoughts. I haven't had any customers asking for this, so
> it's not a priority for me, but that's how I'd do it.

I say that... but I do hear people talk about this at times...

People want ways to provide files and links to resources to only authenticated users.  So there is a bigger (but related) feature gap than just what is described here. 

Still probably not a priority for me at this point, but it's always possible that I might revisit this one day. (He says optimistically.)