Re: [Koha] Improving permissions on lists (virtual shelves)
Excellent but I want to add a useful feature, list categories and subcategories like in this Koha fork called "Estantes virtuales": http://biblioteca.exactas.unlp.edu.ar/cgi-bin/koha/opac-shelves.pl?startfrom... Saludos, Felipe Adalid Ortiz Anzaldo Bibliotecario de sistemas Universidad Iberoamericana Tijuana Biblioteca Loyola http://clavius.tij.uia.mx Ave. Centro Universitario 2501 Playas de Tijuana 22200, Tijuana, B.C. 0 664 630-1577 Ext. 623 adalid@tij.uia.mx "En una jerarquía, el poder lo tiene quien guarda secretos; en una red el poder lo obtiene quien disemina información. -John Perry Barlow->
Subject: Re: [Koha] Improving permissions on lists (virtual shelves) From: Marcel de Rooy <M.de.Rooy@rijksmuseum.nl> Date: Wed, 7 Dec 2011 16:08:58 +0000 To: "koha@lists.katipo.co.nz" <koha@lists.katipo.co.nz>, "koha-devel@lists.koha-community.org" <koha-devel@lists.koha-community.org>
--===============0312935277== Content-Language: nl-NL Content-Type: multipart/alternative; boundary="_000_809BE39CD64BFD4EB9036172EBCCFA3137F0B6SMAIL1Brijksmuseu_"
--_000_809BE39CD64BFD4EB9036172EBCCFA3137F0B6SMAIL1Brijksmuseu_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Thanks all for responding to this inquiry. This was very helpful.
I am merging here the results and will be posting them back to report 7310 = or a wiki page. Feel free to correct me where I made the wrong conclusion.
1 Public lists in OPAC: Currently, a user should be logged in to create a l= ist. I would strongly recommend to keep that restriction. A new preference = is added that allows opac users to create public lists or does not allow th= at.
Additionally, I would add the restriction that another opac user cannot cha= nge the list type of a public list to private list or change the list permi= ssions when he did not create it (currently possible); the owner can do tha= t or a staff member with permissions in the staff client.
2 Three new permissions per list: Add items, Delete own items, Delete other= items. This makes the Open list type obsolete.
3 Share private lists with another patron (as described before). Can be tur= ned on/off with a preference.
4 Staff client features: add an option under Tools to moderate inappropriat= e list names for public lists and shared private lists. (A library is free = to use it or not.) Add staff list permission: allow to manage lists (virtua= l shelves). With that permission a staff member can moderate the list names= as mentioned and access the staff Lists module. (He can change list type a= nd permissions. He can take ownership of a public list if the owner has bee= n deleted.)
Your presentation looks very good. (But seems to me also a matter of customizing css.) You mention subcategories: how did you do that in terms of functional/technical design ? ________________________________________ Van: Adalid Ortiz [adalid@tij.uia.mx] Verzonden: woensdag 7 december 2011 20:47 Aan: Marcel de Rooy; koha@lists.katipo.co.nz; koha-devel@lists.koha-community.org Onderwerp: Re: [Koha] Improving permissions on lists (virtual shelves) Excellent but I want to add a useful feature, list categories and subcategories like in this Koha fork called "Estantes virtuales": http://biblioteca.exactas.unlp.edu.ar/cgi-bin/koha/opac-shelves.pl?startfrom... Saludos, Felipe Adalid Ortiz Anzaldo Bibliotecario de sistemas Universidad Iberoamericana Tijuana Biblioteca Loyola http://clavius.tij.uia.mx Ave. Centro Universitario 2501 Playas de Tijuana 22200, Tijuana, B.C. 0 664 630-1577 Ext. 623 adalid@tij.uia.mx "En una jerarquía, el poder lo tiene quien guarda secretos; en una red el poder lo obtiene quien disemina información”. -John Perry Barlow->
Subject: Re: [Koha] Improving permissions on lists (virtual shelves) From: Marcel de Rooy <M.de.Rooy@rijksmuseum.nl> Date: Wed, 7 Dec 2011 16:08:58 +0000 To: "koha@lists.katipo.co.nz" <koha@lists.katipo.co.nz>, "koha-devel@lists.koha-community.org" <koha-devel@lists.koha-community.org>
--===============0312935277== Content-Language: nl-NL Content-Type: multipart/alternative; boundary="_000_809BE39CD64BFD4EB9036172EBCCFA3137F0B6SMAIL1Brijksmuseu_"
--_000_809BE39CD64BFD4EB9036172EBCCFA3137F0B6SMAIL1Brijksmuseu_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Thanks all for responding to this inquiry. This was very helpful.
I am merging here the results and will be posting them back to report 7310 = or a wiki page. Feel free to correct me where I made the wrong conclusion.
1 Public lists in OPAC: Currently, a user should be logged in to create a l= ist. I would strongly recommend to keep that restriction. A new preference = is added that allows opac users to create public lists or does not allow th= at.
Additionally, I would add the restriction that another opac user cannot cha= nge the list type of a public list to private list or change the list permi= ssions when he did not create it (currently possible); the owner can do tha= t or a staff member with permissions in the staff client.
2 Three new permissions per list: Add items, Delete own items, Delete other= items. This makes the Open list type obsolete.
3 Share private lists with another patron (as described before). Can be tur= ned on/off with a preference.
4 Staff client features: add an option under Tools to moderate inappropriat= e list names for public lists and shared private lists. (A library is free = to use it or not.) Add staff list permission: allow to manage lists (virtua= l shelves). With that permission a staff member can moderate the list names= as mentioned and access the staff Lists module. (He can change list type a= nd permissions. He can take ownership of a public list if the owner has bee= n deleted.)
participants (2)
-
Adalid Ortiz -
Marcel de Rooy