May 2012 - Koha-devel - lists.koha-community.org

Solr demo - current BibLibre solr and stetienne devs (updated)
by Claire Hernandez 03 May '12

03 May '12

Hi all, I updated the solr-demo install. We provided it for kohacon11 demo but it seems it could be usefull sometimes. This is the current stetienne version (solr devs + acquisitions and serials you can find here with "STE" library code https://docs.google.com/a/biblibre.com/spreadsheet/ccc?key=0AuZF5Y_c4pIxdHE… ) Professional interface is here: http://solr-demo.biblibre.com <http://solr-demo.biblibre.com/> There is a "demo" account, you could see for example the current admin interface for indexes preferences http://solr-demo.biblibre.com/cgi-bin/koha/solr/indexes.pl We are re-doing work for the future abstract layer. I will setup a new install to show what we have. Stay tuned :) Claire; (other close subject: you can see the progress for april month for rebase work at BibLibre: https://docs.google.com/a/biblibre.com/spreadsheet/ccc?key=0AuZF5Y_c4pIxdHE…)

1 1

Bug 5572 (refinements to function merge sub merge in C4::AuthoritiesMarc)
by Marcel de Rooy 03 May '12

03 May '12

Hi, This patch from Janusz Kaczmarek dates from Jan 3, 2011 already. And still needs signoff. I have marked it as In Discussion now, hoping for some feedback from you. Please have a look at the report and patch. Do you agree that subfields at the biblio side should be cleared for an active empty authority subfield? Or could that result in unexpected data loss too easily? What is your opinion? Other QA team members are also welcome to respond. Thanks for doing so, Marcel

2 1

Bugzilla component categories
by Marcel de Rooy 03 May '12

03 May '12

Hi all, Recently we discussed in the QA team to make the default QA contact empty. (Ian cleared this field for all components now [for new reports].) In the process the QA team member that starts QA on a report now, enters his name in the QA contact field. This informs reporter, patch writer, etc. that QA started and is also helpful for other QA team members in order to prevent duplication of work. My question now is: Should we do something similar with the default Assignee per component? In practice, the current default assignees will (most of the time) not be working on reports entered by someone else. Having someone in the Assignee field who is not working on that report, could be a misleading signal for an unaware Bugzilla user. If the default assignee wants to be informed on reports of that category, moving him/her to the default CC list of that component would perhaps be better? The current default assignees are (for one or more components): nengard(a)gmail.com<mailto:nengard@gmail.com> henridamien(a)koha-fr.org<mailto:henridamien@koha-fr.org> gmcharlt(a)gmail.com<mailto:gmcharlt@gmail.com> oleonard(a)myacpl.org<mailto:oleonard@myacpl.org> chris(a)bigballofwax.co.nz<mailto:chris@bigballofwax.co.nz> kyle.m.hall(a)gmail.com<mailto:kyle.m.hall@gmail.com> koha.sekjal(a)gmail.com<mailto:koha.sekjal@gmail.com> frederic(a)tamil.fr<mailto:frederic@tamil.fr> cnighswonger(a)foundations.edu<mailto:cnighswonger@foundations.edu> robin(a)catalyst.net.nz<mailto:robin@catalyst.net.nz> colin.campbell(a)ptfs-europe.com<mailto:colin.campbell@ptfs-europe.com> paul.poulain(a)biblibre.com<mailto:paul.poulain@biblibre.com> wizzyrea(a)gmail.com<mailto:wizzyrea@gmail.com> Would you agree with this move? (We need of course consensus before doing so.) Would you like to be added as default CC for one or more components? Please respond. Thanks, Marcel

5 5

Bugzilla component categories
by Chris Nighswonger 02 May '12

02 May '12

On Wed, May 2, 2012 at 8:10 AM, Marcel de Rooy <M.de.Rooy(a)rijksmuseum.nl>wrote: > > My question now is: Should we do something similar with the default > Assignee per component? In practice, the current default assignees will > (most of the time) not be working on reports entered by someone else. > Having someone in the Assignee field who is not working on that report, > could be a misleading signal for an unaware Bugzilla user. If the default > assignee wants to be informed on reports of that category, moving him/her > to the default CC list of that component would perhaps be better? > Like Owen, I try to address most label/card related bugs of which I am the default assignee. I am not convinced that blanking the default assignee would result in much good. Probably a better move would be to encourage developers who decide to work on a bug to do two things: 1. Click the "take" link next to the assignee field. 2. Set the status to "Assigned." Probably any current confusion is due to one of two things: 1. Bugs currently being worked on, but the developer doing the work has failed to do the two things mentioned above. 2. Lack of understanding on the "unaware Bugzilla user's" part which is better remedied by becoming "aware" of how bugzilla works rather than trying to build a better mouse trap. If things were really this difficult, I suspect that Bugzilla would be swamped with enhancement requests or out of business, one. Kind Regards, Chris

4 3