Re: [Koha] Catalogue - SQL Report Help

[SATISH]

Hi,

I would like to have report for the entire library collections as indicated
below:
--
Biblio| Biblio  Record (title) | Author | edition | publisher | ISBN
| Holdings ( no. of copies)
Number
count
--

example:

1  Brief history of timeHawkings.2nd ed.oxford(paper
back)10
2  Brief history of timeHawkings3rd ed.oxford  (paper
back)5
3  Brief history of timeHawkings2nd ed.Oxford  (hard
bound)  2
4  Complete reference- C++
  50
5  Basic electrical engineering...
   30

--

For example, One record is having 10 items, and when I tried to use guided
reports wizard, it fetches and display, 10 times the same records. I wanted
to get only one title on behalf of 10 items. I meant, non-repetative
records ( titles) from the entire library collections. (and exceptions for
change in edition, ISBN, different title).


And secondly,
the same report as per the collection code, which means,
list of unique records in each collection (isbn, change in edition, etc are
exceptions).

Thank you in advance.

Satish MV
Librarian
Govt. Engineering College, Hassan.
Karnataka.
INDIA.
+91-9449765737




On Mon, Dec 8, 2014 at 11:22 PM, Elaine Bradtke  wrote:

> More information may help.
>
> "all unique titles(biblio records)"
> Unique how? different ISBN?  (do they all have ISBN?) Different title?
> Same title different edition?  Only one item record?
>
> Exactly what information would you like to display in the report?
> List of biblio numbers?
> Sorted by collection code?
> or Filtered to show only items with a specific collection code?
>
> It may take a few attempts to make your request clear. I am not an expert
> report writer, but once you question is better understood, we may be able
> to help.
>
>
> On Fri, Dec 5, 2014 at 6:20 AM, SATISH  wrote:
>
>> Hi,
>>
>> Unfortunately, I have not received any help for generating a report on
>> following subject and, re-described my problem.
>>
>> I am looking for a report which has list of all unique titles(biblio
>> records) in a home library AND also by collection code.
>> When I tried for nearest relevant SQL examples given in wiki,
>> it gives me, whole list of items along with biblios records that is not
>> useful and I wanted to have information only on unique records (titles).
>>
>> Please advice.
>>
>> with thanks.
>> Satish MV
>> Librarian
>> Govt. Engineering College, Hassan.
>> Karnataka.
>> INDIA.
>>
>> On Tue, Nov 25, 2014 at 4:58 PM, SATISH  wrote:
>>
>> > Koha 3.16.00.000 installed via packages method, on ubuntu desktop.
>> >
>> > On Tue, Nov 25, 2014 at 4:22 PM, vikram zadgaonkar <
>> > vikramczadgaon...@gmail.com> wrote:
>> >
>> >> Ok. Let me check. I will mail you SQL query.
>> >> Which koha version you are using?
>> >>
>> >> Vikram Zadgaonkar
>> >>
>> >> On Tue, Nov 25, 2014 at 4:20 PM, SATISH  wrote:
>> >>
>> >>> The same is not available over there.
>> >>> Many examples in the website, fetches for whole items in the library.
>> >>> I need to have report on List of Unique titles available in the
>> library
>> >>> ( i.e., Records) and Total Number of books (i.e.,Items).
>> >>> report should include list of {title,author,publisher,edition, price}
>> >>> not just counts.
>> >>>
>> >>>
>> >>> On Tue, Nov 25, 2014 at 1:40 PM, vikram zadgaonkar <
>> >>> vikramczadgaon...@gmail.com> wrote:
>> >>>
>>  Hi,
>>  You can try following link
>>  http://wiki.koha-community.org/wiki/SQL_Reports_Library
>> 
>>  Vikram Zadgaonkar
>> 
>>  On Tue, Nov 25, 2014 at 1:33 PM, satishamv 
>>  wrote:
>> 
>> > Dear Friends,
>> > I am looking for a report which has list of all unique titles(biblio
>> > records) in a home library AND also by collection code.
>> > In my case, new record is created for - change in edition or change
>> in
>> > item
>> > type.
>> >
>> >
>> >
>> > with thanks.
>> > Satish MV
>> > Librarian
>> > Govt. Engineering College, Hassan.
>> > Karnataka.
>> > INDIA.
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> >
>> http://koha.1045719.n5.nabble.com/Catalogue-SQL-Report-Help-tp5820185.html
>> > Sent from the Koha-general mailing list archive at Nabble.com.
>> > ___
>> > Koha mailing list  http://koha-community.org
>> > Koha@lists.katipo.co.nz
>> > http://lists.katipo.co.nz/mailman/listinfo/koha
>> >
>> 
>> 
>> >>>
>> >>>
>> >>> --
>> >>>
>> >>>
>> >>>
>> >>>
>> >>
>> >
>> >
>> > --
>> >
>> >
>> >
>> >
>

Re: [Koha] Potential XSS attack vector in opac

[Robin Sheat]

Chris Cormack schreef op wo 10-12-2014 om 12:46 [+1300]:
> I have reported the bug, and I am just uploading a couple of patches,
> (one for master/3.18 which is bootstrap) and one for 3.16 which has
> the change for bootstrap and prog

Packages for 3.18.01 have been released to the 'squeeze' repository. 

The 'oldstable' repository will get 3.16 when an update for that have
been released. Note that it currently contains 3.14.11, so this will
also be an upgrade for that (which I'd rather didn't happen, but I was
waiting for 3.16.05 anyway before updating it.)

I expect this to happen tomorrow, though I'll be conferencing then so I
can't promise exactly when it'll happen. 

-- 
Robin Sheat
Catalyst IT Ltd.
✆ +64 4 803 2204
GPG: 5FA7 4B49 1E4D CAA4 4C38  8505 77F5 B724 F871 3BDF

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

Re: [Koha] Proposal for fund raising for Koha - to discuss/vote at December General Meeting.

[BWS Johnson]

Salvete!

> 1. A fund-raising organization should not focus exclusively on
> development; Koha should also have reserve funds available for legal
> costs to protect its status, and HLT should receive some funds for
> administrative costs.
> 



I concur wholeheartedly. Some other happy purposes could be Conference 
related, scholarship related, et cetera.


> 3. While I would expect most of the funds raised to be in relatively
> small amounts, certainly large organizations frequently support
> open-source projects with large grants, and these possibilities should
> be considered.



Preach on bruddah. This will continue to be a lost opportunity as long as 
there isn't a formalised structure. Large funders are very skittish about 
donating substantial amounts to something amorphous, no matter how good the 
rationale for decentralised decision making might be.


> 5. After significant funds are raised someone should purchase Biblionix
> and open-source Apollo. Then Sirsi. :)



Why stop there? We can diversify and acquire Rydges and Godiva. 
Integration, my friend. ;)

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

[Koha] Koha 3.18.01 Security release

[Chris Cormack]

The Koha release team would like to announce the release of Koha
version 3.18.1.

This is a security release, and as such we would strongly recommend
that anyone running 3.18.0 upgrades.
There should be a release for  3.16.x shortly.

You can read the full release notes here
http://koha-community.org/koha-3-18-01-security-release/

Chris

-- 
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Potential XSS attack vector in opac

[Chris Cormack]

* Liz Rea (l...@catalyst.net.nz) wrote:
> Hi Bob,
> 
> Thanks for reporting this bug. In the future, it would be better for you
> to file your bug at the community bugzilla - the large blue link here:
> http://koha-community.org/security/
> 
> As a general reminder for everyone, please don't post your found
> vulnerabilities to the public list. Security bugs should be reported at
> the link above. Koha security bugs are restricted viewing to the
> reporter, and the people listed who are in the security group, which
> corresponds with those who need to be involved in organising an
> out-of-sequence release to deal with serious security issues.
> 
> Thanks again for reporting the issue and helping to make Koha better.
> 
Hi All

I have reported the bug, and I am just uploading a couple of patches,
(one for master/3.18 which is bootstrap) and one for 3.16 which has
the change for bootstrap and prog

Chris

-- 
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Potential XSS attack vector in opac

[Liz Rea]

Hi Bob,

Thanks for reporting this bug. In the future, it would be better for you
to file your bug at the community bugzilla - the large blue link here:
http://koha-community.org/security/

As a general reminder for everyone, please don't post your found
vulnerabilities to the public list. Security bugs should be reported at
the link above. Koha security bugs are restricted viewing to the
reporter, and the people listed who are in the security group, which
corresponds with those who need to be involved in organising an
out-of-sequence release to deal with serious security issues.

Thanks again for reporting the issue and helping to make Koha better.

Liz

On 10/12/14 11:42, Bob Ewart wrote:
> When our site was scanned for potential vulnerabilities...
>
>
> Bob Ewart
>
>
>
>
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> http://lists.katipo.co.nz/mailman/listinfo/koha

-- 
--
Liz Rea
Catalyst.Net Limited
Level 6, Catalyst House, 
150 Willis Street, Wellington.
P.O Box 11053, Manners Street, 
Wellington 6142

GPG: B149 A443 6B01 7386 C2C7 F481 B6c2 A49D 3726 38B7


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

[Koha] Potential XSS attack vector in opac

[Bob Ewart]

When our site was scanned for potential vulnerabilities, they came up 
with the following links typed into Firefox.


50.199.57.14/cgi-bin/koha/opac-search.pl?q=123&sort_by='">prompt('Happy_Holidays')&limit=123

and

50.199.57.14/cgi-bin/koha/opac-search.pl?q=ccl=su%3AGay%20men%20and%20su%3ASexual%20behavior&offset=100&sort_by=relevance_asc'">prompt('Happy_Holidays')

Both of these scripts are executed and cause a pop up

This looks similar to bug 11341 which was fixed in 3.14.  We are running 
3.18 on Xubuntu 14.04 LTS installed from the PPA.  I noticed that in the 
patch at 
http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=23313&action=diff 
there were a number of '|html %' entries which appear as '|url %' in 3.18.


Is this a regression on bug 11341?

Bob Ewart




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

Re: [Koha] Proposal for fund raising for Koha - to discuss/vote at December General Meeting.

[glaws]

I fully support this great idea. I do have the following
comments/observations:

1. A fund-raising organization should not focus exclusively on
development; Koha should also have reserve funds available for legal
costs to protect its status, and HLT should receive some funds for
administrative costs.

2. I believe there is still some merit in Koha being associated with an
organization like, as a singular example, Software in the Public Interest.

3. While I would expect most of the funds raised to be in relatively
small amounts, certainly large organizations frequently support
open-source projects with large grants, and these possibilities should
be considered.

4. Where feasible the community should try to bring in new developers.
Most current developers and support companies are already fully-engaged
in writing code; when projects are funded now typically one of the
developers are diverted from their normal daily duties to work on the
paid project. While this "cannibalism", if I may, is understandable, if
significant funds are raised in the future pulling in new programmers
should be considered.

5. After significant funds are raised someone should purchase Biblionix
and open-source Apollo. Then Sirsi. :)

Note: due to sad, unfortunate circumstances I do need to emphasize the
above are my own ideas and should not be associated with the library
where I work.

Greg

 

-- 
Greg Lawson

1912 N. Belt Highway
St. Joseph, MO 64506
---



On 12/09/2014 03:57 PM, Brendan Gallagher wrote:
> Hello All -
>
> After discussing with many of you within the Koha project for many years
> and countless times, I'd like to bring forth the idea of having a
> fund-raising organization for Koha.  It's about time the project raised
> money to help meet the needs and goals of the community.  This idea and
> concept can only be a strong option with the support and help of many of us
> in the community.  We believe that we have great organization to stand
> behind this great proposal in Horowhenua Library Trust (HLT) as a
> non-profit-organization (NPO) to help manage the funds for the Koha
> community in the most responsible way (For the good of the community).
>
> Please read below for some of the ideas and thoughts - and I would like to
> bring to this to a vote at the next General Meeting on if we should all as
> a community move forward with creating a Koha-Fund to use towards and only
> towards Koha.  These are just thoughts and ideas and we can all move
> forward and work on the details and rules and laws etc after we get a "YES
> LET'S RAISE MONEY HOWEVER WE CAN TO SPEND ON KOHA".
>
>
> http://blog.bigballofwax.co.nz/2014/10/09/kohacon-14-day-3-funding-the-koha-project/
>
>
> *Organization for Fund raising:*
>
> Currently the Koha project generates more patches for enhancements and bugs
> than the collective community has time to work on.  There is a need to
> raise funds so that more resources can be purchased to accelerate
> development.  All funds that are raised via the project are to be used for
> improvement in the project.
>
> Koha has become a large international free software and open source
> software project.  There are many projects and needs for a project this
> large.  Many of the responsibilities that are needed for the future need to
> be funded and can not rely on the volunteer hours of the many participants
> of the project.  For example, the current number of patches to be tested
> far outnumbers the amount of volunteer hours that we as a project are able
> to put towards that.  Also in the future there are many software fixes that
> need to be completed that need funding, which can not be expected to be led
> by the users of the project.  The current method of development and fixes
> of the software are led by the funding from the users, I propose that we
> fundraise from within the community and external to the community for being
> able to solve many of these large un-met needs.
>
> The fund raisin entity should be a non-profit organization so that all
> donations are not taxed and if possible the donors can have tax-deductions
> (if that is applicable for your local tax laws).  The goal of this fund
> organization is to gather many many small donations to lead to an effective
> pool of funds available to support Koha development.
>
> Some thoughts so far towards identifying the appropriate fund raising
> entity is using the Horowhenua Library Trust (HLT) (Which we now have the
> full support of and Joanne can fill us in more about that).
>
>
> *Governing board:*
>
> This new fund should be governed by a board.  That board should be made up
> of volunteers, that are interested to continue/champion fund raising
> efforts for the Koha project.  The most important aspect of any board
> member would be to introduce new avenues for pursuing donations.  Ideally
> the board would be representatives from all around the world so that board
> members could lead fund raising efforts in their loca

[Koha] Proposal for fund raising for Koha - to discuss/vote at December General Meeting.

[Brendan Gallagher]

Hello All -

After discussing with many of you within the Koha project for many years
and countless times, I'd like to bring forth the idea of having a
fund-raising organization for Koha.  It's about time the project raised
money to help meet the needs and goals of the community.  This idea and
concept can only be a strong option with the support and help of many of us
in the community.  We believe that we have great organization to stand
behind this great proposal in Horowhenua Library Trust (HLT) as a
non-profit-organization (NPO) to help manage the funds for the Koha
community in the most responsible way (For the good of the community).

Please read below for some of the ideas and thoughts - and I would like to
bring to this to a vote at the next General Meeting on if we should all as
a community move forward with creating a Koha-Fund to use towards and only
towards Koha.  These are just thoughts and ideas and we can all move
forward and work on the details and rules and laws etc after we get a "YES
LET'S RAISE MONEY HOWEVER WE CAN TO SPEND ON KOHA".


http://blog.bigballofwax.co.nz/2014/10/09/kohacon-14-day-3-funding-the-koha-project/


*Organization for Fund raising:*

Currently the Koha project generates more patches for enhancements and bugs
than the collective community has time to work on.  There is a need to
raise funds so that more resources can be purchased to accelerate
development.  All funds that are raised via the project are to be used for
improvement in the project.

Koha has become a large international free software and open source
software project.  There are many projects and needs for a project this
large.  Many of the responsibilities that are needed for the future need to
be funded and can not rely on the volunteer hours of the many participants
of the project.  For example, the current number of patches to be tested
far outnumbers the amount of volunteer hours that we as a project are able
to put towards that.  Also in the future there are many software fixes that
need to be completed that need funding, which can not be expected to be led
by the users of the project.  The current method of development and fixes
of the software are led by the funding from the users, I propose that we
fundraise from within the community and external to the community for being
able to solve many of these large un-met needs.

The fund raisin entity should be a non-profit organization so that all
donations are not taxed and if possible the donors can have tax-deductions
(if that is applicable for your local tax laws).  The goal of this fund
organization is to gather many many small donations to lead to an effective
pool of funds available to support Koha development.

Some thoughts so far towards identifying the appropriate fund raising
entity is using the Horowhenua Library Trust (HLT) (Which we now have the
full support of and Joanne can fill us in more about that).


*Governing board:*

This new fund should be governed by a board.  That board should be made up
of volunteers, that are interested to continue/champion fund raising
efforts for the Koha project.  The most important aspect of any board
member would be to introduce new avenues for pursuing donations.  Ideally
the board would be representatives from all around the world so that board
members could lead fund raising efforts in their local regions.  This board
will also be responsible with managing the funds that are donated, and will
look for recommendations from the general meetings in Koha.   The board
will also be responsible for reporting the status, funds available, and
goals of the Fund during each general meeting.


*Grants Committee:*

The Board will establish a Grants Committee, with the purpose of making
decisions about the allocation of funds to advance the work of the Koha
project.

Members of the Grants Committee may be members of the Board or other
persons with suitable qualifications and experience as determined by the
Board.  The Board will determine a Charter for the Grants Committee that
will describe the procedures to be followed to promote efficacy,
efficiency, equity and transparency in the allocation of funds.

The Board will publish at least annually the details of grants allocated
with sufficient detail to ensure transparency.


*Goals:*  (These can all be adjusted based on recommendations from Koha
Community)

First goal should be to hire a person to complete sign-offs and only
sign-offs for the community development process.

Further goals will be decided in time and as funds increase.  Board members
will decide on future improvements with recommendations from the Koha
community general meetings.

Another longer term possibility - is that the fund can sponsor some
community members for attendance at international conferences/hackfests,
students for attending local KohaCons, and sponsoring schools/universities
with leading 2 week Koha academy sessions for getting more people
interested/involved in the Koha project.

Re: [Koha] Possible bug -- 3.18 catalog search result list??

[Ajeesh Scaria]

I am also facing this same problem, Please somebody help me



--
View this message in context: 
http://koha.1045719.n5.nabble.com/Possible-bug-3-18-catalog-search-result-list-tp5821303p5821518.html
Sent from the Koha-general mailing list archive at Nabble.com.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] make test failed 3.18.0

[Michał Dudzik]

Hi,
Are all the required Perl modules are installed? Perl 5.10 is required!
Try install from packages
http://wiki.koha-community.org/wiki/Debian

Regards
Michał Dudzik




wslyhbb wrote
> Hi,
> When I run make test, two tests fail:
> t/Creators.t  3/16 ERROR in koha-conf.xml --
> missing 

>  at /srv/www/koha/blib/PERL_MODULE_DIR/C4/Creators/PDF.pm line 123.
> ERROR in koha-conf.xml -- missing 

>  at /srv/www/koha/blib/PERL_MODULE_DIR/C4/Creators/PDF.pm line 319.
> 
> #   Failed test 'testing StrWidth() returns correct point width'
> #   at t/Creators.t line 47.
> #  got: '19.344'
> # expected: '23.044921875'
> 
> #   Failed test 'testing Text() writes to the correct x-value'
> #   at t/Creators.t line 51.
> #  got: '29.344'
> # expected: '33.044921875'
> # Looks like you failed 2 tests of 16.
> t/Creators.t  Dubious, test returned 2 (wstat 512,
> 0x200)
> Failed 2/16 subtests





--
View this message in context: 
http://koha.1045719.n5.nabble.com/make-test-failed-3-18-0-tp5821460p5821493.html
Sent from the Koha-general mailing list archive at Nabble.com.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Reindexing after switching from GRS1 to DOM

[Michał Dudzik]

Hi,
It is first time indexing when you changed method from GRS1 to DOM? What
version of Koha you have?What is in the logs?
Look in koha-conf.xml everything is change to DOM. 
http://wiki.koha-community.org/wiki/Switching_to_dom_indexing

Regards
Michał Dudzik



--
View this message in context: 
http://koha.1045719.n5.nabble.com/Reindexing-after-switching-from-GRS1-to-DOM-tp5821489p5821492.html
Sent from the Koha-general mailing list archive at Nabble.com.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Installing koha on window

[Mark Tompsett]

Greetings,

I think the problem is that some people do not understand the difference 
between a desktop application and a web-based application. The key 
difference being where is the processing done, and where does the visual 
output show up.


A desktop application running under Windows, means the program needs to be 
written specifically to run on Windows, because the processing and display 
are on that specific desktop computer. Windows is doing the processing, and 
Windows is doing the displaying.


A web application is different. The processing is done elsewhere. To install 
Koha, you are actually installing the thing that does the processing, not 
what does the displaying, because any* browser on any** computer can view 
and use Koha.


* there are limitations, but not because of Koha, but rather because some 
browsers are really awful.
** there are limitations, because to access you actually have to be able to 
network the server where you installed Koha to the client's computer where 
the browser is calling from.


Just in case this was the conversation that needed to occur. :)

GPML,
Mark Tompsett 


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

Re: [Koha] Cloud-based Koha vs locally hosted Koha

[Jesse Lambertson]

Thank you mark.

We already do have a good plan for back-up. But with these other issues,
your points are valid and jive with some other conversations I am having as
we get ready to set this up (soonish).

I will have to look at Brooke's other point about carefully picking the
(external) hosting environment - one that gives me command-line access to
update everything as needed.
The idea in this thread here seems to be that hosting elsewhere means that
it will not be as easy for me to update. But I have to imagine there is
some host out there that has everything partitioned in a way so that I can
manipulate my own data at will (maybe that is still just a dream).

I will dig into that search next.

Thank you everyone.

Jesse

On Tue, Dec 9, 2014 at 1:56 PM, Mark Tompsett  wrote:

> Greetings,
>
> On 10 December 2014 7:06:37 am NZDT, BWS Johnson <
> abesottedphoe...@yahoo.com> wrote:
> [SNIP]
>
>> The only difference I can spot might actually weigh as a positive in
>> favour of cloud based service. When you have a physical server and
>> suffer a local catastrophe, such as an earthquake, fire, sinkhole, et
>> cetera, there goes your data.
>>
>
> Actually another cost consideration is the hardware costs vs. hosting
> costs. Hardware dies over time and needs to be replaced. Budgets get cut,
> and a monthly hosting cost is less likely to be axed compared to a new
> server cost ever 4-5 years. So, in some sense, I think hosting externally
> and not on your own local hardware is better.
>
> And comparing costs, you may be able to find hosting that works well for a
> cost that when amortized over 4-5 years is actually cheaper. That is,
> $20/month (let's say) * 12 months * 4 years = $960 for 4 years. This is
> comparable to some cheaper machines which perfectly suffice, but I know I
> prefer to drool over the $2500+ machines. :)
>
> Sadly, you aren't likely to be continually upgrading components. After 4
> years, a locally owned piece of hardware will have dropped from a middle
> class machine to low end machine, while the hosted environment may have
> progressed, because of hosting provider upgrades. :)
>
> And, you aren't having to do your own backups, if you hosting on the
> cloud. If you have locally hosted machine, you need to figure out how to
> back up elsewhere. A good backup plan has on-site same drive, on-site
> different drive, and off-site backups. A hosting provider tends to have
> these in place. Do you want the hassle of having that yourself? This is
> related to the point that BWS Johnson made.
>
> And what if your local machine dies? Sure you have a backup, but you
> actually have to spend the day rushing around buying a new server. With
> hosting, hardware failures like that are not your worry. No budget
> stresses, because you don't have the cash to go buy it now, and most
> service level agreements give you less than a hour downtime per year.
>
> GPML,
> Mark Tompsett
>



-- 
Jesse A Lambertson
Librarian
Sultan Qaboos Cultural Center
1100 16th St, NW
Washington, DC 20036
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Cloud-based Koha vs locally hosted Koha

[Mark Tompsett]

Greetings,

On 10 December 2014 7:06:37 am NZDT, BWS Johnson 
 wrote:

[SNIP]

The only difference I can spot might actually weigh as a positive in
favour of cloud based service. When you have a physical server and
suffer a local catastrophe, such as an earthquake, fire, sinkhole, et
cetera, there goes your data.


Actually another cost consideration is the hardware costs vs. hosting costs. 
Hardware dies over time and needs to be replaced. Budgets get cut, and a 
monthly hosting cost is less likely to be axed compared to a new server cost 
ever 4-5 years. So, in some sense, I think hosting externally and not on 
your own local hardware is better.


And comparing costs, you may be able to find hosting that works well for a 
cost that when amortized over 4-5 years is actually cheaper. That is, 
$20/month (let's say) * 12 months * 4 years = $960 for 4 years. This is 
comparable to some cheaper machines which perfectly suffice, but I know I 
prefer to drool over the $2500+ machines. :)


Sadly, you aren't likely to be continually upgrading components. After 4 
years, a locally owned piece of hardware will have dropped from a middle 
class machine to low end machine, while the hosted environment may have 
progressed, because of hosting provider upgrades. :)


And, you aren't having to do your own backups, if you hosting on the cloud. 
If you have locally hosted machine, you need to figure out how to back up 
elsewhere. A good backup plan has on-site same drive, on-site different 
drive, and off-site backups. A hosting provider tends to have these in 
place. Do you want the hassle of having that yourself? This is related to 
the point that BWS Johnson made.


And what if your local machine dies? Sure you have a backup, but you 
actually have to spend the day rushing around buying a new server. With 
hosting, hardware failures like that are not your worry. No budget stresses, 
because you don't have the cash to go buy it now, and most service level 
agreements give you less than a hour downtime per year.


GPML,
Mark Tompsett 


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

Re: [Koha] Cloud-based Koha vs locally hosted Koha

[Sudhir Gandotra]

There is absolutely no problem, as long as you have access to the hosted
machine.

best wishes,

Sudhir Gandotra
Koha demo :  http://koha.openlx.com


On Tue, Dec 9, 2014 at 9:34 PM, Jesse Lambertson 
wrote:

> Happy Tuesday everyone,
>
> I have a question about installation of Koha.
>
> Relative to hosting Koha in the cloud as opposed to on our own local
> servers on our domain (which I assume most people do), what is the thinking
> about the ease of installing and updating if it is hosted "externally"
> versus on our own servers?
>
> What steps might drastically change if we install Koha in the cloud?
>
> Are there any security issues I should be concerned about in either case?
>
> Thank you in advance for your thoughts.
>
> Jesse
>
> --
> Jesse A Lambertson
> Librarian
> Sultan Qaboos Cultural Center
> 1100 16th St, NW
> Washington, DC 20036
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> http://lists.katipo.co.nz/mailman/listinfo/koha
>



-- 
*Wishing you the Freedom to be Human*
*Sudhir Gandotra.  * +91-98101-20918,   +91-93124-65666



*OpenLX Technologies P. Ltd.*

*(Formerly OpenLX Inc.)*

*(ISO 9001:2008 Certified, OpenLX Alliance Enterprise for Linux &
Open-Source Technology)*

Our Profile

List of Clients

   Online Demo


*Head Office : F-34/5, Okhla Indl Area, Phase-II, **New Delhi - 110020,
INDIA*

*Phones: * +91-11-2638-5034,   +91-11-2638-5035

*Email:*

i...@openlx.com   *InterNet:* www. openlx.com



*OpenLX Linux - Humanizing Technology, Transforming Lives !**You don't need
violence to shake the world** - Use Linux !*

*Pl like our pages :  Peace Desktop

 &
 Business Desktop
*

Connect to us on LinkedIN



*Linux Jobs :  http://openlx.com/careers.html
*
*Why Koha ?
**
  Biz Desktop
**
   OpenLX Linux
**
Why Dspace ?
*


*Send your KOHA Enquiry Now !*

Re: [Koha] Cloud-based Koha vs locally hosted Koha

[Chris Cormack]

Hi all 
I agree with Brooke, the cloud is just someone else's computer. With all the 
advantages and disadvantages that brings. 

Chris 

On 10 December 2014 7:06:37 am NZDT, BWS Johnson  
wrote:
>Salve!
>
>> I have a question about installation of Koha.
>> 
>> Relative to hosting Koha in the cloud as opposed to on our own local
>> servers on our domain (which I assume most people do), what is the
>thinking
>> about the ease of installing and updating if it is hosted
>"externally"
>> versus on our own servers?
>> 
>
>
>As long as you have access to the command line and can update and
>change things at will, then there is no difference between the cloud
>and a physical local server. That latter bit seems to be a big problem
>with a lot of companies, though. So choose a service provider with
>great care and after a lot of testing. You not only needs be able to
>update Koha, but all of Koha's dependencies as well.
>
>
>>
>> Are there any security issues I should be concerned about in either
>case?
>
>> 
>
>
>The only difference I can spot might actually weigh as a positive in
>favour of cloud based service. When you have a physical server and
>suffer a local catastrophe, such as an earthquake, fire, sinkhole, et
>cetera, there goes your data. If you found a cloud based service that
>allows you to maintain things routinely, there shouldn't be any
>difference. You're trusting someone else when you select a hosted
>service, but this would be the same trust you would put in a normal
>vendor in most cases, anyway. If you hire a new employee for your
>building and give them a set of keys, you're taking a security risk,
>too, but in both cases that risk ought be calculated.
>
>Security issues in general are shared over a specific listserv that's
>populated by trusted Community members. Bugs on that list are fixed
>with extreme prejudice.
>
>My final note is to consider if you're going to actually *need* the
>data that you collect and keep. A certain naughty Library that shall
>remain nameless used to keep the Social Security Numbers of all of
>their Patrons in a note field on a non Koha system that would literally
>pop up *every* time someone checked out.
>
>Cheers,
>Brooke
>___
>Koha mailing list  http://koha-community.org
>Koha@lists.katipo.co.nz
>http://lists.katipo.co.nz/mailman/listinfo/koha

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Cloud-based Koha vs locally hosted Koha

[BWS Johnson]

Salve!

> I have a question about installation of Koha.
> 
> Relative to hosting Koha in the cloud as opposed to on our own local
> servers on our domain (which I assume most people do), what is the thinking
> about the ease of installing and updating if it is hosted "externally"
> versus on our own servers?
> 


As long as you have access to the command line and can update and change 
things at will, then there is no difference between the cloud and a physical 
local server. That latter bit seems to be a big problem with a lot of 
companies, though. So choose a service provider with great care and after a lot 
of testing. You not only needs be able to update Koha, but all of Koha's 
dependencies as well.


>
> Are there any security issues I should be concerned about in either case?

> 


The only difference I can spot might actually weigh as a positive in favour 
of cloud based service. When you have a physical server and suffer a local 
catastrophe, such as an earthquake, fire, sinkhole, et cetera, there goes your 
data. If you found a cloud based service that allows you to maintain things 
routinely, there shouldn't be any difference. You're trusting someone else when 
you select a hosted service, but this would be the same trust you would put in 
a normal vendor in most cases, anyway. If you hire a new employee for your 
building and give them a set of keys, you're taking a security risk, too, but 
in both cases that risk ought be calculated.

Security issues in general are shared over a specific listserv that's 
populated by trusted Community members. Bugs on that list are fixed with 
extreme prejudice.

My final note is to consider if you're going to actually *need* the data 
that you collect and keep. A certain naughty Library that shall remain nameless 
used to keep the Social Security Numbers of all of their Patrons in a note 
field on a non Koha system that would literally pop up *every* time someone 
checked out.

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

Re: [Koha] Showing the last item checked out with AJAX circulation

[DeMuth, Jennifer]

I really like this idea!

Jen DeMuth
Library Specialist 
Technology & Support Services
City of Roseville
225 Taylor St. 
Roseville, CA 95678
916-774-5238 desk
916-773-5594 fax
www.roseville.ca.us/library



-Original Message-
From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of Owen Leonard
Sent: Tuesday, December 09, 2014 9:04 AM
To: koha
Subject: Re: [Koha] Showing the last item checked out with AJAX circulation

Christopher Brannon made this comment on the bug report:

> I would be more inclined to see the feedback in the same area that I'm 
> scanning in (in the same box).  Maybe at the bottom?

I like this idea too! Here's my take:

http://www.screencast.com/t/ZcsPfJabP

The advantage to this method is that the feedback is visible even for patrons 
with lost of information in the messages column:

http://www.screencast.com/t/3uEHAaWnUyc

  -- Owen

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

Re: [Koha] Showing the last item checked out with AJAX circulation

[Owen Leonard]

Christopher Brannon made this comment on the bug report:

> I would be more inclined to see the feedback in the same area that I'm
> scanning in (in the same box).  Maybe at the bottom?

I like this idea too! Here's my take:

http://www.screencast.com/t/ZcsPfJabP

The advantage to this method is that the feedback is visible even for
patrons with lost of information in the messages column:

http://www.screencast.com/t/3uEHAaWnUyc

  -- Owen

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

Re: [Koha] Showing the last item checked out with AJAX circulation

[Marc Véron]

Hi,

I prefer Owen's proposition (Information in Checkout-Tab)

Marc

Am 09.12.2014 16:33, schrieb Jason M. Burds:
> Either is good with our library, love the addition of the last checked out 
> item!
>
> Jason Burds
> I.T. Supervisor
> Carnegie-Stout Public Library
> (563)589-4229
>
> -Original Message-
> From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of Owen Leonard
> Sent: Tuesday, December 9, 2014 9:30 AM
> To: koha
> Subject: [Koha] Showing the last item checked out with AJAX circulation
>
> One of the issues we're having with the new AJAX circulation feature is that 
> we can't take advantage of the speed gains obtained by not showing checkouts 
> by default because we need confirmation that the last item we scanned was 
> successfully checked out.
>
> Kyle has offered a patch for Bug 13315, " Add feedback for last item checked 
> out to circulation.pl" which updates the display so that a message shows with 
> information about the last item scanned. Here's a
> screenshot:
>
> http://www.screencast.com/t/qNw2U3hwz
>
> I think this is an important improvement, but I'm inclined to do something 
> less obtrusive:
>
> http://www.screencast.com/t/1gsa2prF
>
> ...on the assumption that the visual aspect of checking out was working fine 
> before AJAX circ, and fixes to AJAX circ should look to returning things to a 
> proven-functional state.
>
> However, always assuming that it was better before would prevent us from 
> making improvements, so I'd love to hear others' opinions -- especially from 
> anyone who is running this feature in production.
>
> Thanks,
>
>   -- Owen
>
> --
> Web Developer
> Athens County Public Libraries
> http://www.myacpl.org
> ___
> Koha mailing list  http://koha-community.org Koha@lists.katipo.co.nz 
> http://lists.katipo.co.nz/mailman/listinfo/koha
>
>
> This message has been scanned for malware by Websense. www.websense.com
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> http://lists.katipo.co.nz/mailman/listinfo/koha
>

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

[Koha] Cloud-based Koha vs locally hosted Koha

[Jesse Lambertson]

Happy Tuesday everyone,

I have a question about installation of Koha.

Relative to hosting Koha in the cloud as opposed to on our own local
servers on our domain (which I assume most people do), what is the thinking
about the ease of installing and updating if it is hosted "externally"
versus on our own servers?

What steps might drastically change if we install Koha in the cloud?

Are there any security issues I should be concerned about in either case?

Thank you in advance for your thoughts.

Jesse

-- 
Jesse A Lambertson
Librarian
Sultan Qaboos Cultural Center
1100 16th St, NW
Washington, DC 20036
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] FOSS Conference - Call for Papers

[glaws]

http://www.kansaslinuxfest.us/pages/call-for-papers.html

FOSS conference March 2015 in Lawrence, KS, USA.

Call for papers. Koha anyone?


-- 
Greg Lawson
Rolling Hills Consolidated Library
1912 N. Belt Highway
St. Joseph, MO 64506

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

Re: [Koha] Showing the last item checked out with AJAX circulation

[Jason M. Burds]

Either is good with our library, love the addition of the last checked out item!

Jason Burds
I.T. Supervisor
Carnegie-Stout Public Library
(563)589-4229

-Original Message-
From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of Owen Leonard
Sent: Tuesday, December 9, 2014 9:30 AM
To: koha
Subject: [Koha] Showing the last item checked out with AJAX circulation

One of the issues we're having with the new AJAX circulation feature is that we 
can't take advantage of the speed gains obtained by not showing checkouts by 
default because we need confirmation that the last item we scanned was 
successfully checked out.

Kyle has offered a patch for Bug 13315, " Add feedback for last item checked 
out to circulation.pl" which updates the display so that a message shows with 
information about the last item scanned. Here's a
screenshot:

http://www.screencast.com/t/qNw2U3hwz

I think this is an important improvement, but I'm inclined to do something less 
obtrusive:

http://www.screencast.com/t/1gsa2prF

...on the assumption that the visual aspect of checking out was working fine 
before AJAX circ, and fixes to AJAX circ should look to returning things to a 
proven-functional state.

However, always assuming that it was better before would prevent us from making 
improvements, so I'd love to hear others' opinions -- especially from anyone 
who is running this feature in production.

Thanks,

  -- Owen

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


This message has been scanned for malware by Websense. www.websense.com
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Showing the last item checked out with AJAX circulation

[Owen Leonard]

One of the issues we're having with the new AJAX circulation feature
is that we can't take advantage of the speed gains obtained by not
showing checkouts by default because we need confirmation that the
last item we scanned was successfully checked out.

Kyle has offered a patch for Bug 13315, " Add feedback for last item
checked out to circulation.pl" which updates the display so that a
message shows with information about the last item scanned. Here's a
screenshot:

http://www.screencast.com/t/qNw2U3hwz

I think this is an important improvement, but I'm inclined to do
something less obtrusive:

http://www.screencast.com/t/1gsa2prF

...on the assumption that the visual aspect of checking out was
working fine before AJAX circ, and fixes to AJAX circ should look to
returning things to a proven-functional state.

However, always assuming that it was better before would prevent us
from making improvements, so I'd love to hear others' opinions --
especially from anyone who is running this feature in production.

Thanks,

  -- Owen

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

Re: [Koha] how to install koha in my website (linux hosting with cpanel)

[Owen Leonard]

> can installation is
> possible from window 7 pc. (i use desktop) or any ubntu or other pc
> required.

Koha cannot be installed on Windows. Debian or Ubuntu are recommended
because you can install from packages:

http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages

If you don't have any option other than installing on Windows you will
have to use software like Virtualbox to create a virtual machine
running Debian or Ubuntu.

  -- Owen

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

Re: [Koha] make test failed 3.18.0

[wslyhbb]

Hi Michal,Yes, all of the Perl modules are installed.  When I ran perl 
Makefile.pl the first time I got a few warnings and I installed the missing 
perl dependencies.  When I ran perl Makefile.pl again I no longer had any 
warnings.  I proceeded to run 'make test' as root and got the two failed tests. 
 I am using Perl 5.18.1. Thanks,
Wes Hobbie 

 On Tuesday, December 9, 2014 12:40 AM, Michał Dudzik [via Koha] 
 wrote:
   

  Hi,
Are all the required Perl modules are installed? Perl 5.10 is required!
Try install from packages
http://wiki.koha-community.org/wiki/Debian

Regards
Michał Dudzik




wslyhbb wroteHi,
When I run make test, two tests fail:
t/Creators.t  3/16 ERROR in koha-conf.xml -- missing 
/path/to/font.ttf at 
/srv/www/koha/blib/PERL_MODULE_DIR/C4/Creators/PDF.pm line 123.
ERROR in koha-conf.xml -- missing /path/to/font.ttf at 
/srv/www/koha/blib/PERL_MODULE_DIR/C4/Creators/PDF.pm line 319.

#   Failed test 'testing StrWidth() returns correct point width'
#   at t/Creators.t line 47.
#          got: '19.344'
#     expected: '23.044921875'

#   Failed test 'testing Text() writes to the correct x-value'
#   at t/Creators.t line 51.
#          got: '29.344'
#     expected: '33.044921875'
# Looks like you failed 2 tests of 16.
t/Creators.t  Dubious, test returned 2 (wstat 512, 
0x200)
Failed 2/16 subtests
 
 
   If you reply to this email, your message will be added to the discussion 
below: 
http://koha.1045719.n5.nabble.com/make-test-failed-3-18-0-tp5821460p5821493.html
   To unsubscribe from make test failed 3.18.0, click here.
 NAML 





--
View this message in context: 
http://koha.1045719.n5.nabble.com/make-test-failed-3-18-0-tp5821460p5821575.html
Sent from the Koha-general mailing list archive at Nabble.com.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Can't enable Plugins

[Sami M. Rasheed]

Dears,Set up PluginsKoha version: 3.16.04.000
I set up the Koha plugin system...
   
   - Create the directory /var/lib/koha/plugins
   - Add the lines /var/lib/koha/plugins 
1" to your koha-conf.xml file
   - Add the line Alias /plugin/ "/var/lib/koha/plugins/" to koha-httpd.conf 
file
   - Restart your webserver
   - Enable UseKohaPlugins system preference.   

Problem: Plugins still disabled.
 
Plugins disabled!
 To enable Koha plugins, the system preference UseKohaPlugins must be enabled, 
and the flag enable_plugins must be set in the Koha configuration file
How I can enable Plugins.. 
Thanks.--Sami Al-Asheh
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] acquisition

[vikram zadgaonkar]

Dear All,
I have upgraded from koha 3.14 to  koha 3.16. I am having some problem in
Acquisition.
After upgradation I am not getting option in acquisition which item I want
to receive from selected basket.
I am getting directly
Receipt summary for
*TEST *

*Invoice number:* frc124 *Received by:* admin *On:* 09/12/2014
 Pending orders There are no pending orders.
 Already received There are no received orders.

Can some one tell me where I am going wrong?
Vikram Zadgaonkar
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha