►
From YouTube: Repurposed Library Fields | S3E16
Description
You thought last week was bad. This is worse! Last week we talked about repurposing library fields. Now we actually DO something with it. Yes, that's right. We make it MORE useful. Can you believe it? What will we come up with next?
Contents:
0:00 - Title
0:27 - Intros
2:57 - The Plan: Using the Renamed Library Fields
10:28 - Previous Video: Tab Hackdown
11:03 - The jQuery
20:20 - The Linked Report
Additional Resources:
https://hopperdietzel.org/koha_notes/library_contact_sheet
Music: https://bensound.com/
Text -to-speech: https://wideo.co/text-to-speech/
Audio Effects: https://zapsplat.com/
Visual Effects: https://flexclip.com/
A
A
Welcome
back
everybody
another
exciting
episode.
Today.
Last
time
we
were
together,
George
talked
to
us
about
repurposing
Library
Fields.
He
he
boarded
to
death
with
repurposing
those
fields
in
your
library
accounts
this
week
we're
going
to
slip
you
into
a
coma
by
making
better
use
of
that
data,
but
first
introductions,
I'm
Christopher
Brannon
with
the
Coeur
d'alene
public
library
and
the
Cooperative
Information
Network.
A
C
Koha
us
provides
excellent
information,
both
original
and
curated
from
around
the
internet,
including
the
terrific
every
other
day
training.
Videos
you'll
also
find
several
special
interest
groups
to
connect
with,
as
well
as
our
general
monthly
meeting
Where
We
Gather.
To
talk
about
the
latest
Cohan
news.
You
should
also
check
out
the
koha
U.S
annual
conference
held
at
various
locations
around
the
U.S.
This
is
a
great
opportunity
to
meet
with
other
users
face
to
face
and
build
your
Kohan
Network,
as
well
as
new
friendships
and,
of
course,
don't
forget
about
the
great
presentations
koha.
C
Us
is
also
actively
involved
in
the
koha
community
by
contributing
towards
new
developments.
If
you
are
interested
in
contributing
towards
koha
U.S
funded
developments
join
the
Kohan
U.S
membership.
Your
annual
membership
builds
the
funds
to
sponsor
new
developments
in
the
community
and,
as
a
member,
you
also
help
shape
koha
us
with
your
membership
votes
and
receive
a
discount
on
the
annual
conference.
B
Renaming
Library
fields
in
the
renaming
the
fields
in
the
library
section
of
the
admin
console
and
originally
I
did
that
because
I
wanted
to
rename
those
fields,
so
I
could
keep
track
of
what
information
was
in
there,
not
long
after
that,
though,
I
came
up
with
this
idea
of
writing
a
report
that
would
populate
a
contact
information
sheet
that
I
could
keep
on
our
circulation
page
in
next
search
catalog.
So
that
way
you
know
before
we
used
to
tell
Librarians
you
know.
If
you
need
to
contact
another
Library
they
would.
B
We
would
tell
them
to
go
to
the
northeast
Kansas
library
system
website
click
on
a
link
there.
That
said,
you
know
contact
you
know,
member
libraries
and
then
they
would
have
to
scroll
through
and
find
the
library
that
they
were
trying
to
get
in
touch
with,
and
it
would
have
information
like
you
know,
phone
number
address
and.
B
B
B
Of
all
the
libraries
that
are
members
right,
specifically
next
search,
catalog
and
so
I
you
for
a
long
time
for
about
five
years,
I
just
had
a
report
running
that
was
pulling
this
data
and
plugging
it
into
a
table,
and
it
was
a
report
that
was
cached
and
it
was
live
for
12
hours.
So
somebody
would
log
in
in
the
morning
the
first
person
to
click
on
circulation.
That
report
would
run
and
it
would
build
the
Json
data
and
anytime
anybody
clicked
on
that
for
the
next
12
hours.
C
B
We
ended
up
with
like
50
of
these
things
running
and
they
kept
crashing
and
it
shut
down
our
whole
system
wow.
So
after
some
talking
with
buy
water
solutions,
we
just
killed
it.
We
killed
the
report
which
was
kind
of
frustrating,
because
it
was
a
report
that
ran
fine
for
about
five
years
and
then
it
just
stopped
working
all
of
a
sudden.
B
The
issue
was,
it
was
a
Maria
DB
issue
and
there's
a
way
we
can
probably
reconfigure
mariadb,
but
in
the
meantime
you
know
I
wanted
this
table
still
to
be
there.
So
I
figured
out
how
to
rewrite
it
and
honestly
I
made
it
even
better
using
the
API
because
it
used
to
be
the
table
would
only
update
every
12
hours.
So
if
we
changed
information
about
a
library,
it
wouldn't
be
on
the
contact
page
until
the
next
day
right.
D
B
B
It's
not
resource
intensive.
Instead
of
caching
that
report
once
a
day
through
the
API,
it
can
run
at
100
times
a
day
and
it's
always
live.
It's
always
good
information
and
I
was
able
to
also
change
this
into
a
data
table
and
I
probably
could
have
done
this
with
the
report.
But
what
I
did
is
I
put
a
search
box
up
here.
So
you
know
if
you're,
if
you're,
trying
to
contact
the
Atchison
library
or
Baldwin
City,
that's
pretty
easy.
B
B
D
B
It
works
really
well
and
I'm
really
happy
with
it.
One
of
the
things
we
lost,
though,
by
converting
to
the
API,
is
the
report
automatically
filled
in
some
data
it
filled
in
data
about
you
know
how
many,
how
many
borrowers
are
there
at
this
Library?
How
many
titles,
how
many
items
circulation
in
the
previous
12
months.
B
B
It
takes
almost
half
a
minute,
but
the
data
is
still
there.
But
this
kind
of
information
in
that
previous
report
and
the
and
running
slowly
is
what
was
causing
that
report
to
fail,
because
it
was
getting
that
information
for
50
plus
branches
and
that's
why
the
report
was
timing
out
right.
So
now
you
get
the
data
it
just.
It
takes
about
a
half
a
minute
to
45
seconds,
depending
on
what
kind
of
load
is
on
that
on
the
server
at
the
moment
and
there
it
is
so
so.
B
The
report
that
runs
get
current
borrower
account
current
titles
items
checkouts
in
the
previous
365
days
and
the
number
of
unique
borrowers
in
the
previous
365
days
so
nice
and
the
reason
that
I
had
that
data
in
the
original
table.
There
is
because,
for
a
time
we
were
having
a
lot
of
libraries
were
asking
me
that
information,
because
it
had
to
do
with
the
vendor
that
was
selling
a
third-party
product,
that
they
all
needed
to
know
that
information
and.
B
D
B
B
Content
on
the
cert
page
I've
got
tap
content
on
the
home
page
and
it's
really
easy
to
plug
that
into
the
system.
Preference
for
internet,
circum,
HTML
or
Internet
main
or
Internet
reports
I've
also
got
it
on
there.
Actually,
it's
intranet
intranet
yeah,
it's
I'm
saying
that
but
I'm
speaking
too
fast.
A
B
A
B
B
And
there's
a
couple
of
things
that
I'm
doing
here
to
to
create
that
report
data.
The
report
link
I
need
to
get
the
branch
for
each
row
and
for
a
couple
of
those
for
Donovan
County.
We
have
four
branches
that
are
all
one
library,
but
they
have
four
locations
and
for
pH
I've
got
Prairie
Hills
and
they're
one
Library
they're
a
school
district
with
five
locations
and.
B
B
Doing
is
it's
saying
if,
if
the,
if
the
report
Branch
starts
with
Donovan,
it's
gonna
put
that
d-o-n-I
wild
card
into
the
link
to
run
the
report,
and
the
same
is
true
with
Prairie
Hills.
If
it
starts
with
a
pH,
it's
going
to
replace
the
full
branch
code
with
ph
wildcard,
so
that
the
proper
report
runs
okay
but
then
the
contact
sheet
as
it
builds
it's
just
taking
those
variables
and
it's
plugging
them
into
the
table.
B
B
A
Okay,
I
could
see
that
I
could
see
somebody
doing
a
A
variation
of
this
if
they
were
using
Fields.
You
know
more
of
their
fields
and
couldn't
repurpose
them.
Maybe
they
could
put
all
their
information
in
a
field
and
separate
it
with
pipes
and
I
think
if
they
always
have
the
same
amount
of
pipes,
they
could
always
split
that
information
off
kind
of
like
in
this
manner
to
to
divide
it
and
to
different
yeah
variables.
B
It's
a
workaround
and
that's
why
you
know
I
said
at
the
end
of
the
last
video
that
we
had
talked
about.
You
know
borrower,
Library,
extended
attributes
like
borrower,
extended
attributes.
That
would
be
really
useful
for
us,
because
we've
got
information
that
we
have
to
have
about
each
library
and
there
isn't
a
place
to
put
it
right
in
those.
B
D
B
So
to
modify
koha
to
suit
that
one
need,
it
seems
to
me.
It
would
be
a
lot
better
just
to
have
a
library
extended
attributes
where
libraries
could
add
the
fields
that
they
want,
and
you
know
add,
drop
downs
at
there's
all
kinds
of
stuff
that
we
could
do
to
customize
koha
on
a
library
by
Library
basis
that
wouldn't
have
to
completely
change
koha.
B
B
Extended
attributes
would
be
helpful,
so
I
get
all
of
this
information.
That's
what
this
this
whole
function.
Here,
though,
does
is
it's
getting
the
stuff
from
the
API?
It's
changing
a
bit
of
it.
It's
gets
doing
some
find
and
replaces
on
some
of
it
and
it's
organizing
it
all
under
the
table
so
that
it's
easy
for
me
to
to
put
it
into
that
table
and
that's
what
it
that's.
D
B
And
so
that's
what
we
get
when
we
click
on
here
is
all
of
this.
You
know:
I
get
the
directors.
I've
got
the
director
information,
setups
of
the
directors
in
bigger
letters,
I've
been
bigen.
The
director
contact
stuff
I've
got
the
line
breaks
there.
I've
got
all
of
the
logos,
I
want
and
I've
got
a
button
that
links
it
out
to
the
website.
B
B
What
a
lot
of
those
tables
weren't
data
tables.
Yet
it
was
a
way
of
adding
a
class
to
a
table
and
making
it
filterable
so
sounds
kind
of
Handy,
yeah
yeah.
It
worked
out
for
me
for
this
time
around.
So
so
that's
you
know.
This
is
a
lot
easier
than
doing
it
with
the
report
and
the
advantages
of
course,
or
you
know
that
this
is
live.
So,
if
I
change
information
on
any
of
these
libraries
instead
of
waiting
24
hours,
it's
immediate,
it's
faster
it
loads
faster
than
the
then.
A
D
B
Here's
the
report,
here's
how
it
shows
up
for
oh
for
Donovan
County,
like
I,
said
by
changing
that
doing
that
find,
replace
and
putting
Donovan
in
there
anytime.
You
run
it
for
one
of
the
Donovan
County
Libraries.
You
get
results
for
all
of
the
Donovan
County
Libraries,
but
the
report
is
just
a
well
essentially
it's
a
series
of
sub
queries,
so
I'm
getting
the
library
name
from
the
branches
table
and.
D
B
I'm
running
a
sub
query
called
borrower
account,
that's
getting
the
account
all
the
borrowers.
I'm
running,
another
sub
query:
to
get
the
biblio
count,
I'm
running
another
sub
query:
to
get
the
item
count
and
I'm
running
another
two
sub
queries
to
get
the
checkout
count
and
it's
between
current
date
interval
minus
one
year
and
current
date.
B
Getting
a
a
unique
borrower
account
by
doing
the
same
thing,
just
counting
in
the
statistics
table
the
borrower
numbers
for
that
Branch,
okay.
So
it's
a
pretty
simple
report.
I
think
the
only
thing
weird
about
it
is
that
I'm,
using
one
of
my
custom,
authorized
values
to
get
the
Branch
name:
okay
to
get
the
the
branch
information.
B
A
A
We
have
links
in
our
Circ
page
for
ill
staff
and
for
directors,
but
we
maintain
those
in
separate
documents
from
our
our
website.
So
somebody
goes
in
there
and
updates
that
information.
So
having
all
this
in
a
centralized
location
about
the
library
seems
a
little
bit
handier
in
my,
in
my
opinion,
I'm
thinking
about
maybe
implementing
what
you've
done
there.
B
The
way
that
the
thing
that
I
like
about
it,
you
know
is
that
I
like
it,
you
know
when
people
have
Quahog
questions,
I
like
to
have
the
answers
as
much
as
possible
in
koha,
so
if
they
don't
have
to
go
out
to
a
separate
website
and
do
a
search
in
a
contact
list,
that's
maintained
somewhere
else,
the
more
that
can
be
in
koha,
I
think
the
easier
it
is
for
staff
yeah
and
that's
one
thing
that
I
find
that
staff
like.
Is
they
like
it
when
things
are
easy.