Re: [LIS-Forum] Koha opac purchase suggestions form customization guide

Dear All, Greetings! I completely agree with Dr. Saiful that changes to the original code base of Koha will create a problem in Koha updates and should be avoided. It is always good to work around keeping the original code intact. I appreciate the efforts of Mr. Vinod, but it should be in tandem with the development of Koha's upgrades so that his work is acknowledged by developers/others. Regards, S M Pujar Chief Librarian IGIDR, Mumbai ============== On Thu, Sep 8, 2022 at 9:56 AM Dr. Saiful Amin wrote:

Greetings,

The process described in the link suggests exactly the things that one must avoid while customizing any software.

There are several issues with this approach:

1. Altering database schema is a sacrilege and must be avoided. Future upgrades will probably destroy all the database changes and the accumulated data. It can even prevent applying updates in the future.

2. Changing application code (*.pm|pl) is another thing to avoid for the same reasons as above. However, it is possible to keep a record of the changes in a patch file and applied to the code after every upgrade. But if a future software update changed the same file, then the patch needs to be updated as well. As one can understand that it is not trivial and very time-consuming. Hence, this approach is suitable only for very minor changes of a few lines.

3. Template file (*.tt) changes are another area that has a high chance of breaking after the upgrade. Same suggestions as the point 2 applies here.

4. The "*.3pm" files do not need to be changed at all. These are documentation/manual generated automatically from the code. The effort to change these files is redundant.

I understand that there might be a pressing need to make such changes for local requirements or compliances. Calculate the cost/effort of maintaining a separate code-base and backup of the altered database and syncing it after every update. Make sure that the cost/effort is worth it.

There are two approaches that I can suggest in such a scenario:

1. The recommended process is to submit these changes as patches to the Koha Community Bug Tracker system. Speak to the developers in the forums to get it approved to be made a part of the core software. It however takes time since the developers need to prioritize critical changes over general improvement ones.

2. Write a Koha Plugin which de-couples the code from core Koha software and can be maintained separately. It is less likely to break during the upgrades.

Best regards, Saiful Amin Semantic Consulting Services Pvt. Ltd. Bangalore

On Tue, Sep 6, 2022 at 10:14 AM vinod mishra wrote:

...

Dear all Wish you all a very happy teachers' day! It's my pleasure to share one of my desire and requirement of many libraries to customize the Koha ILMS online purchase suggestion form is fulfilled today. I could able to customize the same and the entire process is shared with the community on auspicious Teacher's Day. Hope this will be utilized by many libraries to make their library purchase suggestion online. Your feedback is highly appreciated and some more development is underway.

http://itshelp.co.in/2022/09/customization-of-koha-online-purchase-suggestio...

...