<div dir="ltr"><table class="Bs nH iY" cellpadding="0"><tbody><tr><td class="Bu"><div class="nH if"><div class="nH aHU"><div class="nH hx"><div class="nH"><div tabindex="-1" style class="h7 ie nH oy8Mbf"><div class="Bk"><div class="G3 G2"><div><div id=":xk"><div class="adn ads" style><div class="gs"><div id=":xi" class="ii gt m14887a172c7fec95 adP adO"><div id=":xj" class="a3s" style="overflow:hidden"><div dir="ltr"><div><div><div>good morning koha users<br>I
am having our library bibliographic details above 2 lakhs records in iso 2709 format. please explain in details how to
convert records iso2709 format in to koha software. <br></div>thanking you,<br></div>your sincerely<br></div>dr.j.Vijaya Kumar<div class="yj6qo ajU"><div id=":x3" class="ajR" tabindex="0"><img class="ajT" src="https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif"></div></div></div></div></div></div></div><div class="gA gt acV"><div class="gB xu"><div class="ip iq"><div id=":xh"><table class="cf FVrZGe"><tbody><tr><td class="amq"><img id=":0_4" name=":0" src="https://plus.google.com/_/focus/photos/private/AIbEiAIAAABECOuruJOzuYbJvwEiC3ZjYXJkX3Bob3RvKig4NDFmYjE1OTRjYmM0M2MwNTU1NTFjMmFkMGM3ZWRlNGI3NDE4ZTA1MAEEgq-MZ-r20vWBvcr6DIBA-Hbdgw?sz=24" class="ajn bofPge"></td><td class="amr"><div class="nr tMHS5d"><div class="amn">Click here to <span id=":y2" class="ams" tabindex="0">Reply</span> or <span id=":xl" class="ams" tabindex="0">Forward</span></div></div></td></tr></tbody></table></div></div></div></div></div></div></div></div></div></div></div></div><div class="nH Gn"><div class="l2 ov"><div id=":nm" class="aeV"><div><div class="md mj"><div><span dir="ltr">1.7 GB</span> (11%) of <span dir="ltr">15 GB</span> used</div><div class="aeW"><a target="_blank" href="https://accounts.google.com/ManageStorage?hl=en" class="l8">Manage</a></div></div></div></div><div class="aeU"><div id=":nl"><div><div class="ma"><span class="l3"><span dir="ltr">©2014 Google</span></span> - <a href="https://www.gmail.com/intl/en/mail/help/terms.html" target="_blank" class="l9">Terms & Privacy</a> <div class="mb">Powered by </div></div></div></div></div><div id=":nj" class="ae3"><div><div class="l6"><div>Last account activity: 35 minutes ago</div><span id=":nx" class="l8 ou" tabindex="0">Details</span></div></div></div></div></div></div></td><td class="Bu yM"><br></td><td style="height:454px" class="Bu y3"><br></td></tr></tbody></table><div style class="nH"><div class="AT" style><div class="aBY"><div class="aEE"><img src="https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif" class="aHY aED"></div><div id=":p9" class="AU Ppr1Ac"><a class="e b8w1me" href="https://mail.google.com/mail/?tab=wm&pli=1#ad/273922/CLHi4Z6b6sACFSKaTAodlk0AdQ/cv_p">Azure StorSimple Solution</a></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 17, 2014 at 9:37 PM, <span dir="ltr"><<a href="mailto:koha-devel-request@lists.koha-community.org" target="_blank">koha-devel-request@lists.koha-community.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send Koha-devel mailing list submissions to<br>
<a href="mailto:koha-devel@lists.koha-community.org">koha-devel@lists.koha-community.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" target="_blank">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:koha-devel-request@lists.koha-community.org">koha-devel-request@lists.koha-community.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:koha-devel-owner@lists.koha-community.org">koha-devel-owner@lists.koha-community.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Koha-devel digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Koha and DBIC (Kyle Hall)<br>
2. Re: Koha and DBIC (Colin Campbell)<br>
3. Re: Koha and DBIC (Marcel de Rooy)<br>
4. Re: Koha and DBIC (Mark Tompsett)<br>
5. Re: Koha and DBIC (Colin Campbell)<br>
6. Re: Koha and DBIC (Chris Cormack)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 17 Sep 2014 06:40:09 -0400<br>
From: Kyle Hall <<a href="mailto:kyle.m.hall@gmail.com">kyle.m.hall@gmail.com</a>><br>
To: Jonathan Druart <<a href="mailto:jonathan.druart@biblibre.com">jonathan.druart@biblibre.com</a>>, Kyle Hall<br>
<<a href="mailto:kyle.m.hall@gmail.com">kyle.m.hall@gmail.com</a>>, Koha Devel<br>
<<a href="mailto:koha-devel@lists.koha-community.org">koha-devel@lists.koha-community.org</a>><br>
Subject: Re: [Koha-devel] Koha and DBIC<br>
Message-ID:<br>
<<a href="mailto:CACpVHfyZnF9jpWKW5hGcmXtG4eZFf%2BYpCzkJGiqEwhm11XkoEA@mail.gmail.com">CACpVHfyZnF9jpWKW5hGcmXtG4eZFf+YpCzkJGiqEwhm11XkoEA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Chris, I'm a bit lost here. The idea behind Koha::Object is that we have a<br>
common base class from which to derive Koha::Biblio, Koha::Serial and so<br>
forth. That is, this class would be used as the base for classes that have<br>
a simple 1 to 1 table mapping to encapsulate DBIC while maintaining a<br>
consistent set of methods across our many classes. ObjectSet would give us<br>
set iterators, set operations, and be a better place to have methods that<br>
return a set ( e.g. Koha::Issue::Set::GetOverdues would return a collection<br>
of overdue checkouts ).<br>
<br>
I'm not sure why you disagree with this idea. Could you expand a bit?<br>
<br>
Kyle<br>
<br>
<br>
> -1 for DBIx::Class calls in the .pl<br>
> -1 for Koha::Object and Koha::Object::Set<br>
> +1 for proper objects like Koha::Biblio, Koha::Account, Koha::Serial etc<br>
><br>
> Chris<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.koha-community.org/pipermail/koha-devel/attachments/20140917/3b5fc3d8/attachment-0001.html" target="_blank">http://lists.koha-community.org/pipermail/koha-devel/attachments/20140917/3b5fc3d8/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 17 Sep 2014 11:49:23 +0100<br>
From: Colin Campbell <<a href="mailto:colin.campbell@ptfs-europe.com">colin.campbell@ptfs-europe.com</a>><br>
To: <a href="mailto:koha-devel@lists.koha-community.org">koha-devel@lists.koha-community.org</a><br>
Subject: Re: [Koha-devel] Koha and DBIC<br>
Message-ID: <<a href="mailto:20140917104923.GA7912@zazou.cscnet.co.uk">20140917104923.GA7912@zazou.cscnet.co.uk</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
A Koha::Object sounds like extremely poor design. What kind of object is<br>
a Koha::Object, what are its properties, when we say a Koha::Biblio isa<br>
Koha::Object what does that mean? In practice what meaningful properties<br>
it has it inherits from Koha::Schema::Result::Biblio which is liable to<br>
be a better representation than the vaguer Onject.<br>
<br>
In practice I've recently written some scripts which in first version<br>
used some abstractions built around dbic ResultSets, As I added to them<br>
I stripped out out the abstractions and used the dbic result sets as I<br>
found this generated cleaner, more straightforward code.<br>
<br>
Colin<br>
<br>
--<br>
Colin Campbell<br>
Chief Software Engineer,<br>
PTFS Europe Limited<br>
Content Management and Library Solutions<br>
+44 (0) 800 756 6803 (phone)<br>
+44 (0) 7759 633626 (mobile)<br>
<a href="mailto:colin.campbell@ptfs-europe.com">colin.campbell@ptfs-europe.com</a><br>
skype: colin_campbell2<br>
<br>
<a href="http://www.ptfs-europe.com" target="_blank">http://www.ptfs-europe.com</a><br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Wed, 17 Sep 2014 12:40:51 +0000<br>
From: Marcel de Rooy <<a href="mailto:M.de.Rooy@rijksmuseum.nl">M.de.Rooy@rijksmuseum.nl</a>><br>
To: Koha Devel <<a href="mailto:koha-devel@lists.koha-community.org">koha-devel@lists.koha-community.org</a>><br>
Subject: Re: [Koha-devel] Koha and DBIC<br>
Message-ID:<br>
<809BE39CD64BFD4EB9036172EBCCFA31423D7E05@S-MAIL-1B.rijksmuseum.intra><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
> I would say: Leave all storage related actions in Koha::Schema. KohaRow does not make sense to me.<br>
> Furthermore, define the objects that actually have 'real' business logic and put that in some Koha::Object.<br>
<br>
Just to add to the confusion ;) When I wrote "some Koha::Object" here, I was not literally suggesting Koha::Object, I was thinking of something like Koha::Biblio or Koha::Patron etc.<br>
I would not suggest to add such an object for every table in Koha. We should clearly define which objects(!) we really need, having sufficient business logic etc. to justify an interface to DBIx.<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.koha-community.org/pipermail/koha-devel/attachments/20140917/036e8ce9/attachment-0001.html" target="_blank">http://lists.koha-community.org/pipermail/koha-devel/attachments/20140917/036e8ce9/attachment-0001.html</a>><br>
-------------- next part --------------<br>
An embedded and charset-unspecified text was scrubbed...<br>
Name: ATT00001.txt<br>
URL: <<a href="http://lists.koha-community.org/pipermail/koha-devel/attachments/20140917/036e8ce9/attachment-0001.txt" target="_blank">http://lists.koha-community.org/pipermail/koha-devel/attachments/20140917/036e8ce9/attachment-0001.txt</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Wed, 17 Sep 2014 08:50:37 -0400<br>
From: "Mark Tompsett" <<a href="mailto:mtompset@hotmail.com">mtompset@hotmail.com</a>><br>
To: "Marcel de Rooy" <<a href="mailto:M.de.Rooy@rijksmuseum.nl">M.de.Rooy@rijksmuseum.nl</a>><br>
Cc: <a href="mailto:koha-devel@lists.koha-community.org">koha-devel@lists.koha-community.org</a><br>
Subject: Re: [Koha-devel] Koha and DBIC<br>
Message-ID: <BLU172-DS21D031DE305CA383185011C6B60@phx.gbl><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Greetings,<br>
<br>
> Just to add to the confusion ;)<br>
> When I wrote "some Koha::Object" here,<br>
> I was not literally suggesting Koha::Object,<br>
> I was thinking of something like Koha::Biblio or Koha::Patron etc.<br>
That?s what I understood. So physically, we may have the tables we currently have accessed via DBIC, but the Koha::Biblio object would blend DBIC objects related to Biblios and Items. Right? This would mean that Koha::Biblio would provide whatever methods regardless of the backend structure.<br>
GPML,<br>
Mark Tompsett<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.koha-community.org/pipermail/koha-devel/attachments/20140917/34f28f56/attachment-0001.html" target="_blank">http://lists.koha-community.org/pipermail/koha-devel/attachments/20140917/34f28f56/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Wed, 17 Sep 2014 14:49:34 +0100<br>
From: Colin Campbell <<a href="mailto:colin.campbell@ptfs-europe.com">colin.campbell@ptfs-europe.com</a>><br>
To: <a href="mailto:koha-devel@lists.koha-community.org">koha-devel@lists.koha-community.org</a><br>
Subject: Re: [Koha-devel] Koha and DBIC<br>
Message-ID: <<a href="mailto:20140917134934.GA10248@zazou.cscnet.co.uk">20140917134934.GA10248@zazou.cscnet.co.uk</a>><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
On Wed, Sep 17, 2014 at 08:50:37AM -0400, Mark Tompsett wrote:<br>
> Greetings,<br>
><br>
> > Just to add to the confusion ;)<br>
> > When I wrote "some Koha::Object" here,<br>
> > I was not literally suggesting Koha::Object,<br>
> > I was thinking of something like Koha::Biblio or Koha::Patron etc.<br>
> That?s what I understood. So physically, we may have the tables we currently have accessed via DBIC, but the Koha::Biblio object would blend DBIC objects related to Biblios and Items. Right? This would mean that Koha::Biblio would provide whatever methods regardless of the backend structure.<br>
<br>
Trouble is it sidesteps fixing the schema. The interplay between biblio<br>
and biblioitems will remain a problem for maintenance in future. There<br>
is already special code added to link the classes because their<br>
relationship is not maintained by the database. Special cases tend to<br>
grow over time and spawn more special cases.<br>
<br>
C.<br>
<br>
--<br>
Colin Campbell<br>
Chief Software Engineer,<br>
PTFS Europe Limited<br>
Content Management and Library Solutions<br>
+44 (0) 800 756 6803 (phone)<br>
+44 (0) 7759 633626 (mobile)<br>
<a href="mailto:colin.campbell@ptfs-europe.com">colin.campbell@ptfs-europe.com</a><br>
skype: colin_campbell2<br>
<br>
<a href="http://www.ptfs-europe.com" target="_blank">http://www.ptfs-europe.com</a><br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Thu, 18 Sep 2014 04:07:55 +1200<br>
From: Chris Cormack <<a href="mailto:chrisc@catalyst.net.nz">chrisc@catalyst.net.nz</a>><br>
To: Colin Campbell <<a href="mailto:colin.campbell@ptfs-europe.com">colin.campbell@ptfs-europe.com</a>>,<br>
<a href="mailto:koha-devel@lists.koha-community.org">koha-devel@lists.koha-community.org</a><br>
Subject: Re: [Koha-devel] Koha and DBIC<br>
Message-ID: <<a href="mailto:3901e549-a890-4824-ba8c-6277e7078f42@email.android.com">3901e549-a890-4824-ba8c-6277e7078f42@email.android.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
<br>
<br>
On 18 September 2014 1:49:34 am NZST, Colin Campbell <<a href="mailto:colin.campbell@ptfs-europe.com">colin.campbell@ptfs-europe.com</a>> wrote:<br>
>On Wed, Sep 17, 2014 at 08:50:37AM -0400, Mark Tompsett wrote:<br>
>> Greetings,<br>
>><br>
>> > Just to add to the confusion ;)<br>
>> > When I wrote "some Koha::Object" here,<br>
>> > I was not literally suggesting Koha::Object,<br>
>> > I was thinking of something like Koha::Biblio or Koha::Patron etc.<br>
>> That?s what I understood. So physically, we may have the tables we<br>
>currently have accessed via DBIC, but the Koha::Biblio object would<br>
>blend DBIC objects related to Biblios and Items. Right? This would mean<br>
>that Koha::Biblio would provide whatever methods regardless of the<br>
>backend structure.<br>
><br>
>Trouble is it sidesteps fixing the schema. The interplay between biblio<br>
>and biblioitems will remain a problem for maintenance in future. There<br>
>is already special code added to link the classes because their<br>
>relationship is not maintained by the database. Special cases tend to<br>
>grow over time and spawn more special cases.<br>
><br>
<br>
It's not an either/or proposition, having Koha::Biblio doesn't mean you can't fix the schema too. It just means all the business logic for dealing with it is in that module/object. Instead of strewn about in scripts all over the place.<br>
<br>
Chris<br>
<br>
<br>
<br>
<br>
>C.<br>
><br>
>--<br>
>Colin Campbell<br>
>Chief Software Engineer,<br>
>PTFS Europe Limited<br>
>Content Management and Library Solutions<br>
>+44 (0) 800 756 6803 (phone)<br>
>+44 (0) 7759 633626 (mobile)<br>
><a href="mailto:colin.campbell@ptfs-europe.com">colin.campbell@ptfs-europe.com</a><br>
>skype: colin_campbell2<br>
><br>
><a href="http://www.ptfs-europe.com" target="_blank">http://www.ptfs-europe.com</a><br>
>_______________________________________________<br>
>Koha-devel mailing list<br>
><a href="mailto:Koha-devel@lists.koha-community.org">Koha-devel@lists.koha-community.org</a><br>
><a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" target="_blank">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br>
>website : <a href="http://www.koha-community.org/" target="_blank">http://www.koha-community.org/</a><br>
>git : <a href="http://git.koha-community.org/" target="_blank">http://git.koha-community.org/</a><br>
>bugs : <a href="http://bugs.koha-community.org/" target="_blank">http://bugs.koha-community.org/</a><br>
<br>
--<br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Koha-devel mailing list<br>
<a href="mailto:Koha-devel@lists.koha-community.org">Koha-devel@lists.koha-community.org</a><br>
<a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" target="_blank">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br>
website : <a href="http://www.koha-community.org/" target="_blank">http://www.koha-community.org/</a><br>
git : <a href="http://git.koha-community.org/" target="_blank">http://git.koha-community.org/</a><br>
bugs : <a href="http://bugs.koha-community.org/" target="_blank">http://bugs.koha-community.org/</a><br>
<br>
End of Koha-devel Digest, Vol 106, Issue 23<br>
*******************************************<br>
</blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr">Dr.J.Vijaya Kumar<br>Engineering College Library<br>Andhra University<br>Visakhapatnam- 530 003<br>Andhra Pradesh<br>India.<br>E-Mail Address: <br><a href="mailto:kumarjammala@gmail.com" target="_blank">kumarjammala@gmail.com</a><br><a href="mailto:kumarjammala@rediffmail.com" target="_blank">kumarjammala@rediffmail.com</a><br><a href="mailto:jammalamadakavijayakumar@yahoo.com" target="_blank">jammalamadakavijayakumar@yahoo.com</a></div>
</div>