Hi All I have pushed up 7 branches on git.koha-community.org new/awaiting_qa/biblibre_memb_circ_upd new/awaiting_qa/biblibre_admin new/awaiting_qa/biblibre_various new/awaiting_qa/biblibre_serials new/awaiting_qa/biblibre_cataloguing new/awaiting_qa/biblibre_opac new/awaiting_qa/biblibre_acquisitions They are all awaiting QA. Another branch new/biblibre_reports Has been through initial QA, and feedback has been sent to Biblibre, once that has been dealt with, that branch will be merged. The other branches do need QA done on them though, before they can move on. Chris -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
I have pushed up 7 branches on git.koha-community.org
new/awaiting_qa/biblibre_memb_circ_upd new/awaiting_qa/biblibre_admin new/awaiting_qa/biblibre_various new/awaiting_qa/biblibre_serials new/awaiting_qa/biblibre_cataloguing new/awaiting_qa/biblibre_opac new/awaiting_qa/biblibre_acquisitions
I've just tested OpacHiddenItems. Here are my comments: - Some documentation should be welcome for the documentation manager and for testers. Some valuable info is found in a text file opac/OpacHiddenItems.txt. - A function (enabled_opac_search_views) references 2 syspref (OPACviewMARC and OPACviewISBD) which are not defined in .pref file nor in DB. Some doc needed also. - Two new syspref are referenced in get_template_and_user but are not defined anywhere else: IntranetXSLTDetailsDisplay, IntranetXSLTResultsDisplay. Not OPAC related. - TemplateEncoding syspref is revived. Isn't it supposed to be dead. - OpacHiddenItems new syspref is defined in DB (kohastructure.sql & updatabase.pl). But it isn't defined in opac.pref. - I can't display anything on result page. I have a result count and pages navigation bar but without records themselves. - If I reference directly opac-detail.pl page with a biblionumber, I get error message when XSLT is enabled. Without XSLT it works. I can see a new functionality to search subjects but the display is strange. I suppose some CSS is missing to pipup search when clicking on subjects. So, from a functional point of view, I can understand that this branch add: - A new way to add/show MARC and ISBD view - A new way to hide items on criteria defined in a YAML encoded syspref - A subject enhanced search functionality on OPAC detail page (not in XSLT mode).
- Some documentation should be welcome for the documentation manager and for testers. Some valuable info is found in a text file opac/OpacHiddenItems.txt.
I'm curious why this directory and file have been created? Do we not have a standard method for providing help for individual system preferences?
- I can't display anything on result page. I have a result count and pages navigation bar but without records themselves.
I get the same result.
- If I reference directly opac-detail.pl page with a biblionumber, I get error message when XSLT is enabled. Without XSLT it works.
I get the same error whether XSLT is on or off: Global symbol "$subscriptionsnumber" requires explicit package name at /home/oleonard/kohaclone/opac/opac-detail.pl line 700. Global symbol "$subscriptionsnumber" requires explicit package name at /home/oleonard/kohaclone/opac/opac-detail.pl line 706. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org
We're talking about this branch: new/awaiting_qa/biblibre_opac
- If I reference directly opac-detail.pl page with a biblionumber, I get error message when XSLT is enabled. Without XSLT it works.
I get the same error whether XSLT is on or off:
Global symbol "$subscriptionsnumber" requires explicit package name at /home/oleonard/kohaclone/opac/opac-detail.pl line 700. Global symbol "$subscriptionsnumber" requires explicit package name at /home/oleonard/kohaclone/opac/opac-detail.pl line 706.
Yes, you're correct. I remember now that I add to do a quick fix to make it work. I send a patch for that. We need some feedback from this branch submitters if we want to do collective QA. -- Frédéric
Le 20/11/2010 08:25, Frederic Demians a écrit :
We're talking about this branch:
new/awaiting_qa/biblibre_opac
- If I reference directly opac-detail.pl page with a biblionumber, I get error message when XSLT is enabled. Without XSLT it works.
I get the same error whether XSLT is on or off:
Global symbol "$subscriptionsnumber" requires explicit package name at /home/oleonard/kohaclone/opac/opac-detail.pl line 700. Global symbol "$subscriptionsnumber" requires explicit package name at /home/oleonard/kohaclone/opac/opac-detail.pl line 706.
Yes, you're correct. I remember now that I add to do a quick fix to make it work. I send a patch for that.
We need some feedback from this branch submitters if we want to do collective QA. -- Frédéric Well, patches welcome, either you want to send on list on directly to me. I wanted to work on that but had no time. So If you want to send me patches or suggestions, please do. -- Henri-Damien LAURENT
Dear all, We have been trying to generate reports from KOHA. However, after building our report, we download it in excel and only get 10000 records (rows). We expect to get at least 40,000 records. Where could we be going wrong or rather what are we doing or not doing? Is this a koha or excel- related challenge? _______________________________ Peter Mwangi Gichiri Systems Librarian, NEGST/ Africa International University P.O.Box, 24686 - 00502 Karen, Nairobi Tel: 254 (02) 882104/5; Cell: 0721 - 621692 Email: peter.mwangi@negst.edu Website: www.negst.edu
Hi Peter, I believe there is a built-in default limit of 10000 for sql reports "to protect users from downloading too much or filling the server with an error"... I also understand that if you add a LIMIT statement to the sql then that takes precedence. So for example you could add " LIMIT 99999" to your sql and see if that works. It might be nice to have something either on-screen or in help about this. Good luck. Ian PS if you are subscribed to the normal Koha list that might be a better list for this question rather than development... On 25/11/2010 09:09, Peter Mwangi wrote:
Dear all, We have been trying to generate reports from KOHA. However, after building our report, we download it in excel and only get 10000 records (rows). We expect to get at least 40,000 records. Where could we be going wrong or rather what are we doing or not doing? Is this a koha or excel- related challenge?
_______________________________ Peter Mwangi Gichiri Systems Librarian, NEGST/ Africa International University P.O.Box, 24686 - 00502 Karen, Nairobi Tel: 254 (02) 882104/5; Cell: 0721 - 621692 Email: peter.mwangi@negst.edu Website: www.negst.edu _______________________________________________ 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/
-- Ian Bays Director of Projects PTFS Europe.com mobile: +44 (0) 7774995297 phone: +44 (0) 800 756 6803 skype: ian.bays email: ian.bays@ptfs-europe.com
participants (7)
-
Chris Cormack -
Frederic Demians -
Frédéric Demians
-
Ian Bays -
LAURENT Henri-Damien -
Owen Leonard -
Peter Mwangi