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

Re: [Koha-devel] [Koha] "borrowers" permission doesn't allow to see
by BOUIS Sonia 03 Dec '15

03 Dec '15

Hi Jonathan ! Here it is : http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15289 Cheers, Sonia Message: 3 Date: Tue, 1 Dec 2015 17:38:19 +0000 From: Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> To: "koha-devel(a)lists.koha-community.org" <koha-devel(a)lists.koha-community.org> Subject: Re: [Koha-devel] [Koha] "borrowers" permission doesn't allow to see current loans Message-ID: <CAJzKNY75nG308f_oYen3aYdv87pbrxEw6SAYdvV9q4eeiPty4g(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Sonia, Yes, it's a bug, please open a bug report Cheers, Jonathan 2015-12-01 17:17 GMT+00:00 BOUIS Sonia <sonia.bouis(a)univ-lyon3.fr>: > Hi, > I have a question about the user permission "borrowers". It gives an access to the Details page of a patron. In our previous version, we can see the list of the document checkout in this page. Now, we just have the information 'loading' in the checkout tables, but we can't see documents on loan. (It's the same on the master version). > It's really damageable because we have some students who works in the library who can't do circulation actions, but who should be able to inform patrons to tell them how many books they have, tell them the due date... > > I don't know if this change of behaviour was done on purpose, but for me, it looks like a regression. If everybody is ok with that, I can fill a bug in bugzilla. > > Best regards, > > Sonia BOUIS > > Responsable du Syst?me int?gr? de gestion des biblioth?ques > > bIBLIOTH?QUES UNIVERSITAIRES > Universit? Jean Moulin Lyon 3 > 6 Cours Albert Thomas - B.P. 8242 - 69355 Lyon Cedex 08 ligne directe > : +33 (0)4 78 78 79 03 | > http://bu.univ-lyon3.fr<http://bu.univ-lyon3.fr/> > > L'Universit? Jean Moulin est membre fondateur de l'Universit? de Lyon > > _______________________________________________ > Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha ------------------------------ _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha-community.org http://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/ End of Koha-devel Digest, Vol 121, Issue 4 ******************************************

1 0

Inventory/Stocktake Tool UX Improvements
by David Cook 03 Dec '15

03 Dec '15

Hi all: It seems to me that the inventory tool isn't working quite right. at least in 3.14.05. I admit that I haven't checked it in 3.20/3.22/master. I've always found the design of the inventory.pl pages to be rather confusing. Perhaps it's time for a make over? When I read the manual/help and when I look at the page, I figure that it should either generate a shelf list, or upload a barcode list of items to update, or upload a barcode list of items to update and compare it against a shelf list. In the first scenario, no barcode list is provided. So it just generates a shelf list that you can print off to go around the library checking off things manually. In the second scenario, you've scanned maybe 20 barcodes, and you want to update the "date last seen" for those 20 items. So you upload the barcode list, hit submit, and it just updates those 20 items - with no reference at all to a shelf list or the items specified by "Select items you want to check" or "Item statuses". In the third scenario, you've scanned maybe 200 barcodes (e.g. your graphic novel collection), you upload the barcode list, you check "Compare barcode list to results", and click submit. It updates those 200 items AND it shows you a list of items that SHOULD have been scanned too. At the moment, I think the "first scenario" and "third scenario" happen correctly. However, the "second scenario" does not. It basically acts like the "third scenario" except it doesn't give you a list of items that should have been scanned too. although it still looks them up. I recall a few changes have been made in 2015, but I'm not sure if any of them deal with this issue. None of the bug report titles seem to suggest that it has been dealt with. Anyway, I figure that logical change should be made, but maybe also some UX changes so that it's actually fairly intuitive what the hell is going on when people use the inventory tool. I've been working on Koha for 4 years, and every time I look at it, I need to figure it out again. -- Tl;dr. Is anyone attached to the current interface for doing inventories? Are folks in favour of it being changed to be more user-friendly? Are people all right with there being 3 logical scenarios which I've outlined above? (guess you do need to read it after all) David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007

2 1

"borrowers" permission doesn't allow to see current loans
by BOUIS Sonia 01 Dec '15

01 Dec '15

Hi, I have a question about the user permission "borrowers". It gives an access to the Details page of a patron. In our previous version, we can see the list of the document checkout in this page. Now, we just have the information 'loading' in the checkout tables, but we can't see documents on loan. (It's the same on the master version). It's really damageable because we have some students who works in the library who can't do circulation actions, but who should be able to inform patrons to tell them how many books they have, tell them the due date... I don't know if this change of behaviour was done on purpose, but for me, it looks like a regression. If everybody is ok with that, I can fill a bug in bugzilla. Best regards, Sonia BOUIS Responsable du Système intégré de gestion des bibliothèques bIBLIOTHÈQUES UNIVERSITAIRES Université Jean Moulin Lyon 3 6 Cours Albert Thomas - B.P. 8242 - 69355 Lyon Cedex 08 ligne directe : +33 (0)4 78 78 79 03 | http://bu.univ-lyon3.fr<http://bu.univ-lyon3.fr/> L'Université Jean Moulin est membre fondateur de l'Université de Lyon

2 1

Can the file misc/maintenance/fix_accountlines_date.pl be removed? (Bug 15076)
by Marc Véron 01 Dec '15

01 Dec '15

Hi all Following bug is "In Discussion": Bug 15076 - Remove file misc/maintenance/fix_accountlines_date.pl Is the file still in use by anybody or can it be removed? Thanks for comments on http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15076 Marc

1 0

Benchmarks - prior to the 3.22 release
by Jonathan Druart 01 Dec '15

01 Dec '15

Hi devs, Please have a look at the these benchmarks: http://wiki.koha-community.org/wiki/Benchmark_for_3.22 I let you draw the appropriate conclusions. Cheers, Jonathan

4 12

Debugging in vim
by Barton Chittenden 01 Dec '15

01 Dec '15

Hi, has anyone gotten debugging to work in vim, using the instructions here? http://wiki.koha-community.org/wiki/Debugging_in_VIM I tried it, and ran into dependency hell... If I remember correctly, Komodo-PerlRemoteDebugging-4.4.1 didn't play nicely with https://github.com/joonty/vdebug. If someone *has* gotten this working, I'd like to know how it was done, so that I can update the wiki. Thanks, --Barton

3 2

Re: [Koha-devel] Proposed "metadata" table for Koha
by David Cook 30 Nov '15

30 Nov '15

For now, I think the metadata.record_id would link to biblionumber, but long-term it would probably link to some “record” table. So if you wanted to get all bibliographic records, you’d do something like: select * from record join metadata ON record.id = metadata.record_id where record.type = ‘bibliographic’ Or maybe you want to search for a bibliographic record with a 001 of 123456789: select * from record join metadata ON record.id = metadata.record_id where record.type = ‘bibliographic’ and metadata.qualifier = ‘001’ and metadata.value = ‘123456789’ -- Of course, off the top of my head, I don’t know how you’d store indicators and subfields in an extensible way. I suppose indicators are attributes and subfields are child elements... I suppose DSpace actually does a “element” and “qualifier” approach for DC. So you’d have a “dc”, “author”, “primary”. Or “marc21” “100” “a”. Of course, that creates a limit of a single level of hierarchy which may or may not be desirable… and still doesn’t account for indicators/attributes. I suppose there is more thinking to do there. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 From: Barton Chittenden [mailto:barton@bywatersolutions.com] Sent: Monday, 30 November 2015 2:17 PM To: David Cook <dcook(a)prosentient.com.au> Subject: Re: [Koha-devel] Proposed "metadata" table for Koha > The basic schema I have in mind would be something like: metadata.id <http://metadata.id> , metadata.record_id, metadata.scheme, metadata.qualifier, metadata.value. > > > > The row would look like: 1, 1, marc21, 001, 123456789 I think this is an interesting idea... Obviously the replication of biblio data is not ideal, but I think that that's a necessary and worthwhile trade off in terms of moving away from MARC. How do you propose linking the metadata fields to the biblio records? Does the metadata.record_id link to biblionumber?

3 2

Koha Community Newsletter: November 2015
by Koha Newsletter 30 Nov '15

30 Nov '15

Fellow Koha users: The Koha Community Newsletter for November 2015 is here: https://koha-community.org/koha-community-newsletter-november-2015/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. Thanks! Chad Roseburg Editor, Koha Community Newsletter

1 0

Koha 3.22 released
by Tomas Cohen Arazi 27 Nov '15

27 Nov '15

It is with great pleasure that we announce the release of Koha 3.22, a major release of the Koha open source integrated library system. Koha 3.22 is a major release, that comes with many new features. See the full release notes here: https://koha-community.org/koha-3-22-released/ Download: http://koha-community.org/download-koha/ Debian packages for this beta will be available soon on the unstable repository. Thanks everyone! -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F

7 6

Indexes of Physical presentation
by Fridolin SOMERS 24 Nov '15

24 Nov '15

Hie, In intranet search, physical presentation uses index ff8-23. In opac search, physical presentation uses index Material-type. This is strange because the search always use the coded values, meaning it is ff8-23 the correct index. Do you agree ? Regards, -- Fridolin SOMERS Biblibre - Pôles support et système fridolin.somers(a)biblibre.com

3 5