Public bug reported:
Essentially the same bug reported in #1875980 python3-pycodestyle has no
executable in /usr/bin or /usr/local/bin - Ubuntu 20.04, but affects the
python3 version of pep8.
$ apt-cache policy python3-pep8
python3-pep8:
Installed: 1.7.1-9ubuntu1
Candidate: 1.7.1-9ubuntu1
V
Opened analogous bug for python3-pep8:
#1958081 python3-pep8 has no executable in /usr/bin or /usr/local/bin - Ubuntu
20.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875980
Title:
python3-pyc
Public bug reported:
The package/program `age` is listed as 'simple, modern and secure
encryption tool'. The name implies that it is time related, which is
confusing.
** Affects: age (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
Public bug reported:
The program wx-config is used to output library and build file
information; it's often used in Makefiles, e.g.
CXXFLAGS+=-Wall -fsigned-char `wx-config --cppflags` -I../jmlib
The call to
wx-config --cppflags
should return
-I/usr/include/wx-3.0/
Without this,
Public bug reported:
when running
sudo do-release-upgrade
I got an error message requesting that I run ppa-purge (I'm afraid that
I no longer have the exact text of the error message). There was
additional text that suggested looking at the contents of /var/log/dist-
upgrade/main.log and /va
Public bug reported:
I have both `csvkit` and `csvkit-doc` installed on my Ubuntu 18.04.2
(Bionic) install.
The installed version is `csvkit 1.0.2-1`
There are no man pages available for csvkit or any of its executables
(csvclean, csvcut, csvformat, csvgrep, csvjoin, csvjson, csvlook, csvpy,
csv
Another possibility would be to create a branch for the sip machines that
had different issuing rules.
On Wed, Apr 10, 2019 at 10:03 PM Mason James wrote:
> hi folks
>
> does anyone have any advice for restricting some Koha item-types from
> being circulated (issued/returned) via a 3M self-check
Another possibility would be to create a branch for the sip machines that
had different issuing rules.
On Wed, Apr 10, 2019 at 10:03 PM Mason James wrote:
> hi folks
>
> does anyone have any advice for restricting some Koha item-types from
> being circulated (issued/returned) via a 3M self-check
Mihai,
A staff user (i.e. a user with 'circulate' permissions) needs to log in to
sco-main.pl in order to make it available to the public.
Once available, there is a system preference called 'SelfCheckoutByLogin'
which can be set to allow users to log in using either 'Username and
Password' or 'C
Here's how to do it using SQL:
SELECT
ExtractValue( metadata, '//datafield[@tag=650]/subfield[@code="a"]' )
as 'Topical term',
biblionumber,
title
FROM
biblio
INNER JOIN biblio_metadata using (biblionumber)
WHERE
ExtractValue( metadata, '//datafield[@tag=650]/subfield[@code="a"
ubuntu)
> But the plan is to fix them, when we have time of course. We could
> maybe make that a push at the hackfest, or kohacon :)
>
> Chris
>
> On Wed, 20 Mar 2019 at 12:14, Barton Chittenden
> wrote:
> >
> > Explainshell.com is a very nifty site that will
Explainshell.com is a very nifty site that will parse the man pages that
they know about, and then tell you what a given command line does.
For example, given the command line
yaz-marcdump -i marc -o marc -f utf-8 -t marc8 -l 9=20 filenametoconvert.mrc
Explainshell will tell you what the -i, -o,
ber=biblioitems.biblioitemnumber)
> LEFT JOIN biblio ON (biblioitems.biblionumber=biblio.biblionumber)
> WHERE items.dateaccessioned BETWEEN <> AND
> <>) AS t
> WHERE Subject LIKE concat('%',<>,'%')
> ORDER BY dateaccessioned DESC
>
> No erro
The data formerly found in biblioitems.xml moved to
biblio_metadata.metadata in Koha 17.05.
On Tue, Mar 19, 2019, 3:10 AM Mohammad Nashbat
wrote:
> Sorry, below is the correct one.
>
> SELECT *
> FROM(SELECT
> items.dateaccessioned,
> items.barcode,
> items.itemcallnumber,
> bibl
Chad,
One way to do it would be to compare filled holds to circulation. That gets
a bit murky because there's no direct link between the old_reserves and
issues tables - the best you can do is compare borrowernumber, item number
and then look at date_issued and old_issues.timestamp.
On Wed, Mar 1
One of the kinds of reports that we get asked for periodically is 'Items
that were owned by the library within a date range' -- essentially, the
library want to know if the accession date is before the end of the date
range, and the deletion date (if there is any) is after the beginning of
the date
On Mon, Feb 25, 2019 at 6:51 AM Chris Cormack
wrote:
>
> Whatever they are changed to needs to be translatable.
>
Agreed. I suspect that the trade-offs between 'We would like this to be
translatable' and 'we need these values to be un-editable' (I.e. not
authorized values) are probably what's ke
The accounts system uses the following codes to show what kind of fee or
credit has been issued:
A = Account management fee
C = Credit
F = Overdue fine
FOR = Forgiven
FU = Overdue, still accruing
L = Lost item
LR = Lost item returned/refunded
M = Sundry
N = New card
PAY = Payment
W = Writeoff
The
I'm missing the thread somehow, I don't think that will work as
> the prior conditions for all 3 branches are still present in the WHERE
> statement.
>
> If we eliminate those, then we still need to include the acquisition
> date condition somehow.
>
> Thanks,
>
+1
On Fri, Feb 22, 2019 at 9:29 AM Tomas Cohen Arazi
wrote:
> Great!
>
> El vie., 22 feb. 2019 a las 11:27, Jesse Maseto (<
> je...@bywatersolutions.com>)
> escribió:
>
> > The Koha community is proud to announce the release of 18.05.09.
> >
> > This is a maintenance release and contains many bu
you could add
count(distinct homebranch) > 1
to your HAVING statement
On Fri, Feb 22, 2019 at 9:03 AM Cab Vinton wrote:
> Hi, All --
>
> We have a report (see below) that generates a random list of items
> held by all 3 of our branches & purchased within the past 30 days.
>
> To generate more
This was added in 18.05.
There is a way to fudge it using SQL variables, but it's such a pain to
write that you're better double-entering the values until you can upgrade
to 18.05.
if you *are* using 18.05, then you'll just need to make sure that whatever
you want repeated, e.g. BETWEEN <> AND <>
note that the format should be
--format=csv
(comma separated values) not
--format=cvs
On Mon, Feb 18, 2019 at 9:33 AM Alvaro Cornejo
wrote:
> Hi
>
> You need to specify all time fields in your command. If you do not want to
> specify one, you must insert an *
>
> Time fields are
> [minut
Suresh,
Unfortunately, there's not a great way to do this -- the problem is that
repeated tags in marcxml are extracted as a single value by ExtractValue.
Here's what the Koha wiki has to say in the matter:
Note that ExtractValue concatenates multiple tags into a single field.
These can be indivi
Could we create a warning for this on the triggers page, or put something
in About > System Information?
I don't run across this very often in support, but when I do, It's always a
facepalm.
On Fri, Dec 14, 2018 at 6:35 AM Katrin Fischer
wrote:
> Hi Sonia,
>
> I think adding the homebranch coul
I will, forever after, congratulate the release manager on every release,
having seen the process (at least second hand).
Awesome job.
--Barton
On Wed, Nov 28, 2018 at 8:31 AM Amit Gupta wrote:
> Congrats Nick.
>
> On Wed 28 Nov, 2018, 6:51 PM Tomas Cohen Arazi wrote:
>
>> Congrats Nick and a
Is there any way to change the default statuses on the bugzilla advanced
search page? https://bugs.koha-community.org/bugzilla3/query.cgi
The default statuses searched are NEW, REOPENED and ASSIGNED... which skips
bugs that are 'In Discussion', 'Needs Signoff', 'Signed off', 'Passed QA',
'Pushed f
uot;
> cataloguing.
> >>It has been removed in Koha ??? (2.2 or 3.0 ?), only MARC cataloguing
> >>remained.
> >>At this time biblioitems table became useless/should have been
> merged,
> >>but no one coded/hacked it. But yes, it can be remov
Nov 2018 at 15:22, Katrin Fischer
> wrote:
>
>> Hi,
>>
>> I feel if we want one source of truth besides the source code, it would
>> make sense to submit patches to the manual directly instead of adding more
>> documentation outside of it. Adding a POD file wi
The field guide is based on the wiki page, which I maintained... but I
think that developers should be documenting any notices they add, which is
why I've added this to the agenda for Wednesday's dev meeting:
*Review of coding guidelines*
- Proposed coding guideline DOC2: Entries in the *lette
Koha doesn't currently have a single point of truth for documentation of
notices and slips, which has lead to a proliferation of markup syntaxes,
especially in regard to repeating detail, e.g.
DUEDGST/PREDUEDGST:
<>
ODUE*
<>
or
CHECKOUT/CHECKIN/RENEWAL
Detail here
---
Just out of curiosity, why does biblioitemnumber exist? There should be a
one-to-one relationship between biblio records and biblioitem records ...
so why not use biblionumber as the primary key for biblioitems?
--Barton
___
Koha-devel mailing list
Koha-
Anabela,
QueryFuzzy and ICU Chains don't work well together. If your collection
contains many non-latin characters or diacritics, you probably have ICU
chains enabled, and QueryFuzzy won't work -- it also affects sort by
relevance, so in a large result set, you won't be able to find your results.
Actually, if you have Zebra facets enabled, turn them *off*. I believe that
they're enabled by default, and they're dog slow.
Zebra is *very* disk IO intensive. Make sure that its temporary directory
is being written to the fastest drive you have.
If you have the QueryFuzzy or QueryStemming syste
I'm guessing that this could be fixed using template toolkit in the notice,
but I don't know the syntax off hand.
On Wed, Oct 24, 2018, 6:38 AM Holger Meissner <
holger.meiss...@hs-gesundheit.de> wrote:
> Dear koha devs,
>
> when we send an order by email <> is formatted with
> decimal point and
I'm not a big fan of items.onloan... If you want to check item
availability, use the checkouts API.
...and then I realized that there's no route for items in the checkouts API.
On Tue, Oct 23, 2018, 6:07 AM Josef Moravec wrote:
> Hello developers,
>
> Me and Michal Denar were thinking a bit abo
On Mon, Oct 22, 2018 at 3:39 PM Liz Rea wrote:
> The term bibliographic number is easily confused with "inventory number"
> and any local or old internal record numbers that migrated MARC may have.
>
Agreed, bibliographic number is confusing.
>
> I think the most accurate long form representa
On Mon, Oct 22, 2018 at 10:14 AM Owen Leonard wrote:
> > I'm starting with looking for instances of 'biblio', which should be
> 'Bibliographic record'.
>
> Hopefully Bug 19833 took care of (most of?) them.
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19833
I found a dozen or so i
I've been looking at the Koha terminology page (
https://wiki.koha-community.org/wiki/Terminology). There are still a
handful of occurrences of incorrect terminology throughout the '.tt' files.
I'm starting with looking for instances of 'biblio', which should be
'Bibliographic record'.
I'm wonder
; Bug 21150 - Data inconsistencies - item types
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21150
>
> It can also check for false authority types, and missing holdingbranch and
> homebranch in items. More could be added to it.
>
> Hope this helps,
>
> K
rogress bar not updating, and allow
use of plack for Stage MARC Import
On Thu, Sep 20, 2018 at 5:02 PM Barton Chittenden <
bar...@bywatersolutions.com> wrote:
> Tomas,
>
> Do you know if there's a bug open for this? If not, would you mind filing
> one?
>
> Thanks,
>
The transport cost matrix is used to determine which libraries will fill
holds at other libraries. I think it may require that the holds queue cron
job be running periodically.
On Tue, Oct 2, 2018, 11:20 AM anjoze wrote:
> Yes, its on.
> What should I expect with transport cost matrix enabled?
>
I think you could use the transfer cost matrix for this -- set the transfer
costs among the school libraries to 0, and between the public and school
libraries to infinity.
On Mon, Oct 1, 2018, 11:48 AM anjoze wrote:
> Hi again.
> I have the fallowing scenario:
>
> 1 Koha instance
> 1 Public Libr
When ByWater started upgrading our partners to 17.11 last spring, I noticed
that we were getting a lot of errors of the form
"can't call method * on an undefined value at ..."
We're starting to see these errors because more and more of our code uses
Koha objects, and these will fail if a method i
not timeout.
>
> El mié., 19 de sep. de 2018 20:04, Barton Chittenden <
> bar...@bywatersolutions.com> escribió:
>
>> On Wed, Sep 19, 2018 at 6:29 PM, Jonathan Druart <
>> jonathan.dru...@bugs.koha-community.org> wrote:
>>
>> > Hi Barton,
>> &g
On Wed, Sep 19, 2018 at 6:29 PM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:
> Hi Barton,
>
> > I believe this typically happens under plack.
>
> These scripts should not run under plack, check your apache config file
> (search for "ProxyPass" in apache-shared-intranet-plack.
Hi, All!
At ByWater, we've had a few reports of
"Home › Tools › Stage MARC records for import" timing out on large import
batches, with the message "there was an error."
When this happens, there are typically two batches under
Home › Tools › Manage staged MARC records
The first batch will show
On Wed, Sep 19, 2018 at 4:42 AM, Michael Kuhn wrote:
> Hi Stephan
>
> > maybe I'm blind, but I can't find the button to merge records. The
> > manual says to search for a record, select the ones you want to merge
> > and click the Button "Merge selected" at the top. But I don't see that
> > butto
11:49 AM, Tomas Cohen Arazi
wrote:
> It seems 18.04 includes 2.0.59:
>
> https://packages.ubuntu.com/bionic/idzebra-2.0
>
> It requires the 'universe' repo active.
>
> El mar., 28 ago. 2018 a las 12:44, Barton Chittenden (<
> bar...@bywatersolutions.com>) escr
As of debian jessie / Ubuntu 16.04 (xenial), I think idzebra-2.0 should be
at 2.0.62 or 2.0.63.
There are known bugs in 2.0.59 which is the default for debian jessie
and Ubuntu 16.04, so you'll need to use indexdata's repos for those.
I don't know what the version is for Ubuntu 18.04, but 2.0.44
Cab++
On Fri, Aug 17, 2018 at 8:17 AM, Cab Vinton wrote:
> On Thu, Aug 16, 2018 at 4:47 PM, Barton Chittenden
> wrote:
> > Cab, would you mind adding that to the 'Catalog/Bibliographic Reports'
> > section of the Koha wiki?
>
> Done! --
>
&
gt; Plaistow Public Library
>
>
> On Thu, Aug 16, 2018 at 9:48 AM, Barton Chittenden
> wrote:
> >
> >
> > On Tue, Aug 14, 2018, 11:29 AM Cab Vinton wrote:
> >>
> >> Hi, All --
> >>
> >> We're using the following report to identify
On Tue, Aug 14, 2018, 11:29 AM Cab Vinton wrote:
> Hi, All --
>
> We're using the following report to identify records w/ duplicate ISBNs.
>
> SELECT GROUP_CONCAT(b.biblionumber SEPARATOR ', ') AS biblionumbers,
> b.title, b.author, GROUP_CONCAT(i.isbn SEPARATOR ', ') AS isbns
> FROM biblio b
> L
Oh, I meant to give a link to the ccl.properties in github as well:
http://git.koha-community.org/gitweb/?p=koha.git;a=blob_plain;f=etc/zebradb/ccl.properties;h=a1ea690c43ef347ebfdd409c51299bdb9cf32777;hb=HEAD
On Tue, Aug 14, 2018 at 9:48 AM, Barton Chittenden <
bar...@bywatersolutions.com>
On Mon, Aug 13, 2018 at 9:52 AM, Caroline Cyr-La-Rose <
caroline.cyr-la-r...@inlibro.com> wrote:
>
> In the manual, there is a kind of mapping section for searches that gives
> you the indexes for each marc field: https://koha-community.org/man
> ual/18.05/en/html/searching.html#koha-search-indexes
soon that incorporates this.
On Sat, May 26, 2018 at 4:58 AM, Katrin Fischer
wrote:
> I don't know about other sources, but in Germany I've never encountered
> data where the numbers in $w minus MarcOrgCode don't match the one in 001.
> Maybe this problem is just specific to
I'm pretty sure that I've seen Heather up-shift, down-shift and
double-clutch her pearls, which I suspect individually milled from high
carbon steel and inspected daily with a micrometer for wear. ;-)
On Thu, Jul 26, 2018 at 5:38 PM, Heather Hernandez <
heather_hernan...@nps.gov> wrote:
> Hi, Kel
Yeah, that should be super-easy to do. If I'm not mistaken, SVG can be
manipulated via CSS, so it might be as easy as giving a class to each
section in the drawing that represents a shelving location. For a given
item, you'd read items.location, and then change the color for that class.
As long as
I agree entirely about the duplication, I'm not a fan.
I think that someone had filled in the template with a real report; I
edited it and made it generic:
https://wiki.koha-community.org/wiki/SQL_Reports_Library#SQL_Report_Template
On Sat, Jul 21, 2018 at 2:19 PM, Cab Vinton wrote:
> > If you
I agree entirely about the duplication, I'm not a fan.
I think that someone had filled in the template with a real report; I
edited it and made it generic:
https://wiki.koha-community.org/wiki/SQL_Reports_Library#SQL_Report_Template
On Sat, Jul 21, 2018 at 2:19 PM, Cab Vinton wrote:
> > If you
On Fri, Jul 20, 2018 at 4:21 PM, Cab Vinton wrote:
> Hi, All --
>
> All Holds, Patrons, & Circulation reports have been copied over from
> the main wiki reports page to the appropriate dedicated page.
>
> I believe it should now be safe to delete these sections from the main
> page (sections 2, 3
On Fri, Jul 20, 2018 at 4:21 PM, Cab Vinton wrote:
> Hi, All --
>
> All Holds, Patrons, & Circulation reports have been copied over from
> the main wiki reports page to the appropriate dedicated page.
>
> I believe it should now be safe to delete these sections from the main
> page (sections 2, 3
te ...
>
> So my initial thought is to just proceed w/ these relatively trivial
> edits to the wiki. Will certainly hold off, though, if there's
> consensus that it's a waste of time :-)
>
> Cheers,
>
> Cab
>
>
> On Thu, Jul 19, 2018 at 9:56 AM, Ba
te ...
>
> So my initial thought is to just proceed w/ these relatively trivial
> edits to the wiki. Will certainly hold off, though, if there's
> consensus that it's a waste of time :-)
>
> Cheers,
>
> Cab
>
>
> On Thu, Jul 19, 2018 at 9:56 AM, Ba
On Fri, Jul 20, 2018 at 8:07 AM, Tomas Cohen Arazi
wrote:
> Maybe run the QA script should be one of them?
+1
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website :
Cab,
the reports wiki is in a state of benign neglect, because of development of
_mana_, which will create a way for reports to be shared to and imported
from a central server.
See
https://wiki.koha-community.org/wiki/Recommendation_engine_integrated_with_Mana_project_RFC
https://wiki.koha-comm
Cab,
the reports wiki is in a state of benign neglect, because of development of
_mana_, which will create a way for reports to be shared to and imported
from a central server.
See
https://wiki.koha-community.org/wiki/Recommendation_engine_integrated_with_Mana_project_RFC
https://wiki.koha-comm
On Wed, Jul 18, 2018, 5:14 AM Martin Renvoize <
martin.renvo...@ptfs-europe.com> wrote:
> European Southern Observatory have been doing this for as long as I can
> remember.
>
>
> https://eso.koha-ptfs.eu/cgi-bin/koha/opac-detail.pl?biblionumber=121769&query_desc=callnum%2Cphr%3A%20A%2014-1
Mart
Nate says this was done using 'stackmap'.
On Tue, Jul 17, 2018 at 4:50 PM, Barton Chittenden <
bar...@bywatersolutions.com> wrote:
> Cab,
>
> Apparently not impossible:
>
> https://hartford.waldo.kohalibrary.com/app/work/141581
>
> I don't know
Cab,
Apparently not impossible:
https://hartford.waldo.kohalibrary.com/app/work/141581
I don't know any details of the implementation, though.
--Barton
On Tue, Jul 17, 2018 at 3:44 PM, Cab Vinton wrote:
> Wonder how hard it would be implement something like this in Koha:
>
> http://tallons.l
There are a couple of good open source drawing packages that should be
available on Windows, Mac or Linux:
OpenOffice has a package called 'draw' that works quite well
For vector graphics, I would look at inkscape: https://inkscape.org/en/
On Mon, Jul 16, 2018 at 12:40 PM, jeff haskell
wrote:
I'm going out on a limb here, I think that Teresa might be referring to a
print slip that wraps around a book. If so, this could probably be done
with the HOLD_SLIP and some CSS.
On Mon, Jul 9, 2018 at 7:17 PM, Katrin Fischer
wrote:
> Hi Teresa,
>
> I am not familiar with the term "holds wrapp
Wow, that's a really interesting question -- I think you're right, if the
patron is going to get a notice, the'll get debarred if one of their
overdues triggers the notice, regardless of their relationship to the
branch.
On Tue, Jul 10, 2018 at 5:19 PM, Cab Vinton wrote:
> Re: using the notic
On Fri, Jul 6, 2018, 9:41 AM Cab Vinton wrote:
> On Thu, Jul 5, 2018 at 5:45 PM, Barton Chittenden
> wrote:
> > Another possibility would be to use the message triggers and
> automatically
> > suspend patrons on their last notice.
>
> Ah, that's an interestin
Another possibility would be to use the message triggers and automatically
suspend patrons on their last notice.
On Thu, Jul 5, 2018 at 3:49 PM, Cab Vinton wrote:
> Hi, All --
>
> We've used the noissuescharge setting in the Circulation preferences
> to prevent patrons from checking items out wh
Congratulations!
I have to say, I got goosebumps when I saw
Results of search for 'juggling' with limit(s): 'suppress:0'
rather than
Results of search for 'kw,wrdl: juggling'
Cheers,
--Barton
On Fri, Jun 29, 2018 at 3:16 PM, Nicolas Legrand
wrote:
> thank you Tomas ^^
>
> 2018-06-29 17:42
We ran into an unpleasant little bug upon upgrade of one of our servers --
patron quicksearch on the main search bar of members.pm causes a software
error for non superlibrarian staff.
The bug only occurs if independent branches is enabled, which is why it
wasn't caught earlier. Nick wrote a one-l
It would be useful for Koha to have a 'Deprecated' function, which would
send a warning about the caller() function and the version of Koha where
the function will be deprecated, and what it will be replaced by... so
let's say that C4::Adequate::DoEET() is being replaced by
Koha::Awesome->sauce().
tatus : NEW
On Sat, Jun 16, 2018 at 3:32 PM, Barton Chittenden <
bar...@bywatersolutions.com> wrote:
> Very interesting!
>
> Thanks for the link.
>
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koh
Very interesting!
Thanks for the link.
___
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://git.koha-community.org/
bugs
On Sat, Jun 16, 2018 at 2:37 AM, Michael Kuhn wrote:
>
> Dewey Decimal Classification uses characters that indeed do look like
> Arabic numbers (standing for classes, divisions, sections), but these
> characters do not behave like numbers, so the correct sorting is actually
> not as you would exp
The documentation for GetClassSortKey says
* Concatenates class and item part.
* Converts to uppercase.
* Removes leading and trailing whitespace and '/'
* Separates alphabetic prefix from the rest of the call number
* Splits into tokens on whitespaces and periods.
* Leaves first digit group as is
This is an old issue that's never really been addressed. As I understand
it, at one time, we had a tool that used the unix 'at' scheduler to run
requested reports. This was a huge security hole, and we disabled it
and it's never worked since.
As such, those who host servers must add calls to r
On Wed, Jun 13, 2018 at 3:07 PM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:
> Hi Barton,
>
> Yes, and no. It depends.
>
... the dark side of TMTOWTDI ;-)
I read through your examples, they all made good sense.
Basically, we should avoid indentation blocks (if ( defined $i
Calling a method or accessing a member of an undefined object will throw a
fatal error that looks like this: "can't call method * on an undefined
value at ..."
For example, this code will cause a software error if $data->{itemnumber}
exists, but the item doesn't exist (maybe it's been deleted?):
I haven't run into that.
What version of Koha are you using?
What information is in the template and layout?
What happens when you export as CSV?
On Wed, Jun 13, 2018, 7:57 AM Ari wrote:
> Hi guys,
>
> I am trying to print off some labels for some books. I have set the correct
> label templat
Yes, that's the one. Thanks!
On Tue, Jun 12, 2018 at 7:31 AM, Magnus Enger wrote:
> On 6 June 2018 at 15:17, Barton Chittenden
> wrote:
> > This is not currently possible, but if you check the bywatersolutions
> > github page, you can find a plugin called 'k
Cab,
I assume that you were talking about the 'Runtime Variables' section of the
wiki:
https://wiki.koha-community.org/wiki/SQL_Reports_Library#Runtime_Variables
... Nick, Jesse (pianohacker) and I have all played with this at one time
or another, and I think that our consensus was that trying t
This is not currently possible, but if you check the bywatersolutions
github page, you can find a plugin called 'koha-plugin-reports-plus', or
something similar (on mobile, or I'd link to it). That plugin will allow
you to add a parameter that lets you enter a list.
On Wed, Jun 6, 2018, 07:38 ksor
+1
On Mon, Jun 4, 2018 at 2:20 PM, Katrin Fischer
wrote:
> +1 !
>
> :)
>
>
> On 04.06.2018 18:27, Séverine Queune wrote:
>
> I like that one !
>
> 2018-06-04 18:10 GMT+02:00 Owen Leonard :
>
>> If there is consensus that the add/edit buttons should be in line with
>> the section headings:
>>
>>
ot;; xmlns:kohaidx="
http://www.koha-community.org/schemas/index-defs
" type="update" z:id="1">
a
m
I've attached /etc/koha/marc21-retrieval-info-bib-dom.xml
On Mon, Jun 4, 2018 at 11:27 AM, Barton Chittenden <
bar...@bywatersolutions.com> wrote
I'm trying to trouble-shoot an error with the 'arp' index (accelerated
reading point -- indexed at 526$d).
I'm searching for
arp:14
In the staff client and opac and getting no results.
I added 'request' to zebra_loglevels in $KOHA_CONF and found the following
error:
09:30:50-04/06 zebrasrv
I like screenshot #2; It manages to be more compact *and* it feels less
cluttered, which is all win as far as I'm concerned.
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-de
Jan,
Do you have console access to the *Koha* server?
If so, log in there, and assuming that you are running a package install of
Koha, you can run
sudo koha-list
This will tell you which instances of koha are installed (unless you've
gotten fancy, there will only be one)
Then you can run
sud
On Thu, May 24, 2018 at 3:34 PM, Katrin Fischer
wrote:
> Hi Barton,
>
> Control-number is the index on 001. 001 should have the number and 003 the
> MarcOrgCode, that's why it's stripped from $w for search. I don't know
> about OCLCs practices, so can't tell how numbers are handled there. The
> e
On Fri, May 25, 2018 at 11:36 AM, Barton Chittenden <
bar...@bywatersolutions.com> wrote:
>
>
> In terms of the error message that you're seeing, MARC::File::XML isn't
> actually part of the Koha distribution, which makes it difficult to tell
> what's happenin
Markus,
First, welcome to the Koha community. There's also a German mailing list,
Katrin or Mirko can point you in the right direction if you're more
comfortable _mit Deutsch_ although your English seems quite good.
In terms of the error message that you're seeing, MARC::File::XML isn't
actually
I'm working on generating links for 7XX linking fields in XSLT, a-la Bug
15140 - Add MARC21 776 to OPAC and staff display (
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15140).
This Takes the 773$w, and uses the XSLT template 'extractControlNumber'
which strips the leading MARCOrgCode
On Sat, May 19, 2018 at 6:20 PM, Katrin Fischer
wrote:
> Hi Manos,
>
> it's an item field, so it's added for every item in 952/955.
>
> As the complete items information is added on time of indexing, I think
> what Barton suggests is already the case?
>
That's my understanding.
For background:
One of my first trouble-shooting experiences with Koha involved a report of
search results where an item was showing as 'available', but the detail
showed it checked out to a patron. Some helpful bywaterian pointed me to
items.onloan, and issues.date_due, and showed me that they didn't match. A
dat
1 - 100 of 327 matches
Mail list logo
