►
Description
Presenters:
- Jim Minges (Minges & Associates Consultants, former NEKLS director)
- Liz Rea (ByWater Solutions)
Slides:
- https://docs.google.com/presentation/d/1NlSkLcLNBkB12sxEsG1_t8B4DK0MPCGK/edit?usp=sharing&ouid=106844837026229096502&rtpof=true&sd=true
- https://docs.google.com/presentation/d/1NHfNyA3OK8BkkCDk6PEdq3oIUB1EVUsv/edit?usp=sharing&ouid=106844837026229096502&rtpof=true&sd=true
A
A
We
knew
that
we
were
sort
of
on
the
right
track
when
a
teenager
from
one
of
our
participating
libraries
sent
us
a
a
message.
That
being
part
of
this
system
was
like
having
a
a
a
big,
well-funded
big
City
Library
without
leaving
the
country,
because
that's
kind
of
what
we
wanted
was
everyone
to
have
that
access.
A
Very
few
of
them
had
Broadband
access
and
if
they
had
any
kind
of
local
automation
system,
it
was
a
standalone
system
that
did
not
provide
access
to
anything
but
that
local
collection.
Well,
we
started
working
through
those
kind
of
basic
automation
issues
and,
as
we
did,
that
we
came
up
with
a
a
vision
and
that
was
that
users
have
direct,
can
search
the
they
can
have
direct
and
convenient
access
to
Library
resources
and
that
and
that
included
that
they
could
access
the
collection
from
any
internet
device.
A
I
also
I
also
mentioned
that
at
the
time
that
we
started
this
out.
Of
course,
there
was
a
Statewide
interlibrary
loan
system,
but
to
me
that
was
not.
That
was
not
direct
and
convenient
access,
that
was
indirect
and
eventual
access,
but
the
patron
did
not
have
the
ability
to
actually
now
be
the
user.
A
A
A
That
is,
we
undertook,
with
funding
from
the
State
library,
to
provide
a
number
of
Statewide
services
that
were
sort
of
beyond
our
own
boundaries
and
another,
and
we
also
I
think
thanks
in
large
part,
to
to
Liz
and
to
Brenda
our
our
our
tech
people,
an
involvement
in
open
source
software,
including
a
a
a
service
providing
websites
for
libraries
throughout
the
state
we
I,
don't
we
probably
were
operating
one
time
about
200
websites
for
public
libraries
all
right.
So
what
what
did
we
do?
A
I'm
going
to
talk
a
little
bit
about
what
went
right
and
what
went
wrong,
and
this
kind
of
comes
in
several
different
stages,
because
it
seems
like
every
time
we
took
a
step
forward.
We
also
took
a
little
bit
of
a
step
back
and
I
want
to
thank
the
member
libraries
have
knuckles
for
their
patients
as
we
work
through
each
of
these
stages
of
difficulty.
A
A
You
ought
to
invest
a
lot
of
money
in
those
shared
systems,
but
what
we
did
at
that
time,
partly
because
there
were
certain
members
of
our
board
who
were
really
interested
in
us,
utilizing
the
resources
of
one
of
the
major
libraries
in
the
Kansas
City
area.
We
joined
an
existing
Consortium
in
one
of
those
libraries
that
was
utilizing
the
Cersei
automation
system
and
had
a
number
of
academic
libraries
in
their
Consortium.
A
In
addition
to
the
the
host
Public
Library,
so
we
joined
that
library
and
I
have
a
lot
of
good
friends
there,
but
it
didn't
quite
work
out
with
how
we
wanted
they
hadn't
brought
in
new
members.
In
a
long
time
they
had
brought
in
a
lot
of
college
libraries
and
special
libraries
sometime
in
the
past,
and
they
weren't
really.
A
They
weren't
used
to
work
with
a
small
public
libraries
and
they
weren't
used
to
bringing
in
a
bunch
of
new
libraries
and
what
we
we
did
was
we
had.
We
had
what
I
call
the
nine
Pioneers.
These
are.
This
select
group
of
libraries
that
said
yeah
they'll,
try
they'll
try
this
out
because
it
wasn't
as
if
our
library
is
just
all
swamped
into
into
our
system
and
said
yeah.
A
They
also
were
not
used
to
bringing
on
nine
new
libraries
at
a
time
they
hadn't
probably
brought
a
library
on
for
quite
a
few
years.
At
the
time
that
we
joined
in
addition
to
the
automation
side
of
this
I've
always
felt
a
courier
delivery
service
was
a
essential
for
a
resource
sharing
system.
It's
not
just
an
option.
So,
at
the
same
time
that
we
we
we
started
down
that
Cersei
system.
A
A
We
wanted
to
be
independent
and
man
in
manage
with
assistance
this
the
service-
and
we
definitely
didn't
want
to
be
part
of
Cersei
I-
went
to
a
Cersei
conference.
One
time
when
I
was
with
that
that
outfit
and
learned
that
it
takes
about
three
years
to
suggest
some
sort
of
change
and
to
actually
have
it,
go
through
the
the
various
hoops
and
become
a
part
of
the
software,
and
at
that
time,
when
we
were
talking
about
well,
what
are
we
going
to
do?
A
A
Mostly
that's
what
we
did
and
we
looked
at
equinox
and
we
looked
at
koha
at
that
point
in
time,
Equinox
was
at
a
fairly
early
stage.
It
had
an
interlock.
Basically,
it
had
an
interlibrary
loan
system
and
a
catalog,
but
it
didn't
have
some
of
the
other
functionality,
and
so
and
and
quite
honestly,
they
didn't
make
a
major
push
to
be
the
provider
for
us.
So
we
ended
up,
choosing
coaha
and
see
I'm
kind
of
getting
ahead
of
my
I
thought,
I'm
going
talking
and
not.
A
But
then
there
was
that
other
part
of
the
of
the
equation,
which
was
the
delivery
there
had.
There
had
once
been
a
delivery
service
in
Kansas
in
Kansas,
but
it
was
not
a
a
very
universal
one
and
the
Homegrown
one
we
were
operating.
It
was
time
to
go
to
move
past
that,
because
there
were
Regional
automation
systems
developing
in
all
parts
of
Kansas,
there
was
no
State
real
Statewide
system
and
the
so
what
happened
was
well
actually
I.
A
A
A
It's
it's
beyond
me
to
specify
for
you
exactly
what
changes
were
made,
but
we
did.
We
did
improve
that
the
technical
problem
now,
what's
as
as
we
had
kind
of
really
settled
in
with
Bywater,
and
we
had
brought
in
more
libraries
each
of
those
libraries
having
a
slightly
different
situation,
some
some
of
them
had
robust
Acquisitions
budgets,
some
of
them
didn't.
Some
of
them
were
more
interested
in
sharing
their
materials
than
others.
A
Although
it
was,
it
was
sort
of
a
part
of
the
deal
with
with
our
our
system
that
you
had
to
share.
But
what
that
meant
exactly
was
not
uniformly
understood
in
the
same
way
by
all
of
our
members.
And
so
we
did
have
a
number
of
of
debates
about
exactly
what
restrictions
should
be
placed
or
could
be
placed
and
all
and
I'm
not
in
a
position,
particularly
having
been
away
from
knuckles
for
eight
years
now.
To
say
how
that's
all
all
worked
out.
A
But
I
do
know
that
in
general,
Our
member
of
libraries
did
believe
in
the
concept
of
sharing
and
it
was
a
matter
of
defining
exactly
what
they
meant
and
whether
there
were
exceptions
for
particular
library
to
some
extent
or
another.
But
I
am
very
proud
of
the
the
member
libraries
of
Nichols
who
have
been
so
willing
to
share
the
resources
that
they
have
purchased
with
one
another.
A
Wish
to
elaborate.
Currently
we
have
46
member
library
locations.
We
have
one
library
system
that
has
several
branches,
but
most
of
our
lot,
most
of
our
libraries
are
in
our
koha
system.
Are
single
branch
more
or
less
rural
or
exorbent
type
type?
Libraries?
We
have
one
one
School
District
Library
that
has
five
locations.
C
A
B
C
No,
but
but
seriously,
why
should
we
use
free
and
open
source
software
in
libraries?
I
mean
the
too
long
and
I
didn't
read
and
didn't
care
to
listen.
Is
it's
the
values
right
like
we
all
believe
in
this
thing,
and
we
think
that
it's
good
and
we
should
continue
to
do
it,
so
you
probably
want
to
know
who
I
am.
My
name
is
Liz
Ray
I'm
originally
from
Kansas
my
dad
worked
in
a
non-profit
Consortium
of
colleges
in
Central
Kansas
and
my
mom
worked
for
the
Arts
Council.
C
Sharing?
How
many
of
you
have
code
in
koha?
There's
a
only
actually,
you
didn't
raise
your
hands.
I
know
there's
more
of
you,
okay,
so
why
do
you
do
that?
You
do
it
because,
probably
it's
part
of
your
job,
but
also
you
want
to
do
things
that
are
good
for
yourself
and
your
libraries
and
the
people
that
you
serve
openness,
because
when
something
is
Hidden,
Away,
In,
A,
Box,
there's
no
way
that
anybody
knows
what's
happening
there.
C
We
want
to
make
sure
that
the
software
that
we're
using
is
transparent,
we
know
what's
in
it
and
what
we
can
get
out
of
it
and
what
it
can
do,
collaboration.
How
many
of
you
here
are
friends
and
have
met
people
today
that
you
have
only
ever
talked
to
online
right
like
how
closely
do
we
collaborate
day
to
day?
C
C
C
C
The
Quahog
bug
tracker
has
over
30
000
bugs
in
it
now,
which
is
a
lot
of
bugs,
but
I'm
going
to
imagine
and
I
haven't
taken
statistics.
So
if
anyone
actually
knows
right
now
what
the
actual
number
of
open
ones
are,
it
is
nowhere
near
that
number
and
that
is
The
Testament
to
the
companies
and
the
people
who
work
on
koha.
C
And
we
want
to
be
good
stewards
of
the
resources.
We're
given
I
mean
in
the
case
of
Nichols.
You
know
it
wasn't
all
about
the
money,
but
it's
kinda
About
the
Benjamins
right
so
I
don't
know.
Jim
probably
doesn't
really
remember
this,
because
this
kind
of
happened,
but
while
next
press
was
coming
in
with
Cersei,
but
we
had
a
library
in
a
very
little
town,
probably
about
I,
don't
know
how
big
is
McLeod
small
less
than
a
thousand
okay
Library
less
than
a
thousand.
C
They
did
not
have
an
automation
system.
It
was
a
fairly
new
library
at
the
time
they
wanted
to
spend
their
money
on
doing
programs
and
buying
materials
and
doing
all
those
wonderful
things
that
libraries
do
for
their
communities
and
they
did
not
want
to
spend
money
on
a
library
system.
But,
let's
be
honest,
they
needed
one.
C
So
you're,
gonna
I,
know
you're
gonna,
I
know
what
you're
thinking
you're
like.
Oh,
she
put
koha
in
that
Library
wrong
nope
we
there
at
the
time
there
was
another
open
source,
Library
System.
It
had
Mark
support
and
it
was
web-based-
and
this
should
all
somebody
familiar,
but
it
was
open.
Biblio
and
I
put
open
biblio
in
this
library
and
they
used
it
for
several
years.
In
fact,
until
they
came
into
nexpress
they
we
migrated
them
out
of
it.
C
But
the
thing
was
that
we
took
an
old
computer
and
we
put
Linux
on
it
and
we
put
open
biblio
on
it
and
they
used
that
system
in
their
Library
for
several
years
and
they
didn't
pay
anything
really
I
mean
they
had.
You
know
a
computer
and
expertise
from
the
necklace
system
which
the
county
paid
some
taxes
for,
and
that
system
worked
for
for
several
years
and
the
reason
that
I'm
telling
you
this
story
is.
C
It
was
that
that
moment
that
I
said
how
can
we
do
this,
but
bigger
and
better
and
at
the
time
I
didn't
actually
think
that
there
would
be
a
product
as
cool
as
Kawa
that
where
the
people
were
cool
and
you
like
to
work
with
them
and
they're
fun
to
talk
to
and
they
get
stuff
done.
I
didn't
I
didn't
know
about
that.
C
So
yeah,
so
we
were
working
on
this
Cersei
product
Cersei
project
and,
as
we've
learned,
there
were
very
big
things
happening
at
Nichols.
This
Cersei
Dynex
Consortium,
Jim
kind
of
glossed
over.
Some
of
this
I'm
going
to
be
I'm
going
to
be
like
super
pointed
so
don't
be
mad
if
the
searsy
people
are
watching
I
I
deep
respect
for
you,
it
was
super
spendy
to
you,
Cersei
right
it
had
Percy
licensing.
C
The
rules
of
the
Consortium
we
joined
were
very
rigid.
The
Nichols
libraries
are
often
as
Jim
alluded
to
they're
very
full
of
mad
schemes,
and
they
don't
fit
well
into
the
proprietary
boxes
that
you
want
to
put
them
in,
like
you
want
to
put
them
in
a
box.
It's
like
it's
a
square
square
hole
round.
Peg
it
isn't
going
to
work.
C
Okay,
the
values
of
nickels
itself
were
kind
of
taping
against
this
you
know.
Nichols
wanted
free
and
open
resource
sharing
between
libraries,
and
this
Consortium
wasn't
really
willing
to
support
that
in
the
way
that
we
wanted
them
to.
So
we
thought
that's
not
great
and
the
first
seven
libraries,
seven
six,
how
many
there
were
eight
I
thought
there
were
seven.
You
know,
but
the
first
eight
libraries
didn't
particularly
like
this
system.
It
was
not
great,
it
was
UN.
It
was
difficult
to
learn
the
training.
C
C
C
At
the
time
like
specifically
around
the
time
when
we
were
coming
into
Cersei,
it
was
untested
at
any
sort
of
scale,
and
there
was
a
period
there
where
there
was
big
jumps
in
koha,
so
I'm
talking
about
like
2.2.
It
was
untested
at
any
sort
of
scale
and
our
scale
wasn't
huge,
but
for
koha
it
was
gonna,
be
pretty
big.
C
The
support
for
open
source
at
that
exact
moment
was
going
to
be
from
within
Nichols
I.E
me
and
I'm.
Pretty
clever,
but
I
know
a
lot
more
now
and
at
the
time
I
was
super.
Noob
like
this
could
have
gone
so
badly
all
right.
It
was
a
lot
harder
to
run
kuha
at
that
time.
You
guys
it's
so
much
easier.
Now.
C
And
the
libraries
had
to
be
brought
on
board
with
any
change,
so
they're
sitting
out
there
using
Cersei
and
they're
feeling
annoyed
by
it,
but
the
idea
of
going
back
through
and
migrating
all
of
this
stuff
again
and
changing
the
system
that
they've,
maybe
only
just
changed
a
few
years
ago.
It's
not
super
appealing
like
not
to
say
that
they
wouldn't
do
it,
but
it's
like
maybe
not
don't
want
to
do
that.
C
There
were
only
a
very
few
libraries
in
the
US
using
COA
and
almost
all
of
them
were
libraries
with
local
system,
administration
or,
and
maybe
also
possibly
a
pearl
developer
sitting
around
who
wanted
to
play
with
something
I
mean
that's
the
way
that
most
people
get
into
cool
Huts
like
somebody's
like
hey
I,
got
this
Pearl
app.
What
do
you
think
and
they're
like
I?
Don't
know
Pearl,
but
this
looks
fun
and
those
people
are
nice.
C
C
As
Jim
mentioned,
we
were
already
working
on
a
project
called
the
Kansas
libraries
on
the
web,
which
used
WordPress,
which
at
the
time
was
not
as
slick
as
it
is
now,
and
we
were
running
websites
for
the
Kansas
and
we
had
been
running
a
squid
guard
proxy
for
internet
filter
internet
filtering
for
across
the
state.
So
we
already
had
some
experience
with
running
large-scale
systems,
but
not
this
particular
one
for
a
really
crazy,
Mission,
critical,
app.
C
C
Song
and
dance
koha
had
just
gotten
Mark
support
and
it
was
paid
for
by
one
of
their
partners,
and
it
had
only
taken
six
months
to
get
this
massive
feature
into
koha
Wowie
like
two
years
for
a
feature
in
Cersei
right,
like
that's
unheard
of
in
library
software,
it
was
using
a
fast
full
text.
Indexer.
Now
it
wasn't
just
depending
on
SQL
wow.
You
could
do
relevancy
and
faceting
whoa
version.
Three
was
so
fly
like
it
was
so
fly
and
they
were
like
we're.
C
If
your
ILS
is
a
bus,
libraries
can
not
only
drive
the
bus,
but
they
can
help
you
spec
the
bus
and
design
the
bus
and
build
the
bus,
and
all
of
that
is
alluding
to
the
fact
that
the
kuha
community,
which
is
you
all,
are
here
to
make
this
thing
that
we
use
better.
All
the
time
I
mean
you
can
kind
of
imagine
that
this.
C
C
C
C
C
We
waded
through
bugs
and
customizations
and
doing
it
wrong
and
you
making
use
of
features
that
made
upgrades
really
hard
and
doing
things
a
weird
way
and
modifying
our
code
and
not
staying
on
the
strictly
Community.
We
had
a
tiny
fork
for
a
while
with
features
that
we
had
commissioned
that
you
know
we
desperately
needed,
but
hadn't
been
merged
back
in
these
are
bumps
in
our
road.
C
C
We
had
many
many
meetings
where
we
questioned
whether
we
were
doing
the
right
thing,
things
kind
of
looked
sort
of
upsetting
and
bad
there
were
there
were
there
were
times
when
we
had
really
angry
phone
calls
with
our
former
vendor.
It's
just
being
like
why?
What's
going
on,
we
don't
understand
this
Open
Source
process.
We
don't
you
know
you're,
making
us
promises
and
we
don't
understand
what's
happening.
C
We
offered
up
the
system's
time
and
resources
to
the
community
and
we
embraced
openness
sharing
and
interoperability.
We
want
we
wanted
this
to
work,
I
mean
we
did.
We
were
stubborn,
stubborn,
stubborn.
We
wanted
it
to
work
and
we
could
because
we
believed
in
those
boss-
values
not
just
for
open
source
nature,
but
for
libraries.
C
C
So
what's
next,
so
what's
next
really
depends
on
you
all,
and
not
just
you
here
in
this
room,
although
you're,
excellent
and
wonderful
for
being
here
and
in-person
collaboration
is
awesome,
but
all
of
you
around
the
world
who
are
listening
to
this
talk
or
watching
it
later,
don't
be
afraid
of
us.
The
community
wants
you
here.
C
We
want
you
here.
There's
current
developments
in
kuha
and
developments
in
the
Library
environment
are
bringing
new
people
into
koha
all
the
time
there
are
going
to
be
budgetary
concerns.
Coming
potentially,
you
know,
some
of
those
bigger
systems
are
going
to
be
too
burdensome
for
you.
If
you
need
to
go
it
on
your
own.
There
are
very
good
resources
for
you
now,
so
you
don't
ever
have
to
feel
like
you're
on
your
own.
C
C
The
few
things
that
I
think
about
is,
if
you
run
a
company,
you
can
have
internships,
so
you
bring
in
a
very
voraciously
smart
young
person,
and
you
show
them
this
thing
that
they
can
play
with,
and
you
show
them
how
they
can
make
this
better
and
I
swear
to
you.
They'll
be
hooked,
I've
seen
it
over
and
over.
C
B
C
B
All
right,
thank
you,
Liz
and
thank
you.
Jim
I
appreciate
it.
My
name
is
Christopher
Brandon
I'm,
the
vice
president
of
kohai
US,
and
thank
you
again
to
everyone
that
made
it
here
today.
It's
so
nice
to
see
so
many
faces
and
we're
going
to
be
going
into
our
next
presentation,
which
is
actually
pre-recorded
so
before
we
actually
get
started
here
with
that.
We
need
to
do
a
quick
check
to
make
sure
our
online
people
can
actually
hear
the
presentation
so
bear
with
us
for
just
a
moment.