> 18:01:28-14/05 zebraidx(22552) [warn] Index 'tpubdate' not found in
> attset(s)
> 18:01:28-14/05 zebraidx(22552) [warn] Index 'Modified-code' not found
> in attset(s)
> 18:01:28-14/05 zebraidx(22552) [warn] Index 'char-encoding' not found
> in attset(s)
> 18:01:28-14/05 zebraidx(22552) [warn] I
Hi,
I've noticed differences between English and French syspref:
/installer/data/mysql/en/mandatory/sysprefs.sql
/installer/data/mysql/fr-FR/1-Obligatoire/unimarc_standard_systemprefs.sql
I've done a script which identified those differences.
Variables available in 'en' but unavailable
> - opac-results = 16kB (3 results in my tests). OK, not too much
> - css = opac.css is 28kB, others (ui.css & print.css) are 2.xkB. Could
> opac.css be "smallified" ?
> - js = 300KB !!! with utilities.js being 100KB !!! that's huge !!!
Thank you for raising this question. JavaScript and CSS is c
> No, the difference between 16Kb and 100Kb is not peanuts. 16Kb will
> display on nearly all mobile phones. 100Kb will not.
You're shifting to another subject. Improving Koha usability with mobile
devices is interesting by itself but is not the question. Paul question
is about relation betwee
> (continuing investigations)
> I tried to investigate -d:DProf, but could not run a search with DProf.
opac-main.pl page profiling with Dprof give this result:
Total Elapsed Time = 1.573963 Seconds
User+System Time = 1.503963 Seconds
Exclusive Times
%Time ExclSec CumulS #Calls sec/call Csec/c
Profiling an OPAC search with dprofpp -I gives this result:
Total Elapsed Time = 4.046462 Seconds
User+System Time = 3.676462 Seconds
Inclusive Times
%Time ExclSec CumulS #Calls sec/call Csec/c Name
38.6 0.008 1.420 1 0.0081 1.4195 C4::Search::searchResults
35.6 0.030 1.310
> mod_perl = x3 improvement
> memcache = x2 improvement
>
> so :
>
> both = x6 improvement
>
> lol. I agree that's only theory.
>
> A quick question again : did someone experiment mod_perl recently ? it
> used to work pretty well something like 1 year ago.
It works perfectly for OPAC. I didn't te
> These %s add up to considerably more than 100% don't they? What does
> that mean?
This is a dprofpp -I result. It means that it displays subroutine times
inclusive of child subroutine times. I suppose for example that
C4::Context::new call C4::Context::read_config_file that call
XML::Simple:
>> Why isn't it as simple as caching the result, as in
>
> I think it probably really is that simple, at least for now - could
> you test your approach and submit?
Yes, but context objects will be created 23 times, one per module using
C4::Context. I just send a patch which uses class variable f
> Have you tested to see if the zebra engine does handle the stopwords
> correctly? I didn't know that it did that.
No I haven't tested and I don't know also if Zebra supports stop words.
I can't find any information on the subject. Stop words have less and
less interest with zebra mechanisms
>> Yes, but context objects will be created 23 times, one per module using
>> C4::Context. I just send a patch which uses class variable for default
>> context.
> Good eye, Frédéric.
A tribute must be paid to MJ Ray who expressed his astonishment about
C4::Context::read_config_file being called
>>> Have you tested to see if the zebra engine does handle the stopwords
>>> correctly? I didn't know that it did that.
>> No I haven't tested and I don't know also if Zebra supports stop words.
>
> I found the first part of your sentence troubling, but perhaps I worry
> too much. :)
I haven't te
> We have noticed that even we have translated some words (into Greek)
> these do not appear on opac/staff. We keep on seeing them in
> English. Does anybody know why this happen and how we can fix it?
How have you done this translation? After translating Greek .po files,
did you update you
Hello koha-translate list,
Currently, Koha translation into Arabic raises issues concerning RTL
(right-to-left) support. See attached screenshots:
* koha-rtl.png -- That's how a page is displayed now in Arabic.
* koha-rtl-modified.png -- That's how this page should look like.
In a LTR l
Hello again koha-translate list,
Here is what I've find out about RTL support. It seems that CSS opac.css
has to be tweaked to handle correctly RTL languages.
For this issue:
In a LTR language (English/French), in a form you have on a single line:
* label
* input box
* button.
I
> Comments welcomed
It's a good rule because it helps RM to validate, test and apply patches.
But not only. There is another advantage: it helps identifying already
submitted bugs and comments/solution. It avoid investigating bugs
already solved. I have an example...
Yesterday, someone on ko
Thanks Andrew. I've tried out your patch. As a proof of concept, it
works for me! I was pleasantly surprised by how easy it has been
to test your patch thanks to git...
The question is: how your logging mechanism will play with current Koha
logging systems: warning in code and C4/Log.pm? I'd sugge
> 4. Discuss options for filling the position of QA manager for 3.2.
I volunteer for this role.
I am Frédéric Demians. I've been providing solutions and services to
French specialized libraries for years with my own company: Tamil.
I'm selling now SaaS based on Koha. I have a developer backgroun
> Would you be actively reviewing many or most patches that are
> submitted, and
> perhaps maintaining a QA Git tree? Or do you see your role more as
> organizing testing or advocating good software development practices?
Let's set the records straight. I wouldn't be a QA manager in the strict
> 1: the item-level_itypes system preference be removed.
> 2: biblioitems.itemtype be renamed to biblioitems.default_itemtype
> 3: items.itype be renamed to items.itemtype
> 4: all circulation parameters will be determined by items.itemtype.
> 5: AddItem and ModItem will automatically fill items
> I need to create a perl script to update wrong information in the item
> table.
> The holdingbranch data is wrong.
>
> How can I simultaneously change the data in the koha items table and
> the item data in the marc structure?
You have to use Koha API to modify items. Take a look at C4::Ite
> (*) the scripts and perl modules themselves are precompiled and
> cached. When a script or module is modified the web server has to be
> restarted.
Not necessarily:
http://perl.apache.org/docs/2.0/api/Apache2/Reload.html
--
Frédéric
___
Koha-devel
> Which UNIMARC subfield to link to, and
In UNIMARC, sub-title field: 200$e.
--
Frédéric
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
>> And if we know where the XML parser is called (directly or indirectly),
>> we can set in the koha file(s) the global variable
$XML::SAX::ParserPackage = "XML::LibXML::SAX";
>> in order to force the good XML parser without requiring to modify a
>> global configuration file
> Primarily, Koha
> I prepared two commits for koha to force the use of the LibXML parser.
> Can you test them and apply them if they are ok ? (I only greped for
> any occurrences of XML::Simple and MARC::File::XML and add the correct
> line). Both commits are available at the top of my wip-for-upstream
> branc
> I am not sure the proper way to do this, and I hope someone can assist
> me formalizing and sending this patch to the patches list, or to a
> maintainer directly --
Since Koha relies already on YUI, why not switching from TinyMCE to YUI
text editor?
http://developer.yahoo.com/yui/editor/
-
> I'll add a feature / coherence request if I may : the graphical editor
> is only used for the online help, as noted earlier, but it should also
> be used for news at koha-news.pl. Could it be added here
I can't agree more. I did it in the past:
http://tinyurl.com/9t6epd
I don't remember, if
> As far as the UNIMARC format is concerned, BibLibre did change the
> "default" framework when the standard changed: it's the
> frameworkthat's available as an sql file with a release.
I can confirm that thanks to BibLibre, and specifically Nicolas for the
last version, Koha UNIMARC users enj
> As another example, you have a fully parsed MARC::Record object
> representation for a given biblio. You can store that object away,
> and the next time you need to reference it (when a user clicks for the
> details page, or the MARC page, etc.) you can retrieve and use it
> without having
> I would like to install Koha 3.0 wiht postgresql but the script on the
> installation is not good Somebody install this and help me?
I suspect you won't find anybody having installed Koha with PostgreSQL.
Koha 3 PostgreSQL support is at a very beta stage. A lot of work still
has to be done.
> I want to use XSLT display for Unimar also.
> I read the code of Opac and I found two points
> to fix:
>
> opac.detail.pl
> line 63
> my $newxmlrecord =
> XSLTParse4Display($biblionumber,C4::Context->config('opachtdocs')."/prog/en/xslt/MARC21slim2OPACDetail.xsl");
>
> opac-showmarc.pl
> line 68
Koha Z39.50 client process isn't easy to understand from a end-user
perspective.
Current process:
◊ In cataloguing, a search to multiple z3950 target is sent.
◊ Result is displayed. 20 first results are displayed for each target.
◊ Each record is stored in import_* tables for further usage via
'r
> I also intend to start as release maintainer for 3.2, although as time
> passes, it may be necessary to find another RMaint. Regardless, I will
> continue to be involved in Koha.
Very sad news for Koha! You've accomplished a lot. Thanks.
--
Frédéric DEMIANS
http://www.tamil.fr/u/fdemians.ht
> I have not yet been able to figure out how to pass the syspref into
> the XSLT files, but I have been able to hardcode those files to force
> opening a new window instead of the default same window.
I have a patch to do that. I will package it and send it to patches
list. You will have sysp
> "If this is switched on, patrons cardnumbers will be shown instead of
> their name on the holds and catalogue screens"
Active l'affichage du numéro des adhérents à la place de leur nom dans
les pages de réservation et du catalogue.
But is it only for holds or also for check-out items?
__
Why are you using directly DocBook format which is a nightmare to deal
with, editing, transforming? when you could use as lightweight markup
language like asciidoc?
http://www.methods.co.nz/asciidoc/
asciidoc files can be translated to HTML and DocBook (and then PDF).
asciidoc source files c
> Because that was what was asked of me by those who work in other
> languages :) No clue why I'm using it - I just do whatever I have to
> to make things accessible to all.
Speaking accessibility... This documentation:
http://progit.org/book/
is written with asciidoc. An html version is
Hi,
Is there a way in Koha to know if a borrower is allowed to check out a
book without trying to do it effectively? I would like to be able, given
a borrower number, to know immediately if he's blocked. This is related
to Koha SIP2 Server. In the protocol, the Self-Check can ask to Koha
such
> The problem is that none can say if "this borrower can issue", one can
> just say "this borrower can issue an item of type X, from branch B",
> as issuing rules are based on patron categ/itemtype/branch (except if
> patron is debarred, but that's not your question ;-) )
That's the answer I w
> misc/cronjobs/cloud-kw.pl
> misc/cronjobs/cloud-sample.conf
cloud-kw.pl generates HTML keywords clouds from Koha Zebra indexes.
cloud-sample.conf is a configuration file sample driving this script
operations.
For help, enter ./cloud-kw.pl without argument. perldoc command must be
installed.
> Where then would this new page with the clouds on it be visible? I see
> that it generates files in the template folder - does this mean it's
> up to the librarians to add links?
As you may have noted, this script does a similar job as
build_browser_and_cloud.pl. The difference is that its
> Has anyone configured and ran this utility in the misc folder?
>
> Looks like a cool tool but I don't know enough about perl to know what needs
> to be modified. I'll take it to my resident perl expert and have him
> interpret for me and maybe play with it. Just checking before I spend time
>
> Anyone have a suggestion on how to get at least a count of these 856's
> in the
> MARC record in my database?
SELECT COUNT(url) FROM biblioitems;
will give you the number of biblio records having at least one 856. A
biblio record with several 856 tags will be count as 1 url.
If you want som
Those kind of things can be tricky and messy. Something like a
dependency graph would be required, which is all but easy to implement.
It has something to do with how patches are applied with git: order
matters. 'git log --graph --pretty-oneline' displays s a representation
of this order. Git m
> As release maintainer for 3.0 I **had to*** create and arrange db
> updates in a different order than master branch. Knowing wich db version
> you were on 3.00.01 and not 3.01 was really important, even though its
> management could have been improved. (Things that would add some tables
> and ma
And since you must backup daily your Koha DB, you should truncate
sessions table just before mysqldump-ing in order to backup as few
sessions data as possible.
--
Frédéric
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mail
> I'm going to see if any of Aeon's developers are fluent in SIP; in
> case I have to set this up myself, can you recommend a good source of
> documentation for using SIP2 with Koha?
Have you read 3M SIP2 protocol reference document? It's here:
http://solutions.3m.com/wps/portal/3M/en_US/
> Frédéric - can you confirm willingness to update the license of
> check-url.pl to GPL 2+? Ditto for cloud-kw.pl?
I confirm.
--
Frédéric
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
Hi,
> As announced in our presentation, we have implemented a new management
> of the fines in days.
> This development is in the repository http://github.com/xercode/kohaWe
> would like to hear your vision
Thanks. It's a very nice idea.
Could you give some perspective? Could you give a functi
Thanks a lot to PTFS for contributing back to Koha its customer's code.
> I'm hoping that PTFS can help creating these branches, but anyone can
> do so at let me know where to pull from. They need to have the changes
> isolated if possible and be based on new_features. (Which at the
> moment tr
50 matches
Mail list logo
