Re: [Koha-devel] Web crawlers hammered our Koha multi server
The real problem lies in the nature of bots of any species that find a form to fill and and hit your website with all possible values being selected, one by one. This is the behaviour I saw in our Apache logs. EVERY possibility for the advanced search was being requested and presumably indexed. heya Rick, i'm curious... what was the bot's ID-string in your access.log? (i want to check my logs for those bots too) Mason. ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Stack Smashing
On 2010/01/6, at 7:07 AM, Chadwick, John, DCA wrote: Here is a good challenge. I have seen this question posed a few times, but have not seen an answer. We are running 3.01.00.061 on Ubuntu 8.04.3. Using the icuchain method for indexing records. When we got to just over 10,000 records we started to get the following error message when Zebra gets to the point of inserting records. Any ideas on this one? We are running Koha 3.01.00.061 with Zebra. Rebuilding Zebra is failing and we are unable to search indexes. *** stack smashing detected ***: zebraidx terminated=== Backtrace: =/lib/tls/i686/cmov/libc.so.6(__fortify_fail +0x48)[0xb6d7cda8]/lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x0) [0xb6d7cd60]/usr/lib/libidzebra-2.0.so.0[0xb7fc10c4]/usr/lib/ libidzebra-2.0.so.0[0xb7f69a0a][0x13c] Any ideas or suggestions would be appreciated on this one. No one has answered on the Zebra list. hi John, what version of zebra are you running?, the latest? can you update your zebra to a newer version? Mason. ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] A couple of Debian install questions
On 2009/12/7, at 1:47 AM, Owen Leonard wrote: which installation instructions ? Sorry-- The Debian Lenny INSTALL file. -- Owen bah, i saw 'OSX' and thought you were looking at an OSX-install.txt doc (which doesn't yet exist :O) ) ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] A couple of Debian install questions
On 2009/12/6, at 8:44 AM, Owen Leonard wrote: I just tried my first Koha install on Debian: OSX + VirtualBox + Debian + Koha dev install. I ran into a couple of problems I wanted to ask about: 1. Install didn't proceed correctly until I manually created the koha-dev folder alongside the location of my git checkout. 2. I got several warnings about prerequisites missing after running Makefile.PL. Does that mean that the installation instructions are missing a step? which installation instructions ? ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] [Koha] Release 3.0.4 Bug fix
On 2009/10/23, at 7:32 AM, Chris Cormack wrote: 2009/10/23 LAURENT Henri-Damien henridamien.laur...@biblibre.com: Here comes a link to an update of the Koha 3.0.4 http://koha-fr.org/content/diffusion-koha-version-304 You can download from there since I cannot upload to download.koha.org at the moment. Since this website is meant for French people, text is in English. But it is the translation of yesterday's release notes. I think it is entirely unacceptable that both the Release Maintainer and the Release Manager now no longer have access to put releases on download.koha.org This access needs to be reinstated by Liblime or if they are unwilling to do so, download.koha.org needs to point to a server were the elected Release manager and maintainer can put up releases. We have a situation now, where the file on download.koha.org has a bug, we have a fixed version, but we can't replace it. This is farcical and cannot be accepted. umm, so this *deliberate* ?!?, surely not? ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] OPAC Log-in
On 2009/10/12, at 1:18 PM, Bob Birchall @ Calyx wrote:
Hi all,
Is it possible to configure the opac so that a user can perform a
search
only if logged in? A special library wishes to expose its
catalogue to
internal eyes only. So the required sequence would be to enter the
url, be
directed to a log-in page (the way the staff client works) and then
when
logged in be directed to opac-user.pl (as happens now when you log
in from
opac-main.pl)
How can that be achieved?
Thanks,
Bob Birchall
Calyx
1) jquery in the template, to hide the search-bar,
FYI: this wont stop people hacking a url to access your koha, of
course.
or...
2) edit the perl code and change the 'authnotrequired' value to '0',
per page
---
my ( $template, $borrowernumber, $cookie ) = get_template_and_user(
{
template_name = opac-main.tmpl,
type= opac,
query = $input,
authnotrequired = 1, CHANGE ME
flagsrequired = { borrow = 1 },
}
);
---
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Diacriticals, Unicode, and PDF's
On 2009/09/29, at 12:23 PM, Chris Nighswonger wrote: Does someone have a few bibs they can shoot my way which contain lots of diacriticals and are unicode encoding? Maybe something in French or Spanish for starters. I'm working toward fixing the unicode problems with labels as a back-burner project. Kind Regards, Chris great stuff Chris, i really appreciate someone tidying up my kludgey code :) so - i'm curious... is there a newer/better way to get around the less-than-perfect character-conversion issues with UTF to PDF, that were discussed on the lists in the last year or so (approx) Mason ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Transition and continuity
On 2009/07/23, at 6:41 AM, Galen Charlton wrote: Hi folks, As some of you may have heard or been speculating about, I will be joining Equinox at the beginning of August. Although that of course means that I will start hacking on Evergreen, I am committed to seeing 3.2 to completion and release and will continue on as release manager. 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. I look forward to continuing to work with you all. heya Galen i too want to thank you for all the extra time you have spent working on Koha, and thanks for all those times you helped me out when i was stuck! ive really enjoyed your coding style too, and have learnt a lot of good habits from studying your code, so elegant! :) I think that one of the exciting things that may happen with you working for Equinox is the possibility for more 'cross-pollination' between the Koha and Evergreen projects. yay for the future of open-source ILS's, and remember folks... we are all working towards the same goal Mason. ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] [koha-devel]: 'syndetic' usage in koha
On 2009/07/13, at 11:36 PM, Galen Charlton wrote: Hi, On Mon, Jul 13, 2009 at 6:31 AM, Mason Jamesmason.loves.su...@gmail.com wrote: Does anyone know if the 'syndetic' book-jackets/cover-images are free to use for general usage or is a payment required to use the service? is the service free-to-use , but throttled - for non-paying usage? Syndetic's book covers and other content services are entirely fee-based. Bowker provides no gratis option that I'm aware of. heya Galen, thanks for the reply, as i said - it seems that the syndetic book-cover feature seems to be working out-of-the-box which is a nice win for the koha-project in general cheers, Mason. ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
[Koha-devel] [koha-devel]: 'syndetic' usage in koha
Bonjour peoples, Does anyone know if the 'syndetic' book-jackets/cover-images are free to use for general usage or is a payment required to use the service? is the service free-to-use , but throttled - for non-paying usage? I have had a look around, but i cant quite find any decent info regarding the TOC any clues? cheers, Mason ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] ITEM Count
On 2009/07/7, at 1:16 AM, M L N wrote: Hi Nicole, Thanks for a reply however it didn't really help. I've attached a screen dump to show what i am talking about. Any help will be much appreciated. please don't send big attachments to mailing-lists especially word documents with embedded images use something like http://www.flickr.com/ , and paste the *url* instead ;) ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] [Koha] Saving MARC records very slow
On 2009/06/30, at 11:52 AM, Rick Welykochy wrote: Cab Vinton wrote: This was covered on the list a while back -- in Firefox it was taking 40-50 s on our staff clients to save records. We've switched to Google Chrome the time is now much more manageable. I don't believe a diagnosis or fix were ever found for the Firefox issue. As pointed out, this is because of Javascript. Question: can Koha operate properly with JS disabled? If not, why not? Observation: JS is quite slow compared the server itself. Perhaps the *HUGE* task of validating a MARC save could be (optionally) left to the server to validate. this is a good suggestion, but might require a pretty big rewrite of the marc-editor code (not for the faint-hearted) another easier speed win could be to find the slow/often-executed JS code thru profiling, and rewrite it with some optimised jquery is jquery code faster? ermmm i'm not sure actually ;) just a thought... ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Barcode Not Found
On 2009/06/24, at 6:21 AM, Roche III, Edward wrote: Is this a script that needs to be run? no, its a subroutine in ./C4/Items.pm, see... http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=blob;f=C4/ Items.pm;h=6c58365ef0d192d4ee7126823397f3f7fc9c9780;hb=HEAD#l453 How would you use the C4:Items:ModItems() API? take a look here for an example of it being used in a script http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=blob;f=catalogue/ updateitem.pl;h=7b0b673727fe1e55299332a2ff13a1130ebe2f41;hb=HEAD ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Barcode Not Found
On 2009/06/23, at 8:54 AM, Roche III, Edward wrote: OK...now I opened a item record (through Webmin)like I was going to edit it didn't change anything then saved the record and now I can enter that barcode and it will allow me to check it out with no error. These barcodes were import into a temp table then I ran a UPDATE sql statement to update the barcodes in the item table from the temp table. Can anyone think of a reason why the system will not find the barcode unless I open and save the record first? well, if you *manually* use sql to UPDATE your barcode values , zebra doesnt know about that ;) so rebuild your zebra-index after, and try searching again FYI: the correct way to do this is to use the C4:Items:ModItems() subroutine - then zebra is updated correctly too ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] RFC : Item level 'hold-fee' and 'not-for-hold' feature?
What do people think about allowing a item-type level 'not-for-hold' checkbox, and a item-type level hold-fee (that overrides the patron-type level hold-fee) The development version of Koha allows hold policies to be set up by branch and itemtype (and soon, patron type) that can allow holds, allow them only to patrons from the item's home branch, or disallow them. So #2 will be possible in 3.2. -- Jesse Weaver Hi Jesse, I just spotted your hold-policy stuff in 3.2 after i sent the email :) It looks really good too Mason ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] [Koha] To Liblime professional
On 2009/05/20, at 6:48 PM, john smith wrote: Hi Mason When i run zebrasrv-2.0 -f /etc/koha/koha-conf.xml , i will get error message as below zebrasrv-2.0: Option -f unsupported since YAZ is compiled without Libxml2 support what happen i dont know please help me to solve thois problem, i had installed : Yaz 3.0.45 IDzebra 2.0.18 thnks what linux? debian? ubuntu? ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
[Koha-devel] zebra and yaz error 'Option -f unsupported'
On 2009/05/20, at 7:15 PM, john smith wrote: Ubuntu 9.04 CC: koha-devel@lists.koha.org From: mason.loves.su...@gmail.com Subject: Re: [Koha] To Liblime professional Date: Wed, 20 May 2009 19:06:50 +1200 To: smith...@live.com On 2009/05/20, at 6:48 PM, john smith wrote: Hi Mason When i run zebrasrv-2.0 -f /etc/koha/koha-conf.xml , i will get error message as below zebrasrv-2.0: Option -f unsupported since YAZ is compiled without Libxml2 support what happen i dont know please help me to solve thois problem, i had installed : Yaz 3.0.45 IDzebra 2.0.18 thnks what linux? debian? ubuntu? check out the rest of the Windows Live™. More than mail–Windows Live™ goes way beyond your inbox. More than messages great! so what do these say on your system?? $ dpkg -l |grep yaz $ dpkg -l |grep zebra heres what mine says. $ dpkg -l |grep zeb ii idzebra-2.0 2.0.34-1indexdatavirtual package with most components ii idzebra-2.0-common 2.0.32-1 IDZebra common files ii idzebra-2.0-doc 2.0.32-1 IDZebra documentation ii idzebra-2.0-utils 2.0.34-1indexdatautility programs including indexer and serve ii libidzebra-2.0 2.0.34-1indexdataIDZebra libraries ii libidzebra-2.0-dev 2.0.34-1indexdatadevelopment files ii libidzebra-2.0-mod-alvis 2.0.34-1indexdatarecord filter module for XSLT indexing (obso ii libidzebra-2.0-mod-dom 2.0.34-1indexdatarecord filter module for XSLT indexing (repl ii libidzebra-2.0-mod-grs-marc 2.0.34-1indexdatarecord filter module for indexing MARC/ISO27 ii libidzebra-2.0-mod-grs-regx 2.0.34-1indexdatarecord filter module for indexing using Tcl ii libidzebra-2.0-mod-grs-xml 2.0.34-1indexdatarecord filter module for indexing XML using ii libidzebra-2.0-mod-text 2.0.34-1indexdatarecord filter module for indexing plain text ii libidzebra-2.0-modules 2.0.34-1indexdatarecord filter modules $ dpkg -l |grep yaz ii libyaz 2.1.54-1 The YAZ Z39.50 toolkit (runtime files) ii libyaz3 3.0.42-1indexdatalibraries for the Z39.50 toolkit ii libyaz3-dev 3.0.42-1indexdatadevelopment files for the Z39.50 toolkit ii yaz 3.0.42-1indexdatautilities for the Z39.50 toolkit ii yaz-doc 3.0.42-1indexdatadocumentation for the Z39.50 toolkit ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] GSAFD authority records and koha
On 2009/04/23, at 1:41 AM, Galen Charlton wrote: Hi Mason, On Wed, Apr 22, 2009 at 8:12 AM, Mason James mason.loves.su...@gmail.com wrote: I have imported them just fine into a koha3 using the DOM zebra- filter But, i cant quite get a match on them using the link_bibs_to_authorities.pl script What do the bib headings look like? In order to match, the heading in the bib records must be in the 651 tag, have the second indicator set to '7', and contain a subfield $2 gsafd - otherwise, it will not match the corresponding authority. Regards, Galen heya Galen, thanks for the reply, i was hoping you would have a suggestion :) my bibs seem to have their headings stuffed in the 655 tag, not 651 and a *1st* indicator set to 7, not the 2nd - eep :/ but thanks for the info, ill manually correct a bib or 2, and see how i get on thanks again, Mason fyi: example bib below... - MARC biblio : 10474 ( The shining / ) 245 14 - TITLE STATEMENT a Title The shining / c Statement of responsibility, etc Stephen King. snip... 650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM a Topical term or geographic name as entry element Hotelkeepers Auth v Form subdivision Fiction. 9 9 (RLIN) 111002 655 7# - INDEX TERM--GENRE/FORM a Genre/form data or focus term Occult fiction. 2 Source of term gsafd. a Genre/form data or focus term Horror tales. 2 Source of term gsafd. ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] [Koha] Zebra Setup
On 2009/04/4, at 12:47 AM, Roche III, Edward wrote: Mason The answer you gave for [Koha] Make Fails on koha-3.00.01-stable fixed my issue as well. great ;) Now the catalog search will not work, returns no records. and please, more info - if you really want some help Ed, do you have zebra running? do you have records in your DB? have you checked your zebra logs when starting? , searching? what do your logs say when you search??? please paste this basic infomation into your emails! only then will people be able to help you with your problems Mason. ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] [Koha] Zebra Setup
On 2009/04/3, at 12:36 AM, Mason James wrote: 23:06:14-01/04 zebraidx(5173) [log] zebra_start /etc/koha/zebradb/ zebra-biblios.cfg 1.3.50 fyi: 1.3.50 is an old version of zebra, get version 2.x ;) ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Possuble Bug when running rebuild_nozebra.pl
On 2009/03/24, at 12:40 AM, Roche III, Edward wrote: Good Morning All Whenever I run this script I have to add the /C4 to the koha- httpd.conf file at the end of SetEnv PERL5LIB /usr/share/koha/lib line. when you run scripts from a shell, simply set your environment- variables using 'export'. like this... $ export KOHA_CONF=/home/mason/koha/etc/koha-conf.xml $ export PERL5LIB=/home/mason/koha3.git fyi: no /C4 $ /path/to/my/rebuild_zebra.pl -r -b -v As Joe mentioned, changing anything in your apache config has *no* effect on the behavior of your commandline scripts, the two are completely unrelated. ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] [Koha] {Possible SPAM} RE: Barcode Don't Found
On 2009/03/29, at 1:41 AM, Roche III, Edward wrote: I missed replying to the groups. I am being dumb but where does this patch go? I found what I need to do for the sys.pref but not sure where to put the patch. you apply patches in git, using... $ git-apply ./my.patch ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] [Koha] {Possible SPAM} RE: Barcode Don't Found
On 2009/03/30, at 3:59 PM, Roche III, Edward wrote: When I apply the pacth with the following command: git-apply ./home/sysadmin/Desktop/0001-Add-less-aggressive- whitespace-removal-to-itemBarcod.patch error: C4/Circulation.pm: No such file or directory error: installer/data/mysql/en/mandatory/sysprefs.sql: No such file or directory I don't something is right? Especially the 2 errors at the end. What am I doing wrong? run git-apply from any dir *within* your koha3 repo thats how git-apply works out where to apply the patch ;) ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] a simple update-items.pl tool
On 2009/03/27, at 12:08 PM, Owen Leonard wrote: The functionality required is the ability to collect a batch of barcodes of items that are affected and the ability to change the status of collected barcodes in one action. I looked back at Mason's description and believe that he and WALDO are thinking alike. I think the key is his description similar to circ's current branchtransfers.pl script. That means scanning each item individually with the updates happening in individually, rather than collecting barcodes in a batch for processing en masse. Does that sound right Mason? It may not have a functional difference as far as your requirements go, but I would hope that a Bulk status change feature would offer more than one way of building a batch, just like the inventory script gives you the option of choosing a call number range, barcode range, etc. That's just my idea of it though. hi Folks thanks for the feedback. down the track i can see the potential for the tool to be enhanced with add/mod/saving item-batches to run status-updates on, or uploading a text-file of barcodes, or selecting items using various fields and min/max ranges etc... but yes, at the moment ill keep the 1st draft nice and simple, and focus on it accepting scanned barcodes from Circ (like the branchtransfer.pl tool) ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
[Koha-devel] 'OpacSuppression' syspref?
hi Folks, does anyone know what the 'OpacSuppression' syspref does? Turn ON the OPAC Suppression feature, requires further setup, ask your system administrator for details heres the commit by Joshua http://git.koha.org/cgi-bin/gitweb.cgi? p=Koha;a=commit;h=dd47f7bf7cd3c725ac2028a48ce1fab451a131fd ive grepped thru the latest stable repo , and cant see it refered to anywhere other that the sql structures stable$ grep -ril 'OpacSuppression' ./* ./admin/systempreferences.pl ./installer/data/mysql/updatedatabase.pl ./installer/data/mysql/uk-UA/mandatory/system_preferences_optimal.sql ./installer/data/mysql/ru-RU/mandatory/system_preferences_optimal.sql ./installer/data/mysql/fr-FR/1-Obligatoire/ unimarc_standard_systemprefs.sql ./installer/data/mysql/en/mandatory/sysprefs.sql ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
[Koha-devel] a simple update-items.pl tool
Hi Folks, i have an idea around a simple update-items.pl tool. my idea is a tool similar to circ's current branchtransfers.pl script (that takes scanned barcodes as input), and it updates the scanned item's various values what values ??? perhaps some/all of these... (any others??) Item Information 1. Home Library: 1. Holding Library: 2. Item type: 3. Collection: Statuses ( Lost Damaged ) 1. Current Location: 3. Lost Status: 4. Damaged Status: 5. Withdrawn: do other libraries use a different method that i'm unaware of? is there another update-items.pl type tool i have missed? Cheers, Mason ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Need to Modify Marc Import Tool
Folks, One of our customers wants the ability to import Follett marc records without having to use Marc Edit (to change fields 852 to 952). We want to make this change generic such that it will work for any import file that has holdings in fields other than 952. This is what we were thinking, will appreciate feedback on this design: 1. Use marc_subfield_structure table to store field structure of the import file. So Follett would have records under its framework code. We could create frameworks for other vendors too. 2. Accept framework code as user input from stage-marc-import.pl. User could choose nothing which means input file already has holdings in 952. Or could choose Follett or some other vendor. 3. Pass framework code as parameter to BatchStageMarcRecords (C4/ImportBatch.pm) and from there to AddItemsToImportBiblio (C4/ImportBatch.pm). 4. In AddItemsToImportBiblio - Use the input framework code in GetMarcFromKohaField (C4/Biblio.pm) to fetch Follett holdings fields and subfields - Fetch default fields and subfields (952) using null framework code, as is currently done. - For each subfield set values appropriately (in the case of Follett 952s = 852s) before saving item record. 5. Initially the code will help with holdings tags, and later we could extend this to biblio tags as well. Thanks, Savitra Sirohi Nucsoft OSS Labs http://www.osslabs.biz heya Savitra I think this is a *very* useful idea some suggestions: write a feature to do a remap of the vendor's itemlevel info to koha's 952, during the MARC import rather than rewriting koha3 to internally accept non 952 item-info from MARC records i suspect that an attempt to have koha3 use non-952 item-info may be tricky, as this change would affect many areas of koha3 code and would need much testing to ensure it is safe. a safer/easier way to your goal would be to have a feature where the source item-info gets remapped to koha's 952 i think we could use another table to store this remapping info. perhaps a 'import_vendor_items_map' table...? a example record would look something like this.. vendor_code = 'FOLL' vendor_field= '852' vendor_subfield = 'a' vendor_subfield_desc= 'HOME BRANCH' koha_field = '952' koha_subfield = 'a' ... etc what do others think about this idea? this looks to be a nice simple way to build a collection of other ILS vendor's item-level structures. and allow those vendor's MARC-records to be correctly remapped into koha's 952 structure during a bulkimport - from the GUI, without a custom script. Mason. ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] [Zebralist] Extended MARC indexing
On 2009/02/25, at 6:01 PM, savitra sirohi wrote: Folks, I use Zebra with Koha. I am trying to index MARC tags with indicators. But can't seem to get the notation right, keep getting Error 114. I am trying to index Tag 521, indicator 8, sub-field a Here is the what I have in various files: /etc/koha/zebradb/biblios/etc/bib1.att att 9014lex /etc/koha/zebradb/marc_defs/marc21/biblios/record.abs melm 5218_$a_ lex,lex:n /etc/koha/zebradb/ccl.properties # Lexile Number lex 1=9014 r=r Get Error 114 when I try something like this in the search box: lex, st-numeric, ge:450 or lex, lt:450 Will appreciate any help with this. Hi Savitra I know nothing of defining a new zebra-index etc, but... have you started debugging your zebra problem using 'yaz-client' first? that way, you eliminate Koha as being a possible cause of your problem (which i suspect it is too ;) ) Mason ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Importing Data
Roche III, Edward wrote: !...@#$%@%^^ Thanks Ed mime-attachment.jpegmime-attachment.jpeg mime-attachment.jpegmime-attachment.jpeg mime-attachment.jpegmime-attachment.jpeg dont forget to turn off those sig images Ed ;) ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Item Type Images have various sizes
I'll admit that it is nice to have the larger icons for the kids ( to this end one of my librarians has asked me to increase the font size on the opac ). So, in my opinion, it would be best to have variable padding with the icons. I just don't look forward to trying to code that. I think the best way would be to have it statically set. That way we would save the time it takes to parse the image to find it's width. On Wed, 2009-02-11 at 15:14 -0500, Galen Charlton wrote: Hi, On Wed, Feb 11, 2009 at 3:07 PM, Michael Hafen mdha...@tech.washk12.org wrote: I think it would be best to standardize on a size for these images, so that the css can be set once and look right. I would prefer that we accommodate different sizes for the icons rather than settle for just one standard size. I'm not sure how many libraries are using the liblime-kids set, but the icons in it are larger than npl or bridge to support a common design pattern for childrens' OPACs. Regards, i agree with Galen here. Michael, i guess the quick-fix for you, is to change your templates/ css for the bridge-set dimensions i wonder if the padding could be changed to a '%' value, rather than a 'px' value... could we have some magical auto-boundary handling here? li title= style=margin: 0.4em 0pt; padding: 3px 0pt 3px 30px; list-style-image: none; list-style-position: outside; list-style- type: none; background-image: url(/opac-tmpl/prog/itemtypeimg/bridge/ book.gif); background-repeat: no-repeat; background-position: 0pt 50%; Centerville (1)/li ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Item Type Images have various sizes
There would be no more guessing that way, just have to specify the image width when setting up the icon set. yep, this is a pretty doable solution too. i still think there is some CSS fiddle that will make the itemtype- image and the text align happily together Owens' the guy to answer that Q best, round here ;) thoughts Owen? ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Item Type Images have various sizes
This icon set is not uniform in size, unfortunately for us. Otherwise you have an excellent idea there. another idea - perhaps the icon's author's license allow use to resize the icons to a default dimension? ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] A solution to add debugger functionality to most koha *.pl scripts, thoughts please?
On 2009/02/10, at 8:15 PM, John Beppu wrote:
Also, if you want to be able to just type Dumper (instead of
Data::Dumper::Dumper), add Dumper to the list of symbols that
C4::Debug exports.
On Mon, Feb 9, 2009 at 10:30 PM, John Beppu
john.be...@liblime.com wrote:
Give C4::Debug an import() function like this:
sub import {
if ($debug) {
require Smart::Comments;
Smart::Comments-import;
require Data::Dumper;
Data::Dumper-import;
}
C4::Debug-export_to_level(1, @_);
}
That should do the trick.
Woo, this is all new stuff for me.
I'll play about and test this code of yours during my work week, and
read up on the OO-import example you gave.
I aim to send in a patch based on your code in the next few days.
Thanks again John!
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] A solution to add debugger functionality to most koha *.pl scripts, thoughts please?
On 2009/02/10, at 6:01 PM, Mason James wrote: Hi Koha developers, I have been talking with John and Paul at BibLibre for some months now about a correct way to add Data::Dumper, Smart::Comments, insert::your::favorite::debugger stuff to the Koha perl files *once and for all* After a few false starts and some googling - this is the method I have used and tested... use C4::Debug; use if $debug, 'Data::Dumper' ; use if $debug, 'Smart::Comments' ; # use if $debug, 'YAML::Dumper; # etc Is there a better way than this? A question from me too.. Is there a clever way to add this code to *just* Debug.pm which would enable D::D and S::C functionality to all perl files that 'use C4::Debug'? That would be the cleanest way, i think - but i don't know how to do this, or if it's possible in perl :/ anyone? ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Koha 3 Reset Database
On 2009/01/27, at 9:39 AM, David Riggs wrote: On Mon, Jan 26, 2009 at 3:20 PM, Marc Chantreux marc.chantr...@biblibre.com wrote: On Mon, Jan 26, 2009 at 03:04:00PM -0500, David Riggs wrote: I've truncated the tables listed above, but I still have items showing up in search results. Do I need to run some command to purge the Zebra index also? don't carre about that and just use rebuild_zebra.pl with the -r flag. I ran the following commands (Ubuntu 8.04) and still get items showing up in search results. Clicking on the item gives a 404 error. $ sudo su - koha $ export PERL5LIB=/usr/share/koha/lib/ $ export KOHA_CONF=/etc/koha/koha-conf.xml $ perl -I /usr/share/koha/lib /usr/share/koha/bin/migration_tools/rebuild_zebra.pl -b -a -r Thanks, - DR just use 'rebuild_zebra.pl -r' no -a or -b args ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Koha 3 Reset Database
On 2009/01/27, at 10:10 AM, David Riggs wrote: On Mon, Jan 26, 2009 at 4:01 PM, Mason James mason.loves.su...@gmail.com wrote: On 2009/01/27, at 9:39 AM, David Riggs wrote: I ran the following commands (Ubuntu 8.04) and still get items showing up in search results. Clicking on the item gives a 404 error. $ sudo su - koha $ export PERL5LIB=/usr/share/koha/lib/ $ export KOHA_CONF=/etc/koha/koha-conf.xml $ perl -I /usr/share/koha/lib /usr/share/koha/bin/migration_tools/rebuild_zebra.pl -b -a -r just use 'rebuild_zebra.pl -r' no -a or -b args Apparently that's not allowed. $ k...@linimac:~$ perl /usr/share/koha/bin/migration_tools/ rebuild_zebra.pl -r Must specify -b or -a to reindex bibs or authorities Please do '/usr/share/koha/bin/migration_tools/rebuild_zebra.pl --help' to see usage. Thanks, - DR ah, ok try a 'zebraidx -c /yourpath/koha-conf.xml init' then FYI: have a peek at line 488-ish of the rebuild script system(zebraidx -c $zebra_config -g $record_format -d $zebra_db_name init) if $reset_index; ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] authorities question again
On 2009/01/10, at 6:33 AM, Rafael Antonio wrote: Dear all I have seen several KOHA 3.0 demos where the page Authority search results allways show 0 biblio records. I have tested and did some links between biblio and authority but it never never changes. Does we need to run any script? Thanks, run 'rebuild_zebra.pl -a -b -r' after you update your authorities stuff this works well for me fyi: if your indexing daemon is running, then no need for this script. :) Rafael Antonio ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
[Koha-devel] UPDATE: strange recent indexing problems on koha 3.0.x branch, anyone?
On 2009/01/6, at 12:30 AM, Mason James wrote: Hi All The basic issue seems to be that the latest koha 3.0.x branch has some strange indexing (and encoding?) errors (for me at least) Jan 5 23:58:35 fugu Koha Zebraqueue [27085]: Starting Zebraqueue log at Mon Jan 5 23:58:35 2009 Jan 5 23:58:35 fugu Koha Zebraqueue [27085]: Mon Jan 5 23:58:35 2009 POE Session Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: 10 operations waiting to be run Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: Executing zebra operations Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: biblioserver record 10 is malformed: Entity: line 1: parser error : Invalid XML encoding name Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: biblioserver record 9 is malformed: Entity: line 1: parser error : Invalid XML encoding name any ideas, can anyone else replicate this, or confirm otherwise? Just a followup to my own previous post... I re-updated my problem box with the preferred debian packages, rather than the latest random CPAN builds and my 3.0.x HEAD indexing glitch disappeared :) $ sudo dpkg --set-selections ./koha3.git/install_misc/debian.packages cheers to the debian-packages people for saving my ass again ;) Mason. ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Git Repository Questions
On 2009/01/7, at 10:38 AM, Kyle Hall wrote: Hello All, I'm trying to do something that I'm sure is doable with git. I would like to set a 'middle-man' git repository that I can push and pull from to manage our development and production servers for our switchover to koha 3 and future development. (git.koha.org) -- (MyKohaGit) --- (KohaDevServer) \- (KohaProductionServer) So MyKohaGit pulls changes from git.koha.org, I pull and push changes between MyKohaGit and KohaDevServer, and when I'm satisfied that the changes are production ready, I pull the changes from MyKohaGit to KohaProductionServer. I know I could just go straight between KohaDevServer and KohaProductionServer, but I'd like to make MyKohaGit public so others can track my updates that haven't made it into the official git repo yet. Is it really as simple as cloning git.koha.org and making it available via http/ssh? yep ;) install gitweb too, so people can browse your repo with ease I've tried creating an empty repository and pushing to it from a clone of git.koha.org, and it populates it, but I don't seem to have a mechanism to update MyKohaGit directly from git.koha.org. a 'git pull git://git.koha.org/pub/scm/koha.git' should do it ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
[Koha-devel] strange recent indexing problems on koha 3.0.x branch, anyone?
Hi All The basic issue seems to be that the latest koha 3.0.x branch has some strange indexing (and encoding?) errors (for me at least) i have spotted these 'Invalid XML encoding name' errors when running the zebraqueue_daemon.pl / koha-zebraqueue-ctl.sh scripts - after adding a new bib via... * a z39-pull * web-gui batch-import * cmdline bulkmarcimport.pl script i can replicate this on 2 separate debian-etch boxes rolling my repo back from the latest 3.0.x commit, to the 'v3.00.00' tag fixes the issue (which is good, but i havent clicked to what the issue actually is yet ;/ ) the best way to replicate the indexing error for me, was this... fetch, and rewind the repo $ git-fetch $ git-fetch --tags #needed too ?? $ git rebase origin/3.0.x $ git reset --hard v3.00.00 $ ./misc/migration_tools/bulkmarcimport.pl -d -v -fk -n 10 -file / tmp/sample.mrc deleting biblios .. 10 MARC records done in 0.157172918319702 seconds $ ./misc/bin/zebraqueue_daemon.pl -f ~/etc/koha-conf.xml 22:52:52-05/01 zebrasrv(17) [session] Session - OK 17 unix:/home/ mason/koha/ashs/var/run/zebradb/bibliosocket 26837 22:52:52-05/01 zebrasrv(17) [request] Auth idPass kohauser - 22:52:52-05/01 zebrasrv(17) [request] Init OK - ID:81/81 Name:ZOOM-C/ YAZ Version:1.116/2.1.54 22:52:52-05/01 zebrasrv(17) [log] function: 1 22:52:52-05/01 zebrasrv(17) [log] Waitaction: 2 22:52:52-05/01 zebrasrv(17) [log] Received DB Update 22:52:52-05/01 zebrasrv(17) [log] action 22:52:52-05/01 zebrasrv(17) [log] specialUpdate 22:52:52-05/01 zebrasrv(17) [log] database: biblios 22:52:52-05/01 zebrasrv(17) [log] enabling shadow spec=/home/mason/ koha/ashs/var/lib/zebradb/biblios/shadow:4G 22:52:52-05/01 zebrasrv(17) [log] cache_fname = /home/mason/koha/ashs/ var/lib/zebradb/biblios/shadow/cache 22:52:52-05/01 zebrasrv(17) [log] record 0 type XML 22:52:52-05/01 zebrasrv(17) [log] 2095 bytes: ?xml version=1.0 encoding=UTF-8? record xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://www.loc.gov/MARC21/slim http://w ... 22:52:52-05/01 zebrasrv(17) [log] update grs.xml no file 0 22:52:52-05/01 zebrasrv(17) [log] Iterations: isam/dict 8/2 22:52:52-05/01 zebrasrv(17) [log] Dict: inserts/updates/deletions: 1/0/1 22:52:52-05/01 zebrasrv(17) [log] Records: 1 i/u/d 0/1/0 22:52:52-05/01 zebrasrv(17) [request] Extended Service: Update (done) 22:52:52-05/01 zebrasrv(17) [log] function: 1 22:52:52-05/01 zebrasrv(17) [log] Waitaction: 2 22:52:52-05/01 zebrasrv(17) [log] adm request database biblios 22:52:52-05/01 zebrasrv(17) [log] adm-commit ... SUCCESS roll the branch forward... $ git rebase origin/3.0.x $ ~/git/stable/misc/migration_tools/bulkmarcimport.pl -d -v -fk -n 10 -file /tmp/sample.mrc deleting biblios .. 10 MARC records done in 0.157172918319702 seconds $ ./misc/bin/zebraqueue_daemon.pl -f ~/koha/ashs/etc/koha-conf.xml $ sudo tail /var/log/syslog Jan 5 23:58:35 fugu Koha Zebraqueue [27085]: Starting Zebraqueue log at Mon Jan 5 23:58:35 2009 Jan 5 23:58:35 fugu Koha Zebraqueue [27085]: Mon Jan 5 23:58:35 2009 POE Session Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: 10 operations waiting to be run Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: Executing zebra operations Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: biblioserver record 10 is malformed: Entity: line 1: parser error : Invalid XML encoding name Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: biblioserver record 9 is malformed: Entity: line 1: parser error : Invalid XML encoding name Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: biblioserver record 8 is malformed: Entity: line 1: parser error : Invalid XML encoding name Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: biblioserver record 7 is malformed: Entity: line 1: parser error : Invalid XML encoding name Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: biblioserver record 6 is malformed: Entity: line 1: parser error : Invalid XML encoding name Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: biblioserver record 5 is malformed: Entity: line 1: parser error : Invalid XML encoding name Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: biblioserver record 4 is malformed: Entity: line 1: parser error : Invalid XML encoding name Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: biblioserver record 3 is malformed: Entity: line 1: parser error : Invalid XML encoding name Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: biblioserver record 2 is malformed: Entity: line 1: parser error : Invalid XML encoding name Jan 5 23:58:36 fugu Koha Zebraqueue [27085]: biblioserver record 1 is malformed: Entity: line 1: parser error : Invalid XML encoding name FAIL any ideas, can anyone else replicate this, or confirm otherwise? Cheers, Mason ___ Koha-devel mailing list Koha-devel@lists.koha.org
Re: [Koha-devel] Git whitespace whining
white-space causes trouble for git's diffing (and all RCS too?) thats why its on by default, i guess... i turn it off personally, and manage my own white-space tidying others can do what they want... hth On 2008/12/5, at 10:25 AM, Rick Welykochy wrote: I am new to git and its brain twisting operation. Nonetheless the Koha version control system is starting to work with me. The gazillions of warning messages that its spews out about trailing white space produce so much useless noise that I cannot see the real warnings or error message without considerable effort. This warning message provides no useful information. I propose we disable it. I you disagree then please provide an example of a source code file, language processor or other instance where trailing white space actaully can cause trouble. I'm at a loss to find such. cheers rickw -- _ Rick Welykochy || Praxis Services Finster's Law: A closed mouth gathers no feet. ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Label and barcode generator broken
On 2008/11/26, at 2:54 AM, Bernard Shiundu wrote: Just noticed that the label generator seems broken … While it still does produce the barcode numbers with the guide boxes, It doesn’t generate the actual barcodes anymore. A peek at the logs shows first stack underflow:tags stack is empty, referer: http://myserver/ cgi-bin/koha/labels/label-manager.pl?op=add_batchtype=labels label-print-pdf.pl: failed to parse label formatstring: io and barcode at /opt/koha/src/C4/Labels.pm line 862., referer: http:// myserver/cgi-bin/koha/labels/label-manager.pl? op=addbatch_id=1itemnumber=1itemnumber=2itemnumber=3 Hiya Bernard, The good news is - this *does* work for me (on the latest stable build) I suspect you have some config-settings (?missing values perhaps?) that are causing it to barf (which is a legitimate bug) Open up a bug for this, and we can compare our settings and get it working for you. Mason. ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] bumping the authorised_values.category column to 20 chars ?
On 2008/11/21, at 8:05 AM, Ryan Higgins wrote: I favor Galen's approach. Yep, i think it will do the job just fine I've always found the interface confusing for adding a new auth_val category: you have to enter the category's first authorised_value at the same time you create the category. Ryan Me too, and if you remove all the auth_value rows for a category, the category dissapears ;/ Currently the common categories are hardcoded to be displayed (Asort1/2, Bsort1/2 etc..) I'll put my hand up and add this mod to the end of my list of SAN-OP acqui work. ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Tab stops in source code
On 2008/11/13, at 3:35 PM, Andrew Moore wrote: On Wed, Nov 12, 2008 at 8:15 PM, Rick Welykochy [EMAIL PROTECTED] wrote: Hi all In the file abort.pl in Koha 3 I see the follow cryptic comment: # Please use 8-character tabs for this file (indents are every 4 characters) I don't know the history of this comment, but i wouldnt wotry too much about it its old and not very well enforced (at least) I think we should all agree on a standardised .perltidyrc format, and i vote for Andy's ;) Ive been using Andy's since he first posted it on the list, and its a nice format for me Thanks again Andy! Hi Rick - I recently tried to gather some of the more common preferences for formatting perl code in the Koha community and put together this perltidyrc file: http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=blob;f=xt/perltidyrc -Andy ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Koha 3.0 _FC7: DBD::mysql
On 2008/07/12, at 2:53 AM, Partha Mukhopadhyay wrote: /usr/bin/ld: cannot find -lmysqlclient collect2: ld returned 1 exit status make: *** [blib/arch/auto/DBD/mysql/mysql.so] Error 1 /usr/bin/make -- NOT OK you are missing some 'mysqlclient' library package??? ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] [Koha-bugs] Choose anothero language problems
On 2008/07/3, at 12:57 PM, constantine wrote: Dear koha developers, I successfully install koha, but after choosing in the beginning of http://localhost:8080 installation procedure the language uk_UA, I got in a koha installation that does NOT use English language. Instead it uses a language with characters like Управління параметрами системи !!! :( How can I change that? hmm, I noticed this during a recent install too. does uk_UA mean ukraine perhaps? fyi: during install scroll down and choose 'en' for english To fix your installed koha, try this sql... mysql update systempreferences set value = 'en' where variable = 'language'; mysql update systempreferences set value = 'en' where variable = 'opaclanguages' ; Mason. ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] code formatting (was: [Koha-patches] [PATCH] Bug 2176: adding SMS::Send to list of dependencies)
I'd really like to be able to use perltidy to make the code that I edit and contribute more readable. Is there a particular indentation style that you think would be good to use on code that I change in Koha? I couldn't find much about this on the wiki. If my notes from 1.9 are accurate, we used to use perltidy -bar -ce -pt=2 -vt=2 -en=4 which is almost what is in the perlstyle manual, except cuddled elses. However, it's not been enforced much and more readable depends on what you're using to read it... Super, a step towards consensus! I've opened up bug 2269 to add a perltidyrc file with these options and will work to follow it. http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2269 Heya Andy Just a quickie from me on this great topic i have recently found 2 nice vim macros that allow you to select a block of text and perltidy it, and perltidy the whole file too (the following example has these 2 macros bound to keys f4, and f5) stick this in your ~/vimrc file, and feel good ;) Enable Perltidy processing map F4 Esc:%! perltidyCR map F5 Esc:','! perltidyCR cheers, Mason. ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Status of Debian and Koha
On 2008/06/18, at 8:28 PM, Marc Chantreux wrote: hello Adam, On Wed, Jun 18, 2008 at 10:05:50AM +0200, Adam Dickmeiss wrote: AFAIK, YAZ 3.0.30 is packaged without SSL completely (due to the problem with GNU TLS Openssl). If you can't fix the soft, you can fix the license (http://www.gnome.org/~markmc/openssl-and-the-gpl.html) without having side effect ;) regards Interesting link - thanks Marc ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
[Koha-devel] RFC on adding 'Independant-Branches' restrictions to letters/notices
Hi All, I'm working on a feature to add branch-specific restrictions the editing of Tools-Notices letters The restriction could be set using a syspref (the existing Independant-Branches syspref looks good) , or a user-level-permission (my personal choice 'edit_notices_branch_only' perhaps?) The only current issue is that the 'letter' table really needs a new 'branchcode' column for this to work simply I have an version of this feature working on my dev koha, but the 'branchcode' is currently being stored in the code field , and appended to the code value, separated by a ' : ' - eg:'ACCTDETAILS:MAIN' - which is a workaround for the missing branchcode field , but obviously isnt ideal... What are people's thoughts to added a 'branchcode' column 'letter' table? , I know we have a bit of a DB-structure freeze before the koha-beta3, but i thought i'd ask what everyone thought Is this a nice feature everyone? Paul and HDL what do you think of this, (as both of you did almost all of the existing 'Notices' work?) Any thoughts poeples? Thanks, Mason. ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
