Am 2014-01-27 um 14:26 schrieb Samuele Kaplun <[email protected]>:

>> is there any documentation on access permissions? I couldn’t find anything
>> helpful.
> 
> The official documentation is available in every installation of Invenio:
> <http://invenio-demo.cern.ch/help/admin/webaccess-admin-guide>

Ahh, of course again I forgot one of the few places to look at.

>> I’d like to know
>> - how to check for permissions within web templates (show some parts only to
>> some groups/roles) 
> 
> That's often not possible. ...

Thank you very much for the extensive explanation!
I’ll probably follow Ludmilla’s advise and use a bibformat element, that way I 
know already.

> If the template does not receive any req or user_info object you will have to 
> patch the code that calls the given template (typically some method in a 
> _webinterface.py file) in order to pass them. Feel free to contribute such a 
> patch for integration.

I guess I’ve to maintain another repository for potential submissions. The one 
I’m using for my adaption contains also configuration and thus passwords. 
(Maybe I should have chosen a different approach than to just install from my 
own branch…)

>> - how to restrict access to full records and especially
>> „fulltext“ (i.e. downloads) to logged in users (or some groups/roles)
> 
> Restriction in Invenio are at the level of a whole collection (through the 
> "viewrestcoll" WebAccess action) or at the level of the single document 
> (meaning a BibDoc, i.e. all the given formats and revision of the same 
> document), through the "viewrestrdoc" action. More on this at:
> <http://invenio-demo.cern.ch/help/admin/bibupload-admin-guide#3.6>
> 
> See the section about FFT $r 

Thank you! I overlooked that when I read about FFT. Seems the right way for us, 
because I can depend it on our license field.

For the traveling server (that is not publicly accessible and should work 
without logged-in users) I must patch the database anyway with regard to local 
URLs (would have been easier to make them relative), so I’ll add a change to 
the permissions table(s).

>> A tutorial about how to create/configure users, roles and permissions would
>> be really nice: What can/must I do in WebAccess Admin, what can I do in
>> text files or with cli scripts.
> 
> Indeed such a documentation is currently missing…

I won’t promise to write it - I’ve still too much open promises to other open 
source projects. :-(





Greetlings, Hraban
---
http://www.fiee.net
https://www.cacert.org (I'm an assurer)







Reply via email to