good morning koha users
I am having our library bibliographic details of our library collection above 2 lakhs records in iso 2709 format please explain indetails how to convert in iso2709 from in to koha software.
thanking you,
your sincerely
dr.j.Vijaya Kumar



On Wed, Sep 17, 2014 at 4:02 AM, <koha-devel-request@lists.koha-community.org> wrote:
Send Koha-devel mailing list submissions to
        koha-devel@lists.koha-community.org

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
or, via email, send a message with subject or body 'help' to
        koha-devel-request@lists.koha-community.org

You can reach the person managing the list at
        koha-devel-owner@lists.koha-community.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Koha-devel digest..."


Today's Topics:

   1. Re: problem to perform a simple query (Adnier Rosello)
      (Adnier Rosell? Carrazana)
   2. Dom indexing operational with a fresh install?
      (Francois Charbonnier)
   3. Re: Dom indexing operational with a fresh install?
      (Tomas Cohen Arazi)
   4. Re: Koha and DBIC (Kyle Hall)


----------------------------------------------------------------------

Message: 1
Date: Tue, 16 Sep 2014 16:15:13 -0400 (CDT)
From: Adnier Rosell? Carrazana <arosello@uci.cu>
To: koha-devel@lists.koha-community.org
Subject: Re: [Koha-devel] problem to perform a simple query (Adnier
        Rosello)
Message-ID:
        <1412455981.134123159.1410898513042.JavaMail.zimbra@uci.cu>
Content-Type: text/plain; charset=utf-8

Robin:
apology not specify in my previous mail that my koha version is 3.0.6, which has a preference variable to not use the zebra (NoZebra), so the search of bibliographic records are handled directly by MySQL, grateful by the response, I hope to clarify the problem, Greetings

Ad
----- Mensaje original -----
Send Koha-devel mailing list submissions to
        koha-devel@lists.koha-community.org

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
or, via email, send a message with subject or body 'help' to
        koha-devel-request@lists.koha-community.org

You can reach the person managing the list at
        koha-devel-owner@lists.koha-community.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Koha-devel digest..."


Today's Topics:

   1. Re: Koha and DBIC (Marcel de Rooy)
   2. Re: problem to perform a simple query (Robin Sheat)
   3. VIAF and Koha 3.16.x (Partha Mukhopadhyay)


----------------------------------------------------------------------

Message: 1
Date: Mon, 15 Sep 2014 19:11:35 +0000
From: Marcel de Rooy <M.de.Rooy@rijksmuseum.nl>
To: Koha Devel <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] Koha and DBIC
Message-ID:
        <809BE39CD64BFD4EB9036172EBCCFA31423D34C8@S-MAIL-1B.rijksmuseum.intra>
Content-Type: text/plain; charset="iso-8859-1"

> I am troubled by the idea that we should wrap all our dbic classes in yet more classes. Every example I've seen of this has more code by a factor of almost 10. I don't know if Koha is so complex that it requires a repository pattern.
I think that it would require rewriting Koha. This changeover might just be too complex for us.

> How much more difficult will this be for developers, and how much more overhead will it require if we wrap our objects in more objects? We'd have to fetch the Row objects, wrap them in KohaRow objects, wrap those in a KohaRowSet, and return them. Certainly, but far more complicated.
I would say: Leave all storage related actions in Koha::Schema. KohaRow does not make sense to me.
Furthermore, define the objects that actually have 'real' business logic and put that in some Koha::Object.

Marcel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20140915/425d46d2/attachment-0001.html>

------------------------------

Message: 2
Date: Tue, 16 Sep 2014 11:26:54 +1200
From: Robin Sheat <robin@catalyst.net.nz>
To: koha-devel@lists.koha-community.org
Subject: Re: [Koha-devel] problem to perform a simple query
Message-ID: <1410823613.20051.38.camel@zarathud.wgtn.cat-it.co.nz>
Content-Type: text/plain; charset="utf-8"

Adnier Rosell? Carrazana schreef op ma 15-09-2014 om 08:54 [-0400]:
> I need to know if the search system koha have any character limitation
> to perform a simple query (without using zebra)

What do you mean "without using zebra"? There shouldn't be an option to
not use zebra any more.

--
Robin Sheat
Catalyst IT Ltd.
? +64 4 803 2204
GPG: 5FA7 4B49 1E4D CAA4 4C38  8505 77F5 B724 F871 3BDF
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: This is a digitally signed message part
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20140916/92e8546d/attachment-0001.pgp>

------------------------------

Message: 3
Date: Tue, 16 Sep 2014 08:15:55 +0000 (UTC)
From: Partha Mukhopadhyay <psm_vu@india.com>
To: koha-devel@lists.koha-community.org
Subject: [Koha-devel] VIAF and Koha 3.16.x
Message-ID: <1466111020.197668.1410855355242.JavaMail.tomcat@be02>
Content-Type: text/plain; charset="us-ascii"

An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20140916/c053264e/attachment-0001.html>

------------------------------

_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

End of Koha-devel Digest, Vol 106, Issue 19
*******************************************
Concurso "Mi selfie por los 5". Detalles en http://justiciaparaloscinco.wordpress.com


------------------------------

Message: 2
Date: Tue, 16 Sep 2014 10:55:57 -0400
From: Francois Charbonnier <francois.charbonnier@inlibro.com>
To: "dev >> koha-devel" <koha-devel@lists.koha-community.org>
Subject: [Koha-devel] Dom indexing operational with a fresh install?
Message-ID: <54184F7D.209@inlibro.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Hello,

Yesterday, I bumped into an indexing bug. The 008 language code is not
indexed. I can't find the records using this value. I checked on
bugzilla and found this old bug :
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7586. This bug
changed "ln:n" by "ln:w" in record.abs .

It works with grs-1 indexing. On Katrin advice, I checked if the
installation is using dom or grs-1 indexing.

I'm on 3.14.07. So it should use dom. koha-conf.xml says "dom" but
zebra-biblios.cfg seems to say "grs"...

So, I checked "zebra-biblios.cfg" on master and the default values are :

  *   iso2709.recordType:grs.marcxml.record
  *   marcxml.recordType:grs.sgml
  *   recordType:grs.xml

Shouldn't we have a reference to dom for these parameters?

I also checked biblio-zebra-indexdefs.xsl and biblio-koha-indexdefs.xml
and the language index is "ln:n".
I tried to change it by "ln:w", restarted zebra server, reindexed but it
didn't work.

I followed the wiki instruction
(http://wiki.koha-community.org/wiki/Switching_to_dom_indexing) to
change the "zebra-biblios.cfg" values as well but didn't work either.

Any ideas?

Thanks!
--
Fran?ois Charbonnier,
Bibl. prof. / Chef de produits

T?l.  : (888) 604-2627
francois.charbonnier@inLibro.com <mailto:francois.charbonnier@inLibro.com>

inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20140916/e431fe2b/attachment-0001.html>

------------------------------

Message: 3
Date: Tue, 16 Sep 2014 19:29:13 -0300
From: Tomas Cohen Arazi <tomascohen@gmail.com>
To: Francois Charbonnier <francois.charbonnier@inlibro.com>
Cc: "dev >> koha-devel" <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] Dom indexing operational with a fresh
        install?
Message-ID:
        <CABZfb=UMNgxbL88_LUyju=F8t39iBeAbxBbAPi5CZjfhv=XoEQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

On Tue, Sep 16, 2014 at 11:55 AM, Francois Charbonnier <
francois.charbonnier@inlibro.com> wrote:
>
> Hello,
>
> Yesterday, I bumped into an indexing bug. The 008 language code is not
indexed. I can't find the records using this value. I checked on bugzilla
and found this old bug :
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7586. This bug
changed "ln:n" by "ln:w" in record.abs .
>
> It works with grs-1 indexing. On Katrin advice, I checked if the
installation is using dom or grs-1 indexing.
>
> I'm on 3.14.07. So it should use dom. koha-conf.xml says "dom" but
zebra-biblios.cfg seems to say "grs"...

Your koha-conf.xml file should be pointing to zebra-biblios-dom.cfg in
the id="biblioserver" section.

Best regards
To+

--
Tom?s Cohen Arazi
Prosecretar?a de Inform?tica
Universidad Nacional de C?rdoba
? +54 351 5353750 ext 13168
GPG: B76C 6E7C 2D80 551A C765  E225 0A27 2EA1 B2F3 C15F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20140916/a2922d99/attachment-0001.html>

------------------------------

Message: 4
Date: Tue, 16 Sep 2014 07:16:18 -0400
From: Kyle Hall <kyle.m.hall@gmail.com>
To: Marcel de Rooy <M.de.Rooy@rijksmuseum.nl>
Cc: Koha Devel <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] Koha and DBIC
Message-ID:
        <CACpVHfwyGN7ZwOASMTMgFuRagBCotNYvyuK-jY9e7e+-oEsxug@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Yes. I'm imagining something along the lines of Koha::Object, and
Koha::Object::Set which would have all the boilerplate we need for general
use ( get, set, find, search, etc ). Then all our table-tied objects would
inherit from Koha::Object and a set of those objects would inherit from
Koha::Object::Set. Both of those classes can be DBIC-aware internally.

Internally Koha::Object would have a DBIC Result as a property, which can
be used independently from the database ( which would be good for unit
testing ). Each Koha::Object::Set would normally keep only a ResultSet
internally and work on that until asked to return a Koha::Object, at which
point it would wrap each Result in a Koha::Object and store them
internally, or return an array of them depending on what type of return
value the method was called with.

I would be willing to write up Koha::Object and Koha::Object::Set if this
is what Robin, Tomas et. al. are looking for.

In this way we have DBIC totally encapsulated so the code using
Koha::Object and Koha::Object::Set's is totally DBIC unaware but internally
is DBIC aware.

In addition, if we have these two classes to inherit from, it will reduce
the amount of code we must write, and make it much easier for new
developers. One we have Object and Object::Set written, we don't have to
rewrite our CRUD boilerplate for each and every new class we add.

What do you think?

Kyle

http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federated Library System ( http://www.ccfls.org )
Mill Run Technology Solutions ( http://millruntech.com )

On Mon, Sep 15, 2014 at 3:11 PM, Marcel de Rooy <M.de.Rooy@rijksmuseum.nl>
wrote:

>  > I am troubled by the idea that we should wrap all our dbic classes in
> yet more classes. Every example I've seen of this has more code by a factor
> of almost 10. I don't know if Koha is so complex that it requires a
> repository pattern.
>   I think that it would require rewriting Koha. This changeover might
> just be too complex for us.
>
>  > How much more difficult will this be for developers, and how much more
> overhead will it require if we wrap our objects in more objects? We'd have
> to fetch the Row objects, wrap them in KohaRow objects, wrap those in a
> KohaRowSet, and return them. Certainly, but far more complicated.
> I would say: Leave all storage related actions in Koha::Schema. KohaRow
> does not make sense to me.
> Furthermore, define the objects that actually have 'real' business logic
> and put that in some Koha::Object.
>
> Marcel
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20140916/27e01607/attachment.html>

------------------------------

_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

End of Koha-devel Digest, Vol 106, Issue 20
*******************************************



--
Dr.J.Vijaya Kumar
Engineering College Library
Andhra University
Visakhapatnam- 530 003
Andhra Pradesh
India.
E-Mail Address:
kumarjammala@gmail.com
kumarjammala@rediffmail.com
jammalamadakavijayakumar@yahoo.com