►
From YouTube: The Future of Past Data - George Williams
Description
Slides: https://hopperdietzel.org/presentations/kohaus.2021/past.html#/title
A
A
A
A
A
I've
been
in
eccles
since
2016..
Before
that
I
had
a
bunch
of
different
library,
jobs
and
just
a
bunch
of
other
jobs
in
general,
and,
like
I
said
before,
in
2019,
I
was
the
quahog
us
president.
I
was
thinking
about
it
when
I
was
getting
ready
for
this,
and
I
realized
that
out
of
the
eight
quahog
con
koha
us
conferences,
this
is
the
seventh
one.
I've
been
to
so
happy
to
be
here.
This
is
a
great
organization
and
I
love
to
support
it.
A
A
It's
spelled
just
like
it
sounds
for
those
of
you
that
don't
want
to
venture
out
and
spell
hopefully,
so
you
can
also
go
to
bitly.
I've
got
a
bit
link.
That's
b,
I
t
dot.
L
y
slash
pass
data
2021.
That
will
also
take
you
straight
to
the
slides.
If
you
don't
want
to
learn
how
to
spell
poverty
so,
like
I
said
before,
I'm
going
to
talk
today
about
data
or
data,
I'll
probably
call
it
both
throughout
this
presentation.
A
So
I'm
going
to
go
back
and
look
at
those
three
questions
that
I
mentioned
in
the
introduction,
they're
kind
of
going
to
be
the
theme
of
what
I
talk
about
today.
So
these
are
paraphrases,
but
these
are
more
or
less
questions
that
I've
had
since
the
beginning
of
this
year.
So
one
of
the
questions
was,
I
have
a
borrower
wants
to
know
the
title
of
every
book.
They've
checked
out
since
2002.
A
A
Can
you
help
and
the
third
one
was,
I
want
to
know
circulation
by
zip
code
since
2011.
Can
you
write
a
report
for
that?
After
talking
to
them,
it
turns
out
they
wanted
circulation
by
borrower's,
zip
code.
You
know
who,
at
this
zip
code,
checked
out
things
at
my
library
and
they
wanted
to
go
back
10
years
and
I
actually
had
two
requests
like
that
that
were
similar.
A
A
I
hear
the
answers
that
I've,
given
these
three
questions,
number
one,
no
number,
two
no
and
number
three.
No,
these
are
all
kind
of
complex
questions
and
it's
not
uncommon
for
me
to
get
questions
like
this.
A
I
think
what's
happened
as
far
as
people's
expectations
goes.
I
think
that
a
lot
of
people
have
seen
too
many
episodes
of
csi
or
ncis
or
criminal
minds.
A
There's
always
some
point
in
an
episode
of
criminal
minds
where
the
bau
is
out
in
the
field
and
derek
has
to
call
penelope
back
in
washington
dc
and
after
some
sexually
inappropriate
small
talk.
He
will
make
a
request
of
like
you
know.
We
need
a
list
of
everybody
who
served
time
in
a
county
jail
in
the
1970s
and
they've
had
at
least
two
root.
A
A
I
think
people
have
this
notion.
This
expectation
that,
just
because
some
some
data
that
they're
interested
in
isn't
on
paper
or
in
a
filing
cabinet
or
a
book
or
in
the
background
of
the
building
in
a
banker's
box,
they
think
that
this
data
is
kept
forever
and
that
we
can
access
it
instantly.
Just
like
that.
A
They
think
that
since
the
data
is
stored
in
the
cloud
that
there
is
no
burden
to
keeping
that
data
forever,
they
think
of
the
cloud
as
an
unlimited
resource.
A
A
A
So
there
are
two
basic
reasons
that
we
don't
keep
data
forever,
there's
a
practical
reason
and
and
there's
a
philosophical
reason.
The
practical
reason
is
that
it
takes
that
physical
space
on
our
server.
A
A
Let
me
get
you
a
price
and
we
can
add
that
into
your
contract,
the
more
data
we
keep,
the
bigger
the
server
we're
going
to
need
and
the
bigger
server
is
going
to
have
a
greater
cost.
A
Just
looking
at
our
next
statistics
from
the
last
few
years,
you
know.
Currently,
we
have
over
400
000
bibliographic
records.
We
have
over
a
million
item
records
over
115
000
borrower
records
and
up
until.
A
Up
until
the
pandemic
started,
we
were
checking
out
about
100
000
items
a
month
on
average
if
we
had
been
keeping
all
of
that
kind
of
data,
all
the
way
back
to
2008
when
we
started
using
koha,
our
storage
needs
would
be
significant
as
far
as
the
philosophical
reasons
go.
Potential
breaches
of
confidentiality
are
always
a
risk,
and
I
know
that
in
the
upcoming
versions
of
quahog
we
are
currently
on
2005
and
beginning
in
2011.
A
Public
libraries
are
public
institutions
and
there
are
open
record
laws
that
affect
us,
but
the
kansas,
open
record
laws
have
exceptions
for
certain
library
records
that
are
considered
confidential.
You
know
like
a
borrower,
registration,
circulation
or
loan
records
and
payment
records
that
are
that
relate
to
identifiable
individuals.
If
there's
something
in
the
record
that
could
point
to
a
specific
person.
Those
records
are
considered
confidential
and
then
there's
the
usual
things
like.
You
know
somebody
donates
stuff
to
the
library
materials,
the
library
and
they
want
to
be
anonymous.
A
That
information
is
considered
confidential
personnel
records
are
normally
confidential,
but
kansas
law
specifically
also
includes
correspondence
between
the
library
and
a
private
individual,
whether
it's
print
correspondence
or
email
or
text,
or
you
know
whatever
messaging,
you
use
your
library
for
us
in
northeast
kansas
confidentiality
and
the
private
nature
of
borrow
records
has
been
an
issue
well,
first
off
because
in
the
last
six
years
we've
had
two
libraries
that
are
necklace
members,
they're,
not
part
of
our
coho
shared
catalog
they're
using
different
ilses.
A
In
the
19
years
that
I
worked
in
libraries
before
I
moved
to
kansas,
there
was
one
time
in
my
career
where
somebody
a
law
enforcement
asked
me
for
patron
records
and
when
I
said
you
know,
those
are
considered
confidential
under
idaho
law
and
I
can't
give
them
to
you
without
a
warrant,
and
the
police
were
fine
with
that
here
in
kansas,
in
the
last
six
years,
I've
had
at
least
five
requests
from
law
enforcement
asking
for
confidential
data
from
our
system
and
the
most
effective
way
of
keeping
borrower
information
confidential
is
to
delete
it.
A
When
you
don't
need
it
anymore.
That's
you
know.
Anonymizing
records
and
hashing
out
the
the
borrower
numbers
and
the
card
numbers,
and
the
data
is
a
good
step,
but
you
know
an
even
easier
step
is
just
if
you
don't
need
the
data
anymore,
just
delete
it.
A
I
was
told
that
I
should
preserve
any
data
that
we
had
because
they
were
going
to
get
a
subpoena
and
when
they
gave
me
card
numbers,
usually
in
all
these
cases
that
where
I've
been
asked
to
preserve
data,
it's
because
they
gave
me
a
card
number
and
they
wanted
to
know
information
about
the
person
that
held
that
card
and
in
two
of
those
cases
the
card
had
been
used
in
such
a
long
time
that
the
data
had
been
deleted
in
another
one
of
those
cases.
A
There
was
information
about
the
person,
but
then
they
never
they
had
hadn't
checked
anything
out
in
so
long
there
was
no
history
on
their
card
of
what
their
borrowing
had
been
and
in
the
one
case
where
they
actually
did
subpoena
me
and
asked
me
to
come
to
court
with
information
the
night
before
the
the
court
appearance
they
settled
out
of
court.
They
took
a
plea
agreement,
so
so
the
most
surefire
way
of
keeping
borrower
data
confidential
is
to
delete
the
data.
You
don't
need.
A
So,
let's
you
know
talk
about
what
to
save
and
what
not
to
save
and
that's
what
the
question
really
becomes.
Quahog
can
save
a
ton
of
data.
A
You
can
save
as
much
data
as
you
want,
but
it's
good
to
limit
what
you
save
in
quahog
and
what
you
don't,
because
of
the
physical
space
and
patron
confidentiality,
and
even
if
you
do
save
everything
there
are
limits
on
what
you
can
do
with
old
data,
and
so
it's
a
good
idea
to
come
up
with
a
strategy
for
what
to
save
what
not
to
save
and
then
how
to
collect
it
and
when
to
collect
it.
A
And
it's
a
good
idea
to
come
up
with
a
regular
schedule
for
collecting
data,
because
you
want
to
save
data
when
it's
fresh.
You
want
to
collect
the
data
when
the
data
is
fresh,
expired
data
is
when
data
gets
old,
it's
going
to
get
less
fresh
and
it's
less
useful
and
I'll
talk
more
about
that
in
a
few
minutes,
with
some
examples
from
some
sql
queries.
A
So
this
is
our
retention
schedule
for
the
tables
for
the
statistics
table
and
all
the
old
issues,
reserves,
messages,
biblio's
items
and
action
logs,
and
let
me
talk
specifically
about
some
of
these
for
most
data.
We
keep
13
months.
A
The
big
exception
has
been
action
logs
until
recently,
we
were
only
keeping
action
log
data
for
the
previous
60
days,
and
that
has
to
do
with
the
way
that
the
cataloging
law
used
to
work
up
until
I
think
1811
or
maybe
1905,
I'm
not
sure
how
long
ago
it's
been,
but
it
used
to
be.
If
you
had
the
cataloging
log
turned
on
every
time.
A
You
checked
out
an
item
and
every
time
you
checked
in
an
item,
if
you
were
using
the
cataloging
log,
each
check
in
and
check
out
updates
the
mark
record
for
date
last
scene
date,
last
borrowed
number
of
borrows
number
of
renews.
A
All
of
that
information
gets
updated
and
it
used
to
be
the
cataloging
log
entered
each
of
those
actions
as
a
separate
line
in
the
cataloging
log.
So
we
wanted
to
leave
the
cataloging
log
on
because
it
gave
us
a
lot
of
good
information.
We
could
use
in
tracking
down
problems,
but
the
problem
was
is
that
it
was
generating.
You
know
we're
checking
out
a
hundred
thousand
items
a
month.
A
That
means
we
were
generating
about
eight
hundred
thousand
lines
worth
of
data
in
the
actual
logs.
Just
from
the
catalog
log
every
month,
so
we
cut
that
down
to
60
days
so
that
we
could
retain
that
data.
Now
that
the
cataloging
log,
the
action
logs,
don't
record
some
of
that
cataloging
data.
The
way
they
used
to
we
felt
like
it
was
time
to
up
that
to
120
days
so
that
we
can
save
more
data.
A
So
when
we
actually
I'm
going
to
run
a
report
in
a
few
minutes,
that'll
actually
show
us
how
old
some
of
our
data
is.
The
cataloging
log
we're
still
in
that
period
where
we
were
at
60
days,
but
we
haven't
gotten
120
days
out
from
the
change
yet
so
so
it's
a
weird
number
right
now.
A
The
two
other
exceptions
are
message:
queue
and
statistics.
The
message
queue
the
sent
messages
on
the
patrons
notices
tab.
We
only
keep
those
for
the
last
six
months
and
I'm
thinking
upping
that
to
13
months
too,
I
haven't
really
made
a
final
decision
on
that
and
I'm
in
no
hurry
to
do
it.
It's
not
like
a
critical
issue.
A
So
I've
talked
about
how
long
we
keep
some
of
this
data
in
next
search.
Catalog
and
now.
Let
me
talk
about
the
statistics
table
specifically
because
it
has
some
benefits
and
pitfalls.
A
So
every
time
you
do
that
you
check
something
in
check
something
out
renew
an
item
or
if
a
fee
is
paid
or
if
a
fee
is
written
off.
All
of
that
data
is
written
into
the
statistics
table
and
the
date
time
field
is
created.
When
you
do
one
of
those
actions.
A
The
statistics
branch
records
the
location
where
the
item
where
the
transaction
is
taking
place
value,
I'm
not
sure
what
the
value
field
does,
but
type
is
whether
it's
issue
renew
write-off
payment.
A
Other
is
another
one
that
I'm
not
sure
what
it
does.
But
then
we've
got
item
number
item,
type,
location,
borrower,
number
and
collection
code.
A
So,
item
number
and
borrower
number
are
pretty
straightforward,
but
statistics
item
type
will
take
the
item
type
of
the
item
at
the
time
that
it's
being
checked
out
and
statistics
location
is
the
is
items.location
at
the
time
that
the
item
is
being
checked
out
and
statistics
c
code
collection
code
is
whatever
is
in
items.c
code
when
the
item
is
being
checked
out.
A
So
the
advantage
of
this
is
that
if
you
have
situations
where
maybe
you're
using
a
an
item,
type
like
new
book
or
a
location
like
new
bookshelf
or
a
collection
code,
that's
like
new
video
or
whatever
those
are
being
recorded
in
the
statistics
table
and
they're
being
recorded
at
the
time
that
the
item
was
checked
out.
So
if
the
item
type
changes
from
new
book
to
book,
the
statistics
table
the
item
type
for
that
transaction
will
always
be
new
book.
A
As
long
as
it's
in
the
statistics
table,
it's
not
affected
by
changes
to
the
item
record
in
the
items
table
and
a
couple
of
things
that
I
want
to
point
out
too
and
be
very
clear
about
our
statistics
branch.
That's
the
branch
for
item
and
issues
renews
and
check-ins
returns.
A
That's
the
branch
library
where
the
transaction
is
happening.
So
if
my
library
and
seneca
sends
an
item
to
payola,
when
that
item
gets
checked
out
at
paola
statistics
branch
is
going
to
record
piola
as
statistics,
branch
and
statistics
location
is
the
item's
current
shelving
location.
That's
in
the
item
record.
That's
items,
location,
not
items,
dot,
permanent
location.
A
So
if
you're
using
the
cart
feature,
where
I
mean
that's
a
feature
in
coho
where
you
check
an
item
in
and
it
is
temporarily
assigned
a
location
with
the
code
of
cart
and
we
use
cart
and
we
call
it
in
the
catalog,
it
appears
as
recently
returned,
and
so
this
helps
people
using
the
catalog
know
that
the
item
was
recently
returned.
So
it
may
not
be
on
the
shelf
where
it's
supposed
to
be
because
it
may
be
on
a
card
somewhere
on
its
way
back
to
the
shelf.
A
A
So
let
me
look
now.
Let
me
show
you
a
very
basic,
some
very
basic
sequel.
All
of
this
data
is
coming
from
statistics
and
it's
just
a
count
of
lines
and
statistics
by
group
by
branch
where
the
statistics
type
is
issue
or
renew,
so
that's
check
out
a
renewal.
So
all
this
report
is
doing
is
counting
the
total
number
of
checkouts
and
renewals
and
statistics
table,
and
if
we
look
for
atchison
here,
we'll
notice,
we've
got
133
089
lines
for
issues
in
the
nichols
system.
Right
now.
A
So,
if
I
add
item
type
to
this
report
and
I'm
getting
item
type
from
statistics,
then
that's
going
to
be
the
item
type
that
the
item
had
when
it
was
checked
out,
and
it's
going
to
be
a
really
similar
report
to
this
one.
It's
just
that
you
know
now.
I've
got
atchison
audiobook.
A
There
are
36
3
699
of
those
133.
000
transactions
were
audio
books,
eighty
thousand
books,
twenty
one
thousand
videos
and
so
on.
A
If,
however,
we're
in
a
big
system
like
this,
we
want
to
know
what's
the
home
branch
of
the
items
that
were
checked
out
at
atchison.
That's
a
different
report
and
I've
got
results
here.
So
audiobook
now
we're
down
to
2653.
A
A
This
is
that
same
report
with
the
item
home
library
and
I've
got
it
set
to
sum
up,
I'm
using
the
rollup
function
so
over
here.
In
this
first
report
I've
got
133
000
items
lines
in
that
table
and
over
here
I've
only
got
127
953.
A
A
So
if
the
item
record
has
been
deleted
from
the
items
table,
there's
no
longer
a
way
to
count
that,
because
we
can't
pull
the
item
home
library
out
of
an
item
record
that
no
longer
exists.
So
this
is
the
pitfall
with
the
statistics
table
is
that
there
are
anytime.
We
need
to
look
outside
of
the
statistics
table
to
link
item
records
or
borrower
records
back
to
the
statistics
table.
A
So
this
is
the
same
report
as
before
and
if
but
what
I've
got
here
is
I'm
putting
a
date
limit
on
it?
I'm
saying
statistics
where
the
date
time
is
between
september
1st
and
october
1st
of
2021
so
this
month,
and
if
I
run
this
report
on
october
1st
to
get
september
data,
that
data
is
going
to
be
fresh
and
if
I
actually
run
that
you
know
here,
we've
got
atchison
audiobook,
38
audiobook.
A
A
If
I
do
that
which
should
be
this
report,
yes,
then
you
know
who
knows
how
many
audiobook
item
records
may
have
changed
in
those
intervening
two
years
so
by
linking
out
from
statistics
to
other
tables.
A
A
In
my
system,
though,
deleted
item
records,
those
are
only
those
only
go
back
13
months,
so
even
there
there's
a
potential
that
we're
not
going
to
get
good
results,
because
this
data
isn't
fresh
and
the
same
is
true
with
borrower
numbers.
So
out
of
all
of
the
things
you
know
in
the
statistics
table,
we've
got
item,
number
item,
type,
location
and
collection
code.
A
So
if
I
do
a
report
like
this,
where
I'm
getting
the
zip
code
from
the
borrower
table,
this
is
again
a
situation
where,
if
I
run
this
report
for
september
21
on
october
1st.
A
A
This
is
another
situation
where
there
is
a
potential
that
borrowers
could
no
longer
be
their
borrower
record
could
have
been
changed,
updated
or
deleted,
and
I'm
not
going
to
get
a
good
result.
A
You
know
here
are
some
statistics
for
our
deletions
just
a
little
since
2019.
You
know:
we've
already
deleted
15
000
borrowers
this
year.
That's
because
we
do
that
on
a
regularly
scheduled
process
that
I
run
manually,
trying
to
do
it
almost
monthly,
but
we've
so
far.
This
year
we've
deleted
65
000
item
records.
A
So
those
are
item
records
that
I
can
no
longer
link
to
from
statistics.
I
could
link
to
deleted
items
for
the
until
13
months
have
passed,
but
after
that
I'm
not
going
to
get
good
reliable
data
and
in
2020
we
deleted
a
lot
fewer
borrowers
in
2020,
only
3
900,
but
we
did
delete
186
000
items
in
2020
and
we
deleted
253
000
items
in
2019
and
we
deleted
12
000
borrowers
in
2019.
A
A
So
the
questions
I've
gotten
so
far
this
year,
I'm
going
to
go
back
to
these.
Yet
again,
so
the
first
one
the
question
was
borrower,
wants
to
know
all
everything
they've
checked
out.
Is
there
a
report?
A
A
So
if
there
are
any
records
from
before
2011,
that's
a
library
that
wasn't
automated
before
they
joined,
so
they
might
have
some
pre
2011
data
like
written
down
in
their
library,
but
we
don't
have
it
in
co-op
and
what
I
told
them
is
that
no,
we
don't
keep
that
data
because
we
only
keep
it
for
13
months
and
that's
for
the
patrons
confidentiality.
A
A
My
answer
to
that
question
was
no,
I'm
not
going
to
do
it
weekly,
but
we
have
been
keeping
that
data
for
the
last
couple
of
years
for
collection
code
and
for
the
last
year
as
item
type
we've
been
storing
that
offline,
because
it
is
something
that
libraries
were
continually
asking
for.
They
have
always
had
the
ability
to
run
reports
monthly
at
their
will
and
then
save
the
data
and
do
whatever
they
want
with
it.
A
The
issue
that
always
comes
up
is
they
don't
think
of
doing
this
until
after
they
discovered
that
they
have
a
need
for
the
data
so
rather
than
disappointing
people,
and
just
saying
no,
we
don't
keep
that
data.
It's
happened
often
enough
that
I
just
save
it
for
everybody,
so
that
when
people
ask
me
where's
the
report
for
that,
I
can
just
say:
hey,
there's
a
spreadsheet,
for
it.
A
The
next
question
was
circ
by
zip
code
checkouts
by
borrower,
based
on
the
borrower's
zip
code.
Can
you
write
a
report
for
that
and
they
wanted
10
years
worth
of
data.
This
is
for
their
strategic
planning
process
at
one
library,
and
I
think
it's
probably
that's.
Probably
why
the
other
library
that
asked
me
about
it
asked
me
about
it.
A
A
A
It's
also
you're
also
almost
certainly
going
to
have
a
year-end
report
for
the
state
library,
because
that
state
library
data
that
you
think
is
just
going
to
the
state
library
if
you're
a
public
library
in
the
united
states
isn't
just
going
to
the
state
library
it's
going
to
the
institute
of
museum
and
library
sciences,
library,
services
in
washington
dc
the
data
that
the
state
collects
they
collect
because
the
imls
wants
it
and
it's
a
good
practice
to
be
in,
and
then
you've
got
to
ask
questions
like
what
kind
of
collection
development
data
would
be
useful
to
collect
regularly
for
the
people
making
decisions
about
what
to
buy.
A
You
know
if
you
find
that
right
now,
the
trend
that
I'm
seeing
in
circulation
is
that
music
cds
just
do
not
circulate.
A
That's
good
data
to
collect,
that's,
probably
really
useful,
to
collect,
and
then
the
zip
code
data
is
demographic
gap.
You
know
what
kind
of
decision
making
process
do
you
go
through
for
your
strategic
plan
and
what
kind
of
data
do
you
need
to
make
that
plan
to
base
that
plan
on
evidence-based
data
and
then
for
us
in
a
consortium
where
we're
shipping
things
back
and
forth
all
the
time
you
know
what
kind
of
data
do
we
need
for
planning
for
the
future
of
how
things
are
shared
between
libraries.
A
So
when
I
get
to
work
on
the
first
work
day
of
each
month
in
my
email,
there's
just
all
these
reports
that
I
have
to
pretty
up
and
present
to
our
members
and
currently
we
store
the
data
in
google
drive,
but
we're
going
to
be
switching
to
github
in
january.
A
So
the
main
set
of
reports
I
use
once
again
these
are
all
links.
So
if
you
go
to
hopperdiesel.org
and
find
the
the
presentation,
I'm
going
to
click
on
one
of
these
reports
and
show
you
where
it's
going
to
take
you,
I
you
have
a
process
where
I
back
up
all
of
the
reports
for
next
search
catalog
onto
github
once
a
month-
and
here
is
the
sequel
for
one
of
the
reports
that
I
run
each
month
to
collect
circulation
data
in
our
system.
A
On
the
first
of
the
month,
and
then
I
send
it
to
my
inbox
and
when
I
get
to
work
on
the
next
morning,
it's
already
there,
but
we
used
to
run
my
predecessor
used
to
run
six
or
seven
different
reports
every
month
and
then
share
links
to
those
reports,
save
them
as
google
sheets,
and
then
she
would
share
links
to
them,
and
so,
at
the
end
of
the
year
there
would
be
six
or
seven
reports
per
month
times
12
months
a
year.
That
would
be
how
many
google
sheets
were
produced.
A
I've
got
this
set
up
so
that
this
can
this
data
can
be
plugged
into
an
excel
spreadsheet
and
instead
of
this
is
actually
running
one
two
three
four
five:
six
seven
reports,
because
I've
got
them
all
set
up
as
sub
queries.
This
first
line
of
the
report
says,
give
me
a
branch
code
and
then
the
second
line
says
get
me
the
account
of
items
owned
at
each
branch
on
the
first
day
of
the
month.
From
this
sub
query.
A
And
then
that
gets
repeated
again
and
again
and
again
so
I've
got
a
sub
query
that
gets
the
items
on
the
first
day
of
the
month,
the
number
of
items
on
the
last
day
of
the
month,
how
many
items
were
added?
How
many
items
were
deleted?
How
many
holdings
did
each
library
have
in
the
first
of
the
month
how
many
holdings
were
added,
how
many
holdings
were
deleted,
so
I've
kind
of
got
these
broken
up
into
my
main
set
of
reports?
These
are
the
ones
that
we've
been
doing
for
a
significant
amount
of
time.
A
If
you're,
looking
at
the
slides,
you'll
notice
that
there's
there's
always
been
a
left
arrow
and
a
right
arrow.
If
you
click
on
the
down
arrow
that'll
give
us
reports
by
circulation
for
different
categories,
circulation
by
location
and
item
type,
location
and
collection
code,
borrower,
zip
code,
hourly
circulation
statistics.
A
My
next
batch
is
for
counting
items
and
requests.
The
next
batch
is
for
local
item.
Checkout
net
borrows
is
in
the
consortium.
A
What's
your
library's
ratio
of
how
many
things
you
borrow
to
how
many
things
you
lend
and
then
borrower
count
by
category
and
borrower
account
by
zip
code,
and
you
can
click
on
any
of
these
and,
like
I
said,
it'll,
take
you
to
github.
A
I
just
clicked
on
borrower
account
by
no,
maybe
that
one
isn't
linked
right,
I'll,
try
and
fix
that
as
soon
as
I
can
here,
we've
got
another
one
that
doesn't
work.
That's
unfortunate,
I'll
fix
these
broken
links
as
soon
as
I
can
here
and
what
does
all
this
look
like?
How
do
I
distribute
them
to
our
number
libraries?
That's
the
next
question,
if
I
pop
that
okay,
so
if
I
actually
pop
over
to
had
a
little
technical
problem
there,
if
I
pop
over
to
coha
our
staff
client.
A
A
So
that's
I've
got
a
whole
bunch
of
notes
here
about
which,
which
ones
were
added
on
march
1st,
which
ones
were
discontinued
on
june
1st
and
which
ones
were
added
june.
1St
july
8th,
so
there's
been
a
lot
of
changes
to
collection
codes,
but
if
we
go
back
to
the
slideshow
and
we
go
down
to
the
down
arrow
here,.
A
There's
nothing
proprietary
or
confidential
in
any
of
those
spreadsheets,
so
you're
welcome
if
you
want
to
download
them
and
look
at
them.
If
you
click
on
any
of
these
links,
you
should
just
get
a
download
window
there.
It
is,
I
don't
know
if
you
can
see
that
in
the
screen
share,
but
you
will
see
a
download
window
that'll,
just
it'll.
Just
ask
you
to
open
up
or
save
the
excel
file
to
your
computer.
A
And
I've
got
these
broken
down
into
like
our
main
statistics
package,
which
I
divide
up
into
one
for
this
calendar
year
and
once
for
the
fiscal
year,
and
then
I've
got
detailed
statistics,
cataloging
borrower
holdings
and
item
statistics,
and
then
resource
sharing
statistics
and
there's
another
report
here
that
you
can
use.
That
is
one
of
the
craziest
reports
I've
ever
written
again.
If
you
click
on
the
link,
you
should
be
able
to
go
to
github
and
this
link
does
work.
A
I
tested
it
when
I
had
my
technical
malfunction
to
make
sure
it
worked
correctly
before
we
got
to
this
point.
This
report
is
big.
It's
actually
one
of
the
longest
reports.
I've
ever
written
two
thousand
362
lines
long,
but
it
runs
in
about
30
to
40
seconds.
A
A
What
we've
got
here
is
a
table
name,
and
for
some
of
these
I
include
a
subfield
and
a
type,
but
what's
the
oldest
oldest
date,
in
the
account
offsets
table
for
the
created
on
subfield,
what's
the
oldest
date
and
what's
the
newest
date.
A
A
So
I've
got
here
my
action
logs.
It
might
be
hard
to
see
this
on
the
screen
at
the
actual
conference,
but
you
can
see
in
our
action
logs.
I
don't
have
any
data
older
than
july
9th
and
that's
because,
like
I
said,
I'm
still
in
that
transitional
phase,
where
we
just
updated
from
60
to
120
days,
biblios
you'll
see
that
I
don't
have
any
old
deleted
biblio
or
deleted
biblio
metadata,
that's
older
than
that
has
a
timestamp
older
than
2020
august
and
in
statistics
and
issues.
A
A
Thanks
for
listening,
I
hope
this
was
useful
to
some
of
you
and
again
the
slides
are
available
at
hopperdiesel.org
the
credits,
all
the
images
that
ask
for
attribution.
I
put
the
attribution
in
the
highlighted
in
the
photo,
the
star
wars
intro
I
created
using
star
wars,
crawl
at
playstarwars.com
and
the
intro
music
I
didn't
want
to
get.
A
I
didn't
want
to
use
the
copy
written
in
star
wars
music,
so
I
found
some
free
music
called
battle
ready
by
brian
teo,
on
freepd.com,
it's
a
great
site
for
finding
free
public
domain
music
that
you
can
download
and
use
for
whatever
you
want
and
again
here's
my
contact
information
and
the
bitly
link
that'll
get
you
to
that
to
that
slideshow.
So,
thanks
for
coming,
I
know
that
this
presentation
is
pre-recorded.
That
was
because
of
an
unexpected
time
conflict.
A
Now
that
the
presentation's
over
I
am
available,
I'm
back
at
my
desk
and
I'm
available
to
answer
questions.
So
I'm
going
to
stop
the
recording
and
come
back,
live
and
I'll
be
able
to
answer
any
questions
you
guys
might
have
thanks
a
lot.