►
From YouTube: System Administration Special Interest Group - 12/14/21
Description
Chat logs -
00:08:20 Heather Hernandez (she/her): I'll be right over, Lisette!
00:09:10 George Williams: It won't get above freezing again this year -- and people wonder why I moved to Kansas
00:30:32 Lisette: https://docs.google.com/document/d/1x9Wm4-mrbLmuXKIz3fZ_LL8YO70La6C9HaArB9MYXGs/edit?usp=sharing
00:31:15 Lisette: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28900
00:31:55 George Williams: SELECT Coalesce(statistics.branch, "NEKLS") AS branch, Coalesce(statistics.itemtype, "BOOK") AS itemtype, Count(*) AS CKO_REN FROM statistics LEFT JOIN items ON items.itemnumber = statistics.itemnumber WHERE (statistics.type = 'issue' OR statistics.type = 'renew') AND Year(statistics.datetime) = Year(Now() - INTERVAL 1 MONTH) AND Month(statistics.datetime) = Month(Now() - INTERVAL 1 MONTH) AND If( Coalesce(statistics.location, "PROC") = "CART", Coalesce(items.permanent_location, "PROC"), Coalesce(statistics.location, "PROC") ) LIKE "%ADULT%" GROUP BY Coalesce(statistics.branch, "NEKLS"), Coalesce(statistics.itemtype, "BOOK")
00:35:46 Heather Hernandez (she/her): I'd totally watch that movie!
00:45:13 Heather Hernandez (she/her): Journals are engaging puzzles!:)
00:49:29 Jason: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29411
00:49:29 Lisette: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29411
00:54:02 Barbara Johnson: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26058
00:55:59 Lauren Denny: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28800
01:03:52 Lisette: FacetMaxCount
A
I
hope
the
rest
of
my
day
goes
better
than
making
coffee
did
right
before
this,
because
my
espresso
machine
decided
to
froth
milk
all
over
itself,
in
addition
to
into
the
cup.
That's
why
I
was
a
couple
minutes
late,
so
hopefully,
things
go
smoother
from
here,
how's
everyone
doing
this
morning,
good
thanks.
A
C
A
A
We
have
a
late
serials
report
and
it
includes
anything,
that's
claimed
or
expected
and
is
late
and
is
anything
that's
like
missing
and
the
way
that
it
was
sorted
was
sorting
it
all
by
like
subscription
title
and
then
status,
but
we
wanted
to
put
all
the
ones
that
are
claimed
at
like
the
bottom
of
the
list.
So
it's
still
easy
for
our
person,
who
does
that
to
see
what's
been
claimed,
but
it's
not
it's
it's
easier
for
her
to
go
through
and
just
deal
with
the
ones
that
need
to
be
dealt
with.
A
So
I
just
like
split
it
into
two
and
unioned
it
with
the
claims
in
one
report
below
ones
that
have
been
claimed
below
and
the
ones
that
hadn't
above
I've
also
been
using
case
more
especially
for
like
lost
statuses
and
stuff.
Just
say
like
case.
If
it's
this
say
what
the
description
actually
is,
instead
of
having
to
like
link
in
values,
and
it's
a
lot
faster
that
way
and
my
staff
appreciate
that
too.
D
D
Oh,
I
was
playing
with
the
idea
of
generating
a
tag
cloud
like
the
opec
has
the
tag
cloud
thing
right,
but
it
doesn't
get
much
use
because
it's
like
patron
generated
for
the
most
part.
So
I
was
playing
with
the
idea
of
replacing
that
with
a
subject
cloud
so
pulling
subjects
out
of
all
of
our
records
with
counts
and
then
generating
a
cloud
based
on
the
counts
so
like
if
the
more
frequent
it
the
subject
is
used.
The
bigger
the
word
would
be
that
kind
of
thing,
but
I
don't
progress
on
that.
D
D
C
B
D
For
a
little
while
so
so
it's
pulling
just
650s
it's
looking
at
the
first
five
650s
in
every
record
that
isn't
a
buy
sack,
because
I
didn't
like
how
those
looked
and
I'm
only
looking
at
bib
numbers
greater
than
500
000.
So
it's
only
the
newest
stuff
I
was
thinking
about
and
that
this
report
still
took
like
two
minutes
to
run,
but
it
gives
you
the
count
of
how
many
times
it's
used,
it's
sorted
by
frequency.
D
D
B
B
D
And
there's
some
good
information
on
the
wiki
about
querying
our
data.
Some
good
examples
so
like
this
one
here
is
kind
of
what
I
pulled
from
to
get
the
subfield
a,
but
I
I
know
that
you
can
pull
like
the
full
tag
as
well,
so
you
you
can
look
through
this
information
a
little
bit
more.
It
might
give
you
what
you're
looking
for,
but.
B
A
I
would
just
like
take
a
report
that
was
as
similar
to
what
I
was
trying
to
do
as
I
could
find
either
out
of
our
many
reports
that
we
already
had,
or
the
reports
library
and
then
just
start
like
okay.
Well,
this
is
close,
but
I
needed
these
fields
instead
and
I
needed
to
query
off
of
that
instead
and
just
like
little
replacements
as
much
as
I
could
so.
H
H
When
you
turn
on
the
cart
feature,
you
create
a
secondary
location
in
the
item
record,
called
item,
permanent
location
and
all
of
the
things
that
have
the
item,
location
and
the
item.
Permanent
location
should
always
match.
Unless
the
item
has
just
been
recently
returned,
and
it's
got
that
cart
location
for,
however
many
hours
you
tell
quahog,
you
want
it
to
have
that
cart,
location
after
a
check-in.
H
The
problem
is
that
when
you
check
something
out
that
has
that
cart
location,
the
statistics
table
records
cart
as
the
item's
location.
It
doesn't
record
the
item's
permanent
location
in
the
statistics
table.
It
records
the
cart
location,
so
I've
just
updated
all
of
our
statistical
reports
that
gather
data
from
the
statistics
table
so
that
in,
if
an
item
has
a
cart
location
instead
of
calling
it
cart,
it's
gonna
it.
H
It
slows
down
the
statistic
gathering
because
if
you
have
all
that
data
in
statistics,
the
report
runs
really
fast
because
you're
only
querying
one
table,
but
what
I've
got
now
is.
I
have
it
set
so
that
if
it
comes
across
those
cart
locations,
then
it
tries
to
find
the
item
record
if
the
item
hasn't
been
deleted
yet
and
pull
in
the
permanent
location
and
replace
that
with
the
with
the
cart
location.
H
So
so,
naturally,
I
screwed
that
up
and
I
accidentally
had
some
libraries
checking
out
more
things
in
there.
You
know
we
have
a
one
column
on
the
statistics
table
and
there's
monthly
statistics.
That
says
these
are
the
total
number
of
items
you
checked
out.
Our
three
shelving
locations
are
adult
children's
and
young
adult,
and
so
they
would.
G
G
H
Have
the
timing
on
ours
set,
I
believe,
for
four
hours,
but
then
I
only
have
the
report
run
like
eight
in
the
morning
noon
and
I
think
it's
just
eight
in
the
morning
and
noon
so
that
kind
of
gives
it.
You
know
if
things
are
checked
in
in
the
morning
there
they
show
back
on
the
shelf
by
the
end
of
the
day.
H
But
if
things
are
checked
in
in
the
afternoon,
they
won't
show
back
on
the
shelf
until
the
next
morning,
and
that
was
at
the
request
of
of
our
libraries
because
some
of
our
libraries,
you
know
initially
when
we
turned
on
the
cart
feature.
We
had
it
set
for
four
days,
because
libraries
were
checking
things
in
and
then
quarantining
them
for
four
days.
H
D
H
G
Okay,
yeah
I'm
having
a
little
bit
of
trouble
hopping
through
some
of
the
tables,
but
maybe
at
the
next
meeting
I'll
present
it
to
see
if
anybody
can
help
me
if
I
haven't
figured
it
out,
but
then
I
just
started
this
request.
So
it's
it's
been
kind
of
interesting
trying
to
jump
through
tables.
I
don't
usually
use
so.
Okay.
E
G
A
H
A
H
H
So
if
that
statistics
location
equals
cart,
then
it's
gonna
coalesce
with
it's
gonna
grab.
The
item
permanent
location-
and
if
it's,
if
it
doesn't
equal
cart,
then
it's
just
gonna
do
what
it
did
at
the
beginning.
So
it's
pretty
simple
just
for
that.
One
part
of
the
just
for
that
one
sub
query,
but
the
way
I
complicate
it
more
is
I
don't
want
to
run
this
report.
I
don't
want
to
run
one
two
three
four
five
reports,
so
I've
just
got
them
all
joined
together
into
one
report
with
five
sub
queries.
So.
H
H
F
A
A
A
A
A
A
A
So
our
person
who
does
purchase
suggestions
is
very
pleased
with
the
new
additions
because
she's
been
spending
a
lot
of
time
lately
running
down.
All
those
issues,
like
almost
all
of
our
purchase
suggestions
last
week,
were
audiobooks
from
the
same
couple
of
staff
members
who
are
newer
and
she
had
to
spend
quite
a
bit
of
time
like
talking
to
them
about
it,
and
then
they
had
to
call
all
the
patrons
and
confirm
if
they
wanted
books
or
audio
books,
because
they
hadn't
filled
it
out
right
because
our
staff
member
hadn't
filled
out
right.
H
H
H
Are
you
interested?
You
really
want
this
movie
about
gay
in
the
closet,
gay
dancers
in
the
early
80s
at
the
beginning
of
the
aids
epidemic
she
was
new.
She
didn't
know
me
that
well
and
she
did
kind
of
give
and
she
kind
of
rolled
her
eyes.
When
I
told
her,
I
was
just
a
mistake
like
yeah,
really,
that's
a
mistake.
H
H
A
H
A
H
H
H
Yeah,
you
don't
have
to
query
the
action
logs
to
find
out.
I've
got
this
set
up
for
claims
returns
and
creating
invoices,
creating
credits,
write-offs
payments
and
it
seems
like
a
couple
of
other
places
where
and
that
way
leaves
a
note
that
staff
can
see
instead
of
without
having
to
run
a
report
to
say
you
know
when
did
this
happen
and
who
was
logged
in
and
what
library
were
the
app
when
this
happened,
but
I
think
you're
right.
I
think
that
information
is
in
the
purchase
suggestions.
I
just
it
is.
H
D
So
I
looked
at
my
jquery
and
I
do
have
some
stuff
I
was
working
on.
I
can
share
if
you
want.
Oh,
let
me
share
my
screen
this
one,
maybe
okay.
So
the
first
thing
is
the
links
to
the
cover
images.
This
is
something
that
changed
during
the
upgrade
and
I
was
having
frustration
with
it.
My
catalogers
were
having
frustration
with
it,
so
I
so
like
when
you
click
on
this.
Sometimes
it
takes
you
to
the
image
directly.
D
Sometimes
it
does
like
a
lightbox
thing,
but
it
never
takes
you
to
amazon
and
we
use
that
because
we
have
to
go
out
and
check
like
pub
dates
and
stuff
like
that.
So
I
had
a
little
icon
here
that
just
generates
the
amazon
link
based
on
the
isbn
which
is
stored
in
this
image
that
takes
you
out
to
amazon
and
that
jquery
is
here.
D
Oh
so,
basically,
it's
just
generating
it's
grabbing
the
isbn
from
that
image
link
which
is
there
and
then
it's
generating
a
new
one
and
appending
it
to
the
end.
It
still
does
funky
stuff
so
like
if
it
doesn't
have
an
image.
It's
I
need
to
clean
this
up.
A
little
more
and
actually
it's
not
doing
it
on
my
test
server
on
my
live
server.
I
think
it
still
says
like
there's
an
image
from
amazon
here,
even
though
there's
not
and
then
the
links
don't
work.
D
So
it's
a
little
clunky,
but
it
gives
us
a
direct
route
to
amazon.
So
we
can
look
at
the
information
they
have
there.
Oh,
so
that's
that
one
and
then
I've
been
fighting
with
series
from
the
api
again
barbara,
and
I
have
talked
about
this
a
little
bit.
I
thought
that
I
didn't
need
to
worry
about
it
anymore,
because
the
series
information
is
in
the
style
sheets
by
default.
Now,
so,
if
you're
using
the
default
style
sheets,
you
get
series
links
on
your
search
results,
but
it
still
traces.
D
So
if
there's
an
800,
then
it's
generating
extra
stuff
and
the
search
string
like
goes
to
both
the
series
title
and
the
author,
and
that's
not
what
we
want
that
to
do.
We
want
it
to
just
search
the
series
title,
so
I
I've
hidden
that
and
then
I've
used
the
the
api
to
bring
the
series
information
back
in
using
some
code
that
I
harvested
from
barbara
who
got
from
lucas.
D
So
it's
still
clunky,
but
it
works
better
and
it
allows
me
to
not
have
to
use
custom
xslt,
which
is
my
end
goal
with
this,
and
in
the
same
vein
on
the
opac
I've,
I
figured
out
how
to
add
the
007
icons
that
I've
got
so
in
my
live.
Catalog.
I've
got
these
here
and
it's
that's
built
into
the
xslt
right
now.
In
my
test.
D
Catalog
I
haven't
pushed
this
in
looks
the
same,
but
I
don't
have
custom
access
lt
running
these
are
just
pulling
in
from
the
api,
so
it's
overly
complex,
but
basically
it's
looking
at
the
07,
the
different
positions,
so
the
zero,
the
one
and
the
four
building
a
string
based
on
that
and
then
checking
that
and
depending
on
what
that
string
is
putting
in
a
different
icon.
So
you
can
see
that
if
it's
vdv,
then
I'm
putting
in
the
dvd
icon,
if
it's
vfd,
then
it's
a
vhs
icon
so
yeah.
D
D
B
H
I've
been
working
on
something
with
jquery
that
I
haven't
gotten
very
far.
My
big
breakthrough
was
figuring
out
why
it
only
worked
like
30
of
the
time,
but
the
question
has
come
up
here.
You
know,
after
if
you
use
the
claims,
return
feature
and
you
mark
something
as
claims
returned
and
you
click
the
box
that
says,
don't
build
a
patron
for
it
or
whatever
it
is
whatever
step
you
take,
that
doesn't
build
a
patron
for
it.
H
One
of
our
libraries
would
like
to
you
know,
mark
things
as
claims
returned
search
for
it
three
or
four
times,
and
then,
if
they
don't
find
it
then
go
back
and
build
a
patron
for
it
and
there's
no
way
to
go
to
a
claims.
Return
now
and
say:
okay
now
build
this
item,
and
so
I've
been
working
on
creating
a
button
that
will
pull
the
item.
H
For
that
item
record
from
a
report
or
from
the
api
and
then
sticks
all
that
data
into
the
forum
and
I've
gotten
as
far
now
as
creating
the
button
and
getting
it
to
load
on
that
data
table,
and
that
was
a
colossal
pane,
because
the
problem
with
that
data
table
is
that
it
doesn't
load
until
you
open
the
claims,
return
tab,
and
so
I
figured
out
the
jquery
to
get
the
button
on
there,
but
it
was
only
working
about
30
to
40
percent
of
the
time.
Sometimes
it
would
be
there
and
I
go
great.
H
H
H
H
A
C
H
A
D
A
A
A
So
they
can't
like
look
up
users
by
id
if
they
don't
have
their
card
with
them,
which
has
been
a
problem
for
some
of
our
libraries
that
run
on
volunteers
or
that
sometimes
have
like
teachers
cover.
If
the
librarian's
gone,
especially
because
a
lot
of
the
schools
they
just
look
them
up
by
name
and
don't.
H
I
can
explain
what
happened
here.
There
was
a
shortcut
fix
you
used
to
be
in
checkout.
If
you
did
a
search
for
like
the
letter.
If
you
just
type
in
s
in
the
search
box,
it
would
try
to
load
a
full
page
of
everybody
who
had
an
s
in
their
name,
and
so
somebody
said
why
don't
we
just
instead
of
but
it
doesn't
do
that
in
the
patron
search,
because
that's
a
data
table.
H
H
And
I
initially
I
said
this
is
not
a
bad
bug
to
fix,
but
I
didn't
realize
there
was
going
to
be
that
secondary
consequence.
I
don't
remember
who
was
fixing
that
who
wrote
that
patch
to
redirect
everything,
but
that's
the
underlying
issue
is
that
somebody
was
fixing
one
problem
and
not
realizing.
There
was
an
unintended
side
effect.
A
A
A
F
F
We've
got
chromebooks
and
hotspots
and
other
stuff
like
that,
and
we
don't
want
them
to
keep
putting
a
hold
on
the
hot
spot
they
already
have
out.
I
did
this
a
while
ago,
so
I'm
trying
to
remember
exactly
what
we
wanted,
but
just
bringing
attention
to
that.
If
that's
something
that
you
know
would
be
of
use
to
other
libraries.
A
Yeah
that
would
be
helpful
for
us
for
the
same
reasons
like
our
hot
spots
and
stuff
being
able
to
say
we
have
a
few
patrons
who
just
you
know,
they'll
have
one
checked
out
and
they'll
have
like
three
holds,
because
that's
how
many
holds
we
allow
per
item
record
and
just
like
always
have
one
of
our
hot
spots,
basically
which,
like,
if
they're
not
getting
used.
You
know
like
right
now.
A
We
have
a
couple
on
the
shelf
available,
but
if
there's
a
long
holds
list,
that's
like
extra
annoying
that
the
same
person
is
basically
just
like
always
taking
up
one
or
sometimes
more
than
one.
If
one
comes
in
and
is
like
waiting
on
hold
and
then
they
come
just
like
traded
out.
So
I
totally
agree
with
that
and
I've
added
myself
to
the
list.
B
B
H
A
F
A
B
H
The
best
way
I
can
think
of
the
test-
if
this
is
a
problem
with
your
javascript-
is
to
open
a
notepad
file
and
then
go
to
the
system,
preference,
internet,
user
js
and
take
all
of
that
data
out
of
that
system.
Preference
and
put
it
in
the
the
notepad
file
and
then
save
everything
and
then
reload
that
page
and
see
if
it
works
without
all
your
javascript
there.
C
B
H
H
B
Yeah
and
I
need
to
go
through
our
system
preferences,
it's
it
feels
like
when
they
did
the
upgrade
something
in
the
system.
Preferences
didn't
transfer
correctly
on
some
like
we
thought
it
meant,
or
it
meant
this
on
the
old
system,
and
it
doesn't
mean
that
anymore
or
it
it
re.
You
know
it's
relying
on
a
separate
connected
preference
and
I
haven't
had
a
chance
to
look
at
it,
but
that's
happening
and
then
on
our
facets.