Re: [Koha] Regarding the KOHA old version migration issue

[Rejeesh K.Nair]

Hi Owen,

Thanks for your mail.

Please see the below link.

https://ibb.co/K7ddjz0

Thanks & Regards,
*Rejeesh K.Nair* | Senior Software Engineer
Web Designing and Development | Web Hosting
Email:rejeeshkn...@gmail.com |
rejeeshkn...@yahoo.com
Web: www.rejeeshknair.com |Skype:rejeeshkalliyilnair
Mob: +91 (0) 9495316906
Find Me : Facebook |LinkedIn
|Twitter
|Google+


Disclaimer : This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify us.
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and
delete this e-mail from your system. If you are not the intended recipient
you are notified that disclosing, copying, distributing or taking any
action in reliance on the contents of this information is strictly
prohibited.
*Please consider the environment before printing this email.*


On Fri, May 3, 2019 at 5:11 PM Owen Leonard  wrote:

> > Please see the below image for your reference.
>
> This mailing list doesn't accept attachments, so you'll need to post
> the image somewhere else and provide a link.
>
>   -- Owen
>
> --
> Web Developer
> Athens County Public Libraries
> https://www.myacpl.org
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] new item for ebook in Acquisitions

[Giuseppe Angilella]

Hi,

I usually link "items" for an ebook record to my (only) Kindle reader, 
also present as a record, using the 773 MARC field for the host item entry 
in the record for the ebook, and a corresponding 774 MARC field in the 
constituent unit entry in the record for the kindle.


This automatically generates an "item" in the ebook record, which actually 
points so the (only available) Kindle reader.


But now, if I want to enter a new ebook in the Acquisition module, this 
is actually displayed as a "new" and separate item in the ebook record 
(not pointing to the Kindle reader's record).


How can I solve this inconsistency?

(I wouldn't mind acting directing on the database via mysql commands, as 
this issue happens quite rarely.)


Many thanks and best regards,

Giuseppe.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Restricted Page -- need advice/help

[Andy Boze]

Hi, Eric.

Thanks, I appreciate your reply. I'll have to investigate this. We're 
hosting Koha ourselves on AWS, so I wonder whether AWS could somehow be 
obscuring the user's IP address. Well, that'll be something for next week.


Andy

On 5/3/2019 8:08 PM, Eric Phetteplace wrote:

Hi Andy,

We had looked into this feature for some content we wanted to host and
provide access to on campus, but sadly I found the same issue to be the
case: users have to authenticate to view the Restricted Page and it isn't
truly able to filter by IP address. Our Koha instance is hosted by ByWater
and they identified their proxy server as the root of the problem. Here's a
rather long message from Larry Baerveldt about it:

"I spent some time last night after hours, looking in this. The main issue
is
the Restricted Page functionality in Koha depends on the seeing the user's
IP
address, so it can make a decision whether to load the page immediately, or
present them with the login prompt. However, for sites that are behind a
proxy,
the Koha server does not see the user's IP, it sees the IP of the proxy
server.

When a server is behind proxy, the original user's IP is preserved in the
HTTP
headers, as X-Forwarded-For. Unfortunately there is not yet support in Koha
to
look at the X-Forwarded-For header (although there now a Koha bug open on
this).

Until Koha supports the use of X-Forwarded-For, then we have limited
solutions.

Solution 1) Implement the IP restriction in proxy server. This works, but
has
the side effect that if the user is NOT in one of the allowed ranges, then
they
are presented with a proxy server error: "There are no servers to handle
this
request."

Solution 2) Implement an Apache solution that restricts that page to view
only
from a set of X-Forwarded-For addresses. This should also work, but will
have
the side effect that if the user is NOT in one of the allowed ranges, they
will
get an Apache error that says that page is forbidden (Error 403).

In either case, there does not appear to be way to maintain BOTH the
functionality of immediate access for users in a specific IP range AND
allowing
users to login to view the page if they are not in that IP range.

There is still the option of Solution 3) which is to implement the page but
leave out the pass through for IPs, and just require everyone to login to
view
it.

I'm sorry I don't have a better solution to offer, but until Koha supports
X-Forwarded-For, these seem to be our only choices."

If I understand correctly, if your instance is *not* behind a proxy then
you shouldn't be encountering this problem, though, so I can't explain what
the issue is in that case. We ultimately went with option #3 forcing
everyone, even on-campus users, to authenticate to see our restricted
content since none of the alternatives presented were viable.

Best,

ERIC PHETTEPLACE Systems Librarian (he/him)

ephettepl...@cca.edu | o 510.594.3660

5212 Broadway | Oakland, CA | 94618

:(){ :|: & };:


On Fri, May 3, 2019 at 4:12 PM Andy Boze  wrote:


According to the 18.11 manual page at <

https://koha-community.org/manual/18.11/en/html/systempreferences.html#restricted-page
  >, a page can be configured so that it is accessible only to users
accessing it from specific IP addresses/ranges. The information isn't
entirely clear, but I take it to mean that the user need not be
authenticated to view the page as long as their machine is at a
designated IP address. It's also unclear whether authenticated users
should be able to access the restricted page unless they are at a
designated IP address. I'm taking it to mean that the restricted page
should be accessible to any authenticated user or to unauthenticated
users at a designated IP address

In testing this feature, I can access the restricted page when I am
authenticated. But I cannot access the restricted page if I am at a
designated IP address -- I am prompted to log in, and only then can I
access the page.

I'm wondering whether I'm not entering the IP address correctly. The
manual page isn't entirely clear on that from the examples it gives. I'm
assuming that I can enter a complete IP address (four octets) or several
IP addresses separated by commas. If I want to enter a range, it looks
like I just need to enter the beginning two or three octets, and maybe
end with a dot (.) followed by a caret (^) (or is the caret a typo and
meant to be a quotation mark?). Anyway, I've tried entering a complete
IP address and a range, but so far nothing has worked.

Have I missed something, or have I run into a bug?

The original feature request for this is at <
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13485 > in
case that's useful.

Thanks for any assistance.

--
Andy Boze, Associate Librarian
University of Notre Dame
271H Hesburgh Library
(574) 631-8708
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Restricted Page -- need advice/help

[Eric Phetteplace]

Hi Andy,

We had looked into this feature for some content we wanted to host and
provide access to on campus, but sadly I found the same issue to be the
case: users have to authenticate to view the Restricted Page and it isn't
truly able to filter by IP address. Our Koha instance is hosted by ByWater
and they identified their proxy server as the root of the problem. Here's a
rather long message from Larry Baerveldt about it:

"I spent some time last night after hours, looking in this. The main issue
is
the Restricted Page functionality in Koha depends on the seeing the user's
IP
address, so it can make a decision whether to load the page immediately, or
present them with the login prompt. However, for sites that are behind a
proxy,
the Koha server does not see the user's IP, it sees the IP of the proxy
server.

When a server is behind proxy, the original user's IP is preserved in the
HTTP
headers, as X-Forwarded-For. Unfortunately there is not yet support in Koha
to
look at the X-Forwarded-For header (although there now a Koha bug open on
this).

Until Koha supports the use of X-Forwarded-For, then we have limited
solutions.

Solution 1) Implement the IP restriction in proxy server. This works, but
has
the side effect that if the user is NOT in one of the allowed ranges, then
they
are presented with a proxy server error: "There are no servers to handle
this
request."

Solution 2) Implement an Apache solution that restricts that page to view
only
from a set of X-Forwarded-For addresses. This should also work, but will
have
the side effect that if the user is NOT in one of the allowed ranges, they
will
get an Apache error that says that page is forbidden (Error 403).

In either case, there does not appear to be way to maintain BOTH the
functionality of immediate access for users in a specific IP range AND
allowing
users to login to view the page if they are not in that IP range.

There is still the option of Solution 3) which is to implement the page but
leave out the pass through for IPs, and just require everyone to login to
view
it.

I'm sorry I don't have a better solution to offer, but until Koha supports
X-Forwarded-For, these seem to be our only choices."

If I understand correctly, if your instance is *not* behind a proxy then
you shouldn't be encountering this problem, though, so I can't explain what
the issue is in that case. We ultimately went with option #3 forcing
everyone, even on-campus users, to authenticate to see our restricted
content since none of the alternatives presented were viable.

Best,

ERIC PHETTEPLACE Systems Librarian (he/him)

ephettepl...@cca.edu | o 510.594.3660

5212 Broadway | Oakland, CA | 94618

:(){ :|: & };:


On Fri, May 3, 2019 at 4:12 PM Andy Boze  wrote:

> According to the 18.11 manual page at <
>
> https://koha-community.org/manual/18.11/en/html/systempreferences.html#restricted-page
>  >, a page can be configured so that it is accessible only to users
> accessing it from specific IP addresses/ranges. The information isn't
> entirely clear, but I take it to mean that the user need not be
> authenticated to view the page as long as their machine is at a
> designated IP address. It's also unclear whether authenticated users
> should be able to access the restricted page unless they are at a
> designated IP address. I'm taking it to mean that the restricted page
> should be accessible to any authenticated user or to unauthenticated
> users at a designated IP address
>
> In testing this feature, I can access the restricted page when I am
> authenticated. But I cannot access the restricted page if I am at a
> designated IP address -- I am prompted to log in, and only then can I
> access the page.
>
> I'm wondering whether I'm not entering the IP address correctly. The
> manual page isn't entirely clear on that from the examples it gives. I'm
> assuming that I can enter a complete IP address (four octets) or several
> IP addresses separated by commas. If I want to enter a range, it looks
> like I just need to enter the beginning two or three octets, and maybe
> end with a dot (.) followed by a caret (^) (or is the caret a typo and
> meant to be a quotation mark?). Anyway, I've tried entering a complete
> IP address and a range, but so far nothing has worked.
>
> Have I missed something, or have I run into a bug?
>
> The original feature request for this is at <
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13485 > in
> case that's useful.
>
> Thanks for any assistance.
>
> --
> Andy Boze, Associate Librarian
> University of Notre Dame
> 271H Hesburgh Library
> (574) 631-8708
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Restricted Page -- need advice/help

[Andy Boze]

According to the 18.11 manual page at < 
https://koha-community.org/manual/18.11/en/html/systempreferences.html#restricted-page 
>, a page can be configured so that it is accessible only to users 
accessing it from specific IP addresses/ranges. The information isn't 
entirely clear, but I take it to mean that the user need not be 
authenticated to view the page as long as their machine is at a 
designated IP address. It's also unclear whether authenticated users 
should be able to access the restricted page unless they are at a 
designated IP address. I'm taking it to mean that the restricted page 
should be accessible to any authenticated user or to unauthenticated 
users at a designated IP address


In testing this feature, I can access the restricted page when I am 
authenticated. But I cannot access the restricted page if I am at a 
designated IP address -- I am prompted to log in, and only then can I 
access the page.


I'm wondering whether I'm not entering the IP address correctly. The 
manual page isn't entirely clear on that from the examples it gives. I'm 
assuming that I can enter a complete IP address (four octets) or several 
IP addresses separated by commas. If I want to enter a range, it looks 
like I just need to enter the beginning two or three octets, and maybe 
end with a dot (.) followed by a caret (^) (or is the caret a typo and 
meant to be a quotation mark?). Anyway, I've tried entering a complete 
IP address and a range, but so far nothing has worked.


Have I missed something, or have I run into a bug?

The original feature request for this is at < 
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13485 > in 
case that's useful.


Thanks for any assistance.

--
Andy Boze, Associate Librarian
University of Notre Dame
271H Hesburgh Library
(574) 631-8708
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] marging same title and ISBN record -SQL query/other options

[Martha Fuerst]

Hi, Yatheesh -

Check out the duplicate reports in the Koha SQL Report Library. 
https://wiki.koha-community.org/wiki/SQL_Reports_Library#Duplicates 


Best,

Marti Fuerst
Systems Librarian and Manager of Technical Services
Huntsville-Madison County Public Library
915 Monroe St, Huntsville, AL 35801
http://hmcpl.org/ — mfue...@hmcpl.org

> On May 3, 2019, at 9:13 AM, Yatheesh lis  wrote:
> 
> Dear all
> 
> Kindly help how to identify duplicate records.  SQl query option to create
> report
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] marging same title and ISBN record -SQL query/other options

[Yatheesh lis]

Dear all

Kindly help how to identify duplicate records.  SQl query option to create
report
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Regarding the KOHA old version migration issue

[Owen Leonard]

> Please see the below image for your reference.

This mailing list doesn't accept attachments, so you'll need to post
the image somewhere else and provide a link.

  -- Owen

-- 
Web Developer
Athens County Public Libraries
https://www.myacpl.org
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Regarding the KOHA old version migration issue

[Rejeesh K.Nair]

Hi All,

We had to migrated our KOHA version 16.05 from one server to another.

For this, we have installed latest version of KOHA (18.05) in the new
server and replaced the /usr/share/koha folder & database from old server
to new server.

In new server all modules are working fine except the search. All the
search modules din't work and on diagnosis we found that indexing is
replaced.

For resolving the issue, we have done changes as per the below link to
switch the indexing as dom.

https://wiki.koha-community.org/wiki/Switching_to_dom_indexing

But it will shows an error while restarting the zebra indexing.

Can anyone help me urgently on this issue?

Please see the below image for your reference.

Thanks & Regards,
*Rejeesh K.Nair* | Senior Software Engineer
Web Designing and Development | Web Hosting
Email:rejeeshkn...@gmail.com |
rejeeshkn...@yahoo.com
Web: www.rejeeshknair.com |Skype:rejeeshkalliyilnair
Mob: +91 (0) 9495316906
Find Me : Facebook |LinkedIn
|Twitter
|Google+


Disclaimer : This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify us.
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and
delete this e-mail from your system. If you are not the intended recipient
you are notified that disclosing, copying, distributing or taking any
action in reliance on the contents of this information is strictly
prohibited.
*Please consider the environment before printing this email.*
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha