►
From YouTube: System Admin Special Interest Group - 12/8/2020
Description
Chat logs:
00:11:37 Jenice Tate: We don't send emails
00:17:18 George Williams: Sorting is overrated
00:23:17 Daniel Gaghan: We are trying to move users over to email but phone is still the most preferred method of notification.
00:23:54 Stephanie D'Angelico: We as well, Daniel, a significant number of our patrons don't even have an email listed, still.
00:39:43 Heather Hernandez: Allow to have different password strength and length settings for different patron categories, bug 23816, https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23816
00:41:38 George Williams: https://wiki.koha-community.org/wiki/Koha_Versioning
00:46:29 Barbara Johnson: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27097
00:49:13 Jason Robb: http://sekls.net/Documents/kohaversion.php
01:00:13 Jason Robb: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26961
A
Okay,
so
welcome
everybody
to
the
december
2020
sis
admin
sig
for
koja
us
I'm
running
the
meeting
today,
but
have
to
leave
at
9
30..
As
I
was
saying
before,
we
turned
the
recording
on
last
week
last
month
last
week.
It
does
feel
like
it
was
only
last
week,
but
last
month
I'd
mentioned
that
he
wouldn't
be
able
to
run
the
sig
anymore.
A
I
volunteered
to
do
it,
I'm
going
to
send
out
an
email
about
moving
the
time
since
I
have
a
meeting
that
overlaps
with
this
one
for
now
so
watch
for
that.
If
you're
on
the
sig
mailing
list,
I
don't
have
a
lot
specifically
for
sysadmin
stuff.
Today
we
got
a
test
server,
so
I'm
very
excited
about
test
server
things
that
was
like
last
wednesday,
I
think
was
when
it
finally
got
set
up.
There
was
some
delay,
and
so
we've
just.
A
We
have
a
long
list
now
of
things
to
test
from
the
new
update,
because
we
updated
to
2005.
we're
an
early
adopter
and
we
have
a
bunch
of
stuff
that
we
were
kind
of
like.
Let's
wait
to
try
that
until
we've
got
the
test
server,
and
so
our
next
meeting
is
just
going
to
be
like
trying
all
the
things
and
we're
also
testing
paypal
but
of
course
everything's
in
maintenance
right
now
on
paypal,
both
the
sandbox
side
and
the
production
side
has
maintenance
going
on
right
now,
so
testing
has
not
been
completed
there.
B
So
we're
actually
going
fines
free
pretty
soon
and
I
was
testing
something
out.
I've
got
a
test
running,
but
I'm
not
sure
if
I'm
just
wasting
my
time
or
not.
But
what
we're
trying
to
do
is
get
it
so
that
a
person
is.
If
anybody
has
anything
that
is
overdue.
They
can't
check
out,
but
we
don't
want
them
to
accrue
fines.
B
So
what
I've
done
is
set
several
items
to
have
no
fines
in
there
in
their
circ
rules,
but
I
have
given
them
a
14
day
grace
period
and
what
I'm
thinking
is
that,
after
that
14
day,
the
item
will
be
set
to
overdue,
which
will
set
the
account
to
be
blocked
from
checking
out.
I've
got
that
that
one
admin
setting
to
say
that
yes
block
people
from
checking
out
if
they
have
overdue
items-
and
I'm
wondering,
has
anybody
done
that
and
has
it
worked
or
am
I
barking
up
the
wrong
tree.
C
A
B
A
A
A
I
think
we're
set
for
january,
but
we
had
the
cloud
migration
first.
So
who
knows
what
that
will
be
yeah?
Well,
I
know
I
know
that
there
had
been
some
problems
with
the
cloud
migration,
because
that
was
part
of
our
trouble.
Getting
our
test
server
set
up
was
that
we
got
it
set
up
like
right
in
the
middle
of
cloud
migration
stuff
and
caused
them
a
headache.
A
A
A
C
That's
probably
because
he's
been
struggling
with
me,
we
got
our
email
verification
done,
but
then,
amidst
all
of
that,
someone
deleted
one
of
the
email
addresses
and
then
when
we
put
it
back
now
we
can't
deliver
emails
to
it.
So
we've
been
trying
all
this
like
setting
dms
records
and
stuff
to
get
the
emails
to
come
back
through
and
it's
still
not
working
so.
A
We
ended
up
needing
to
update
a
lot
of
email
addresses
at
schools
where
the
school
librarian
had
changed
and
they'd
never
told
us,
but
so
we
ended
up
like
sending
out
a
list
to
our
and
a
list
of
the
emails
that
still
needed
to
be
confirmed
to
the
whole.
Our
whole,
like
mailing
list
and
said
like
if
your
library
is
on
here,
you
gotta
confirm
it
or
contact
me
that
it's
their
own
email
address.
F
I
noticed
that
my
personal
reminder,
notices
and
hold
pickup
notices
went
to
my
junk
email.
Now,
I'm
using
my
city
email
to
get
those.
So
I
don't
know
if
that's
something
you
know
that
the
city
has
set
up
that
directed
it
there.
But
I
do
wonder
if
you
know
patrons
may
miss
it
the
first
time
because
it
goes
to
junk
and
they
don't
realize.
A
F
A
B
C
A
Or
your
mail
server
thing
too,
like
it
could
send
them
a
cue
them
up
and
then
it
just
sits.
There
we've
had
that
problem
before
we're
not
like
the
rest.
We
have
our
messages
only
going
once
a
day,
so
they're
queued
up,
for
I
think
they
start
at
eight
in
the
morning,
so
we
send
them
between
eight
and
one
p.m.
A
D
A
A
A
B
A
D
D
E
D
B
A
A
A
A
F
F
A
Yeah
we
changed
our
overdue
notice
settings.
It
was
like,
I
would
say,
like
three
and
ten
days
and
we
changed.
We
pushed
that
out
to
like
five
and
twelve.
I
think
so
you
know
give
it
a
couple
more
days
for
quarantine,
but
that's
the
only
thing
we've
done
but
yeah.
I
agree,
I
think,
having
a
notice
adjustment
where
you
can
pause.
F
F
A
G
I
don't
know
if
this
is
even
in
this.
You
know
we're
relatively
new
we're
new
as
of
the
beginning
of
this
year,
and
then,
of
course,
we
went
shut
down,
and
so
a
lot
of
stuff
is
not
even
still
really
working
the
way
we
want
it
to
be
in
our
system.
But
when
we
went
into
quarantine
we
we
also
quarantine
actually
longer
than
you
do,
and
you
know
bywater
set
up
for
us
a
quarantined
status,
so
our
holds
don't
trap
until
they
come
out
of
quarantine.
G
So
that
kind
of
means
that
we
don't
have
to
worry
about
the
notices
like
when
they
go
into
quarantine.
Nothing
is
is
trapped
when
we
want
them
in
again
out
of
quarantine.
That's
when
the
holes
and
other
things
are
trapped
and
that's
when
everything
starts
generating,
so
that
kind
of
you
know
means
that
we
don't
even
have
to
deal
with
any
of
that
happening
at
the
time
of
check-in.
J
I
I
A
To
delay
at
all,
then
they
could
just
leave
it
at
zero.
But
if
the
public
libraries
who
are
maybe
checking
in
further
away
from
the
circ
desk
or
from
wherever
the
holds
are
being
stored,
want
to
check
it
in
separately
or
if
one
library
is
quarantining
because
their
cases
were
quarantining
longer
because
there's
like
a
higher
case
load
in
their
area,
things
like.
A
A
I
A
I
don't
know
much
yet
about
the.
We
only
just
got
it
and
we
haven't
really
talked
to
them
about
like
sinking
the
data
across
and
stuff
yet
in
part,
because
they
have
a
billion
other
things
they're
working
on
right
now,
and
we
don't
necessarily
care
as
much
about
syncing
it
across
because
a
lot
of
what
we
want
to
use
it
for
is
training.
A
So
we
actually
would
like
if
it
didn't
sync
back
to
the
test
server,
because
then
we
could
set
up
like
books
as
like.
This
book
is
a
lost
book
except
when
it
gets
checked
in
so
we
can
show
someone
what
it
looks
like
when
you
check
in
a
lost
book
and
things
like
that.
We
actually
got
a
grant
money,
grant
money
to
get
our
test
server
set
up
for
this
year.
So
we
could
use
it
for
training
and
we
want
to
get
like
a
z3950
setup.
F
We
love
our
test
server
because
you
can
get
in
there
and
play
around
and
do
things
and
see
what
it
might
look
in
the
in
the
opac
or
the
staff
client
and
see
how
bad
you
messed
it
up
before
you
actually
put
something
out
there.
That's
you
know
awful
or
break
something,
and
we
don't
regularly
sync
ours
either.
There
was
one
time
where
I
had
them
do
that
and
I
I
can't
remember
why,
but
I
think
it
was.
F
We
had
some
display
issues
that
we'd
implemented
on
the
the
production
server
that
weren't
on
it.
It
might
have
been
some
xslt
or
something
and
and
then
we
wanted
to
see,
I
wanted
to
be
able
to
compare
data,
but
that
was
the
only
time
we
asked
them
to.
You
know
bring
it
so
that
it
had
the
same
data
and
yeah.
We
don't
really
worry
about
that
too
much
either,
but
it's
really
great
to
have
one.
B
Yeah,
I'm
gonna
join
the
course
and
say
that
we
we
also
don't
really
update
our
data
just
having
that
old
stuff
in
there
is
actually
pretty
good.
It's
helped
us
out
in
some
cataloging
issues
using
it
for
training.
We
haven't
done,
although
I'm
a
meeting
with
our
circulation
staff
and
might
suggest
it
just
to
see
what
they
say.
B
B
That's
been
really
helpful
and
trying
out
new
circulation
rules,
but
I
did
ask
them
to
update
it
and
they
were
pretty
quick
on
getting
our
data
loaded
in
there
and
they
also
are
very
quick
on
updating
it
to
the
newest
version
of
of
cohan,
like
a
couple
of
weeks
before
we
go
live
with
the
with
the
new
update
on
the
production
server.
So,
overall
it's
been
kind
of
a
godsend.
Yeah.
A
Yeah,
if
we
had
had
our
test
server
before
we
upgraded
to
2005,
we
wouldn't
have
upgraded
to
2005
because
of
the
problems
that
we've
run
into
with
specifically
our
very
weird
setup
for
the
way
that
we're
having
some
libraries
be
closed
and
some
libraries
be
open
and
not
all
of
the
libraries
are
doing.
Transfers
to
all
the
libraries
are
open,
like
there's
kind
of
two
groups
of
transfer
groups
right
now,
and
so
we
were
using
the
branch
transfers
table,
which
did
a
really
good
job.
A
None
of
that
worked
after
the
update
unless
you
turned
on
the
new
local
holds
group
sec
sudden
and
it
turns
out
local
holds
groups,
don't
know
how
to
deal
with
the
holds
queue
or
the
holds
queue
doesn't
know
how
to
deal
with
local
holds
groups.
So
when
you
have
holds
groups
turns
on
turned
on,
you
can't
use
the
holds
queue,
so
we
have
to
use,
holds
to
pull,
which
doesn't
tell
us
which
items
won't
it'll.
A
Give
us
lists
for
items
we're
not
transferring
to
libraries
we're
not
transferring
to,
and
things
like
that,
so
that's
been
real,
exciting
and
there's
a
patron
for
it
and
they're
talking
about
it
today
at
a
meeting
about
when
we
might
get
it
pushed
onto
our
system
because
it's
signed
off
but
not
through
qa.
Yet,
although
I
think
someone
was
trying
to
qa
this
morning
so
hopefully
soon
we'll
get
that
fixed
but
yeah,
we
wouldn't,
we
wouldn't
have
upgraded
all
that
stuff's
part
of
our
test
test
plan.
A
I
Yeah,
I
think
we're
mainly
looking
at
it
for
the
idea
of
a
of
a
test
bed
for
new
versions,
test
bed
for
system
preference
changes,
loan
rule
changes,
there's
also
some
issues.
Our
catalogers
are
very
sensitive
about
how
things
appear
in
in
the
opac
in
and
we
we
use
aspen,
so
we'd
also
want
to
get
an
ass.
A
test.
Aspen
server
set
up
that
we'd
wanna,
you
know
play
around
with
presentation
of
things,
and
so
those
are
the
main
things,
but
training
is
also
that's
another.
I
A
I
I
I
C
D
D
But
I
I
can.
I
can
see
that
you
know
once
those
are
in
there,
then
it
would
be
possible
just
to
eliminate
these
as
system-wide
preferences
once
they
can
be
defined
at
the
patron
category
level,
and
I
can
understand
why
you
know
when
coho
was
new
and
most
of
the
libraries
that
we're
using
and
only
have
one
one
there
was.
There
were
just
single
libraries.
D
I
can
understand
why
that
made
sense,
but
you
know
the
issue
we
have
here
is
that
in
order
to
maintain
patron
privacy
most
of
the
time,
the
password
that
a
patron
has
given
when
they
create
a
card
is
just
like
the
last
four
digits,
their
phone
number
or
their
birth
date,
or
something
like
that.
That's
really
numeric
and
libraries
don't
want
to
give
that
up
because
they
don't
want
to
be
too
complicated
for
the
patrons.
D
D
Making
it
easier
to
differentiate
was
to
move
it
into
the
patron
categories,
and
so
that's
probably
I
think
gonna
be
available
in
2105
is
the
way
that
the
development
looks
like
it's
working
as
a
matter
of
fact.
I
think
that
the
overriding
the
the
password
length
and
the
required
strong
password-
I
think
it's
already
been-
pushed
to
21.05
so,
but
that's
the
kind
of
way
that
I
envision
a
lot
of
the
a
lot
of
the
things
that
can
be
moved
into
other
areas
from
system
preferences.
D
C
D
I
I
We
set
them
with
longer
stronger
passwords
and
said:
okay,
you
know,
and
the
policy
was
you
know
you
you
go
in
and
change
it
change
it
to
a
you'll,
keep
it
a
long,
strong
password
as
a
policy,
but
we
don't
have
any
way
in
the
software
to
enforce
it
so
yeah.
I
would
like
for
the
software
to
be
able
to
enforce
it
some
way
yeah.
So
I
look
forward
to
that.
D
I
C
C
F
C
So
master
is
bleeding
edge.
Coho,
it's
like
the
cutting
edge.
It's
the
development
version,
they're
working
on
right
now,
so
things
are
setting
in
master
while
it's
being
worked
on
and
then
once
a
release
comes
out,
it
gets
pushed
back
to
stable
push
back
to
old,
stable,
so
stable
is
the
current
release
on
george
put
in
the
versioning,
which
is
helpful
here
on
the
wiki
old.
C
H
C
F
D
The
first
upgrade
that
I
went
through,
which
it
was
a
different
numbering
system.
I
think
it
was
cohab
3.21
or
3.6
3.16
and
3.14,
something
like
that,
and
there
was
a
bug
that
broke
all
of
the
grace
periods
and
so
all
of
a
sudden,
nobody
had
any
grace
periods,
and
so
there
were
fines
accruing
wildly
and
uncontrollably
and
unexpectedly
throughout
all.
D
D
D
Yeah
part
of
that's
because
they're
weird
I
I
used
to
work
there,
and
so
I
know
the
kinds
of
weird
things
that
are
going
on
there
they're
a
consortium
with
48
members,
but
there
are
several
of
those
members
that
are
in
smaller
groups.
There's
a
school
district,
and
so
the
school
district
is
a
group
inside
of
the
other
group
and
that's
where
valet
has
got
its
own
unique
issues.
H
D
F
I
just
put
a
bug
in
the
chat.
You
know
we
get
the
monthly
small
upgrades
and
I
wasn't
sure
if
there
was
a
schedule
that
bywater
had
you
know
like
did
it
always
happen
on
the
15th
of
the
month
or
whatever,
and
so
I
asked,
and
they
said
no,
it
just
depends
on
lots
of
different
things
and
sometimes
there'll
be
something
really
important
in
those
monthly
updates
and
yet
I'll
not
be
aware
of
when
it
happens.
F
So
I've
added
a
bug
that
I
know
you
can
click
on
the
about
coha
and
go
in
there
and
see
what
version
you're
on.
But
it
occurred
to
me.
It
might
be
nice
to
like
have
it
on
the
main
page
and
the
staff
client,
you
know,
maybe
down
at
the
bottom
or
something
that
would
just
you
know,
outright,
show
you
you're
on
version
such
and
such
and
my
next
part
of
that
that
I
would
like,
and
they
said
they
weren't
sure
how
you
could
do
it
was.
F
You
know
to
add
the
date
that
that
was
installed,
because
sometimes
staff
will
come
back
to
me
and
they'll
say
well
now
such
and
such
isn't
working
or
we
discovered
this
new
thing
and
I'm
like
well,
I
don't
know,
let
me
investigate
and
then
I'll
learn
that
you
know
well.
It
looks
like
maybe
we
had
our
monthly
update
recently,
and
so
maybe
that's
why
it's
different
now.
D
I
think
that's
a
really
good
idea,
because
how
many
of
us
think
every
morning
hey,
I
should
go
in,
and
click
on
about
and
get
around
and
see
if
we've
been
updated,
bywater
used
to
have
us
scheduled,
so
it
was
like
the
first
wednesday
of
every
month.
They
would
do
a
patch
update,
but
that's
they're
they're
no
longer
sticking
to
that
schedule.
It's
just
happening
happening,
I
think
kind
of
whatever
they
they
feel
like
in
normal
seasons.
C
C
C
D
F
D
I
I'm
not
exactly
sure
what,
but
apparently
it
had
not
been
put
into
our
they
called
the
canonical
code
for
us,
and
so
when
they
installed
the
point
release
all
that
went
away
and
it
was
like
hey
what
happened
and
at
that
time
we
had.
Also.
We
had
been
told
that
whenever
they
update
us,
they
would
send
us
an
email
that
they
had
updated
and
we've
since
learned.
I
No,
that's
only
for
the
major
releases,
not
those
monthly
releases,
but
at
the
time
we
were
like
well,
they
didn't
update
us
because
we
didn't
get
an
email
so
what's
going
on,
and
so
that
was
an
experience.
But
no,
I
think
this
would
be
a
good
idea
to
be.
I
have
well
not
every
day
I
do
kind
of
regularly
go
in
and
check
that
about
and
look
for
you
know
big
red
error
messages
or
anything,
but
I
think
something,
that's
more
in
your
face.
More
obvious
would
be
a
good
idea.
C
J
B
D
C
D
I
I
D
D
C
F
C
D
D
C
C
C
D
I
can't
remember
the
name
of
the
preference
and
there
it
goes
hi
hi,
patron
name
and
the
options
in
the
drop
down
are
show
or
don't
show
the
names
of
patrons
that
have
items
checked
out
or
on
hold
on
detail
pages
or
the
place
hold
screen
and
very
slowly
over
time.
They
have
used
this
to
they've
changed
where
hyde
actually
hides
the
patron
name,
without
updating
the
text
of
the
description
of
the
system
preference,
so
it
used
to
be
that
it
would
just
hide
it
on
the
on
the
patron
details.
D
This
barcode
has
this
item
on
hold
instead
of
this
name,
but
then
it
got
added
so
that
when
you
check
something
in
it
doesn't
show
the
name
of
the
patron
when
you're
checking
things
in
and
the
item
has
a
hold
on
it,
it
will
print
it
on
the
receipt,
but
it
won't
show
it
on
the
screen,
but
that
the
description
of
the
system,
preference
doesn't
say
that
it's
going
to
be
hidden
there.
They
just
decided
that.
D
And
the
column
configurations
are
helping
with
some
of
that
because-
and
I
think
that's
the
newest
place
where
hide
affects
this-
the
patrons
name
as
it
used
to
show
it
when
you're
checking
things
in
the
who
was
checked
out
to
would
show
up
in
one
of
those
columns,
but
now
I
think
it
just
if
you
have
it
set
to
don't
show
it
just
shows
a
barcode
number,
and
so
I
don't
disagree
with
the
logic
of
yeah.
That
should
be
it's
not
a
bad
place
to
to
have
that
hidden.
D
J
A
C
C
Yes,
so
lizette's
gonna
send
out
an
email
to
the
list
about
it,
but
I
think
she
was
talking
about
probably
looking
at
just
keeping
it
on
the
same
day
but
moving
it
half
an
hour
earlier.
So
that
would
tentatively
put
us
at
8,
30,
pacific,
10,
30,
central
11,
30
eastern
on
january
12th
for
our
next
meeting
so
but
watch
the
sys.
This
admin
fig
list
for
more
info
on
that.