.
On the plus side, though, I think there are quite a few of us in this boat, and
many of us have found Code4Lib, so while we may not have like-minded colleagues
in our institutions, we can still have a professional network.
Cheers,
Ian Walls
Web Services & Emergin
You can POST to LibAnalytics directly, bypassing their interface, if you
have the following information:
1. LibAnalytics URL
2. your institution ID (iid)
3. your data set ID (did)
4. your answerer ID (answerer)
5. The id numbers of each field in the data set you're submitting
6. How many records
Mark,
Oddly enough, we're looking at this kind of thing right now. I also
just got a message from my ILL Librarian that she saw a great conference
presentation on this kinda thing by Scott Bertagnole of Brigham Young
University.
From our perspective, the trick is authentication. We want t
can start to form a
pool of those libraries who have interested libtech workers, so when we
go to our directors/deans/boards, we can point to peers/aspirational
peers and say "see, we're not alone!".
Thanks,
Ian Walls
This sounds remarkably similar in feature-set to the Hours module I
wrote for our CMS (Silverstripe) for our recent website upgrade. We
defined Academic Terms first (name, startdate, enddate), and then could
associate Regular Hours (start time, end time and optional textual
description for eac
I second Cary's recommendation to go with a CMS. Another one to
consider is SilverStripe. It's highly extensible, though model
administration is done on the PHP level, so be prepared to open up your
favourite text editor and mind your syntax.
Ian Walls
Web Services & Emergin
I don't think IFTTT is the right tool, but the basic idea is sound.
With a spot of custom scripting on some server somewhere, one could take in
an ISBN, lookup via the III WebPac, assess eligibility conditions, then
return yes or no. Barcode Scanner on Android has the ability to do custom
search
I'm the happy owner of an Android Wear device, which looks to do pretty much
everything the Apple Watch does (minus the force sensing). I've been
looking at use cases for this new screen on my wrist, and trying to tune the
notifications I get so they are frequent (it's fun to use this thing!) yet
ff to someone
else for maintenance, but talk to me again in a year, and I should.
Cheers,
-Ian Walls
Web Services & Emerging Technologies Librarian
UMass Amherst Libraries
-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Joshua
Wel
If you're using TinyMCE as the WYSIWYG editor, you could configure it so
that particularly offensive HTML tags or attributes are stripped out, reset
or replaced: http://www.tinymce.com/wiki.php/configuration:valid_elements
If you stripped out 'style' from the list of valid attributes in elements,
A great idea! Some other hardware to consider:
Raspberry Pi alternative:
Beagle Bone Black
Further Arduino support:
Gemma (smaller version of FLORA)
Various breakout boards (GPS, GSM, LCD, etc.)
Sensors
Servos
For helping teach/interest younger folks:
Snap Circuits
littleBits
For larger setup
Perhaps Code4Lib could have some form of nominal membership, and the funds
derived from membership dues could be put into an array of scholarships.
Membership wouldn't necessarily have to be a privileged state, but for some
(many?) library positions, promotion criteria include "membership in
profes
Suma is the most practical and reliable way to do this right now, I think.
I've been investigating using a sensor network, but there are a lot of
limits on the accuracy of PIR, and trip-lasers are low enough and require
enough power that they'd be troublesome to maintain in a busy undergraduate
en
Android has Barcode Scanner, which can do both scan to text, as well as send
to custom URL (if you've got a RESTful kinda setup you want to GET to).
Not sure if there is a good solution for iOS... but you might be able to
build something in Phonegap (now Cordova), if you're keen.
-Ian
-Orig
I'd like to interject here again the idea of creating a stable API for
template variables, so that if people feel the need to template out there
out theme, they can do so without having to re-engineer it mid-release.
Any changes to this API would need to be well publicized between major
releases.
Paul,
You mentioned earlier in this thread that you could reproduce this issue
now that you've restored. Would it be possible for you to create a
screencast of what steps you're taking and what your output is for each of
those steps? When you're performing the commandline operations, what
direc
You can check Koha against WCAG 2.0 AA using open source AChecker (
http://AChecker.ca). Last time I ran it, our default template did very
well. It helps that we're web-based, and our philosophy of not being too
Javascript dependent pays off here.
You can also download the Fangs and WebAIM Firefox
I'd like to throw in another recommendation on Dokuwiki. Out of the box, I'd
call it about 80% of a solution, as there are some things I've wanted to do
with it that have proven really difficult with existing modules strung
together, but overall, it has the potential to do the job of a CMS well
I'm on the side of moving to Koha 4.0, and then looking into a
browser-based means of upgrading the system from there. Firefox, Chrome,
Dokuwiki and most mobile apps do not require any kind of additional process
to upgrade; you just click the button, and it works (or you look up, and
it's updated,
I think the key thing to do is to provide a consistent and well documented
set of template variables that do not change within any given version.
This is a pretty common practice for many CMS and other templatable
systems. That way, we always know what parts we have to work with.
This would great
was you were doing before.
-Justin
On Thu, Feb 21, 2013 at 11:53 AM, Ian Walls wrote:
> Agreed. Each language has its own strengths and weaknesses. Pick the
> one that works best for your situation, factoring in not only what the
> application needs to do, but your and your team's
Agreed. Each language has its own strengths and weaknesses. Pick the one that
works best for your situation, factoring in not only what the application needs
to do, but your and your team's level of experience, and the overall community
context in which the project will live. The peculiaritie
My library is about to launch into a series of quick usability testing
sessions next week for our website. In terms of software, we wanted to do a
screen and audio capture, but the programs we experimented with were not
sufficiently stable or responsive to fit into our workflow. There was far
too
+1
Perhaps, instead of a policy document (which is inherently rules-based), we
have a statement of belief and a pledge to stand by it (which is more of a
good-faith social contract). Those of us who believe in it could sign it in
some way, perhaps through GitHub This way we'd still have a docume
My concern over the anti-harassment policy is part of the definition of
"harassment", particularly:
"It includes offensive verbal comments or non-verbal expressions related to
gender, gender identity, gender expression, sexual orientation, disability,
physical appearance, body size, race, age, rel
The original (white) Square reader is unencrypted, and the output can be
read by an app, but you'll need to a) know how to write an app for the
platform(s) you wish, and b) figure out how to decode the serial data, which
isn't particularly well documented out there in the world.
If you're using Ch
>From the UIC Forum, bus route 12: http://goo.gl/maps/zyPx5, about every
10-15 minutes
-Ian
-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
Fleming, Declan
Sent: Monday, January 14, 2013 2:30 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB
following versions are safe: 3.2.11, 3.1.10, 3.0.19, or 2.3.15
Cheers,
-Ian Walls
Web Services and Emerging Technologies Librarian
UMass Amherst Libraries
So, what we're looking at here is a WALDO library, which is running one of
the LibLime forks. The various features they're offering (Maps, Facelift
and Mobile) are all Javascript libraries that can be dropped into the OPAC
system preferences. The most integration they do is to reference the
templ
I agree with Marc V. agreeing with Katrin. :)
Ian
On Oct 24, 2012 11:11 AM, "Marc Véron" wrote:
> Hi all,
>
> I agree with Katrin in both points.
>
> Marc V.
>
>
>
> Am 24.10.2012 16:53, schrieb Fischer, Katrin:
>
>> Hi all,
>>
>> I think so far we have a lot of votes for keeping the discussion
I believe Koha needs to keep maximum standards compliance and backwards
compatibility, as we often do encounter older hardware and software in the
line of international duty.
However, we do have the mechanisms in place to support multiple templates.
The chief difficulty with using this feature has
Koha Developers,
As I try to get back in the swing of things after a long absence, I'm
finding a lot of changes to Koha's dependencies to be particularly
frustrating, as I need to add new package repositories or even upgrade my
OS.
This leads me to the question: What OS versions does Koha run o
+1
Ian
On Jul 25, 2012 3:07 AM, "Julian Maurice"
wrote:
> Le 24/07/2012 18:06, Robin Sheat a écrit :
>
>> Op 24-07-12 18:02, Paul Poulain schreef:
>>
>>> Do we agree it's a good idea to request that for future scripts, and add
>>> this in the coding guidelines ?
>>>
>>
>> I find this also makes
If no one can voice a reason to have separate indexes for the OPAC v. the
staff client, best to use the same ones. It's what we do for biblios, and
authorities is just another Zebra database.
Keeping things simple will improve life for everyone.
-Ian
On Thu, Jul 12, 2012 at 12:35 PM, Jared Cam
I'm mostly in favour of solution 1 (in that it's close to what I think we
should to, and solution 2 is not good in my opinion). But I think there is
a little more to it.
There are several factors in our current workflow and environment that are
causing these bugs and regressions:
- *Lack of r
Points:
1. Yes, I believe it's okay for someone to do the action of sign off for
someone who is not technically inclined or does not have access to Git,
provided the person doing the signoff has verifiable permission from the
person who's name it is they are using. It would primarily be on the
IP address is not sufficiently rigourous to identify and individual or even
a location (TOR network and all that). It's routinely mis-used as such an
identifier. I don't see any benefit to adding it to Koha's outgoing
emails, since it cannot be relied upon, and it could put people at risk of
ill-
Umer,
There is no Koha 4.2; the highest version of Koha available right now is
3.8.2. It looks like you may have downloaded LibLime Koha (a fork of the
Koha project). I'd highly recommend you stick with the stable release as
available from http://koha-community.org/download-koha/, as LibLime Ko
Bug 8251 has also been a bit nasty, and is now passed QA.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8251
-Ian
On Wed, Jun 20, 2012 at 1:39 PM, Paul Poulain wrote:
> Le 19/06/2012 22:54, Melia Meggs a écrit :
> > Hi Koha developers!
> Hi Melia,
>
> > We have hundreds of libraries
Just bringing this back to original intent: it's hard for developers and
testers to work with patches that have DB revs, so we want to fix that.
Basically, that means being able to easily tell what changes have been made
to the DB beyond the natural Koha progression.
The problem with the code we
> This should never have been in the database. Also, there is a 1-1
> relationship between almost all the language tables. We should just have
> sort of configuration file with that information (maybe in YAML?). Also,
> using just one type of language code might be nice.
>
> * XSLT parsing. That's
I think we've got two issues here to resolve here:
1. some kind of asynchronous voting mechanism. We need to be able to
create arbitrarily many issues to vote on, with set opening and closing
datetimes. We also need some kind of mechanism for preventing spam or
other abuse. Personal
It would probably be best to take me off as default assignee for any
components, since I have little time for coding lately, and what time I do
have is going towards QA.
Cheers,
-Ian
On Mon, Jun 11, 2012 at 9:32 AM, Nicole Engard wrote:
> > On Sat, Jun 9, 2012 at 11:21 AM, Paul Poulain
> wro
Jared,
All you plans are most excellent, and I've been thinking about (and to some
limited capacity, discussing) them for a while now. I'm glad to see them
on the road to reality.
A couple comments:
About point 13, adding a "Did you mean?" feature... this should be done in
a way that applies t
ceilingDueDate and globalDueDate shouldn't be in your 3.8 system; they were
deleted as part of the database update that moved them to the circulation
matrix (issuingrules table).
You should be able to re-enter your rules in the Circulation and Fines
rules area under the Administration. You'll hav
Haik,
In this respect, Koha has 4 entities to keep track of:
1. The Biblio
2. Any Items attached to the Biblio
3. a Subscription attached to the Biblio
4. Serial issues for the Subscription (which can correspond to Items, if
you wish)
You can have multiple Subscriptions to a Bibl
To me, the role of QA is to be highly conservative. The QA team needs to
look at a piece of incoming code, and not only judge it on how well it does
it's intended purpose, but how it affects all the other code and workflows
that surround it. The folks creating and signing off on code are often
lo
I also favour "_id" in general... the underscore separates it out as an
identifier, and it's already this way in a large percentage of the database.
We need to be very careful, though, if we change any of the existing key
names, so that it not only doesn't break the Koha code, but also doesn't
bre
For my part, I tend to review patches textual to see if they make sense as
a changeset. If I cannot tell from reading what this patch does, I'll
either apply and test, or ask for clarification. Generally, both of those
actions take more effort than reading on Bugzilla, and thus take longer.
I ag
Bug 8072 is now Passed QA, and can be added to the 3.8.1 release at the
Release Maintainers discretion.
-Ian
On Thu, May 10, 2012 at 8:06 PM, Chris Cormack wrote:
> On 4 May 2012 23:09, Partha Mukhopadhyay wrote:
> > Dear all
> >
> > Thanks for a great new look (Staff interface in particular)
Chris,
If you don't specify the SCO user in the sysprefs, you have to manually log
in as that user on the workstations you are designating as SCO. This is
then subject to timeout, I believe.
So, if you don't mind maintaining the distinct logins on your workstations
manually, you're in good shap
es would come in.
-Ian
On Thu, May 10, 2012 at 11:53 AM, Paul Poulain wrote:
> Le 10/05/2012 17:04, Ian Walls a écrit :
> > Paul,
> >
> >
> > Creating a new table allows us to develop this in parallel and commit
> > progress incrementally without risking damage
Koha
namespace. I think building new would be better here than modifying what
we already have, since C4::Circulation is already pretty messy.
Cheers,
-Ian
On Thu, May 10, 2012 at 8:15 AM, Paul Poulain wrote:
> Le 10/05/2012 02:47, Ian Walls a écrit :
> > RFC up on the wiki:
> &
Thu, Mar 22, 2012 at 3:46 PM, Ian Walls wrote:
> Chris,
>
>
> I'm seeing the Contextual Preferences Engine (CPE) as a replacement to the
> issuingrules and related tables, first and foremost. It would be put in
> place, then be migrated into slowly over time by develop
I agree with Katrin; this is a very risky proposition and probably
shouldn't be added to the Koha codebase.
Not only is doing this securely hard, but it also makes the job of your
system support specialist much harder (speaking as a former professional
Koha support guy here). If you're in a situa
We haven't nailed this down with any finality as a community, but the
general idea is that when Solr search indexing is ready, we'll bump from
the 3.X line to 4.0. Hopefully, that will be soon, like April or Oct of
2013.
-Ian
On Tue, Apr 17, 2012 at 04:01, Chris Cormack wrote:
> On 17 April 20
Unless we're working with a small catalogue, or one with only a few popular
items, I'm not sure we'd get much benefit from caching the XSLT-processed
HTML for individual biblios. Outside of those cases, I don't think a lot
of people will be looking at the same records, so we're just storing info
u
Greg,
Answers in-line (as best I can), then some commentary.
On Thu, Apr 12, 2012 at 15:20, G. Laws wrote:
> 1. What does KUDOS stand for (the breakout of the acronym, if it is)? I
> presume Koha Users and Developers xxx xxx?
>
Legally (that is, in our founding documents), KUDOS doesn't stan
Marijana,
It'd be great to see Croatia! I don't think we have a strict rule about
KohaCon rotations (aside from not doing it in the same country within 3
years), rather just a convention/tradition of rotating continents westward
by roughly 6-8 hrs. By that rotation, we'd be due for the Americas
...and the other places with XMLout are patron and item card creation, and
the Syndetics external service. Dealing with those places another way
would reduce our dependency on XML::Simple by about half.
-Ian
On Wed, Apr 11, 2012 at 13:15, Ian Walls wrote:
> C4/ILSDI/Services.pm also uses
C4/ILSDI/Services.pm also uses XML::Simple to do output. Strings are
actually composed in the subroutines, making any changes to the schema a
C4-editing patch. Having an ILSDI template directory would serve us much
better here, I think.
-Ian
2012/4/11 Robin Sheat
> Op 11-04-12 23:31,
Right now, the few web services we have all create their XML output using
XML::Simple. This is not the fastest parser in the world, so I've been
looking to minimize/remove it's usage. Looking at it in /svc got me
thinking: perhaps we should be using T:T to generate our web services
output instea
yn SOMERS
> fridolyn.som...@gmail.com
> Marsillargues - France
>
>
> 2012/4/10 Ian Walls
>
>> I'd advocate ISO-2709 only being an import/export format, and never using
>> it internally. It's just got too many limitations, as we're seeing here.
>>
>&
I'd advocate ISO-2709 only being an import/export format, and never using
it internally. It's just got too many limitations, as we're seeing here.
On import, we check for valid leaders, and warn if not.
On export, we calculate the leader, and if it exceeds 9, we warn. We
can develop several
Everyone,
I was doing some thinking this weekend about the overall goal of making
Koha perform faster. We're approaching this from several different angles,
so I thought it might be a good idea to come up with a summary of all the
various methods we could use to speed Koha up.
Tuning & Hardware
Would it be practical and efficient to cache shared data to file (or a
series of files)? My understanding is that reading files is faster than
doing SQL queries, but not as fast as accessing memcached. But, the file
would have the advantage of being non-threaded. I don't think
configuration thin
Just a bump... we still need a Translation Manager (someone with a
non-English first language preferred), and specific module maintainers.
More bug wranglers are always welcome, too!
We have single candidates for the other single-person positions, which will
make the voting quite... limited. Anyo
Just a bump... we still need a Translation Manager (someone with a
non-English first language preferred), and specific module maintainers.
More bug wranglers are always welcome, too!
We have single candidates for the other single-person positions, which will
make the voting quite... limited. Anyo
Looking over the patches on the Equinox branch, it does seem that while
this is a significant feature in terms of it's meaning and utility, it has
very little impact on the existing code, and will sit benignly in the
corner until it is called upon.
One of the XSLTs for DOM authorities is moved so
w there is plenty of
literature on it's merits over MySQL, but how do those translate to
something that the users of Koha can benefit from?
Cheers,
-Ian
On Fri, Mar 23, 2012 at 13:48, Marc Balmer wrote:
> Am 23.03.12 17:23, schrieb Ian Walls:
> > According to rule SQL6 of our Codi
According to rule SQL6 of our Coding Guidelines (
http://wiki.koha-community.org/wiki/Coding_Guidelines#Database), backquotes
are not acceptable, as they are a MySQL-ism. Part of the duty of QA is to
verify that the coding guidelines are met, so it is reasonable to say that
such markings *should*
for a
long while, but other things (like testing Hourly Loans) have taken
priority recently. I'd love to have this in place for 3.10, to some degree
or another.
Cheers,
-Ian
On Thu, Mar 22, 2012 at 13:44, Chris Nighswonger <
cnighswon...@foundations.edu> wrote:
> Hi Ian,
>
Chris,
I've been meaning to write a Contextual Preferences Engine for Koha for a
while now, to solve the problems we have with the Circ Matrix, as well as
with global sysprefs that should really be more configurable.
The idea is that it will be a DB table with 5 main columns: Branch, Patron
Cat
Chris,
I've been meaning to write a Contextual Preferences Engine for Koha for a
while now, to solve the problems we have with the Circ Matrix, as well as
with global sysprefs that should really be more configurable.
The idea is that it will be a DB table with 5 main columns: Branch, Patron
Cat
Kyle,
I can see several use cases where this could be a desirable change... which
is your partner looking for?
1. The particular order was transferred from one vendor to an affiliate
vendor through some partnership process or relationship
2. The initial vendor was absorbed by another, e
The conference also overlaps with the Marseilles Hackfest, so lots of our
international community members will be out that way. So long as I've got
connectivity, I'll try to be on IRC, so we can stay virtually connected.
-Ian
On Thu, Mar 15, 2012 at 11:06, G. Laws wrote:
> I might have been i
We've run up against this problem a few times in recent history. Small
patches are easier to test, but harder to keep track of. Large patches
make our paperwork simpler, but are much harder to test, and one broken
aspect can delay many functional ones.
I think the first part of the solution is t
t to
update the index, and then restore back to master when you're done. If
you're tracing out lots of blames, then this can be a serious crimp in
workflow.
-Ian
On Thu, Mar 8, 2012 at 13:50, Chris Cormack wrote:
> * Ian Walls (koha.sek...@gmail.com) wrote:
> >Doing a large
Doing a large updating commit does not cost us any history. It just counts
as an "update" to the code, even though none of the logic has changed.
This change would alter SLOC counts and such, messing with our statistics,
since we only want to measure intellectually significant contributions
(tidyi
Paul,
Has the work on Shibboleth required a refactoring of C4/Auth? It's sorely
needed. Looking forward to testing it out!
-Ian
On Tue, Mar 6, 2012 at 08:04, Paul Poulain wrote:
> Le 06/03/2012 13:52, Tomas Cohen Arazi a écrit :
> > 2012/3/6 Fridolyn SOMERS :
> >> Hie,
> >> Development can
ulting
> carl.wiedem...@gmail.com | skype: c4rlww
>
>
>
> On Mon, Sep 26, 2011 at 11:04 AM, Ian Walls
> wrote:
>
> > Yup, for better or worse, I'll help shepherd this preconference along.
> > Anyone interested in sharing their knowledge and experience is welc
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>
--
Ian Walls
Lead Development Specialist
ByWater
ause of this
change. Discussion of additional fields to add can be put into separate
threads, for easy readability.
Cheers,
-Ian
On Sat, Jan 14, 2012 at 7:52 PM, Ian Walls
wrote:
> Everyone,
>
>
> As I mentioned in my previous thread about updating Bugzilla to better
> make use of
mails once
the changes are complete.
I'll try to be on IRC for the duration of this maintenance job, in case
anyone has any emergency questions.
Cheers,
-Ian
--
Ian Walls
Lead Development Specialist
ByWater Solutions
ALA Midwinter Booth #2048
Phone # (888) 900-8944
http://bywatersol
ha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>
--
Ian Walls
Lead Develo
lofwax.co.nz/2011/11/04/nice-visualisation-of-when-work-is-done-on-koha/
>
> Great graphics! :-D
>
> Late +1 for the proposal.
> To+
>
--
Ian Walls
Lead Development Specialist
ByWater Solutions
ALA Midwinter Booth #2048
Phone # (888) 900-8944
http://bywatersolutions.com
ian.wa...@b
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel>
>> website : http://www.koha-community.org/
>> git : http://git.koha-community.org/
>> bugs : http://bugs.koha-community.**org/<http://bugs.koha-community.org/>
>>
>
> _
Katrin
wrote:
> **
>
> > What do people think? Does this sound like a reasonable change to make?
>
> +1
>
--
Ian Walls
Lead Development Specialist
ByWater Solutions
ALA Midwinter Booth #2048
Phone # (888) 900-8944
http://bywatersolutions.
es to the Patch
Statuses; otherwise, we'll all get spammed to high heaven with meaningless
updates when the migration occurs.
What do people think? Does this sound like a reasonable change to make?
Any objections?
Cheers,
-Ian
-- Ian Walls
Lead Development Specialist
ByWater Solutions
ALA
users like the fact that the
> language index populates from 008 (chars 35-37), and 041adej
>
> ___
> Koha mailing list http://koha-community.org
> Koha@lists.katipo.co.nz
> http://lists.katipo.co.nz/mailman/listinfo/koha
>
>
>
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>
--
Ian Walls
Lead Development Specialist
ByWater Solutions
ALA Midwinter Booth #2048
Phone # (8
3 questions: don't break existing behaviour, do what it announces,
> consistent with existing feature & code. (double check if there can be a
> security issue !)
>
> --
> Paul POULAIN
> http://www.biblibre.com
> Expert en Logiciels Libres pour l'info-doc
> T
o
>> catalogue our library books. which are in Chinese and English. Does the
>> software support unicode searches and have multi-lingual support where I
>> can translate all the texts into Chinese?
>>
>> thanks
>> nancy
>>
>
>
--
Ian Walls
Lead Development Specialist
ByWater Solutions
ALA Midwinter Booth #2048
Phone # (888) 900-8944
http://bywatersolutions.com
ian.wa...@bywatersolutions.com
Twitter: @sekjal
gt; "Politeness and consideration for others is like investing pennies and
> getting dollars back." Thomas Sowell
>
>
>
> 2011/12/6 Ian Walls :
> > There is a system preferenece, AutoEmailPrimaryAddress, that determines
> > which email is used to send notices. O
all method "as_usmarc" on an undefined value at
> > /usr/share/koha/lib/C4/Search.pm line 2397. *
> >
> > But for the four digit copy numbers that i have entered I get the search
> > reult properly for the given copy number.
> >
> > I am using koha version 3.02.06.000 on Debian Squeeze
> > Please help m
ll help. Perhaps we should have an explanation somewhere in the wiki –
> but the current numbering is logical and has a lot of important information.
>
> -- Katrin
>
>
> From: koha-devel-boun...@lists.koha-community.org [mailto:
> koha-devel-boun...@lists.koha-community.org] On B
//www.software.coop/products/koha
> _______
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http:
enhancements, you remove this
> option.
>
> I maintain my opposition to not back-porting the db update changes.
>
> Kind Regards,
> Chris
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.ko
bin/perl Makefile.PL --testdb=test --testuser=test --testpass=test
> -- NOT OK
> Running make test
> Make had some problems, won't test
> Running make install
> Make had some problems, won't install
> Failed during this command:
> CAPTTOFU/DBD-mysql-4.020.tar.
p://mjr.towers.org.uk/email.html
> Available for hire for various work through http://www.software.coop/
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
>
1 - 100 of 376 matches
Mail list logo
