►
Description
00:14:18 Heather (she/her): Koha IRC info: https://koha-community.org/get-involved/irc/
00:17:00 George Williams - NEKLS: Yeah, cancelling the hold doesn't cancel a transfer that's already been initiated.
00:17:20 Andrew Fuerste-Henry: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25426
00:24:55 Andrew Fuerste-Henry: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28841
00:25:43 Andrew Fuerste-Henry: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30411
00:25:58 Andrew Fuerste-Henry: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29079
00:26:16 Rebecca Coert - APL: Yes George! That's a great idea1
00:33:25 Christie: Can someone post a link to the meeting agenda in the chat? I am unable to access Google Docs....
00:33:37 Andrew Fuerste-Henry: https://docs.google.com/document/d/147fWoAR9z7gafThOB8WYaczi5gUc9ka-EXS1bapI6V0/edit
00:36:37 Juliet Heltibridle: I also have a Lisa who I leave the Aspen problems to.
00:37:06 Andrew Fuerste-Henry: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7972
00:38:08 Heather (she/her): The syspref to turn on the "Most Popular" search is OPACTopIssue, https://koha-community.org/manual//21.05/en/html/opacpreferences.html?highlight=most%20popular#opactopissue
00:38:39 Andrew Fuerste-Henry: https://github.com/Koha-Community/Koha/tree/master/misc/cronjobs
00:51:41 Andrew Fuerste-Henry: https://wiki.koha-community.org/wiki/Community_Roles#22.11_Team
00:56:45 Heather (she/her): Good thing you'll share the report on the Wiki, then, George!!:)
00:57:13 Dwight Walker: please share that SQL on wiki
00:57:34 Juliet Heltibridle: https://pastebin.com/Y2N8VvUW
00:57:40 Heather (she/her): Please also share it on the Wiki, Juliet!
00:57:59 George Williams - NEKLS: Here's a link to the circ by list name report
00:57:59 George Williams - NEKLS: https://paste.nomagic.uk/?3af0b27a4e2470b2#F3DedmmEbJtBBxY4u2i9LmSsqtT7hKawo4XkaMzFwZCo
00:58:49 Dwight Walker: great script - thanks
01:02:34 Heather (she/her): Thanks, everyone!
01:02:35 Daphne Hoolahan: Thanks Andrew
01:02:37 Dwight Walker: what is email for agenda?
01:03:30 Andrew Fuerste-Henry: https://koha-us.org/special-interest-groups/
A
Okay,
now
officially
for
the
recording,
hey,
it's
kohai,
Sig
time.
Let's
talk
about
systems
Administration,
so
yeah
I've
got
a
whole
bunch
of
bugs
to
go
through
I.
Don't
know
that
we
have
a
lot
of
discussion
to
have
about
each
one,
but
we
most
of
what
we
did
at
that
last
meeting
was
kind
of
build.
A
list
of
bugs
people
were
excited
about,
so
I
thought
it
might
be
worth
having
some
follow-up
conversation
there,
but
before
I
do
that?
B
C
E
E
Hi
I'm
Heather
and
I'm
the
technical
services
librarian
at
San,
Francisco,
Maritime,
National,
Historical
Park
we're
a
special
Museum
collection,
supported
by
Bywater,
Solutions
and
I.
Do
lots
of
cataloging
and
whatever
assisted
Min
things.
I
can
do
and
I
joined
late,
so
I
don't
know
who
to
pass
it
to.
D
Hi
I'm
Daphne
Houlihan
I'm
from
in
K
technology
in
Ireland
I'm,
the
sport
manager
here,
so
we
support
all
our
users
in
Ireland
and
do
the
training
and
I
love
this
group,
because
I
try
to
get
ahead
of
bugs
that
we
haven't
encountered
yet
or
the
you
know,
good
reports
that
you're
coming
out
and
then
I
pass.
Some
offers
right
ideas
over
here.
E
I
have
my
own
library
of
three
and
a
half
thousand
books.
My
father
had
a
large
Library,
so
I
used
it
to
research,
a
book.
You
wouldn't
tell
us
what
he
did
so
I
guess:
cataloged
everything
but
yeah
I
find
there's
some
system
and
administration
issues
that
this
may
be
good
for
and
I
do
Linux
service
stuff
like
in
store,
koha
and
imported
records
from
a
resource
mate,
which
was
hard
but
yeah
I,
went
to
the
cohacron
so
and
then
I
have
this
thing
in
my
calendar.
E
F
A
E
A
A
A
A
A
A
This
is
for
like
floating
items
right
now.
You
said
in
your
circles
at
check-in
whether
an
item
should
stay
where
it
got
checked
in
or
go
back
home,
but
that
rule
at
point
of
check-in
always
gets
enforced
based
on
the
items
Home
Library,
rather
than
caring
about,
where
you're
actually
doing
that
check-in
so
exciting
thing
to
get
fixed.
The
thing
that
I've
run
into
this
with
is
libraries
that
want
to
have
a
branch
that
is
their
central
processing
area.
A
So
like
we
have
a
library
that
is
tech
services
and
everything
that
gets
checked
in
at
tech
services
needs
to
Route
off
someplace
else.
Nothing
actually
lives
at
that.
Branch,
there's
not
really
a
way
to
accomplish
that.
Until
this
bug
gets
pushed
but
yeah
good
news
is
it
past
QA,
so
it
should
be
coming
into
Masters
soon
knock
on
wood.
E
E
C
So
we've
noticed
that
when
we
we're
in
a
consortia-
and
we
ship
things
between
the
library,
if
something
is
on
hold-
and
you
check
it
in
and
it
shifts
to
another
Branch,
but
then
you
cancel
that
hold
and
you
try
and
check
it
back
in
at
its
Home
Library.
We
still
own
the
item.
It's
still
Co-op
still
wants
you
to
ship
it
to
the
library.
F
If
I,
if
I,
if
I
check
it
in
then
it
recognizes
the
holds
not
there
than
it
wants
to,
you
know,
remove
that
I
think
I
haven't
tested
it
in
a
while,
but
I
don't
think
we
have
that
issue.
I
think
it's
related
to
one
of
the
system
preferences,
but
off
the
top
of
my
head,
I,
can't
think
of
which
one
it
has
to
do
with.
E
F
C
C
C
E
A
E
A
F
A
Oh
yeah,
the
claims
returned
warning
threshold.
If
your
Patron
has
more
than
this
many
claims
put
the
big
Angry
note
on
their
their
account
at
checkout.
This
bug
is
to
make
it
possible
for
that
threshold
to
only
count
unresolved
claims
which
makes
sense.
We
don't
need
to
get
them
in
trouble
for
stuff
that
ultimately
was
resolved.
D
Yeah
I
mean
we
just
we
have
so
many
patrons
that
have
hundreds
of
claims
returns,
especially
if
it
had
kids
books
and
when
we
look
at
the
counters
we're
like.
Oh
my
gosh.
This
is
a
really
bad
picture
and
then
you
realize
99
of
them
are
resolved
and
you're
like
oh
well.
No,
it's
really
on
us
so
yeah.
Anything
with
improving
the
claims
return
function
would
be
much
appreciated
good
morning.
D
A
E
Right
so
just
just
the
previous
one,
I
had
an
idea.
Why
don't
kind
of
rolls
back
to
the
old
Old
Branch?
You
know
that
earlier
one
you
had
goes
to
the
wrong
one.
It
like
keeps
going
forward.
Maybe
it
should
like
what
they
call
rollback.
You
just
have
a
setting
draw.
The
logic
will
say
if
it's
canceled
also
pushes
it
back
to
the
other
Branch,
rather
than
not
changing
the
branch,
there's
something
it's
like
because
yeah
when
things
breaking
databases,
usually
you
say,
let's
roll
back
to
the
previous
one.
C
A
I,
don't
have
an
example
of
this.
I
can
show
you
that
won't
have
Patron
names
on
it,
but
this
is
on
the
holds
awaiting
pickup
page
that
lists
all
your
things
that
are
sitting
on
the
whole
shelf.
It
gives
you
a
little
cancel
button
right
from
there
if
you've
decided
that
if
the
patron
lets
you
know,
they
don't
want
it
anymore
right
now
that
will
always
route
that
item
back
to
its
Home
Library,
which
again
like
for
a
lot
of
Consortium.
That's
just
not
a
thing
that
makes
sense.
A
A
And
then
a
couple
things
about
customizing
the
holds
Cube,
which
probably
I
would
guess
that
y'all
are
using
the
holds
Cube
more
than
hold.
No
sorry
that
thought
didn't
make
any
sense
forgot
forget
that
sentence
started
it's
a
non-sentence
but
yeah,
two
things
about
the
whole
scoop,
making
a
specific
shelving
location
column.
A
F
A
F
C
Like
as
the
page
numbers
in
the
ISBN,
like
that's,
not
helpful,
I
wouldn't
think
there's
hardly
anybody.
When
they're
pulling
things
I
actually
wrote
an
SQL
report
that
replaces
the
whole
two
just
so
we
can
touch
it
sure,
but
if
we
could
have
it
just
built
into
the
circulation
like
just
just
the
information
just
in
what
displays
in
the
title
column,
if
we
could
edit,
what
that
is,
would
be
super
helpful.
C
A
A
F
E
A
A
A
A
A
A
B
B
A
Well
then,
I
know
like
if
you're
using
this
popularity
sort
in
your
search
results
that
looks
at
the
biblios
dot
issues
number
that
requires
your
koha
to
be
running
the
Cron
job
that
takes
the
individual
item,
issue
totals
or
individual
item
issue
counts
and
totals
them
into
the
bib,
and
that
Cron
job
is
probably
not
running
if
you're,
if
buy
water
is
supporting
your
system
just
because
it's
a
big
messy
resource
hog,
which
makes
this
this
drop
down.
Network
very
well.
A
A
This
is
another
four
digit
bug
filed
in
2012.
Do
you
want
to
talk
about
things
that
have
been
a
cohort
topic
forever
and
really
do
need
someone
to
jump
in
with
a
vision
and
a
pot
of
money?
This
would
be
the
one
or
you
know,
one
of
the
ones
toss
this
back
into
the
meeting
chat,
and
this
is
just
the
idea
that
you
know
right
now.
E
A
A
This
page
I
broadly
recommend
it.
This
is
just
the
koha
GitHub,
so
this
is
the
koha
code,
but
this
is
specifically
that
the
section
of
GitHub
that
lists
all
of
the
cron
jobs
that
koha
can
run.
This
is
still
a
level
of
like
let's
go
parse
out
some
Pearl
code,
but
it
can
be
helpful
like
if
I'm
looking
at
Micron
file-
oh
I,
don't
even
wanna,
see
like
it's
we're
running
cleanup
database
with
all
of
these
arguments
and
I
can
come
over
here
to
the
GitHub
page
and
find
cleanup
database.
A
It's
kind
of
a
lot
technically
doable
so
yeah
again,
this
bug
is
the
the
crazy
idea
that
all
of
these
things
could
be
set
in
the
koha
staff
interface,
where
we
would
have
both
visibility
on
them
and
control
on
them
to
be
able
to
like
change
those
things
on
the
Fly
rather
than
put
in
a
ticket.
Have
somebody
else
to
do
it
or
for
folks
who
are
self-supported
ugly,
would
just
give
you
like
a
more
rational
way
to
interact
with
all
of
this
question.
E
You
could
use
the
rejects
with
Bill
and
then
I
get
a
because
all
those
options
that's
tricky,
but
there
must
be
some
there'll
be
a
finite
number
of
options
if
they're,
like
all
those
commands,
yeah
and
then
then,
hopefully,
there's
not
too
many
more.
You
just
have
to
keep
adding
more
as
they
came
in.
A
A
Another
one
I'll
look
kind
of
along
similar
lines
of
this
could
happen
and
it
would
be
cool
if
it
did
I
think
Christopher
brought
this
one
up
actually
haven't
seen
Christopher.
This
bug
is
in
discussion,
which
is
the
often
sort
of
the
polite,
kohak
Community
way
of
saying
nobody
wants
to
get
into
it.
No,
like
no
one
wants
to
touch
this
bug,
but
this
is
the
idea
that
we
could
merge
a
bunch
of
tables,
so
the
biblio
table
and
the
items
table
and
related
ones.
A
They
all
there's
the
live
version
that
are
the
bibs
that
are
actually
in
your
system
right
now
and
then
the
deleted
version.
When
you
delete
a
bib
it
just
pops
over
to
the
deleted
table,
there
are
a
whole
bunch
of
reports
that
would
be
a
lot
easier
to
write
If.
Instead,
that
was
just
one
big
table
all
of
your
bibs
with
a
flag
in
there
is
this
deleted
or
not?
So
when
you
deleted
a
bib
instead
of
moving
to
a
new
table,
it
would
just
get
a
new
flag
on
it.
F
A
A
A
I
can't
think
of
any
well.
There
are
places
in
koha
that
look
at
those
deleted,
bibs
and
deleted
items.
To
like
tell
you
the
title
of
a
book
that
a
patron
had
an
overdue
fine
for
a
long
time
ago,
or
something
like
that
yeah
and
that's
the
stuff
that
makes
me
nervous
that
we're
gonna
misplace
the
in
pushing
this
book
out
we're
gonna,
miss
places
where
we
actually
we're
using
that
data,
and
now
we've
moved
it
and
some
module
doesn't
know
where
to
find
it
anymore.
A
D
A
Yeah,
so
next
is
that
somebody
on
the
QA
team
needs
to
QA.
This
needs
to
like
make
sure
it
does
what
it
says
and
doesn't
break
anything
that
can
get
to
be
a
little
bit
of
a
sticking
point,
because
Lucas
who
wrote
this
code
works
at
Bywater.
Nobody
else
at
Bywater
can
QA
this
so
they're,
relying
on
somebody
else
in
the
community
there's.
You
know
pretty
good
quid
pro
quo
there,
but
that
can
be
a
sticking
point
just
because
nobody
at
Bywater
can
just
do
it.
For
you.
F
F
And
then
find
the
right
screen
here,
so
we
had
an
issue
last
week
where
we
have
all
of
our
staff
at
51
libraries
sign
into
their
into
the
staff
interface
using
like
a
like
Leavenworth
Public
Library.
Their
director
is
Lev
director,
their
cataloging
staff
are
Lev
tech.
There
are
circulation,
staff
are
Lev,
Circ,
well,
one
of
our
libraries.
F
Somebody
logged
in
as
Library
Circ,
went
in
and
changed
all
of
the
data
on
the
private
library
card
of
their
supervisor
and
left
some
nasty
messages
and
and
changed
their
data,
and
so
because
this
is
a
library
where
there's
like
eight
people,
that
log
in
as
as
Cirque
from
that
Library
all
at
the
same
time
every
morning.
So
there's
no
really
good
way
to
figure
out
who
did
it
so
we're?
F
Looking
at
the
idea
that
every
employee
at
51
libraries
is
going
to
need
to
have
a
personalized
login
and
one
of
the
things
that
I
think
that
would
help
that
is
having
a
timeout
different
than
the
right
now.
The
login
timeout
is
set
globally
for
staff
and
for
the
OPAC,
and
so
this
is
what
I'm
looking
at
this
is.
What
I've
asked
if
I
wanted
to
write
a
speck
on
is
what
would
it
take
to
get
a
timeout
to
be
controlled
at
the
borrower
category
level
and
so
I
wanted
to?
F
So
people
have
talked
about
this
before
in
the
past
different
timeout
preference
for
the
OPAC
and
the
internet
and
I
think
this
would
be
one
way
to
solve.
That
is
to
say,
you
know,
borrowers
that
are
just
regular
borrowers
set
one
time
out
and
for
staff
borrow
for
staff
Accounts
at
a
different
timeout.
So
I
wanted
to
make
everybody
aware
of
that,
because
if
it's,
if
it's
an
easy
bug,
if
it's
only
a
few
thousand
dollars,
that's
not
a
big
deal
for
us.
F
This
is
what
I'm
thinking
of
in
terms
of
this
is
my
mock-up
of
what
that
would
look
like
on
the
borrower
category
page
that
just
kind
of
mimics
what
the
system
preference
already
does
and
it'd
be
like
the
minimum
password
link
preference,
that's
in
there
now
and
the
other
ones
to
say
either
follow
this
existing
preference
or
override
it.
For
this
category,
with
this
new
setting
so.
F
E
A
One
more
thing
on
Rebecca's
question
about
QA
to
do
this
is
the
release
team
page
on
the
koha
wiki
listing,
who
is
the
current
2211
release
team,
including
who
all
the
QA
people
are.
So
these
are
the
folks
who
are
empowered
in
the
community
to
do
that
next
step
on
your
bug,
if
you
know
any
of
these
people
at
all,
if
you
want
to
go
over
to
IRC
and
ask
for
some
favors
that
I've
had
some
luck
in
the
past,
with
trading
sign-offs
for
qas.
That
can
work
well.
A
E
F
E
F
The
end
users,
the
the
actual
patrons,
are
usually
divided
into
adult
or
child,
or
some
variation
on
adulter
child
and
then
there's
a
I
think
there's
about
10
each
of
adult
and
child
borrower
categories
and
then
there's
some
professional
ones
and
a
couple
of
organizational
ones.
So
so
we
have
plenty
of
places
to
where
it
makes
sense
for
us
to
have
different
different.
F
Okay
and
that's
the
same
way
we
paid
when
we
ask
spy
water
to
develop
the
preference
that
does
password
link
because
password
link
has
always
been
had
always
been
a
global
system,
preference
but
I,
and
for
our
borrowers
you
know
a
four
or
five
digit
password
makes
sense,
but
then
for
the
staff
client.
That
means
for
the
staff
interface
there's
also
a
minimum
of
a
four
or
five
digit
password
and
I
wanted.
Some
I
wanted
a
way
to
make
one
stronger
for
certain
categories,
and
so
that's
the
way
we
handled
that
is.
F
It
follows
the
system
preference
unless
there's
an
override
on
a
specific
category
and
I
think
there's
a
couple
of
other
areas
where
that's
something
in
the
future.
That
might
be
a
good
way
to
deal
with
differences
between
the
staff,
client
and
typical
Borrowers
is
to
have
you
know
the
ability
to
override
a
global
system
preference
through
changing
the
adding
a
function
to
the
hardware
category.
E
A
We've
got
10
minutes
left.
The
other
thing
we're
we're
supposed
to
talk
about
is
reports.
We
haven't
talked
about
SQL
at
all.
Does
anybody
have
something
really
amazing
they've
done
in
SQL
recently
that
they
can't
wait
to
brag
about
or,
conversely,
does
anyone
hate
SQL
right
now
and
want
to
gripe
about
something?
That's
been
driving
them,
nuts.
F
F
I
mean
that's
it
right
there.
It
gets
me
the
list
name,
titles
in
the
list
and
the
Circ
renew
count
for
their
last
pre
for
the
previous
calendar
month
and
then
I've
got
a
link
here.
That'll,
take
me
to
the
list
on
the
staff
interface
or
a
link.
That'll.
Take
you
to
that
same
list
in
the
OPAC
foreign.
C
I
had
to
write
an
interesting
report
this
month,
so
we're
switching
to
an
automated
system
for
sorting,
and
so
it
prints
the
whole
slips
and
it
doesn't
understand
people
with
two
last
names,
and
so
we
have
to
I
wanted
to
know
how
many
of
our
patrons
had
two
words
in
their
last
name.
So
I
had
to
rewrite
a
report
that
found
everybody
that
had
more
than
one
word
in
their
last
name,
and
that
was
quite
easy.
Once
I
figured
it
out,
but
I
was
really
excited
that
I
got
that.
A
B
A
B
A
C
A
A
How
many
items
can
a
patron
have,
at
a
time
and
I've
been
trying
to
figure
out
some
way
to
get
kohat
to
like
talk
to
me
about
how
often
our
patrons
are
hitting
those
limits,
and
this
seems
like
a
sequel
challenge
like
probably,
if
I
wanted
that
data
I
should
have
been
saving
snapshots
of
some
sort
every
day
in
order
to
go
back
and
look
because
I
can't
really
figure
out
at
this
point.
How
to
say
like
which
patrons
had
50
books
checked
out
on
October
3rd.
E
Or
just
before
you
do
I
I
had
a
when
I
was
trying
to
clean
up
books
and
split
it
into
books
and
I
Don't,
Know
audio
or
something
yeah
I
use
either
I
tried
it
and
I
had
a
little
thing
on
my
topical,
but
why
I
typed
with
the
code
in
and
I
think
it
listed
out?
So
you
could
triage?
You
know
you
mess
up.