I forgot to say that another reason we don't use the standard Invenio access roles is that for some submissions each category has very different restrictions i,e, for category a user_lista, category b user_listb, category c e-groups listc...
Tony On Fri, 23 Jan 2009 [email protected] wrote: > Theodoropoulos, > For our submissions we normally restrict to either a set of email > addresses (we get the submitter email address in the 'SuE' field in > curdir) or to membership of (an) email list(s) - at CERN the user's > profile contains the list of Simba or (now) e-group lists that a user > belongs to. > > We apply this restriction by having - on a submission page the first and > last fields as response elements - which if the user is NOT allowed to > proceed, will put a message on the screen 'Sorry but...' and which comment > out the intermediate fields i.e. > > So the html source becomes.. > > You ([email protected]) are not authorized to use this submission. If > you believe that you should be able to use it then please contact > [email protected]. <!-- > .... > .... > .... > > --> > > The <!-- and the --> hide all the stuff in between (but you may also have > to hide some of the stuff in between by the same method if the html > contains '--'. > We could have used the more standard Invenio access roles but we have > found this not to be flexible enough. i.e. we sometimes restrict > submissions not only depending on who the user is but also depending (for > modifications to documents i.e.) on the document itself. In some cases > we restrict certain fields to modify or enter depending on who the user > is. > > Of course you could handle these restrictions by the use of websumit > functions - but then the user would first enter data and then be told > 'Sorry...' which is not so nice.... > > regards > > Tony Osborne > > On Fri, 23 Jan 2009 [email protected] wrote: > > > > > Hello everyone, > > > > Is there a way to change the DEFAULT behavior of a NEWLY registered Invenio > > user (standard 'internal' account), so that he can NOT submit any documents, > > UNLESS special crafted submit authorizations are applied to him? > > > > Furthermore, I couldn't find a way to restrict submission to certain > > doctypes > > even to already registered users in my test installation. Writing a new role > > (ie articlesubmitter) that involved action 'submit' with authorizations > > "allow > > DEMOART" and "deny any" did not do the trick... Everyone can submit any of > > the > > doctypes available! > > > > Do you have any ideas regarding this issue? What do you use in your site to > > restrict the submission of certain documents to certain users? > > > > Best regards, > > Theodoropoulos Theodoros > > > > > > > > -- ---- CERN - European Laboratory for Particle Physics ------------- - Tony Osborne email: [email protected] - - CDS section, UDS Group,IT Dept. Phone: +41 22 767 3567 - - CERN Fax : +41 22 767 8630 - ------------------------------------------------------------------
