Hello all,

We had a quite productive meeting regarding mana-kb during the hackfest. We had many ideas regarding improvements / new features that could be added, I've created a bugzilla entry for each idea. Below is a summary of our work

reminder : and "object" is something that is shared through mana. For now, subscription patterns and reports can be shared.

 * there's a web interface (ui.mana-kb) to look at data, and delete
   old/outdated. The idea is to curate data regularly. Anyone can apply
   to become a curator of the data in mana-kb. New features idea :
     o add a button "apply as curator"
       https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23738
     o prepare some SQL queries that could show librarians contributing
       a lot, and proposing them to join the list of curators
       https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23739
     o Let curators flag a content (3 values : non-flagged / hide this
       object, to be discussed for deletion / 'star' this object, it
       has a high quality/value)
       https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23740
 * Sharing reports guidelines
   https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23741
     o When you share a report, Koha could check if there's a runtime
       value to set (<<xxxx|yyyy>>). If there's none, add a
       confirmation checkbox, most useful reports need a runtime parameter.
     o Add a hint : "do not share a report with hardcoded value related
       to your own data" that is displayed when the librarian want to
       share a report
 * Languages checks are made on the full language code (fr_FR). We need
   only the first 2. Thus, reports with language fr_FR are displayed
   also for our canadian-Quebec friends (same thing for en_EN, en_US,
   en_NZ, of course)
   https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23742
 * In the admin/share_content.pl page => show if a token has not been
   validated yet
   https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23743
 * In the result lists (for object (reports, ...) searching, add a
   column with the language of submission, that can be filtered/sorted
   https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23744
 * in ui.mana-kb :
   https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23745
     o hide the token column, a curator does not need to know the token
       of a librarian
     o add a feature 'resend token' => resend the validation email to
       the librarian
 * In Koha : check that the associated email is an email, to avoid
   unvalidable tokens
   https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23746
 * replace a local Koha object by a mana-kb one: currently, it's not
   possible to modify a local object with one coming from Mana-kb. Add
   this feature, 2 sub-features:
   https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23747
     o if the local object comes from Mana, have a message "hey, the
       mana object has been updated, clic here to update your local one"
     o if the local object is 'home-made', add a button "update from
       mana-kb" that let the librarian search in mana, and update his
       local data.
 * "golden mana-kb contributor": we expect to have some librarians
   contributing very efficiently and frequently. Those librarians
   should be able to update existing mana objects. The golden mana-kb
   contributor is given by curators, coopt/consensus. The golden
   contributor status can be given for reports and for subscriptions,
   separately.

--
Paul Poulain, Associé-gérant / co-owner
BibLibre, Services en logiciels libres pour les bibliothèques
BibLibre, Open Source software and services for libraries

_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to