Comments in line below:<br><br><div class="gmail_quote">On Mon, Dec 5, 2011 at 5:42 AM, Marcel de Rooy <span dir="ltr">&lt;<a href="mailto:M.de.Rooy@rijksmuseum.nl">M.de.Rooy@rijksmuseum.nl</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

Hi all,<br>
<br>
Still hoping to get some feedback on this subject, I would now propose the following. Please respond to the list, if you agree or disagree.<br>
<br>
1  Do not allow to create a public list in the OPAC. (Only private lists.)  Public lists are only created by staff users in the staff client.<br></blockquote><div><br>I think this should be a preference that the librarians can choose from the following options :<br>

<br>   1. Allow anyone to create public lists without moderation<br>   2. Allow patrons to create public lists with moderation<br>   3. Allow only staff (with permission) to create public lists<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">


2  Add three permission options to any list: a) Allow adding entries b) Allow deleting your own entries (that you added)  and c) Allow deleting entries that someone else added.<br>
   This makes the distinction between public list and open list no longer needed and adds some refinement in lists management.<br>
   Only the owner of the list can change these permissions.<br></blockquote><div><br>In addition I&#39;d say we need general staff list permissions which we don&#39;t have right now. <br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">


3  Add a new (opac) feature to private lists: Share a list (with another patron).<br>
   Let the user share access to a list by Koha sending an email with a URL including some (temporary) invitation key. When the invited patron clicks that URL (when logged in) he gains access (in accordance with the described permission options for that specific list).<br>


   The invited patron can always &#39;delete&#39; the shared list, i.e. delete the share.<br>
   The owner can &#39;unshare&#39; the list and remove all shares for that list.<br></blockquote><div><br>I like!<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">


4  With respect to user privacy, a feature may be added in staff client to moderate shared list names.<br></blockquote><div><br>Right now patron names don&#39;t show on lists at all - not sure if we need them really.<br>

 </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
5  Possibly, libraries do not want patrons sharing lists. So the option could be disabled with a preference. In that case points 2 and 3 still apply.<br></blockquote><div><br>Yes, preferences to turn things off are always good.<br>

 <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Note that the shared private list concept makes report 7281 (Hiding some lists) obsolete.<br>
Bug 7310 will be used for this feature.<br>
<br>
Your comments are very welcome!<br>
<br>
Marcel<br>
<br>
_______________________________________________<br>
Koha mailing list  <a href="http://koha-community.org" target="_blank">http://koha-community.org</a><br>
<a href="mailto:Koha@lists.katipo.co.nz">Koha@lists.katipo.co.nz</a><br>
<a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_blank">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br>
</blockquote></div><br>