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

Re: [Koha-devel] [Koha] RFC for MARC holdings record support
by Ere Maijala 21 Feb '19

21 Feb '19

Good morning! Thanks for the feedback. I added a note to the RFC about embedded holdings in bibliographic records. They cover a lot of needs and we have considered embedding the holdings, but there are issues if there are multiple holdings. Regards, Ere Sebastian Hierl kirjoitti 5.4.2018 klo 10.08: > Good morning! > > I think that the feature would provide added flexibility, in particular > for monographic series and periodicals. Institutions who currently work > with an ILS that has holdings records would want to see the same in > Koha, should they be considering Koha. We currently use the 866 to > display holdings information, thus I don't see this as essential, but it > would be a useful enhancement. > > Greetings from Rome, > Sebastian > > -- > Sebastian Hierl, Ph.D. > Drue Heinz Librarian, Arthur & Janet C. Ross Library > American Academy in Rome > Via Angelo Masina 5 > 00153 Rome > Italy > > T: +39 06 5846 417 > F: +39 06 5810 788 > > On Wed, Apr 4, 2018 at 5:11 PM, Nick Clemens <nick(a)bywatersolutions.com > <mailto:nick@bywatersolutions.com>> wrote: > > There was some discussion of this at the IRC meeting today, > forwarding on > to the general list as well for librarian input/feedback > > On Tue, Apr 3, 2018 at 3:33 AM Ere Maijala <ere.maijala(a)helsinki.fi > <mailto:ere.maijala@helsinki.fi>> wrote: > > > Hi Katrin, > > > > Thanks for the comments. I'll try to clarify the RFC. > > > > --Ere > > > > Katrin Fischer kirjoitti 1.4.2018 klo 17.32: > > > Hi Ere, > > > > > > thx for your work on that! I've added some comments and > questions at the > > > bottom of the RFC page. I think key is to break the big > development down > > > into multiple steps that can be easily tested. > > > > > > Katrin > > > > > > > > > On 26.03.2018 12:58, Ere Maijala wrote: > > >> Hi Everyone, > > >> > > >> I've written an RFC for adding support for MARC holdings records, > > >> available here: > > >> > <https://wiki.koha-community.org/wiki/MARC_Holdings_Records_RFC > <https://wiki.koha-community.org/wiki/MARC_Holdings_Records_RFC>>. I'd > > >> be grateful for any feedback on this. I know there have been some > > >> initiatives to add (back) holdings records, but this proposal > is a bit > > >> different in that it relies on the MARC format and I already > have it > > >> working in a local custom branch apart from OPAC support. > > >> > > >> Regards, > > >> Ere > > >> > > > > > > _______________________________________________ > > > Koha-devel mailing list > > > Koha-devel(a)lists.koha-community.org > <mailto:Koha-devel@lists.koha-community.org> > > > > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > <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/ > <http://bugs.koha-community.org/> > > > > -- > > Ere Maijala > > Kansalliskirjasto / The National Library of Finland > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel(a)lists.koha-community.org > <mailto:Koha-devel@lists.koha-community.org> > > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > <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/ <http://bugs.koha-community.org/> > > > -- > Nick Clemens > Sonic Screwdriver (Development Support) > ByWater Solutions > IRC: kidclamp > _______________________________________________ > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> > https://lists.katipo.co.nz/mailman/listinfo/koha > <https://lists.katipo.co.nz/mailman/listinfo/koha> > > -- Ere Maijala Kansalliskirjasto / The National Library of Finland

5 8

SQL queries showing data that will cause software errors.
by Barton Chittenden 19 Oct '18

19 Oct '18

When ByWater started upgrading our partners to 17.11 last spring, I noticed that we were getting a lot of errors of the form "can't call method * on an undefined value at ..." We're starting to see these errors because more and more of our code uses Koha objects, and these will fail if a method is called on an undefined object. I brought this up here: http://lists.koha-community.org/pipermail/koha-devel/2018-June/044613.html I think that there was also another thread about this, which I can't find at the moment... Jonathan's opinion on this is that we should start creating queries which find data that will fail. This thread is for those queries, since I have an example: Circulating or holdable items without item type SELECT biblionumber, itemnumber, barcode, title, notforloan FROM items INNER JOIN biblio USING (biblionumber) WHERE notforloan < 1 AND itype IS NULL Once we have a few of these at hand, I'll start a page on the Koha wiki.

2 2

Problem of OpacHiddenItems
by DevinimKoha 01 Oct '18

01 Oct '18

Hello everyone, We faced a quite big problem in Opac search for a while and we were not able to find a workaround for that. When we use OpacHiddenItems system preference value for a specific items, let's say withdrawn items, in the Opac search result, related item become hidden and the numbering is being closed automatically. However if all items in the second page were also hidden then it says "0 results found". Is there anybody hit this problem and any workaround for that? We created the bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19688 and we think that the change in the bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10584 may be the result of this bug. Thanks. Devinim Koha team.

3 3

Koha Community Newsletter: September 2018
by kohanews 29 Sep '18

29 Sep '18

The Koha Community Newsletter for September 2018 is here: https://koha-community.org/koha-community-newsletter-september-2018/ 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. -- Chad Roseburg Editor, Koha Community Newsletter

1 0

git trailers: should we use more of them ?
by Julian Maurice 28 Sep '18

28 Sep '18

Hi all, AFAIK in our commit messages we are using two different trailers: - Signed-off-by tells who tested/reviewed the patch - Sponsored-by tells who sponsored the patch I recently stumbled upon the contribution guidelines for git [1] which suggests to use Reported-by, Acked-by, Reviewed-by, Tested-by and others (Thanks-to, Mentored-by, ...) I think it can be good to credit people who reported bugs or helped in a way other than signing off or writing patches (testers that find bug are helpful but they're not always the signoffers). Also, the distinction between Tested-By and Reviewed-By could help in situations where we don't know for sure if a signoff is only a test or a full QA review. This guide (and the git-commit manpage [2]) also states that we're not really using the Signed-off-by trailer as intended. In short, a "signoff" means (for git developers) that the patch author agrees to https://developercertificate.org/ I'd like to know what you think about this. Should we use Reported-By ? Should we replace Signed-off-by by Tested-By (for testers) and Reviewed-By (for QA) ? Should we use Signed-off-by as suggested in the git-commit manpage ? Do you think it is not worth the effort or that a change would be bad in some way ? Thanks [1] https://github.com/git/git/blob/master/Documentation/SubmittingPatches [2] https://git-scm.com/docs/git-commit#git-commit--s -- Julian Maurice <julian.maurice(a)biblibre.com> BibLibre

6 7

Bug 1993 - Task Scheduler Needs Re-write
by Barton Chittenden 28 Sep '18

28 Sep '18

This is an old issue that's never really been addressed. As I understand it, at one time, we had a tool that used the unix 'at' scheduler to run requested reports. This was a huge security hole, and we disabled it.... and it's never worked since. As such, those who host servers must add calls to runreport.pl by hand. Bug 1993 was opened to address this. It was marked as 'In Discussion' in 2013. I would like to see this move forward -- server admins are dying from a thousand paper cuts, and I think that users would benefit from having more control over when their reports are scheduled. What still needs to be discussed here? Thanks, --Barton

5 5

Inventory lists incorrectly sorted
by David Cook 28 Sep '18

28 Sep '18

Hi all, Has anyone had a problem where the lists generated by the inventory tool don't seem to be sorted correctly? I received reports of this and during my investigation I found https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19021 but that didn't seem to solve the root problem, which actually appears to be with the item data stored in the database - rather than Koha code per se. I've opened https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21447 to look into this. I've solved it in my case using touch_all_items.pl, but it might not be feasible for everyone to run this. Keen to hear ideas about how people think we should resolve this issue for all people. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

1 0

ILS-DI GetRecords
by Jonathan Druart 28 Sep '18

28 Sep '18

Hi devs, I am trying to remove the subroutine GetItemsByBiblioitemnumber, which is only used from C4::ILSDI::Services::GetRecords. It generates timestampX, cardX and borrowerX for the last 3 patrons who checked out the items. I have no idea if it is a desired effects but, as this code has been there for a very long time (2005), I suspect it's not. Could anyone confirm? The "doc" (/ilsdi.pl?service=Describe&verb=GetRecords) does not say anything about the checkouts info. Cheers, Jonathan

4 3

Koha 18.11 Dates
by Nick Clemens 25 Sep '18

25 Sep '18

Hi All, My planned dates for the 18.11 release are: November 2 - Feature slush - no enhancement/new features that have not passed QA will be considered for release November 9 - Feature freeze - only bugfixes will pushed after this - 1st draft of release notes November 16 - String Freeze - 2nd draft of release notes November 27 - Release Let me know if there is any feedback or a need to adjust the dates. Thanks, Nick -- Nick Clemens Sonic Screwdriver (Development Support) ByWater Solutions IRC: kidclamp

1 0

zebra package
by Paul A 24 Sep '18

24 Sep '18

Has anyone else had a problem installing zebra (possibly 2.0.44) on Ubuntu 18.04LTS? We are currently updating our IT structure as part of our two-year LTS cycle. Koha (various versions, all tarball which is a policy decision) install properly, have perfect www interfaces (admin and public), but fail as all searches report nothing found, because zebra is apparently mis- | badly | not installed ("about" gives a blank, where 12.04, 14.04 and 16.04 report "Zebra 2.0.44") On the other hand, commands such as: ./bin/migration_tools/rebuild_zebra.pl -a -r -v ./bin/migration_tools/rebuild_zebra.pl -b -r -v -x work perfectly, reporting proper numbers of auths and bibs, cleaning, and reporting no errors. I would welcome any thoughts, particularly a debian/ubuntu package repository/name suitable for either apt or cpan. Thanks. Paul

6 11