October 2013 - Koha-bugs - lists.koha-community.org

[Bug 7712] New: a single holds report
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '14

08 Oct '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7712 Priority: P5 - low Change sponsored?: --- Bug ID: 7712 CC: gmcharlt(a)gmail.com Assignee: koha.sekjal(a)gmail.com Summary: a single holds report QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: melia(a)bywatersolutions.com Hardware: All Status: NEW Version: master Component: Hold requests Product: Koha Koha currently has two holds reports: Holds to Pull and Holds Queue. The difference between them is often unclear and confusing. The system shall provide a single report page to detail which materials should be pulled from a branches shelves, and where these items should be sent. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 7711] New: clear holds statuses and workflow
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '14

08 Oct '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7711 Priority: P5 - low Change sponsored?: --- Bug ID: 7711 CC: gmcharlt(a)gmail.com Assignee: koha.sekjal(a)gmail.com Summary: clear holds statuses and workflow QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: melia(a)bywatersolutions.com Hardware: All Status: NEW Version: master Component: Hold requests Product: Koha Created attachment 8197 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=8197&action=edit Status Workflow Mapping Clear statuses For each hold in the system, there should be a clear, single status to describe it's current state. These statuses should include: Waiting (in holds queue) Ready to pull Pulled and awaiting pickup Filled Expired Long waiting In transit Suspended Canceled Since these statuses have concrete system states attached to them, they must be hard coded into the system. The use of an Authorized Value list would not be sufficient. Status Workflow Not every status should be reachable from every other status. Attached is a mapping of which statuses a hold shall be able change between. O with a green background indicates possible, while X with a red background indicates impossible. Grey cells are for self-references. [Please see attachment.] Holds shall be considered 'waiting in queue' until they reach the top position of the queue, at which time they change to 'ready to pull'. While in the queue, they can expire, be suspended, or be canceled. Once the hold is ready to pull, the next natural next step for the hold to transition to the “Pulled” state, where it awaits being picked up by the patron. Since this status just means the hold is at the top of the queue, if the queue is rearranged, the status of the hold could go back to 'Waiting in queue'. The hold can also expire, be suspended or be canceled. After the hold is pulled, it should either be picked up by the patron and marked as 'filled', or put 'in transit' to the pick up location. It can also still expire or be canceled. If the hold waits to be picked up for more than appropriate MaxReservePickupDelay circ rule, it will be marked as 'long waiting'. If a hold needs to be transferred to another branch, the status shall go from 'Ready to Pull' to 'In Transit'. Once the item arrives at it's destination and is received, it shall be marked as 'Pulled and ready for pickup' Expired, Suspended and Canceled holds can be brought back into the queue. “Filled” is a terminal status; the hold record can now be archived. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 6891] New: LDIF interoperability - a proposal
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '14

08 Oct '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6891 Bug #: 6891 Summary: LDIF interoperability - a proposal Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Tools AssignedTo: gmcharlt(a)gmail.com ReportedBy: xan(a)biblionix.com QAContact: koha-bugs(a)lists.koha-community.org Hello Koha Community, I'm Xan Charbonnet with Biblionix. We're a small company that provides a hosted ILS, Apollo, to small and medium-sized public libraries in the US. We're not open-source, but we do strongly believe in open interchange: library data belongs to libraries, and shouldn't be used as a hostage to keep libraries chained to their automation systems. Far too many systems do treat their customers this way. There are even Koha consortia which are charging their librarians multi-thousand dollar extraction fees just to get their own data out! We've developed what we call LDIF (library data interchange format), which is a W3C XML Schema that defines a way for library data to be stored and exchanged in a vendor-independent manner. We believe this is an important capability which has been missing in the library world. Any Apollo library is able to generate an LDIF file at any time, and download (practically) everything that Apollo knows about their library in a single, well-defined file, complete with the schema. Ideally, that file would be easily importable into any other ILS. Part of making LDIF "real", of course, is engaging other ILS vendors. The Koha Community seemed like the place to start. Is there anyone working on the Koha project who would have an interest in developing support for this fledgling standard? And of course, in working with you, there will likely be changes to be made to LDIF, which will make it better for everyone. LDIF Schema: http://www.biblionix.com/ldif.xsd Example library export (I recommend that you download this rather than view it in your browser; it's a 4MB XML file): http://www.biblionix.com/demolibrary_2011-09-20.xml -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 26

[Bug 7611] New: Show the NOT_LOAN authorised values for item status in XSLT OPAC search results.
by bugzilla-daemon＠bugs.koha-community.org 07 Oct '14

07 Oct '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7611 Bug #: 7611 Summary: Show the NOT_LOAN authorised values for item status in XSLT OPAC search results. Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: fcapovilla(a)live.ca QAContact: koha.sekjal(a)gmail.com Created attachment 7905 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=7905 XSLT Results template improvement : Use the NOT_LOAN authorised values Improvement : Use the NOT_LOAN authorised values when showing items status in the OPAC search results. Before this patch, these items were only considered as "unavailable". Note : This patch only affects the OPAC XSLT search results template for MARC21 records. This patch was not tested on UNIMARC or NORMARC records. I won't be able to support these formats, so I'm hoping someone could do the same for these other record formats. Patch attached. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 7

[Bug 10873] New: Lots of wasted space in Serial Search Result table
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '14

02 Oct '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10873 Bug ID: 10873 Summary: Lots of wasted space in Serial Search Result table Change sponsored?: --- Product: Koha Version: 3.12 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com /cgi-bin/koha/serials/serials-search.pl?routing=1&searched=1&title_filter= Users with low resolutions or small screens may have an issue where this table exceeds the width of their viewable area. There appears to be a lot of wasted space in the columns, perhaps we could reduce the amount of space allotted to some of those columns and make the experience a little more comfortable for these users. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 6748] New: Add link to fast add framework while circulating, if a barcode is not found
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '14

02 Oct '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6748 Bug #: 6748 Summary: Add link to fast add framework while circulating, if a barcode is not found Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: chris(a)bigballofwax.co.nz QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Work To Be Done: * Add a button to the "unknown barcode" message in checkout that would bring the user to the Fast Add Framework (for consistency with the rest of Koha) o Automatically populate the barcode with the value scanned o Automatically populate the homebranch and holdingbranch with the currently logged in branch o Automatically populate the non public note to say “return the item to cataloging” * Upon save, the item will automatically be checked out the patron. How to test: * Scan a barcode that is not in your system in the check out screen * Confirm that the behavior follows the above -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 12

[Bug 6858] New: Adds staticfines.pl for static fines processing
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '14

01 Oct '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6858 Bug #: 6858 Summary: Adds staticfines.pl for static fines processing Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: matthias.meusburger(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Add a tool to calculate static fine. For example, 7 days left = 1€ fixed fine -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 39

[Bug 6809] New: Add branch filter in holds to pull report
by bugzilla-daemon＠bugs.koha-community.org 30 Sep '14

30 Sep '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6809 Bug #: 6809 Summary: Add branch filter in holds to pull report Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Hold requests AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: savitra.sirohi(a)osslabs.biz QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Currently only date filters available, add branch filter. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 5

[Bug 8074] New: Holds to pull
by bugzilla-daemon＠bugs.koha-community.org 30 Sep '14

30 Sep '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8074 Priority: P5 - low Change sponsored?: --- Bug ID: 8074 CC: gmcharlt(a)gmail.com Assignee: kyle.m.hall(a)gmail.com Summary: Holds to pull Severity: enhancement Classification: Unclassified OS: All Reporter: stephane.delaye(a)biblibre.com Hardware: All Status: NEW Version: rel_3_8 Component: Circulation Product: Koha To create the list 'Holds to pull' we must enter the branch and the location at the bottom of the page. It is possible to store in memory the informations(branch, location) that we have chosen; We don't want enter the same informations each time we refreh the screen -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 10135] New: Adding the ability to define customised basketgroups pdf layouts
by bugzilla-daemon＠bugs.koha-community.org 29 Sep '14

29 Sep '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10135 Bug ID: 10135 Summary: Adding the ability to define customised basketgroups pdf layouts Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P3 Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathieu.saby(a)univ-rennes2.fr We have 2 available layouts for basketgroups : layout2pages and layout3pages. Both are untranslatable, and not very pretty. We defined our own layout in Rennes 2, in french, with the logo of the universiy, etc... To use it, we were forced to make a local development, because there is a safty condition in basketgroup.pl. M. Saby -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13