►
From YouTube: System Administration Special Interest Group - 1/11/2022
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
A
It
all
basically
comes
down
to
the
statistics
table
in
co-host
prior
to
pseudonymization.
The
Assumption
was,
you
might
be
anonymizing
your
reading
history
by
you
know.
Turning
on
the
co-op
privacy
settings,
which
means
that
in
the
old
issues
table
where
koha
remembers
every
past
checkout
you've
done
the
borrower
number
of
the
the
patron
gets
replaced
with
the
anonymous
borrower
number
there.
A
So,
in
the
old
issues
table,
you
can't
see
which
item
got
checked
out
to
which
Patron
win,
but
koha
is
meanwhile
also
keeping
the
statistics
table,
which
is
not
a
record
of
checkouts.
It's
a
record
of
transactions
so
we're,
while
we're
no
longer
remembering
that
this
loan
that
went
from
this
date
to
this
day
was
to
this
Patron.
We
are
still
remembering
that
you
know
on
January
1st
Jason
checked
out
this
particular
book
to
Rebecca.
A
Turning
on
the
pseudonymization
system
preferences,
it
doesn't
do
anything
to
that
statistics.
Data,
it
all
stays
there,
but
it
starts
making
a
parallel
data
structure
that
records
every
time
you
you
do
a
checkout
or
a
check-in
or
but
there's
one
other
type
of
action
that
happens
in
there.
That
is
directly
related
to
a
patron.
It
records
a
pseudonymized
version
of
that
transaction.
A
That
is,
a
staff.
Member
did
a
thing
with
a
patron
that
Patron
within
the
pseudonymization
table
is
identified
by
a
unique
string.
It's
like
a
long
list
of
gibberish
that
doesn't
in
any
way
tie
back
to
that
actual
person,
but
is
uniquely
identifiable
within
the
pseudonymization
table.
So
you
can
still
run
a
report
that
says
in
December
2022.
How
did
my
checkout
break
out
in
terms
of
Patron
category?
Because
pseudonymization
is
remembering
that
this
Patron,
who
is
this
long
unidentifiable,
string
they're
a
regular
Patron
and
they
live
in
this
ZIP
code?
A
Thank
you
so
yeah,
that's
the
big
the
vocabulary.
Difference!
Anonymized
means
we
have
no
idea
who
did
what
pseudonymize
means.
We
have
an
idea
of
a
unique
borrower,
a
statistical
borrower
for
each
Patron.
We
just
they're
known
by
pseudonyms.
Instead
of
their
actual
name,
they
don't
have
their
card
number.
You
just
have
this
long
string
of
gibberish.
C
A
And
at
that
time
this
is
all
the
information
we've
recorded
about
them.
Oh
here
we
go.
They
checked
something
out.
They
checked
out
this
item,
so
it's
like
the
statistics
table
only
a
lot
more
information
about
each
individual
paper,
so
we
are
remembering
yeah
like
their
category
and
their
home
Library.
A
Sort
one
and
sorry
two
all
this
stuff
would
normally
like.
If
you
were
writing
a
report
that
looked
at
statistics,
you'd
join
in
the
borrowers
table
to
get
that
data.
This
is
instead
recording
what
that
information
was
at
the
point
of
of
the
transaction,
which
is
also
nice,
because
it
saves
you
that
that,
like
hassle
of
reporting
on
patrons
who
have
since
been
deleted,.
A
A
That's
the
step
we
haven't
gotten
to
yet
because
we
want
to
just
sort
of
add
that
statistics
data
out
a
little
bit
because
it
is
going
to
be
taking
some
data
and
chopping
it
off
we're
going
to
know
less
about
our
past
circulation
than
we
used
to,
because
I
turned
on
and
I
should
call
those
up.
I
turned
on
this
pseudonymization
system
preferences
in
June,
so
we've
only
got
six
seven
months
of
that
data.
A
A
B
Which
is
a
noise
bad
thing,
yeah
yeah,
so
my
this
sort
of
came
up
because
I
started
digging
into
totally
unrelated.
Somebody
asked
if
I
could
add
like
annual
savings
lifetime
savings
to
check
out
slips.
So
then
I
was
like
yeah
I
can
I
can
look
at
that?
So
then
I
was
like
oh
wait,
so
this
borrower
has
opted
out
of
keeping
their
checkout
history.
B
B
D
A
B
Might
transaction
and
check
out,
but
my
my
year-to-date
is
working
at
this
point,
but
I
was
running
that
on
statistics
and
I.
Think
I
want
to
run
it
on
old
issues
so
that
if
the
borrowers
opted
out,
then
it's
not
going
to
give
them
a
year-to-date,
because
that's
telling
them
hey
we're
keeping
that
information
and
I
don't
want
them.
Yeah.
C
B
So
I'm
still
I'm
still
cracking
on
that,
but
yeah
basically
I'm
what
I
did
was
I
I
ran
the
report.
I
put
it
into
like
a
local
storage
variable
and
then
that
lets
me
pull
it
on
the
on
the
print
slip,
screen
and
populate
it
there
and
it
seems
pretty
rapid,
like
if
I
check
out
a
series
of
items
pretty
fast
and
then
it'll
still
show
up
on
the
on
the
slip
like
the
report
runs
fast
enough.
A
In
the
back
of
my
head-
and
it
is
like
there's
a
big
difference
between
having
that
data
accessible
via
reports
versus
like
actually
just
visible
right
there,
the
patron
record,
but
it's
still
not
particularly
private.
That's
a
low
bar,
especially
while
we're
out
here
like
I'm,
trying
to
encourage
all
of
my
staff
to
feel
real,
empowered
to
use
reports
and
ask
for
reports
data.
But
but
not
this,
not
this
data.
We
don't
look
at
that.
A
A
C
A
Is
fine,
we
probably
don't
need
that
data.
Most
of
the
time
we
had
a
little
like
freak
out
of
oh
my
God.
What
if
somebody
like
that
means,
if
I've
Got,
a
Hold
fitting
on
the
whole
shelf
and
I,
don't
pick
it
up
in
time
and
that
hold
gets
canceled
and
then
an
hour
later,
the
patron
shows
up
and
says:
I
need
my
book
that
was
on
hold.
What
was
it?
A
B
I
would
say
that
that
just
hasn't
affected
us
too
much
because
of
our
situation,
where
we're
still
opt
out
instead
of
opt-in.
So
most
of
my
patients
are
keeping
their
history,
which
we'd
like
to
reverse
that
at
some
point,
but
right
now,
yeah
and
we
lived
without
holds
the
streets
for
quite
a
while.
So
a
lot
of
people
don't
even
realize,
there's
a
tab
on
the
patron
stage
that
you
can
look
back
to
the
whole
history.
A
I
have
a
report
that,
just
like,
finds
every
every
entry
in
those
action
logs
for
a
whole,
given
a
patron
and
a
biblio
number
and
I
feel
like
it
is
the
report
I
used
I
used
most
often
when
staff
come
up
here.
This
thing
went
weird:
what
happened
where
that
whole
transferred
from
and
all
that,
so
it
was
definitely
when
I
had
to
to
rewrite
to
still
be
workable,
with
a
little
less
data.
B
E
A
Yeah
we
use
Aspen
and
not
The
Coho
OPAC
at
all.
So
all
of
our
all
of
our
patrons
are
set
to
never
keep
history
and
there's
no
way
for
them
to
enable
their
history
in
koha,
but
they
could
turn
on
their
Aspen
reading
history,
which
remembers
all
their
checkouts
there,
where
we
can't
see
them
otherwise,
because
we've
been
definitely
could
see
them,
as
we
asked
the
actors
people
to
give
us
that
data
and
I
guess,
most
importantly,
like
law
enforcement
could
see
them
if
they
really
were
determined
to
do
so.
B
F
F
A
Looks
like
a
general,
no
okay,
we
talked
about
it
a
little
bit.
We
are
going
to
take
advantage
of
the
new
password
expiration
period
by
Patron
category
so
like
we're,
leaving
all
of
our
Adrian
passwords
alone,
they're
going
to
remain
very
simple,
four
digit
pins
because
we
don't
want
to
make
our
patrons.
Do
it
any
more
complicated,
but
we
are
making
all
of
our
staff
have
strong
passwords
that
expire
every
six
months,
because
now
you
can
do
that,
and
so
we
talked
about
how
like
really
best
security
practices.
A
We
should
turn
on
two-packed
your
authentication
and
make
everybody
do
that
because
really
that's!
Why
we're
increasing
that
difficulty
for
staff?
We
know
that
they
have
access
to
a
whole
bunch
of
sensitive
data
and
they
should
have
to
do
something
more
more
strong
than
just
the
last
four
digits
of
their
phone
number
to
get
into
that.
But
if
we
didn't
have
the
will
to
push
the
two-factor
authentication
I
think
that
would
be
a
little
bit
much
for
some
of
our
staff.
F
F
D
F
A
C
F
A
It
was
easy
enough
on
my
test
Patron,
if
I
let
my
staff
password
expire,
there
is
still
a
like
a
password
reset
option,
so
you
go
through
and
you
give
your
email
address
and
you
get
an
email
and
you
click
the
link
off
of
it
just
like.
If
a
patron
forgets
their
password,
it
needs
to
get
into
the
OPAC
and
it
worked
fine.
A
It
was
several
steps,
so
I
did
set
up
a
patron
email
or
crime
job
to
email
staff
members
whose
password
is
going
to
expire
in
two
weeks,
I
just
wrote
a
short
email
it.
You
should
go
reset
your
password.
Now,
like
you
will
be
sad.
If
you
have
not,
this
is
like
the
laid
out
generally,
you
will
be
able
to
do
a
password
reset
but
like
please
don't
put
yourself
in
that
position
and
that
at
two
weeks
a
minute
one
week
and
then
it
one
day
and
we'll
see
how
it
goes.
E
E
E
A
A
I
think
if
you
switch
that
local
use,
toggle
I
mean
those
that
wouldn't
make
a
great
local
use
count
for
you.
It
would
be
inflated,
but
it
would
at
least
make
it.
So
there
would
be
a
distinction
between
a
scan
of
the
barcode
that
actually
ended
an
issue
versus
a
scan
of
a
barcode
that
did
not
because
it
would,
it
would
record
return
if
it
actually
ended
an
issue
and
it
would
Record
local
use
if
it
were
anything
else.
E
E
E
E
A
Yeah
I
don't
know
that
so
koha
is
going
to
record
that
there
was
a
transfer
and
that
that
transfer
ended
and
that
transfer
was
related
to
a
hold
and
it's
going
to
record
the
scan
of
the
barcode
that
happened
that
triggered
the
ending
of
the
transcript.
But
I.
Don't
know
that
it's
gonna
tie
those
two
events
together
in
any
direct
data
way.