Re: [Koha] Koha Digest, Vol 44, Issue 55

23 Jun 2009


      On Tue, Jun 23, 2009 at 5:30 AM, <koha-request@lists.katipo.co.nz> wrote:
...
Send Koha mailing list submissions to
       koha@lists.katipo.co.nz
To subscribe or unsubscribe via the World Wide Web, visit
       http://lists.katipo.co.nz/mailman/listinfo/koha
or, via email, send a message with subject or body 'help' to
       koha-request@lists.katipo.co.nz
You can reach the person managing the list at
       koha-owner@lists.katipo.co.nz
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Koha digest..."
Today's Topics:
1. Re: libxml problem (Andy Giesler)
  2. MARC fields: server-independent URLs (S?bastien Hinderer)
  3. Re: MARC fields: server-independent URLs (tajoli)
  4. Re: [Koha-devel] Multiple installs of Koha on same server
     (Michael Hafen)
  5. Re: new patron page customization, default library loation
     (Owen Leonard)
  6. Re: MARC fields: server-independent URLs (Doug Dearden)
----------------------------------------------------------------------
Message: 1
Date: Mon, 22 Jun 2009 11:45:11 -0700 (PDT)
From: Andy Giesler <news@blazingmoon.org>
Subject: Re: [Koha] libxml problem
To: koha@lists.katipo.co.nz
Message-ID: <24153080.post@talk.nabble.com>
Content-Type: text/plain; charset=us-ascii
hi,
install perl-XML-SAX

perl-XML-LibXML
[root@localhost ~]# updatedb
[root@localhost ~]# locate ParserDetails.ini
/usr/lib/perl5/site_perl/5.8.8/XML/SAX/ParserDetails.ini
[root@localhost ~]# cd /usr/lib/perl5/site_perl/5.8.8/XML/SAX/
[root@localhost SAX]# vi ParserDetails.ini
[root@localhost SAX]# ..
bash: ..: command not found
[root@localhost SAX]# cd
[root@localhost ~]# cd Desktop/koha\ installation/Koha
[root@localhost Koha]# cd misc/
[root@localhost misc]# ./sax_parser_print.pl
Koha wants something like:
    XML::LibXML::SAX::Parser=HASH(0x81fe220)
You have:
    XML::LibXML::SAX::Parser=HASH(0x99400a0)
Looks good.
[root@localhost misc]# cd..

basavaraj
dpl
...
Hi,
This page might help you. Follow the instructions in the section titled
"Verify SAX Parser".
http://www.blazingmoon.org/guides/k3-on-u810-7.html
...Andy
MATINE LOUIS wrote:
...
I am using Ubuntu-9.04, While running
root@martin-desktop: /home/martin/library/koha-3.00.02#
misc/sax_parser_print.pl
Koha wants something like:
    XML::LibXML::SAX::Parser=HASH(0x81fe220)
You have:
    XML::LibXML::SAX=HASH(0x93a0548)
Looks bad, check INSTALL.* documentation.
--
View this message in context:
http://www.nabble.com/libxml-problem-tp24133587p24153080.html
Sent from the Koha - Discuss mailing list archive at Nabble.com.
------------------------------
Message: 2
Date: Mon, 22 Jun 2009 21:01:56 +0200
From: S?bastien Hinderer <Sebastien.Hinderer@snv.jussieu.fr>
Subject: [Koha] MARC fields: server-independent URLs
To: koha@lists.katipo.co.nz
Message-ID: <20090622190156.GA31810@localhost>
Content-Type: text/plain; charset=iso-8859-1
Dear all,
Is it possible with Koha to store only the book-specific part of an URL
in the record for that book ?
To explain the queston in more details, suppose all the books are files
that can be downloaded from
http://someserver.org/download.pl?book=XXXX&format=YYY&volume=ZZZZ
Obviously one does not want to repeat the whole URL in all records,
since one would have to change all of them, should the server change.
A similar question concerns file formats.
Indeed, for the computer it may be easier to store in 856$q a MIME media
type or even a number referring to an SQL table that describes each
format. However one would prefer to display a format descrition.
Does koha permit such things ? If it does, how should such
functionalities be implemented ?
Many thanks in advance for your helo !
Best wishes,
S?bastien.
------------------------------
Message: 3
Date: Mon, 22 Jun 2009 21:27:43 +0200
From: tajoli <tajoli@cilea.it>
Subject: Re: [Koha] MARC fields: server-independent URLs
To: S?bastien Hinderer <Sebastien.Hinderer@snv.jussieu.fr>
Cc: koha@lists.katipo.co.nz
Message-ID: <d65bea5cb3c7347720be47efc281ea07@cilea.it>
Content-Type: text/plain; charset="UTF-8"
Dear Sebastien
...
Is it possible with Koha to store only the book-specific part of an URL
in the record for that book ?
your best option is to manipolate the detail templates and cgi.
(opac-detail.pl and opac-detail.tmpl)
In cataloguing insert only the information to know format and book.
With opac-detail.pl and opac-detail.tmpl you can create your display.
Koha uses templates for this specific task:
to have standard data but personalised visualisation.
Bye
Zeno Tajoli
------------------------------
Message: 4
Date: Mon, 22 Jun 2009 11:22:41 -0600
From: Michael Hafen <mdhafen@tech.washk12.org>
Subject: Re: [Koha] [Koha-devel] Multiple installs of Koha on same
       server
To: "Chadwick, John, DCA" <john.chadwick@state.nm.us>
Cc: koha@lists.katipo.co.nz, koha-devel@lists.koha.org
Message-ID: <1245691361.6891.0.camel@koha-dev>
Content-Type: text/plain
I have this sort of setup myself.  I have one install of Zebra with two
seperate instances of zebra running.  Seems to work pretty good.
On Mon, 2009-06-22 at 11:10 -0600, Chadwick, John, DCA wrote:
...
I need a bit of a sanity check here before I get going and find myself
in too much trouble.
I would like to have 2 installations of koha on the same server. This
would require two koha databases and two koha web directories. I would
be doing some virtual hosting to accomplish this. Do I need two
installations of zebra?
John
+----------------------------------------------------------------------------+
...
John Chadwick, Ed.D. Information Technology Manager
New Mexico State Library
1209 Camino Carlos Rey
Santa Fe, NM 87507
Phone: 505-476-9740  Cell: 505-629-8116 Fax: 505-476-9761
john.chadwick@state.nm.us
http://www.nmstatelibrary.org
Confidentiality Notice: This e-mail, including all attachments is for
the sole use of the intended recipient(s) and may contain confidential
and privileged information. Any unauthorized review, use, disclosure
or distribution is prohibited unless specifically provided under the
New Mexico Inspection of Public Records Act. If you are not the
intended recipient, please contact the sender and destroy all copies
of this message. -- This email has been scanned by the Sybari -
Antigen Email System.
Confidentiality Notice: This e-mail,including all attachments is for
the sole use of the intended recipient(s) and may contain confidential
and privileged information. Any unauthorized review,use,disclosure or
distribution is prohibited unless specifically provided under the New
Mexico Inspection of Public Records Act. If you are not the intended
recipient, please contact the sender and destroy all copies of this
message. -- This email has been scanned by the MessageLabs Email
Security System.
_______________________________________________
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://development.washk12.org/gitweb/
or
git://development.washk12.org/koha
------------------------------
Message: 5
Date: Mon, 22 Jun 2009 16:06:03 -0400
From: Owen Leonard <oleonard@myacpl.org>
Subject: Re: [Koha] new patron page customization, default library
       loation
To: Chris Albrecht <chrisalbrecht@gmail.com>
Cc: koha@lists.katipo.co.nz
Message-ID:
       <c0aa2140906221306m15e72e49ic446fe8ce5e4f4a4@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
...
Can anyone tell me how I can disable/hide data entry fields on the new
patron page?
We do a little bit of this with javascript. In System Preferences look
for the intranetuserjs system pref. Then use a little jquery to hide
lines based on the ID of the input field. Paste the following into
intranetuserjs:
$(document).ready(function(){
       $("#entryform #initials").parent().remove();
});
That bit of code looks for an element with ID "entryform," (the patron
entry form) and looks for an element with ID "initials" inside the
form. Then it removes that element's "parent," the list item
containing that form field.
You'll have to view the source of the page to find out what the input
field's ID is. For example:
<input type="text" value="" size="20" name="othernames" id="othernames"/>
If you used "othernames" in the code above it would hide the line
labeled "Other name." Note that you can add as many lines as you want:
$(document).ready(function(){
       $("#entryform #initials").parent().remove();
       $("#entryform #othernames").parent().remove();
       $("#entryform #altcontactaddress1").parent().remove();
       $("#entryform #altcontactaddress2").parent().remove();
       $("#entryform #altcontactaddress3").parent().remove();
       $("#entryform #altcontactzipcode").parent().remove();
});
-- Owen
--
Web Developer
Athens County Public Libraries
http://www.myacpl.org
------------------------------
Message: 6
Date: Mon, 22 Jun 2009 16:13:13 -0600
From: "Doug Dearden" <dearden@sarsf.org>
Subject: Re: [Koha] MARC fields: server-independent URLs
To: <koha@lists.katipo.co.nz>, " S?bastien Hinderer "
       <Sebastien.Hinderer@snv.jussieu.fr>
Message-ID: <sa3fadb5.087@mail.sarsf.org>
Content-Type: text/plain; charset=ISO-8859-1
Sebastien,
Check this post - it helped me set up my Apache server so I could point to
files located in a particular place on the server now, but provide for
moving them in the future.
Best,
Doug
http://thread.gmane.org/gmane.comp.misc.koha/11760/focus=11801
...
...
...
S?bastien Hinderer <Sebastien.Hinderer@snv.jussieu.fr> 6/22/2009 1:01
PM >>>
Dear all,
Is it possible with Koha to store only the book-specific part of an URL
in the record for that book ?
To explain the queston in more details, suppose all the books are files
that can be downloaded from
http://someserver.org/download.pl?book=XXXX&format=YYY&volume=ZZZZ
Obviously one does not want to repeat the whole URL in all records,
since one would have to change all of them, should the server change.
A similar question concerns file formats.
Indeed, for the computer it may be easier to store in 856$q a MIME media
type or even a number referring to an SQL table that describes each
format. However one would prefer to display a format descrition.
Does koha permit such things ? If it does, how should such
functionalities be implemented ?
Many thanks in advance for your helo !
Best wishes,
S?bastien.
_______________________________________________
Koha mailing list
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha
------------------------------
_______________________________________________
Koha mailing list
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha
End of Koha Digest, Vol 44, Issue 55
************************************

Basu Talikoti

tags

participants (1)