November 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

Bugzilla search question
by Barton Chittenden 05 Dec '18

05 Dec '18

Is there any way to change the default statuses on the bugzilla advanced search page? https://bugs.koha-community.org/bugzilla3/query.cgi The default statuses searched are NEW, REOPENED and ASSIGNED... which skips bugs that are 'In Discussion', 'Needs Signoff', 'Signed off', 'Passed QA', 'Pushed for QA', 'Failed QA', 'Patch doesn't apply' or 'Pushed to (Mater|Stable)'... in other words, most of the statuses that we use the most. I'd prefer to customize this on my own account, but it certainly wouldn't hurt my feelings if the changes were made globally. Thanks, --Barton

2 1

Autorenewals renewing an item then sending a renew failure email the next day
by David Cook 30 Nov '18

30 Nov '18

Hi all, I've found a case where autorenewals will renew an item one day (e.g. Monday) and the next day (e.g. Tuesday) it will say that a hold has been found and that it can't renew the item. (Someone must've put a hold on the item between the two cronjob runs.) It seems to me this is a bug in how C4::Circulation::CanBookBeRenewed is written. The first check it makes is for holds and if it finds a hold it returns an error. However, if you're using autorenewals, you should first check to see if it's too early to even bother renewing. I'm just emailing here to see if anyone else is having this issue, or if anyone knows if there is already a Bugzilla issue open for it. It seems like there are a lot of autorenewal Bugzilla issues but I couldn't find anything. Figure asking first lessens the need for someone to mark one as a duplicate later. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

2 4

Koha 18.11.00 released
by Nick Clemens 29 Nov '18

29 Nov '18

Hello everybody, It is with great pleasure that the Koha community announces the release of Koha 18.11, a major release of the Koha open source integrated library system. This release (as always) is the work of many librarians, developers, and community members who donate their time and effort to the project. Their contributions help shape the release, and the project going forward. None of this would be possible without them, and my sincere thanks goes out to everyone who had a hand in the project Read the full release notes here: https://koha-community.org/koha-18-11-release/ Debian packages are available, if you are following a suite you will automatically upgrade to the next branch with this release, more info here: https://wiki.koha-community.org/wiki/Koha_on_Debian#Follow_a_suite:_stable.… Thank you all, Nick (kidclamp) -- Nick Clemens Sonic Screwdriver (Development Support) ByWater Solutions IRC: kidclamp

6 5

Re: [Koha-devel] [Koha] 18.11 Release
by Nick Clemens 27 Nov '18

27 Nov '18

Unfortunately we hit an issue during the packaging, Mirko filed a bug here: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21895 Any help is appreciated to get this cleared and the releas out the door. On Tue, Nov 27, 2018 at 2:35 PM King, Fred <Fred.King(a)medstar.net> wrote: > Congratulations! The Avenging Chicken is all aflutter. > > (New Adventure of Fred and the Avenging Chicken now available at > avengingchicken.online.) > > Fred King > Medical Librarian, MedStar Washington Hospital Center > fred.king(a)medstar.net > 202-877-6670 <(202)%20877-6670> > ORCID 0000-0001-5266-0279 > MedStar Authors Catalog: http://medstarauthors.org > > Somehow it seems I managed to get old. I really have no idea how that > happened. > --Brian Baker > > > -----Original Message----- > From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Nick > Clemens > Sent: Tuesday, November 27, 2018 1:54 PM > To: Koha Devel; Koha > Subject: [Koha] 18.11 Release > > ** ATTENTION: This email originated from outside the MedStar network. ** > DO NOT CLICK links or attachments unless you recognize the sender and know > the content is safe. > > HI All, > > Just a heads up the release is prepared, we are waiting on packages and > final details. Will let you know once it is all set and ready to go. > > Your excited RM, > Nick > -- > Nick Clemens > Sonic Screwdriver (Development Support) > ByWater Solutions > IRC: kidclamp > _______________________________________________ > Koha mailing list > https://urldefense.proofpoint.com/v2/url?u=http-3A__koha-2Dcommunity.org&d=… > Koha(a)lists.katipo.co.nz > > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.katipo.co.nz_mai… > -- Nick Clemens Sonic Screwdriver (Development Support) ByWater Solutions IRC: kidclamp

1 0

18.11 Release
by Nick Clemens 27 Nov '18

27 Nov '18

HI All, Just a heads up the release is prepared, we are waiting on packages and final details. Will let you know once it is all set and ready to go. Your excited RM, Nick -- Nick Clemens Sonic Screwdriver (Development Support) ByWater Solutions IRC: kidclamp

3 2

Building Koha Debian packages in Docker
by David Cook 27 Nov '18

27 Nov '18

Hi folks, I was wondering if anyone had a Docker image for building Koha Debian packages. I scouted around a bit and found this image from Jonathan https://gitlab.com/joubu/koha-dpkg-docker but nothing else. So I've put together my own project which you can find here: https://gitlab.com/minusdavid/koha-deb-builder-docker The "build.sh" script is still rough around the edges, but it all works. Basically you build the Docker image, dump a tarball into "input" (generated using git archive with a properly formatted prefix and filename), run a container, run the build.sh script, and then when the process is done you should have some Debian packages in your "output" directory which is shared with your host computer. Happy to accept pull requests or talk about it in general. The Docker image is pretty heavy, but that's because the Debian packaging tools are heavy. The build process is also a bit long because it has to install all the "build dependencies", although I think we could tweak the debian/control file so that we don't have to install everything just to build the packages. Also I couldn't get the tests to complete successfully on the first go so I've turned them off for now. Fixing the image or the tests so that they can run would be cool. Anyway, just thought I'd share that with everyone. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

3 9

Koha 18.05.06 release
by Renvoize, Martin 26 Nov '18

26 Nov '18

The Koha community is proud to announce the release of Koha 18.05.06. This is my final release as the 18.05.x maintainer, but I will be returning next cycle as the next stable (18.11) maintainer. The 18.05.x series will live on in the capable hands of Lucas Gass and Jesse Maseto. This is a maintenance release containing 67 bugfixes The full release notes are available at https://koha-community.org/koha-18-05-06-release/ Debian packages will be updated within a few days Many thanks to everyone involved, *Martin Renvoize* <https://www.ptfs-europe.com> Development Team Manager *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvoize(a)ptfs-europe.com *Fax:* +44 (0) 800 756 6384 www.ptfs-europe.com Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info(a)ptfs-europe.com

2 1

Koha 17.11.12 release
by Fridolin SOMERS 26 Nov '18

26 Nov '18

The Koha community is proud to announce the release of Koha 17.11.12. This is a maintenance release. The full release notes are available at https://koha-community.org/koha-17-11-12-release/ Debian packages will be upgraded in a few days. Regards, -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> BibLibre, France - software and system maintainer

1 0

What is biblioitemnumber for?
by Barton Chittenden 21 Nov '18

21 Nov '18

Just out of curiosity, why does biblioitemnumber exist? There should be a one-to-one relationship between biblio records and biblioitem records ... so why not use biblionumber as the primary key for biblioitems? --Barton

9 16