[Koha] Setting DueDates and Sending OverDue Notices

[Jesse Lambertson]

Hello everyone,

We are working in a koha set up (3.20 on debian 7 - package install on
local server).

Our notifications are edited to send, most of them are going out etc.

But the system is sending NO Overdue notices for some reason,

Let me summarize what I have set up in case this is helpful to anyone.

In Administration > Circulation & Fine Rules, we have set the circulation
polices, renewal permissions per patron types etc.

In Patron Category Admin, we have set Overdue notices to YES.

In that same Category, we have the set circulation unit in days (30) which
seems like it SHOULD trigger overdue notices at the appointed time - it is
not.

*Why might this be*?

Also, regarding the set up of Hard Due Dates: *Do these have to be set to
trigger OverDue notices if the other circulation rules are set*?
https://wiki.koha-community.org/wiki/Hard_Due_Dates_Circ_Rule_RFC

I am not finding the language here as clear as I think it could be for me.

We are currently sending notices for Advance Notice, Item Due and Holds
Available.
But OverDue notices are not going out.
I might have incorrectly set up the triggers defined here
http://translate.koha-community.org/manual/3.20/en/html-desktop/#noticetriggers
because I have delays set for advance notice and items due and one Overdue
notice. But it SEEMS the advance notice would need a different delay
trigger than overdue because one is before the item is due and one is
after.

The Cronjob is running to check them, the messaging queue is being checked
every 15 minutes according to the logs, but they are still not being sent.

*What is it I am missing here*?
*Is this a trigger set-up issue, a hard due date issue or something deeper*?

Thank you for any advice.

Jesse.

-- 
Jesse A Lambertson
Librarian
عالم الانجازات ينحاز دوماً مع المتفائلين
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Koha General IRC Meeting reminder

[Mirko Tietgen]

Hello everyone,

the next general IRC meeting is 03 February 2016 10 UTC
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+IRC+General+Meeting=20160203T10

Place: The #koha IRC channel (IRC server irc.oftc.net).
If you don't have an IRC client you can join the meeting using your
web browser. http://webchat.oftc.net/?channels=koha

Agenda: https://wiki.koha-community.org/wiki/Next_General_IRC_meeting

Cheers,

Mirko


--

Mirko Tietgen
mi...@abunchofthings.net
http://koha.abunchofthings.net
http://meinkoha.de




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

Re: [Koha] Setting DueDates and Sending OverDue Notices

[Nombre]

El 01/02/16 a las 20:22, Jesse Lambertson escribió:
> Thank you Craig.
> 
> Yes, there is a client running to send mail.
> Our sysadmin set it up for me.
> 
> We are getting all the other notifications EXCEPT overdues.

Have you checked crontab files in /etc?, perhaps the line with overdue
execution is commented.

I think I have commented in my installation, I don't remember clearly.

REagards


> 
> This is why I was thinking it might be a trigger or hard due date issue.
> 
> Jesse
> 
> On Mon, Feb 1, 2016 at 2:19 PM, Craig Butosi 
> wrote:
> 
>> Hi Jesse,
>>
>> Of the top of my head, did you install a mail transfer agent like Postfix
>> or Sendmail on your Debian machine? If not, the lack of an MTA might be the
>> culprit.
>>
>>
>> C
>>
>> Craig Butosi, MA, MLIS, B Mus (Hons.)
>> LIBRARY SERVICES MANAGER
>> THE ROYAL CONSERVATORY
>> TELUS Centre for Performance and Learning
>> 273 Bloor Street West
>> Toronto, ON M5S 1W2
>> 416.408.2824 x338
>> www.rcmusic.ca
>>
>> -Original Message-
>> From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of Jesse
>> Lambertson
>> Sent: February-01-16 2:15 PM
>> To: koha@lists.katipo.co.nz
>> Subject: [Koha] Setting DueDates and Sending OverDue Notices
>>
>> Hello everyone,
>>
>> We are working in a koha set up (3.20 on debian 7 - package install on
>> local server).
>>
>> Our notifications are edited to send, most of them are going out etc.
>>
>> But the system is sending NO Overdue notices for some reason,
>>
>> Let me summarize what I have set up in case this is helpful to anyone.
>>
>> In Administration > Circulation & Fine Rules, we have set the circulation
>> polices, renewal permissions per patron types etc.
>>
>> In Patron Category Admin, we have set Overdue notices to YES.
>>
>> In that same Category, we have the set circulation unit in days (30) which
>> seems like it SHOULD trigger overdue notices at the appointed time - it is
>> not.
>>
>> *Why might this be*?
>>
>> Also, regarding the set up of Hard Due Dates: *Do these have to be set to
>> trigger OverDue notices if the other circulation rules are set*?
>> https://wiki.koha-community.org/wiki/Hard_Due_Dates_Circ_Rule_RFC
>>
>> I am not finding the language here as clear as I think it could be for me.
>>
>> We are currently sending notices for Advance Notice, Item Due and Holds
>> Available.
>> But OverDue notices are not going out.
>> I might have incorrectly set up the triggers defined here
>> http://translate.koha-community.org/manual/3.20/en/html-desktop/#noticetriggers
>> because I have delays set for advance notice and items due and one Overdue
>> notice. But it SEEMS the advance notice would need a different delay
>> trigger than overdue because one is before the item is due and one is after.
>>
>> The Cronjob is running to check them, the messaging queue is being checked
>> every 15 minutes according to the logs, but they are still not being sent.
>>
>> *What is it I am missing here*?
>> *Is this a trigger set-up issue, a hard due date issue or something
>> deeper*?
>>
>> Thank you for any advice.
>>
>> Jesse.
>>
>> --
>> Jesse A Lambertson
>> Librarian
>> عالم الانجازات ينحاز دوماً مع المتفائلين
>> ___
>> Koha mailing list  http://koha-community.org Koha@lists.katipo.co.nz
>> https://lists.katipo.co.nz/mailman/listinfo/koha
>>
>>
>> Note: This email message and any attachments are intended only for the use
>> of the individual to which it is addressed, and may contain information
>> that is privileged, confidential and exempt from disclosure under
>> applicable law. If the recipient of this email is not the intended
>> recipient (or the employee or agent responsible for delivering the email to
>> the intended recipient), you are hereby notified that any review,
>> dissemination, distribution or copying or other use of this message is
>> strictly prohibited. If you have received this communication in error,
>> please notify the sender immediately by return email and delete this
>> message and attachments from your system, thank you.
>>
> 
> 
> 

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

Re: [Koha] Setting DueDates and Sending OverDue Notices

[Jesse Lambertson]

Thank you Craig.

Yes, there is a client running to send mail.
Our sysadmin set it up for me.

We are getting all the other notifications EXCEPT overdues.

This is why I was thinking it might be a trigger or hard due date issue.

Jesse

On Mon, Feb 1, 2016 at 2:19 PM, Craig Butosi 
wrote:

> Hi Jesse,
>
> Of the top of my head, did you install a mail transfer agent like Postfix
> or Sendmail on your Debian machine? If not, the lack of an MTA might be the
> culprit.
>
>
> C
>
> Craig Butosi, MA, MLIS, B Mus (Hons.)
> LIBRARY SERVICES MANAGER
> THE ROYAL CONSERVATORY
> TELUS Centre for Performance and Learning
> 273 Bloor Street West
> Toronto, ON M5S 1W2
> 416.408.2824 x338
> www.rcmusic.ca
>
> -Original Message-
> From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of Jesse
> Lambertson
> Sent: February-01-16 2:15 PM
> To: koha@lists.katipo.co.nz
> Subject: [Koha] Setting DueDates and Sending OverDue Notices
>
> Hello everyone,
>
> We are working in a koha set up (3.20 on debian 7 - package install on
> local server).
>
> Our notifications are edited to send, most of them are going out etc.
>
> But the system is sending NO Overdue notices for some reason,
>
> Let me summarize what I have set up in case this is helpful to anyone.
>
> In Administration > Circulation & Fine Rules, we have set the circulation
> polices, renewal permissions per patron types etc.
>
> In Patron Category Admin, we have set Overdue notices to YES.
>
> In that same Category, we have the set circulation unit in days (30) which
> seems like it SHOULD trigger overdue notices at the appointed time - it is
> not.
>
> *Why might this be*?
>
> Also, regarding the set up of Hard Due Dates: *Do these have to be set to
> trigger OverDue notices if the other circulation rules are set*?
> https://wiki.koha-community.org/wiki/Hard_Due_Dates_Circ_Rule_RFC
>
> I am not finding the language here as clear as I think it could be for me.
>
> We are currently sending notices for Advance Notice, Item Due and Holds
> Available.
> But OverDue notices are not going out.
> I might have incorrectly set up the triggers defined here
> http://translate.koha-community.org/manual/3.20/en/html-desktop/#noticetriggers
> because I have delays set for advance notice and items due and one Overdue
> notice. But it SEEMS the advance notice would need a different delay
> trigger than overdue because one is before the item is due and one is after.
>
> The Cronjob is running to check them, the messaging queue is being checked
> every 15 minutes according to the logs, but they are still not being sent.
>
> *What is it I am missing here*?
> *Is this a trigger set-up issue, a hard due date issue or something
> deeper*?
>
> Thank you for any advice.
>
> Jesse.
>
> --
> Jesse A Lambertson
> Librarian
> عالم الانجازات ينحاز دوماً مع المتفائلين
> ___
> Koha mailing list  http://koha-community.org Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
>
> Note: This email message and any attachments are intended only for the use
> of the individual to which it is addressed, and may contain information
> that is privileged, confidential and exempt from disclosure under
> applicable law. If the recipient of this email is not the intended
> recipient (or the employee or agent responsible for delivering the email to
> the intended recipient), you are hereby notified that any review,
> dissemination, distribution or copying or other use of this message is
> strictly prohibited. If you have received this communication in error,
> please notify the sender immediately by return email and delete this
> message and attachments from your system, thank you.
>



-- 
Jesse A Lambertson
Librarian
Sultan Qaboos Cultural Center 
Ph: (202)-677-3967 Ext. 104
jlambert...@sqcc.org
عالم الانجازات ينحاز دوماً مع المتفائلين
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha and OAI-PMH [and digital materials]

[Coehoorn, Joel]

I'm re-posting your message paragraph by paragraph, with my responses
interspersed.

I originally started working on an OAI-PMH harvester to create an automatic
import of records from DSpace into Koha, so that Koha could show electronic
resources in the catalogue. While having good item types, frameworks, and
templates are good, I found the main problem to be the metadata quality.
Dublin Core doesn’t translate very well to MARC. Although now that I’m
re-reading your email… are you talking about making MARC records in Koha
and then using DSpace’s OAI-PMH harvester to import metadata from Koha?
Then attaching digital materials in DSpace while using Koha to maintain the
metadata? That could be interesting…

At that point I was mainly trying to understand the original message and
working through various possibilities, but yes, that could be interesting.
I think librarians are generally more familiar with circulation software
and formats like Koha/Marc than with DSpace, so it could help with data
quality: all metadata is always entered in Koha, whether physical or
digital, and therefore you only need to learn one system.

I agree that Koha needs to evolve to have better support for digital
materials. However, I’m not sure what you mean by “a first-class framework
for URL-only item types” though. Could you elaborate on that?

At this point I need to mention that I'm the college tech guy. Koha is only
one of several systems I support, and my involvement since our initial
migration is limited. So some of this is based on limited exposure to the
software.

What I mean by "first class framework" is that it's on the same level as
traditional books. My understanding is that, technically, this does happen
already. From Koha's perspective, a biblio framework is a biblio framework
is a biblio framework, and none is more important than any others. What
I've seen so far from a practical standpoint is that librarians will
sometimes try to use the biblio framework created for books as a
one-size-fits all solution for their other item types. Koha could do more
to make it easier to really use multiple kinds of biblio frameworks, and
specifically push a default framework for digital content to the fore in
certain circumstances... even just some warning messages if there are marc
fields present that indicate this might be a digital work with a
non-digital biblio framework would be a step in the right direction.
Eventually the warning messages might also include a short menu of
one-click fixes.

Better integration into systems like DSpace may be achieved using their
evolving REST APIs, although again I’m not sure what you mean by “a user
might end up checking-out some digital content stored there [DSpace? Koha?]
(a record is created in the issues table) that doesn’t need to check back
in”. Why would you need to check out digital content in DSpace? In my
experience, content is either open to the public or limited to logged in
users (as part of licensing/rights restrictions). Are you thinking of
something more like hosting your own ebooks in DSpace and complying with
concurrent user restrictions? That could be interesting as well, although I
think the majority of that work would be done in DSpace with Koha just
hooking into a DSpace API to determine if there are any “available” copies
for the material that they found in the Koha catalogue. I admit I’m not
super familiar with ebook DRM either, so I’m not certain how much
intervention would be required for expiring “on loan” DRM protected library
ebooks.

The idea behind checking out content from DSpace via Koha is for reporting,
so that use for content hosted in DSpace or similar could show up in
existing circulation reports run from Koha. Eventually, this would also
need to have support for DRM, so checking out a protected digital item from
Koha would also send the appropriate information back to DSpace. The idea
is that end users should be able to check out and retrieve digital content
stored elsewhere without ever leaving the Koha opac.

Personally, I find most of our Koha client libraries are interested in
allowing their users to find “only electronic resources” and to provide
seamless access to third-party sites like EBSCO, Proquest, and other
publishers that host the actual content. EBSCO have been putting work into
that with the Koha-EDS plugin, although I’d like to see more done in that
area, although that’s actually more a matter of digital material publishers
providing authentication and API options. If they provide the hooks, we can
provide the services.

We also use EBSCO/Academic Search Premier. It would be nice to search that
content from within Koha. I find an even more compelling solution would be
to let EBSCO have a z39.50 connection to our Koha catalog, and push our
patrons to use their search engine. EBSCO has interfaces into several other
catalogs (PsychArticles, OED, Britanica, JSTOR, etc) to which we also
subscribe, and they have more resources for a fast 

Re: [Koha] Koha and OAI-PMH [and digital materials]

[David Cook]

Hi Joel,

 

Thanks for your email. I think I’ve sorted things out with Flo, but I wanted to 
come back to your email, which I’m going to cross-post to the developer 
listserv as well. 

 

I originally started working on an OAI-PMH harvester to create an automatic 
import of records from DSpace into Koha, so that Koha could show electronic 
resources in the catalogue. While having good item types, frameworks, and 
templates are good, I found the main problem to be the metadata quality. Dublin 
Core doesn’t translate very well to MARC. Although now that I’m re-reading your 
email… are you talking about making MARC records in Koha and then using 
DSpace’s OAI-PMH harvester to import metadata from Koha? Then attaching digital 
materials in DSpace while using Koha to maintain the metadata? That could be 
interesting…

 

I agree that Koha needs to evolve to have better support for digital materials. 
However, I’m not sure what you mean by “a first-class framework for URL-only 
item types” though. Could you elaborate on that? 

 

Better integration into systems like DSpace may be achieved using their 
evolving REST APIs, although again I’m not sure what you mean by “a user might 
end up checking-out some digital content stored there [DSpace? Koha?] (a record 
is created in the issues table) that doesn’t need to check back in”. Why would 
you need to check out digital content in DSpace? In my experience, content is 
either open to the public or limited to logged in users (as part of 
licensing/rights restrictions). Are you thinking of something more like hosting 
your own ebooks in DSpace and complying with concurrent user restrictions? That 
could be interesting as well, although I think the majority of that work would 
be done in DSpace with Koha just hooking into a DSpace API to determine if 
there are any “available” copies for the material that they found in the Koha 
catalogue. I admit I’m not super familiar with ebook DRM either, so I’m not 
certain how much intervention would be required for expiring “on loan” DRM 
protected library ebooks. 

 

Personally, I find most of our Koha client libraries are interested in allowing 
their users to find “only electronic resources” and to provide seamless access 
to third-party sites like EBSCO, Proquest, and other publishers that host the 
actual content. EBSCO have been putting work into that with the Koha-EDS 
plugin, although I’d like to see more done in that area, although that’s 
actually more a matter of digital material publishers providing authentication 
and API options. If they provide the hooks, we can provide the services. 

 

I’m curious to hear your thoughts. If you have ideas for things you’d like to 
see, feel free to share them. If you have a budget for sponsoring development, 
feel free to mention that as well. It’s actually quite an exciting time to be 
working on Koha as large organizations like EBSCO and the National Library of 
Sweden are sponsoring developments in areas like OAI-PMH harvesting (which I’m 
working on now), moving to ElasticSearch for search and retrieval, a new REST 
API, etc. Even if you don’t have the money yourself, you might propose ideas on 
the koha-devel listserv and see if anyone is interested in sponsoring that 
work. 

 

Cheers,

 

David Cook

Systems Librarian

Prosentient Systems

72/330 Wattle St, Ultimo, NSW 2007

 

From: Coehoorn, Joel [mailto:jcoeho...@york.edu] 
Sent: Wednesday, 27 January 2016 10:25 AM
To: David Cook 
Cc: koha@lists.katipo.co.nz; flo.pouye...@gmail.com
Subject: Re: [Koha] Koha and OAI-PMH

 

It sounds like she's talking about using a program that acts kind of like a web 
search crawler, similar to how Googlebot operates, to push information into 
Koha.

 

If that's the case, I don't think Koha would be a good solution for this right 
now, though you might get something working via a z39.50 connection.

 

It may be that she's asking if Koha can store and serve/circulate harvested 
digital content directly. Again, I don't believe Koha in it's current form 
would be good at this. Koha does not currently provide any place to store 
binary files for circulation.

 

It may also be that she's asking if she can use Koha as a front end into 
something like DSpace   or Greenstone 
 .

 

If that's the case, I believe Koha can do this right now, but the setup is not 
yet easy or straightforward. In a nutshell, you would want to enter marc 
records for each item in the repository, just like you do for current 
materials, but you would want to use item types and a custom framework so that 
the material is presented well.

 

I would welcome improvements in Koha to support any of those scenarios. 
Ultimately, I think Koha needs to evolve to have better support for digital 
materials. At a minimum, this means a first-class framework for URL-only item 
types along with first-class integration into systems like DSpace, 

Re: [Koha] [Koha-devel] Koha Search Indexes

[Barton Chittenden]

On Mon, Feb 1, 2016 at 5:54 PM, David Cook  wrote:

> Hi Nicole,
>
> I keep meaning to look over and revise the search documentation, but I
> always seem preoccupied with other work.
>
> I'm not sure whether or not the list at
> http://manual.koha-community.org/3.24/en/kohasearchindexes.html is
> complete at a glance. To be honest, while I think it's a valuable list, I
> think it would be more valuable for end users to have a list of CCL
> qualifiers (and their corresponding registers). While an index may exist in
> Zebra, it's the CCL qualifier that the user needs to know in order to
> access it, and sometimes the qualifier is difference than the index name.
>
> There are 3 vital files for Zebra indexing and Koha searching:
> bib1.att
> biblio-zebra-indexdefs.xsl
> ccl.properties
>
> bib1.att defines which indexes may exist.
> Biblio-zebra-indexdefs.xsl decides what MARC data goes into which indexes.
> ccl.properties provides a query language for accessing those indexes
> through search queries.
>
> Paul asked about the suffixes :n, :p, :w, :u, and :s. These are called
> "registers". :n is numeric, :p is phrase, :w is word, :u is URL, and :s is
> sorting.
>
> Different types of CCL qualifiers allow us to access different types of
> registers. "st-numeric" provides access to the :n register. "st-phrase" and
> "phr" access :p. "st-word", "st-word-list", and "wrdl" access ":w",
> "st-urx" accesses :u, and generally we don't need to access :s when
> searching as that's a behind-the-scenes thing for Koha to worry about.
>
> Different registers have different normalization rules.
>
> If we look at biblio-zebra-indexdefs.xsl, we can see that MARC 245 is
> indexed into Title:w and Title:p. That means "Harry Potter and the
> Philosopher's Stone" would be indexed something like so:
>
> Harry
> Potter
> Phllosopher's
> Stone
> Harry Potter and the Philosopher's Stone
>
> So if we did a search like... "title,wrdl=Harry", we'd get a hit for that
> MARC record. If we did a search like 'title,phr="Harry Potter and the
> Philosopher's Stone"', we'd get a hit for that MARC record.
>
> I'll draw your attention now to 952$u. It's indexed as uri:u (although it
> would also show up in the Any:w and Any:p keyword indexes). In order to
> access uri:u, we'd need to search for 'uri,st-urx="
> http://koha-community.org;'. The "st-urx" maps to the ":u", and we see
> "uri" in "ccl.properties" which maps to "uri" in bib1.att.
>
> If we tried to do a search for 'uri,wrdl="http://koha-community.org;', it
> would fail, because nothing is indexed in the "uri:w" index:register combo.
>
> I have to run to an appointment, but hopefully that helps a bit.
>
> One day, I'd like to write a program which parses ccl.properties to
> provide a list of qualifies that cross-references with
> biblio-zebra-indexdefs.xsl to see which registers are available for which
> qualifier/index pair. The register system is a bit complicated but it can
> be useful. I've recently started doing more with the ":u" register...
>
>
David,

This isn't *quite* what you describe, but it does set up at least a couple
of the linkages that you'd need:

https://github.com/bywatersolutions/koha-script-zebra-config-report

I think that Marcus Enger wrote something similar, but I don't know if it
fist the current code base, and I don't remember the URL.

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

Re: [Koha] Koha Search Indexes

[Nicole Engard]

I'd love if someone could help me there.

Nicole

On Mon, Feb 1, 2016 at 10:35 AM, Paul A 
wrote:

> At 08:42 AM 2/1/2016 -0600, Nicole Engard wrote:
>
>> Hello all,
>>
>> I updated this page in the manual
>> http://manual.koha-community.org/3.24/en/kohasearchindexes.html because
>> there were many indexes not listed in there.  Would index experts please
>> take a look to make sure I caught all of the indexes?
>>
>
> Many thanks. Could you possible add an explanation of the suffixes :n, :p,
> :w, :u (URL?) and :s?
>
> Tnx and br -- Paul
>
> ---
> Maritime heritage and history, preservation and conservation,
> research and education through the written word and the arts.
>  and 
>
> ___
> 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

Re: [Koha] Marcedit on Linux

[Christopher Davis]

Monisa,

I use Ubuntu 14.04 LTS and run MarcEdit via Mono (open source version
of Microsoft's .NET framework). Download the Linux version of MarcEdit
at: , and then
follow the directions found at
.
Basically, you open a terminal shell, navigate to the folder where you
unzipped the MarcEdit file, and then type "mono MarcEdit.exe" and it
runs (don't close the terminal until you are finished using MarcEdit).
Please let me know if you need any other tips on this.

HTH,

Christopher Davis, MLS
Systems & E-Services Librarian
Uintah County Library
cgda...@uintah.utah.gov
(435) 789-0091 ext.261
uintahlibrary.org
basinlibraries.org
facebook.com/uintahcountylibrary


On Mon, Feb 1, 2016 at 10:25 AM, Monisa Aslam  wrote:
>
>
>
>
> Hello everyone.
> Can anyone guide me step by step that how to install marcedit on Linux.  
> Either through wine or mono.
> I tried but it's not working
> Monisa Aslam
> Sent from my Samsung device
> ___
> 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

Re: [Koha] ERROR LOADING MODULE: Date::Manip::DM6

[Jonathan Druart]

Hi Federico,

The error said that you don't have the Date::Manip module installed,
try to install it.

Regards,
Jonathan

2016-02-01 11:43 GMT+00:00 Federico Leva (Nemo) :
> Hello! I'm trying Koha on a small fedora 23 virtual machine for testing (500
> MB RAM, 1 core) and I often get this error in the web interface:
>
> 
>
> Software error:
>
> ERROR LOADING MODULE: Date::Manip::DM6 at
> /usr/share/perl5/vendor_perl/Date/Manip.pm line 34.
> Compilation failed in require at /usr/share/perl5/vendor_perl/C4/Overdues.pm
> line 25.
> BEGIN failed--compilation aborted at
> /usr/share/perl5/vendor_perl/C4/Overdues.pm line 25.
> Compilation failed in require at /usr/share/perl5/vendor_perl/C4/Members.pm
> line 29.
> BEGIN failed--compilation aborted at
> /usr/share/perl5/vendor_perl/C4/Members.pm line 29.
> Compilation failed in require at /usr/share/perl5/vendor_perl/C4/Search.pm
> line 28.
> BEGIN failed--compilation aborted at
> /usr/share/perl5/vendor_perl/C4/Search.pm line 28.
> Compilation failed in require at
> /usr/share/perl5/vendor_perl/C4/AuthoritiesMarc.pm line 24.
> BEGIN failed--compilation aborted at
> /usr/share/perl5/vendor_perl/C4/AuthoritiesMarc.pm line 24.
> Compilation failed in require at
> /usr/share/koha/intranet/cgi-bin/tools/manage-marc-import.pl line 32.
> BEGIN failed--compilation aborted at
> /usr/share/koha/intranet/cgi-bin/tools/manage-marc-import.pl line 32.
>
> 
>
> The error is always identical and goes away with a refresh. When it happens
> I see I have less than 10 MB free memory so it really just seems a resource
> issue. I'll give Koha more memory :) but let me know if I missed something
> obvious.
>
> Federico (BEIC)
> ___
> 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] ERROR LOADING MODULE: Date::Manip::DM6

[Federico Leva (Nemo)]

Hello! I'm trying Koha on a small fedora 23 virtual machine for testing 
(500 MB RAM, 1 core) and I often get this error in the web interface:




Software error:

ERROR LOADING MODULE: Date::Manip::DM6 at 
/usr/share/perl5/vendor_perl/Date/Manip.pm line 34.
Compilation failed in require at 
/usr/share/perl5/vendor_perl/C4/Overdues.pm line 25.
BEGIN failed--compilation aborted at 
/usr/share/perl5/vendor_perl/C4/Overdues.pm line 25.
Compilation failed in require at 
/usr/share/perl5/vendor_perl/C4/Members.pm line 29.
BEGIN failed--compilation aborted at 
/usr/share/perl5/vendor_perl/C4/Members.pm line 29.
Compilation failed in require at 
/usr/share/perl5/vendor_perl/C4/Search.pm line 28.
BEGIN failed--compilation aborted at 
/usr/share/perl5/vendor_perl/C4/Search.pm line 28.
Compilation failed in require at 
/usr/share/perl5/vendor_perl/C4/AuthoritiesMarc.pm line 24.
BEGIN failed--compilation aborted at 
/usr/share/perl5/vendor_perl/C4/AuthoritiesMarc.pm line 24.
Compilation failed in require at 
/usr/share/koha/intranet/cgi-bin/tools/manage-marc-import.pl line 32.
BEGIN failed--compilation aborted at 
/usr/share/koha/intranet/cgi-bin/tools/manage-marc-import.pl line 32.




The error is always identical and goes away with a refresh. When it 
happens I see I have less than 10 MB free memory so it really just seems 
a resource issue. I'll give Koha more memory :) but let me know if I 
missed something obvious.


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

Re: [Koha] Koha Search Indexes

[Paul A]

At 08:42 AM 2/1/2016 -0600, Nicole Engard wrote:

Hello all,

I updated this page in the manual
http://manual.koha-community.org/3.24/en/kohasearchindexes.html because
there were many indexes not listed in there.  Would index experts please
take a look to make sure I caught all of the indexes?


Many thanks. Could you possible add an explanation of the suffixes :n, :p, 
:w, :u (URL?) and :s?


Tnx and br -- Paul

---
Maritime heritage and history, preservation and conservation,
research and education through the written word and the arts.
 and 

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

[Koha] Marcedit on Linux

[Monisa Aslam]

Hello everyone.
Can anyone guide me step by step that how to install marcedit on Linux.  Either 
through wine or mono.
I tried but it's not working 
Monisa Aslam
Sent from my Samsung device
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Conclave Bangalore (17-18 February 2016)

[Amit Gupta]

Hi Mirko,

This mail is with Venue details.

On Tue, Feb 2, 2016 at 12:53 PM, Mirko Tietgen 
wrote:

> Hi,
>
> you have announced this event at least four times within one month
> now. The last email was not even a week ago. It is not common on
> this list to do that. Is it really necessary?
>
> -- Mirko
>
>
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
>


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

[Koha] Koha Conclave Bangalore (17-18 February 2016)

[Amit Gupta]

Hi All,

Informatics is pleased to present National Koha Conclave - a two day event
on Koha and Indian Libraries scheduled on 17th and 18th February 2016 at
Bangalore. The event will be inaugurated by* Mr. Chris Cormack (New
Zealand), the original developer of Koha*. Chris will also be presenting an
advance level half-a-day workshop on Koha during this two day event. The
event will witness several eminent speakers from the Indian Library
landscape and Koha experts through plenaries, panel discussions, case
studies and future development needs and opportunities on Koha. The event
will be attended by existing and prospective users of Koha.

The highlights of the event are:
a) Koha, the Road Ahead: A global view from Chris Cormack.
b) Development/Customization challenges.
c) Wish List by Participating Koha Users - Review Discussion.
d) Successful Koha implementations - Case Studies.
e) Advance Workshop on Koha (150 minutes).
f) Koha on Cloud - Panel Discussion.
g) Koha as a Collaborative Platform for Indian Libraries - Panel
Discussion.

Please mark your calendar and block your dates for this event - National
Koha Conclave and register your participation at the
link: http://informaticsglobal.com/kohameet

Since limited seats are available, please rush your registration.

Venue: *Fortune Park JP Celestial, Bangalore*

http://www.fortunehotels.in/bengaluru-fortune-park-jp-celestial.dh.23

-- 
Regards,
Amit Gupta
Informatics Publishing Ltd.,
Bangalore
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Conclave Bangalore (17-18 February 2016)

[Mirko Tietgen]

Hi,

you have announced this event at least four times within one month
now. The last email was not even a week ago. It is not common on
this list to do that. Is it really necessary?

-- Mirko



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

Re: [Koha] Koha Conclave Bangalore (17-18 February 2016)

[Mirko Tietgen]

Amit Gupta schrieb am 02.02.2016
> This mail is with Venue details.

It's the same email you sent on 27 January, except for a blank line
less and a longer signature.

-- Mirko



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

Re: [Koha] Wiki certificate

[Mirko Tietgen]

Paul,

Paul A schrieb am 31.01.2016
> a) Win XP has a market penetration of one in every nine or ten
> computers world wide;

According to w3cschools.com, Windows XP has a marketshare of 2,3%
(December 2015)[1]

> I might guess that this percentage is higher
> outside the "Western world" where libraries are perhaps just as
> important, or more so, than in "developed countries." 

Citation needed.

> Nothing to do
> with pyramids, but whether or not the Koha Wiki is important to
> them, I'll leave up to you...

My guess is that this percentage is higher in western
administrations that rather pay extra support fees than get their
act together and migrate to a recent operating system, because they
rely on custom software developed around the time of pyramids that
requires XP.

I live in Berlin. 28.902 of 70.223 Computers the Senate of Berlin is
responsible for were runnuning Windows XP end of October 2014. They
paid 300.000€ to get extra support from Microsoft until April
2015.[2] At that point the data security officer demanded 10.000s of
Computers running XP to be shut down immediately. Microsoft agreed
to renew the support contract once again.

In this case the information went public. I really don't want to
know how many cases like that we have in Germany alone. I don't know
what the status is today, but I have guess.

Fun fact: There were also 320 Servers running Windows 2003 Server
mid-2015, the extended support contract was supposed to cost about a
million Euro.[3]

> As to paying Microsoft's licensing fees, we're a charity and prefer
> spending our budget on outreach to school children, rather than
> financing Redmond.

Which means you are running a completely unsupported operating
system on some of your computers. That's scary. Good to hear you
plan to end that.

-- Mirko


[1] http://www.w3schools.com/browsers/browsers_os.asp
[2]
http://pardok.parlament-berlin.de/starweb/adis/citat/VT/17/SchrAnfr/s17-15656.pdf
(German)
[3]
http://www.heise.de/newsticker/meldung/Windows-Server-2003-Berliner-Senat-vor-sicherheitstechnischer-Herausforderung-2766718.html
(German)




> 
> At 08:58 PM 1/30/2016 +0100, Mirko Tietgen wrote:
>> Hi,
>>
>> Paul A schrieb am 30.01.2016
>>
>> > It appears that the Koha/Let's encrypt certificate will never
>> > work on WinXP
>>
>> No, it won't. XP was dead before LE was born. It will probably not
>> work for other ancient stuff, like pyramids.
>>
>> Wikipedia[1] says
>>
>> > On April 14, 2009, Windows XP exited mainstream support and
>> > entered the Extended Support phase; […] Extended support ended  on
>> > April 8, 2014, over 12 years since the release of XP; normally
>> > Microsoft products have a support life cycle of only 10
>> > years.[118] Beyond the final security updates released on April
>> > 8, no more security patches or support information are provided
>> > for XP free-of-charge; "critical patches" will still be created,
>> > and made available only to customers subscribing to a paid
>> > "Custom Support" plan
>>
>> I don't know how much money you would have to put into the paid
>> "Custom Plan" for something like this to happen, but since the rest
>> of the world does not have a paid "Support Win XP forever" plan,
>> it's not really their problem either.
>>
>> If XP still works for you, cool. If it does not, well, there have
>> been a few new versions now to choose an upgrade from. Or switch to
>> GNU/Linux, I hear it's quite good.
>>
>> -- Mirko
>>
>>
>> [1] https://en.wikipedia.org/wiki/Windows_XP#End_of_support
>>
>>
>> ___ Koha mailing list 
>> http://koha-community.org Koha@lists.katipo.co.nz
>> https://lists.katipo.co.nz/mailman/listinfo/koh
> 
> ---
> Maritime heritage and history, preservation and conservation,
> research and education through the written word and the arts.
>  and 
> 
> 



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

[Koha] Koha Search Indexes

[Nicole Engard]

Hello all,

I updated this page in the manual
http://manual.koha-community.org/3.24/en/kohasearchindexes.html because
there were many indexes not listed in there.  Would index experts please
take a look to make sure I caught all of the indexes?

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

Re: [Koha] Marcedit on Linux

[Sher Afzal]

Could you shear that what kind of problem you face wile trying to installed 
marcedit?

Whaich falver of Linux you using?

For installation of marcedit on Linux it is very important to that you have the 
Mono framework installed.Did you installed the Mono framework?

Following Vedio will aslo help you in this regards.

http://m.youtube.com/watch?v=N65IHRiRby8

You can joined this community for koha related problems.

https://www.facebook.com/groups/965873873493081/


Sher Afzal Khan
Chief Librarian
HEC Approved Trainer for Open Source Software Koha & Dspace
Country Ambassador DSpace Software
Mortensen Center Associate  USA 2015


Sent from my Samsung device


 Original message 
From: Monisa Aslam 
Date: 01/02/2016 10:25 PM (GMT+05:00)
To: koha@lists.katipo.co.nz
Subject: [Koha] Marcedit on Linux





Hello everyone.
Can anyone guide me step by step that how to install marcedit on Linux.  Either 
through wine or mono.
I tried but it's not working
Monisa Aslam
Sent from my Samsung device
___
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