[Koha-devel] how to start customization
Hello every body, I have got the clone of koha using the Git after configuring the koha on Debian 4.0. Kindly let me know how can I set development environment to customize koha according to the requirement of our own library. Clone of koha on my local system has all the code of koha modules. Should I access those modules and make changes in required and after saving that locally should commit it using Git? Please help me as I am new entrant in Perl and koha. Have a nice time and thanks in advance. ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
[Koha-devel] Koha Conference in April 16-17th
If you are planning on attending or thinking about attending - I would love to hear what you would be interested in hearing about and or presenting! Drop me an email at dschu...@gmail.com - or post right back here! I want this to be a shared conference of user presentations as well as vendor how to's. Have you setup any special Cron jobs? Cron... What is that! Doing any special SQL's directly on the database or through the Report Wizard? It's amazing what we all do and think everyone else already knows how! I would LOVE to see more on reports Wizard as I don't understand it yet. David Schuster -- View this message in context: http://www.nabble.com/Koha-Conference-in-April-16-17th-tp21204807p21204807.html Sent from the Koha - Dev mailing list archive at Nabble.com. ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
[Koha-devel] Koha3 populate
Yes, the installation usually offers that chance. But in my case, for example, installing Koha3 I had to force some installation steps manually and as a result the DB testing data weren't correctly loaded. Like Rick I will find useful to have those data available as a stand- off download or such. Are there already? Best Matteo Romanello Anyone have a script or SQL file(s) to populate a Koha 3 database with data for testing and development? Isn't that an option offered during installation? -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Koha Conference in April 16-17th
On Tue, Dec 30, 2008 at 4:39 AM, David Schuster wrote: > > If you are planning on attending or thinking about attending - I would love > to hear what you would be interested in hearing about and or presenting! > > Drop me an email at dschu...@gmail.com - or post right back here! > > I want this to be a shared conference of user presentations as well as > vendor how to's. > > Have you setup any special Cron jobs? Cron... What is that! > > Doing any special SQL's directly on the database or through the Report > Wizard? > > It's amazing what we all do and think everyone else already knows how! I > would LOVE to see more on reports Wizard as I don't understand it yet. > If I can suggest as well as responding if people can update the page on the wiki http://wiki.koha.org/doku.php?id=kohacon2009&s=conference Then things are in an easy to find place. Maybe we could start building a skeleton conference programme on there? Chris ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] zebra recDB file growing...
paul POULAIN wrote: > Hi, > > on a large database (SAN-OP, 300 000 items), we have noticed that the > recDB file of zebra is increasing. > On a freshly indexed DB, it's less than 1G, and, in 2-3 weeks, it can > reach up to 2GB. > > Did anyone notice this ? Is there an explanation ? a solution (apart > from doing a full zebra reindexing every week, with DB reset) ? > > Is a probably known problem. See: http://bugzilla.indexdata.dk/show_bug.cgi?id=2338 / Adam ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] COinS in Koha
Hi, I just send a new patch for COinS, which works better with MARC21. The support of COinS(under UNIMARC) is better like document types(based on leader), authors, publisher, etc... I invite someone who is a god in MARC21 to improve the MARC21 support, like document type detection, and add some fields, to patch my patch :) At the moment only the book type is known for MARC21, it should be improved. bests, -- Nahuel ANGELINETTI Le Mon, 29 Dec 2008 13:45:43 -0500, "Galen Charlton" a écrit : > Hi, > > On Mon, Dec 29, 2008 at 11:04 AM, Nahuel ANGELINETTI > wrote: > > Some question about COinS support in Koha, we will integrate the > > unimarc support of COinS in koha, but I have some question about it. > > Actually only "am" document type is "managed", but why? I think it's > > too much restrictive, we should only parse the first char of record > > type(in leader) and compare with known COinS document type. > > AND if there is no equivalent, we use Book as default(cf WorldCat). > > What do you think about this? > > I agree that we should extend the document types that Koha can embed > COinS for. > > Regards, > > Galen ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Koha3 populate
> Yes, the installation usually offers that chance. > But in my case, for example, installing Koha3 I had to force some > installation steps manually and as a result the DB testing data weren't > correctly loaded. It looks like there are lots of goodies in installer/data/mysql -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
[Koha-devel] Database size with InnoDB
Hi people, I don't know if some people have a big experience from InnoDB and MySQL. We just see in mysql documentation innoDB does not reallow the disk space of deleted datas. An example : the disk used by one of our clients, who have only 50 000 notices, is 4GB and is still growing. The explication is innodb don't delete data from disk after a "drop" or a "delete". http://dev.mysql.com/doc/refman/5.0/en/adding-and-removing.html "Currently, you cannot remove a data file from the tablespace. To decrease the size of your tablespace, use this procedure: " The solution to decrease the size of data file, is to dump, and restore the database... A really bad solution for production installations. Does someone have experimented the same problem? What are your solution about this problem ? bests, -- Nahuel ANGELINETTI ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] how to start customization
I'll explain how I handle customization, that should give a good start. First thing is I don't touch the clone. In git the clone is called master. I make a new branch, let's call it custom, like so: `git branch custom origin` `git checkout custom` That will create the new branch and load it's state to the directory. This is what I would change. I would strongly recommend using git, or whatever revision control system you are comfortable with, to save your changes. My first round of customizing on Koha 2.2 I did not save my changes with git, and I soon regretted it. Whenever I wanted to get the new version of Koha I had to diff and merge by hand all my changes. Git can handle most of that work for you. On the topic of getting changes from the clone. First thing is to get the changes. `git fetch` `git rebase origin master` Those commands will pull down changes and apply those changes to the clone. That should go flawlessly. The next part is a little harder. `git rebase origin custom` That will roll back your work, apply the changes from clone, and roll forward your work again on top of the new code. Usually this will go ok. Some time I have a change that happens at where a new change happens. Sometimes (usually) git does not know how to handle this. It will leave both changes in place an kindly tell you in the terminal that a conflict needs to be resolved. It tells you the files, and marks the conflict(s) in the file with "<<<" where the new clone code is and ">>>" where your new code stops, with "==" or some such between them. Since, hopefully, you know your own code, this shouldn't be to hard to fix. Then there are a couple commands to tell git to continue. `git update-index [changed file]` `git rebase --continue` The first command is important, but git will not tell you to do it. That is how I handle my customization. Maybe this description will help you. Good luck. On Tue, 2008-12-23 at 15:08 +0500, Zahoor wrote: > Hello every body, > > I have got the clone of koha using the Git after configuring the koha > on Debian 4.0. > > Kindly let me know how can I set development environment to customize > koha according to the requirement of our own library. Clone of koha on > my local system has all the code of koha modules. Should I access > those modules and make changes in required and after saving that > locally should commit it using Git? > > > > Please help me as I am new entrant in Perl and koha. > > Have a nice time and thanks in advance. > > > ___ > Koha-devel mailing list > Koha-devel@lists.koha.org > http://lists.koha.org/mailman/listinfo/koha-devel -- Michael Hafen Systems Analyst and Programmer Washington County School District Utah, USA for Koha checkout http://koha-dev.washk12.org or git://koha-dev.washk12.org/koha ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
[Koha-devel] MARC Framework Editor
Hi, Paul were you having another crack at the MARC Framework editor as well at the moment? or someone else? Having just spent an hour or 2 working with it and giving up because it's just tooo much clicking to delete all the fields you don't need, we'll resort to a "programmer" method. However, it would be useful to be able to do 2 things 1/. Create a new framework based on either a "blank" or preferably, with only the fields that are mandatory for Koha to work, so that you just add in any fields you want, (usually about 20) rather than deleting all the ones you don't (about 900!) 2/. Be about to do a bulk delete on fields - ie click all the ones you want to delete and get rid of them in one go per page, rather than each delete taking 2-3 clicks. Cheers Rachel ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
