[Koha] Database Upgrade

Sat Mar 9 22:28:11 NZDT 2019

Hi Mohamad,

I am not sure how much performance for both methods would differ. Just
be aware that you will have to maintain your changes through updates and
changes in Koha's architecture, so that is something you need to assess
and decide if it's worth doing for the kind of change you want to make.

Alternatively you can also think about contributing changes back to the
community, of course :) For the fields you mentioned I am not sure if
they would make a good general feature - I'd expect them in the serials
module and not on item level.

Katrin

On 09.03.19 10:22, Mohamad F. Barham wrote:
>
> Thanks Katrin.
>
>
> using my method I were able to see fields in KOHA after editting
> kohastructure.sql to reflect my changes there and running
> update_dbix_class_files.pl from koha root dir. and finally assign mapping.
>
>
> I test you suggested method and work correctly, but whats about
> performance? I think to be in a separate column much better for
> performance, cause in your case every time need to access these new
> fields need more XML parsing  .
>
>
> Regards
>
>
>
>
> cid:image002.png at 01D327F4.25E9A910
>
>
>
> *Mohamad Barham*
>
> System administrator | Information Technology Department
>
> Birzeit University
>
> P.O.Box. 14, Birzeit, Palestine
>
> Tel: + 970 22982012 | Mob: +970 597 861929 | Ext: 5616
>
> mbarham at birzeit.edu | www.birzeit.edu <http://www.birzeit.edu/>
>
>
>
>
>
> ------------------------------------------------------------------------
> *From:* Koha <koha-bounces at lists.katipo.co.nz> on behalf of Katrin
> Fischer <katrin.fischer.83 at web.de>
> *Sent:* Thursday, March 7, 2019 10:05:24 PM
> *To:* koha at lists.katipo.co.nz
> *Subject:* Re: [Koha] Database Upgrade
> HI Mohamad,
>
> I don't think Koha will be able to pick up your changes to the items
> table without making more changes to Koha's code.
>
> But there is another way of adding more information/custom fields to the
> items table: In items there is the column more_subfields_xml. This is
> used to store additional content. All you need to do is change your MARC
> framework and add additional 952 subfields without any mapping. Without
> a mapping to a database column, the content will be automatically saved
> in more_subfields_xml as XML that you can query with SQL, add to the
> item search by configuration etc.
>
> So no changes to Koha's code and db structure would be needed and you
> won't have any problems with updates.
>
> Hope this helps,
>
> Katrin
>
> On 04.03.19 14:36, Mohamad F. Barham wrote:
> > Dears,
> >
> > I am a little bit new to KOHA system.
> >
> > I am trying to test KOHA adaptability to my university library
> (where I work).
> >
> > I want to add new fields to be used with items e.x binding _cost,
> binding_note, binding_type.
> >
> > I already added new columns in the database in items table to be
> used  for binding _cost, binding_note and binding_type. the columns
> were added throug atomicupdate, then running the command
> > koha-upgrade-schema INSTANCE.
> >
> > the columns now exist in the database, but how to add entry for KOHA
> to marc mapping for these new columns?
> >
> > is it automatically? or should is insert something else where?
> >
> > notes
> > KOHA 18.11 on debian
> >
> >
> >
> >
> >
> >
> > [cid:image002.png at 01D327F4.25E9A910]
> >
> >
> > Mohamad Barham
> >
> > System administrator | Information Technology Department
> >
> > Birzeit University
> >
> > P.O.Box. 14, Birzeit, Palestine
> >
> > Tel: + 970 22982012 | Mob: +970 597 861929 | Ext: 5616
> >
> > mbarham at birzeit.edu | www.birzeit.edu<http://www.birzeit.edu/>
> >
> >
> >
> >
> >
> >
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~
> > The information contained in this communication is intended solely
> for the use of the individual or entity to whom it is addressed and
> others authorized to receive it. It may contain confidential or
> legally privileged information. If you are not the intended recipient
> you are hereby notified that any disclosure, copying, distribution or
> taking any action in reliance on the contents of this information is
> strictly prohibited and may be unlawful. If you have received this
> communication in error, please notify us immediately by responding to
> this email and then delete it from your system. The University is
> neither liable for the proper and complete transmission of the
> information contained in this communication nor for any delay in its
> receipt.
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~
> > _______________________________________________
> > Koha mailing list http://koha-community.org
> > Koha at lists.katipo.co.nz
> > https://lists.katipo.co.nz/mailman/listinfo/koha
> _______________________________________________
> Koha mailing list http://koha-community.org
> Koha at lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
> ~~~~~~~~~~~~~~~~~~~~~~~~~~
> The information contained in this communication is intended solely for
> the use of the individual or entity to whom it is addressed and others
> authorized to receive it. It may contain confidential or legally
> privileged information. If you are not the intended recipient you are
> hereby notified that any disclosure, copying, distribution or taking
> any action in reliance on the contents of this information is strictly
> prohibited and may be unlawful. If you have received this
> communication in error, please notify us immediately by responding to
> this email and then delete it from your system. The University is
> neither liable for the proper and complete transmission of the
> information contained in this communication nor for any delay in its
> receipt.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~