<div dir="ltr"><div><div>Thanks Andrew, I get your point. On the other hand, after a few old corpora were removed, their privileges are still there in the list, even after I told CQPweb to auto-generate privileges again. So the no longer needed privileges must be deleted manually, right?<br><br></div>Best<br></div>Jiayue<br></div><div class="gmail_extra"><br><div class="gmail_quote">On 3 October 2017 at 01:26, Stefan Evert <span dir="ltr"><<a href="mailto:stefanML@collocations.de" target="_blank">stefanML@collocations.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
> On 2 Oct 2017, at 14:31, Hardie, Andrew <<a href="mailto:a.hardie@lancaster.ac.uk">a.hardie@lancaster.ac.uk</a>> wrote:<br>
><br>
> Often, it might be better to add the new corpus to the scope of existing privileges. (This is especially the case when you have lots of corpora).<br>
<br>
</span>Oh, I didn't know that this is possible. I was told that one has to "generate default privileges" after installing a new corpus, which we have been doing since for every new corpus, leading to a horrible proliferation of sets of privileges on our CQPweb server.<br>
<br>
I clearly need a better CQPweb administrator. :-)<br>
<br>
Best,<br>
Stefan<br>
<div class="HOEnZb"><div class="h5">______________________________<wbr>_________________<br>
CWB mailing list<br>
<a href="mailto:CWB@sslmit.unibo.it">CWB@sslmit.unibo.it</a><br>
<a href="http://liste.sslmit.unibo.it/mailman/listinfo/cwb" rel="noreferrer" target="_blank">http://liste.sslmit.unibo.it/<wbr>mailman/listinfo/cwb</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Jiayue Wang</div><div>College of Foreign Studies</div><div>Guangxi University for Nationalties</div><div>Nanning, China 530006</div></div></div>
</div>