[Koha-devel] Call for news: March 2017 Newsletter

2017-03-14 Thread kohanews 

I'm collecting news for the March newsletter. Send anything noteworthy to:

k o h a news AT gmail dot com

News criteria:
---

** For events **:
   - Please include dates for past events. If I can't find dates I may 
not add it.
   - Announcements for future events with dates T.B.A. are fine ...Eg., 
Kohacon

   - For past events ,  one month back is the cut-off  .

* News items can be of any length.
* Images are fine
* Anything and everything Koha.
* Submit by the 26th of the month.

If you are working on an interesting project or development related to
Koha, please let me know and I'll include it in the development section.


--
Chad Roseburg
Editor, Koha Community Newsletter

___
Koha-devel mailing list
Koha-devel@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/

Re: [Koha-devel] Interlibrary loans module

2017-03-14 Thread Gaetan Boisson 

 Hi Alex,

Would you consider presenting this work at the hackfest?

I'd be very interested!

Cheers,


Le 22/02/2017 à 07:52, Alex Sassmannshausen a écrit :

Hugo Agud writes:


Hi Alex

Wow! it sounds great.. I will try to do my best with this bug ;)

Fabulous!  Let me know if you need a pointer.

Alex


Kindest Regards
Hugo

2017-02-21 11:57 GMT+01:00 Alex Sassmannshausen 
:

  Hello Kohites!

  Andrew and I have just finished a second major revision of our proposed
  interlibrary loans module for Koha. The code and bug can be found at
  [https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7317].

  We believe the code has now reached the maturity it requires for wider
  engagement, and, more importantly, it's now reached the maturity that it
  should be easy to get it up and running relatively easily in your
  development environments.

  Unfortunately we cannot deploy the module using sandboxes because
  backends are implemented as separate code projects.

  And we would *love* your comments thoughts and concerns about the module
  if you are interested in ILL!

  The final comment on the bug contains basic documentation for the Module
  as a whole, and also some installation instructions. But for reference,
  I've attached the same document to this email too.

  Below you will find some further high-level background and a roadmap of
  what we would like to achieve.

  For now, if you're interested in this module:
  • have a look at the bug, and get involved in the discussion!
  • try to set up the module in your dev environment. It should work
  easily on dev boxes and dev installs that track master.
  • let us know if you face any issues!
  • start a conversation with us if you might be interested in creating a
  backend for your country's / organization's ILL workflows.

  Finally, if you don't have access to a development environment, but you
  would be interested in becoming involved in this project, get in touch
  and we might be able to provide you with access to a testing
  environment!

  Best regards,

  Alex Sassmannshausen

  PTFS Europe

  1 High-level background
  ═══

  The ILLModule aims to provide a core framework against which different
  ILL workflows can be implemented within Koha. It achieves this by
  using 2 new tables as data store, and by using an extensible backend
  system to create 'connectors' to ILL providers.

  The data store consists of the illrequests and the
  illrequestattributes tables. The former is a traditional table that
  stores essential values associated with an ILL request. The later is
  a key/value store, linked to a row in the former. This store can be
  used to store arbitrary data provided by a backend.

  The backends implement highly customizable workflows for several core
  steps in the ILL management process.

  At the same time, each backend can extend the core steps (called
  defined as the `core_status_graph` in Koha/Illrequest.pm) with their
  own additional steps (defined as the `status_graph` in a backend's
  Base.pm).

  Each of these steps, both core and extensions, in turn can define any
  number of 'stages' required to complete each individual step.

  Each step has access to a template include file, which can dispatch on
  'stage'. This is mirrored by each step having a sub in a backend's
  Base.pm, which once again can dispatch on 'stage'. The subs in
  Base.pm have access to the full data store provided by the ILLModule;
  similarly the template includes have full access to Koha template
  features, including access to custom JS blocks through which, for
  instance, external APIs can be called.

  The main aim of this Koha module was to provide a core that is
  comprehensive enough to store core data to only have to implement ILL
  once in Koha, whilst being extensible enough so that virtually any ILL
  workflow can be implemented against this core.

  We believe we have achieved this. I'd be very interested to hear from
  you if you believe you have a workflow that cannot be captured by this
  (obviously, third party tools that do not provide API access will be
  virtually impossible to seamlessly integrate into Koha).

  2 Roadmap
  ═

  The roadmap starts from the current release of code on the bugzilla
  issue.

  • Publication of mature beta level code (21 February 2017)
  ⁃ public testing
  ⁃ public discussion
  ⁃ dogfooding

  • Augment core functionality (~ June 2017)
  ⁃ add advanced configuration options for the core module
  ⁃ add a standard system for configuring backends
  ⁃ allow for an 'unmediated workflow'
  ⁃ finalise 'generic requests' workflow

  • Meet Koha QA standards (~ July 2017)
  • Add unit tests to core ILLModule
  • Ensure UI respects Koha standards
  • Ensure Core code passes qa scripts

  • Addition of Documentation
  ⁃ contributing a chapter to the Koha manual
  ⁃ ensure all pod information is correct and complete
  ⁃ ('writing your own

Re: [Koha-devel] Multi language item types, branch names, sysprefs value, authorised values, and permission descriptions

2017-03-14 Thread Jonathan Druart 
Hello Massoud,

As far as I know there is nothing planned yet.
If you really want it, you can hire a developer to implement what you want.
Note that bug 17762 will allow to translate notices.

Regards,
Jonathan

On Sat, 4 Mar 2017 at 03:29 Massoud Alshareef  wrote:

> Hello Jonathan,
>
> Last year with Koha 3.22 came a nice feature to enable Koha libraries to
> add another description in another language to the following policies'
> names:
> item types, branch names, sysprefs value, authorised values, and permission
> descriptions
>
> Enabling this translation feature was implemented with item types
> description only. When we asked then about the other policies, it was told
> then that they will follow in upcoming releases. Koha 16.xx then came out,
> with all its subsequent major/ minor releases following, and this feature
> do not seem to be placed in the development list to be extended to other
> policies as promised.
>
> I just wonder if we should expect the extension of this feature to enable
> multi language support of other policies' names sometime soon.
>
> Thanks,
> Massoud M. AlShareef
> KnowledgeWare
>
___
Koha-devel mailing list
Koha-devel@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/

Re: [Koha-devel] Expected behaviod when printing serials - add reserve?

2017-03-14 Thread Katrin 

Hi Jonathan,

I think placing a hold in the first place should depend on the 
RoutingListAddReserves system preference that has been broken for quite 
a while.


I think someone told me that it was possible in the past to have a hold 
without an item? Not sure if that is true. But I would suggest this 
behaviour:


- Use the system preference to determine, if a hold should be set
- Only set item level holds. In order to pick the right item, this would 
then depend on "creating items on receive" with your subscription|.|


|There are some bugs files related to this:|

*Bug 2894* 
 - 
Routing list holds are broken


And the following one, that appeared to fix the problem in my testing, 
but is currently sitting in Failed QA:


*Bug 7957* 
 - 
Routing lists: manage several routing list for each subscription, and 
export them as CSV


Hope this helps,

Katrin


On 13.03.2017 17:25, Jonathan Druart wrote:

Hi devs,

I found an obvious bug in serials/routing-preview.pl 
.
If the script is called with ok=1 (hum... yes...), the script will add 
or modify a hold placed on the bibliographic records existing in the 
routing list.
So from /serials/serials-collection.pl?subscriptionid=1 
, click on "Print list" 
you get a pop-up with a print and close button.

When the pop-up is generated, we already have the ok=1 and the go through:
  66: my ($count2,@bibitems) = GetBiblioItemByBiblioNumber($biblio);
Then later:
 96 
AddReserve($branch,$routing->{borrowernumber},$biblio,\@bibitems,$routing->{ranking}, 
undef, undef, $notes,$title);


The problem is that GetBiblioItemByBiblioNumber will always return 
only 1 value (for obvious reasons) and @bibitems will always be empty 
=> reserve is placed at bib level


The thing is that this bug exists for ages (at least 2006, maybe always).
What is the expected behaviour?

No need to tell you that I was going to kick 
GetBiblioItemByBiblioNumber when I found that bug.


Cheers,
Jonathan


___
Koha-devel mailing list
Koha-devel@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/


___
Koha-devel mailing list
Koha-devel@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/

[Koha-devel] Hackfest in Marseille, last call before closing gates

2017-03-14 Thread Paul Poulain 

Hello,

the hackfest in Marseille is next week. If someone is willing to attend, 
it's still time. For now, 44 ppl are attending


BibLibre18
BM Vitré1
BSZ 1
BULAC   1
BywaterSolutions5
CIRAD   1
Dracénie1
IEP G.  4
Lyon 3  1
MOMU1
MPtech  1
Organisation1
PTFS-E  1
U Paris 8   1
Université Aix Marseille4
Université Lyon 2   2
Grand Total 44

Belgium 2
Country 1
France  35
Germany 2
USA 5
Grand Total 45

--
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
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/

Re: [Koha-devel] How to see security fixes

2017-03-14 Thread Chris Cormack 
Hi, 

Normally once they are released the release maintainer shifts them out of 
security. That one got missed, shifted now 

Chris 

On 14 March 2017 9:13:51 PM NZDT, Devinim Koha Development Team 
 wrote:
>Hi all,
>
>How can we see the fixes of security bugs?
>
>We've faced with a vulnerability with Bug# 16969 in a new version, but 
>it's said that it was fixed in 3.22.10.
>
>
>Thanks.
>
>Devinim Koha Dev. Team
>
>___
>Koha-devel mailing list
>Koha-devel@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/

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.___
Koha-devel mailing list
Koha-devel@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/

[Koha-devel] How to see security fixes

2017-03-14 Thread Devinim Koha Development Team 

Hi all,

How can we see the fixes of security bugs?

We've faced with a vulnerability with Bug# 16969 in a new version, but 
it's said that it was fixed in 3.22.10.



Thanks.

Devinim Koha Dev. Team

___
Koha-devel mailing list
Koha-devel@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/