►
From YouTube: Consortia Special Interest Group - 5/12/2022
Description
00:21:05 George - NEKLS: Yes, different George.
00:29:44 Jason (SEKLS): OpacAddMastheadLibraryPulldown
00:31:37 Jason (SEKLS): OpacSeparateHoldings OpacSeparateHoldingsBranch SeparateHoldings SeparateHoldingsBranch
00:32:43 George - NEKLS: Record grouping is awesome
00:37:04 Michael Adamyk (CKLS): https://greatbend.catalog.ckls.org/?browseCategory=greatbend_our_flag_means_death_read_alikes
00:39:13 Lauren Denny: https://library.teamwork-global.net/Here is a link to our catalog in koha
00:41:06 George - NEKLS: I don't exactly write it "for you." I write stuff for me and I'm happy to share.
00:41:51 George - NEKLS: https://koha-us.org/learn/video-playlists/
00:42:13 Michael Adamyk (CKLS): Here's a link to the jQuery library: https://wiki.koha-community.org/wiki/JQuery_Library
00:44:25 Jason (SEKLS): https://github.com/mdnoble73/aspen-discovery
01:02:41 Nelson Fredsell: https://www.youtube.com/c/raflimts : HowTo videos, will produce new ones for a reasonable price. Pakistan
A
All
right
well,
thanks
for
joining
us
for
the
consortia
special
interest
group.
I
think
we'll
start
with
just
a
few
introductions
before
we
get
into
things.
I
know
most
of
you,
but
my
name
is
bob
benhoff.
I
am
the
manager
of
aspencat,
which
is
a
consortium
of
mostly
rural
libraries,
of
all
types
in
colorado,.
B
E
A
B
E
We
use
them
a
little
bit,
so
my
catalogers
use
them
to
keep
track
of
new
items
coming
in.
That's
really
our
our
large
use
case
and
then
my
my
super
user
patrons
like
like
to
use
them,
because
we
can
tell
that
they're
using
them
because
they
immediately
put
their
holds
on
right
after
something
gets
added.
E
I
don't
know
there
may
be
some
documentation
in
the
manual
you
you
do
have
to
have
like
a
separate
rss
feed
reader
for
us
we're
just
using
like
a
plug-in
a
chrome,
plug-in
or
a
firefox
plug-in,
and
then
any
search
you
do
in
the
opac
can
be
turned
into
an
rss
feed,
so
you're
putting
your
filters
in
that
way
and
if
you
sort
it
by
accession
date
newest,
then
then
you're
getting
the
newest
stuff.
First.
So
that's
how
that's
our
main
use
case
for
them.
A
F
Okay,
I
am
just
waking
up,
so
my
camera
will
stay
off,
I'm
in
san,
juan
batista,
california,
part
of
mobak,
and
we
have
been
looking
at
doing
consortia
within
mobac
for
the
last
well
pre-covered
I'll,
say
nine
months
and
we
were
supposed
to
kind
of
be
part
of
it
already,
but
it's
been
delayed.
So
I
just
thought:
I'd
join
the
group
here
to
see
what
to
expect
in
the
future.
F
A
F
F
F
Oh
definitely,
yes,
yeah.
I
think
it
should
go
smoothly.
I
know
on
my
part,
I've
just
been.
We
are
very
small
library,
less
than
10
000
pieces,
so
I'm
just
cleaning
up
our
database
because
it
is
over
the
last
10
years.
We've
migrated
to
at
least
three
different
ils
and
each
time
bad
data
came
over
so
yeah
just
keeping
it
as
clean
as
possible.
A
Yeah
I've
been
involved
in
many
many
migrations
and
that
often
doing
data
cleanup
before
is
really
wise.
So
it's
good
that
you're
doing
that.
Hopefully,
your
the
other
interested
libraries
are
doing
some
of
that
as
well.
It's
going
to
help
that
you,
if
you're,
all
staying
within
quahog,
there's
not
some
of
that
translation
loss
of
data.
C
D
C
C
C
A
That
that's
a
good
question.
If
you
email
me,
I
can
put
you
in
contact
with
bywater's
lead
developer,
so
I'll
just
drop
my
email
in
the
chat,
okay
and
he
might
have
a
better
sense
of
that,
because
the
aspen
discovery
is
open
source.
So
the
code
is
published.
How
easy
that
is
to
do
an
install.
I
have
no
idea,
but
he
would
probably
be
able
to
give
you
a
little
bit
more
of
a
sense.
I
know
that
it's
starting
ptfe
ptfs
europe
is
starting
to
do
some
support.
C
I
see
yeah
and
I've
been
to
the
viewfind
site
too,
and
it
looks
like
there's
a
lot
of
people
who
really
jack
about
viewfind,
but
I'm
not
really
sure
it's
kind
of
like
some
of
the
cms's
where
they
say
yeah.
This
is
easy,
but
actually
it's
not
so
easy.
So
I
didn't
and
then
the
fact
that
there's
the
app
so
to
do
international
consortial
work
and
not
have
to
configure
sms
notifications
across
multiple
countries
seems
like
it'd,
be
better
handled
with
an
app.
C
A
So
I
know
they're,
there
they've
worked
on
a
app
for
aspen
discovery,
so
I
we
haven't
utilized
it
yet,
and
I
know
some
of
our
well.
I
know
lauren's
not
on
aspen
discovery,
but
I
I'm
pretty
sure
the
kansas
folks
aren't
either
at
this
point
or
are
you
michael?
Yes,
have
you
messed
with
the
app
at
all.
D
Not
not
a
whole
lot
it,
and
that
is
the
lida
app
that
nelson
was
talking
about
that's
one
of
my
goals.
For
later
later
this
year
we
added
aspen
in
2020
during
the
shutdown,
and
I
was
about
three
months
into
my
position,
and
so
at
that
point
it
was
kind
of
just
get
this
out
there
and
started,
and
that
was
about
all
I
could
do.
D
A
C
A
That's
the
best
way
to
do
that.
I
mean
that's
one,
one
of
one
of
our
groups
of
libraries:
that's
part
of
our
consortium
is
a
group
of
prison
libraries
and
none
of
the
prisoners
have
email.
So
we
are
still
working
through
trying
to
figure
out
how
to
get
email
note
how
to
get
notifications
when
the
entire
system
is
designed
around
everybody
having
email.
A
So
that's
been
a
bit
of
an
issue,
so
we're
still
kind
of
working
through
that,
but
yeah
that
actually
works
really
well
on
the
cohort
side
for
email,
emailing
out
those
notifications,
with
the
exception
that
periodically
email
service
providers
change
what
they
consider
spam
and
and
so
every
once
in
a
while.
You
have
to
run
through
a
bunch
of
hoops
to
try
to
get
things
working
again
depending
on
the
service
provider,
but
in
general
it
works
well.
C
A
A
I
mean
I
don't
know
about
all
other
countries.
I
know
they
will
set
up
a
local
number,
so
so
you
it
could
potentially
be
a
solution.
I
don't
know
about
other
countries,
I
don't
know
it's.
Basically,
the
guy
is
named
george,
that
does
it
it's
kind
of
like
a
one-man
shop,
but
not
that
not
george
nichols
but
george
clay,
but
he
so
I
don't
know
what
all
the
capabilities
are,
but
he,
but
that's
how
they've
set
stuff
up
for
us
as
they
found
like
a
local
number.
G
E
C
B
C
A
There's
a
lot
of
settings
that
go
into
that,
so
you
can
have
it
set
up
where,
like
branches
are
independent
of
each
other,
so
they're
all
on
the
same
system.
But
you
can
only
see
your
stuff
for
that
for
each
branch.
So
that's
one
setting
that
you
would,
it
would
be
in
the
those
global
settings
and
then
there's
other
things
you
can
do
where
you
can
see
each
other's
items,
but
you
can
partition
patrons.
A
Some
of
that
has
to
do
with
the
permissions
you
assign
the
login.
So
you
would
you
would
have
to
get
your
admin
settings
kind
of
all
squared
away
the
way
you
wanted
them.
You
would
have
to
create
the
library.
Then
you
would
have
to
create
a
login
with
the
permissions
you
want
for
that
particular
library.
A
A
few
like
districts
within
our
consortium,
so
they
need
to
be
able
to
have
a
patron,
be
able
to
check
out
at
multiple
places.
So
so
that
looks
a
little
different,
so
they
they
could
go
to
one
of
those
branches
within.
But
if
they
want
to
another
library
in
our
consortium
that
wasn't
part
of
that
district,
they
would
have
to
get
a
new
card.
So
that's
how
we
set
it
up.
There's
a
lot
of
different
approaches,
though,.
E
Okay
and
like
for
for
us
a
lot
of
that's
driven
by
sharing
so
like
our
big
deal
is
sharing.
If
you
leave
independent
branches
on
that
makes
sharing
between
the
branches
hard,
but
if
you're,
just
trying
to
kind
of
collect
them
together,
but
not
necessarily
share
the
collections
between
the
two
places.
Independent
branches
puts
up.
Independent
branches
does
a
lot
of
things.
E
C
I
kind
of
the
basic
premise
premises
that
I'd
like
for
the
the
librarians
or
the
ones
that
would
be
adding
the
the
items
to
be
able
to
see
pre-existing
bib
records
and
attach
that
that
are
there
were
created
for
other
independent
branches.
I
guess
and
then
to
be
able
to
attach
their
local,
their
local
item
to
that
holding
or
whatever
the
I
forget,
the
terminology,
but
and
then
for
the
for
the
on
the
front
end
side
on
the
opaque
side.
C
C
A
Yeah,
that's
definitely
attainable.
That's
that's
what
you're
describing
is
essentially
what
my
consortium
does
with
probably
some
more
nuance
in
some
different
places,
but
that's
essentially
how
we
have
our
set
up
where
everybody
shares
the
the
records,
and
so
you
just
attach
your
items
to
existing
records,
but.
A
But
when,
on
our
on
our
aspirin
discovery,
you're
only
viewing
well,
you
can
view
either
the
consortium
we
can
set
it
up
either
way,
where
you
view
the
entire
consortium
and
then
have
the
ability
to
limit
to
your
branches
or
the
opposite
or
just
view
just
those
materials
that
are
in
your
library
and
it
kind
of
depends,
because
we
have
some
small
schools
in
our
consortium
that
aren't
resource
sharing.
So
they
benefit
from
those
records
existing
when
they're
cataloging,
where
it's
they
can.
E
And
we
have
it
set
up
and
we,
like,
I
said
we
don't
use
aspen.
So
in
the
the
vanilla,
opaque
you
can
choose
to
divide
those
out
into
tabs
or
not.
So
if
the
patron
is
logged
in
at
their
library,
then
it's
only
going
to
show
if
their
library
owns
it.
It'll
show
that
holding
separated
out
if
their
library
doesn't
own
a
copy.
On
that
record,
then
they'll
see
everybody's
holdings,
but
if
they're
not
logged
in
it
doesn't
know
what
their
library
is.
So
it
just
shows
everybody's
whole
things.
B
B
And
then
we
have
three
libraries
in
three
countries
in
africa,
so
their
east
africa
group
in
west
africa,
africa
group.
So
they
can
either
do
their
individual
library
or
the
group
that
they're
in
on
the
main
public
site
for
them
to
use
to
just
to
default
to
their
local
library.
They
would
have
to
have
to
be
logged
in.
B
B
B
We're
looking
at
aspen
because
we
want
to
be
able
to
pull
resources
from
outside
databases.
I
want
to
be
able
to
search
jstor
inside
cohab.
That's
why
and
there's
some
other
websites.
We
would
like
to
be
able
to
search
that
database
inside
koha
and
to
my
knowledge,
cohort,
does
not
offer
that
only
aspen
offers.
That
is
that
you.
A
A
So
we
have
so
it
all
comes
under
kind
of
one.
A
one
place
you
can
find.
You
can
find
everything.
So
that's
one
advantage.
The
other
huge
advantage
is
record
grouping,
so
it
makes
it
if
you
have
a
lot
of
different
like
if
you
think
in
a
public
library
in
like
tom
sawyer,
there's
a
million
different
editions.
Those
could
all
be
on
their
own
different
records
and
that
makes
a
real
mess
in
the
catalog.
A
This
kind
of,
like
folds
the
accordion
and
put
puts
them
all
together,
which
makes
for
a
particularly
large
consortium
like
ours,
with
messy
bad
cataloging,
from
from
lots
of
libraries
that
used
to
be
independent,
and
it
was
easy
to
find
their
stuff,
no
matter
how
bad
the
cataloging
was.
Well,
you
pull
that
all
together.
It
creates
a
mess
so
that
that's
another
thing
and
then
it's
all
so
much
more
customizable
there's
you
can
really
get
it
to
look
and
feel
the
way
you
want.
A
They've
added
features
like
web
builder,
where
you
can
basically
like
in
uinta
in
utah
they're
using
they
did
that
instead
of
went
out
and
got
a
new
website,
they
just
use
their
their
discovery
as
their
primary
website
now,
because
it
has
so
much
ability
to
add
stuff.
So
those
are
some
of
the
advantages.
A
It
also
works
faster
too,
which
is
you
know,
depending
on
the
size
of
your
consortium.
If
you
have
a
small,
if
you
don't
have
a
a
huge
consortium,
then
things
work
pretty
fast
but
like
when
we
have
like
over
60
items
on
a
record.
Placing
a
hold
in
quahog
takes
like
it's
down
to
45
seconds
we
just
tested
yesterday,
but
it
is
not
fast.
E
On
the
topic
of
record
grouping
and
fiberization,
I've
been
talking
with
sam
at
uinta
and
he
asked
me
to
share
it
wherever
I'm
at
so
he
he
did
say
that
he's
working
on
a
development
and
a
grant
through
the
state
library
of
utah
he's
trying
to
get
that
going
to
bring
that
to
baseline
cohas
because,
like
even
with
aspen,
that's
only
happening
in
the
opac,
and
it
would
be
nice
to
be
able
to
do
that
in
the
staff
client
too,
so
yeah.
I
was
excited
about
that
too.
E
So
I'm
hoping
that
that
can
take
off
and
I'm
thrown
out
there
I
mean
if,
if
he
needs
additional
funding,
I
told
him
that
we
would
definitely
be
able
to
throw
in
on
it
we've
just
never.
It
was
like
a
20
000
development
on
the
bywater
site,
so
it
was
just
out
of
reach,
but
if
he
can
get
that
off
the
ground,
I
think
that
would
be
great
for
for
baseline
co-op.
So.
A
We're
often
like
there's
the
patron
thing
here
and
there's
the
staff
thing
here,
because
they
often
forget,
like
the
terminology,
what
like
cohort
or
aspen
is
or
so
we're
always
like
staff
here
patron
here.
So
I
I'm
assuming
that's
kind
of
where
that
was
coming
from,
but
yeah
there
is
a
behind-the-scenes
administrative
panel
on
aspen
discovery,
but
but
this
would
be
adding
that
very
nice
record
grouping
feature
to
coho,
which
would
be
very
welcome.
C
A
A
Yeah
so
call
current.
It
would
do
that
so
right
now
the
way
aspen
functions
is.
It
does
group
together
different
formats
that
are
considered
the
same
thing,
so
that
would
be
like
a
book
on
cd
or
a
large
print
version.
It
would,
but
it
would
distinguish
the
different
formats
what
it
doesn't
do.
Is
it
doesn't
loop
in
films
into
that,
because
that
is
different
enough
from
the
original.
D
C
A
C
A
Just
because
it's
just
so
much
nicer,
it's
much
easier
to
navigate
like
when
you
have,
because
we
have
600
000,
plus
records
like
and
again
inconsistent
cataloging
practices
like
just
if
you,
if
you
type
in
harry
potter,
you
get
a
mess
on
your
hands,
there's
hundreds
of
results
and
they're
not
organized
particularly
well
and
yeah.
That's
always
my
go-to
example
of
like
use
the
discovery
layer
because
it
works
so
much
better.
D
And
yeah
I
put
in
chat
a
link
to
one
of
our
aspen
catalogs,
and
so
you
can
kind
of
go
through
and
if
you
click
on
a
title,
it
gives
you
a
pop-up
and
it
shows
how
the
different
some
of
them,
the
different
formats,
are
broken
out.
But
they're
still
grouped
into
one
into
one
record.
But
that's
the
that's.
The
aspen
not
necessarily.
A
A
They
basically
expand
the
list
so
like
I
have
that
tom
sawyer
example.
We
have,
I
think,
when
I
looked
at
one
point,
we
had
55
different
editions
of
tom
sawyer,
just
because
it's
in
the
public
domain
and
anytime
somebody
buys
something
it's
probably
a
new
addition,
so
all
that
will
be
if
you
just
want
to
place
a
hold
on
the
book
and
you
don't
care
what
edition
you're
getting
you
just
hit
that
button.
A
B
B
B
D
And
there
are
a
lot
of
options,
for
example,
there's
the
the
koha,
the
jquery
library
and
things
like
that,
and
so,
if
you,
if
you
start
looking
at
the
stuff-
and
you
wonder,
is
there
a
way
to
customize
this?
It
may
not
be
native
to
cohort,
but
there
are
a
lot
of
ways
you
can
customize
things
and
and
make
it
do
what
you
want
through
some.
Some
of
that.
A
All
right
go
ahead,
I
was
just
gonna
say:
george
and
christopher
brennan
also
do
a
series
of
videos
with
a
lot
of
different
ways
to
manipulate
coho
using
things
like
jquery
and
css,
and
those
are
all
in
the
library
but
actually
watching.
Somebody
demonstrate
the
before
and
after
is
highly
effective.
A
A
C
A
Well,
I
know
I
mean
right
now:
the
aspen
discovery
community
is
really
just
starting
to
grow.
It's
nothing
like
coho,
where
there's
so
many
different
options
for
support,
there's
so
many
people
that
are
unsupported
and
like
a
huge
community
out
there,
that's
global
to
lean
on
so
that's
building
so
it'd
be
fantastic.
I
think
if
more
people
started
spreading
that
in
different
ways,
so
it
could
build.
C
A
Variety,
because
I
mean
that
that's
to
me,
that's
the
beauty
of
open
source.
Is
you
get
so
many
people
using
things
in
so
many
different
ways?
It
just
really
improves
the
product
experience
for
everybody.
Even
if
some
ways
you
use
it
will
never
be
the
same
way.
I
use
it.
It
still
just
benefits
the
code
overall.
So
so
I
I
hope
that
you
can
find
a
way
to
make
that
work.
Even
if
it's
having
some
indian
support
to
then
maybe
they
can
once
they're
familiar.
A
Well,
I
mean,
like
I
said
it
is
published
and
they've
been
collaborating
with
ptfs
europe,
so
it
it
is
out
there,
but
I
think
what
has
happened
is
the
majority
of
the
development
is
coming
from
bywater,
because
the
lead
developer
mark
he
he
basically
created,
took
viewfind
and
turned
it
into
what
it
looks.
What
aspen
looks
like
now,
so
he's
really
pushed
it
along
with
a
lot
of
momentum,
but
that
is
not
sustainable
for
the
rest
of
time.
A
You
want,
you,
don't
want
all
your
eggs
in
one
development
basket
so
when
he
was
doing
this
independently,
we
waited
until
he
went
with
bywater
before
we
switched
over
there.
Just
because
now,
there's
other
you
know
knowledge
and
support,
and
right
all
that
and
again
the
more
this
becomes
grows
worldwide.
The
more
it
will
look
like
coho,
where
it's
and
and
even
though
coho
is
global,
there's
still
a
finite
amount
of
people
that
are
actually
writing
code
on
it.
C
C
B
C
E
So
I'm
hoping
that
over
time
that
comes
out
and
it's
easier
because
right
now
I
wouldn't
know
what
to
do
with
it,
but
it
would
be
nice
to
be
able
to
set
up
a
junker
server
to
spin
it
up
and
see
if
I
can
make
it
work
with
our
system
without
paying
for
support.
So
I
do
get
where
you're
kind
of
it
does
sort
of
feel
like
it's
a
bywater
proprietary
thing
right
now
and
when
we
were
first
introduced
to
aspen
back
in
pueblo.
E
I
think
we
can
talk
with
mark
about
it,
but
we
can't
even
really
see
the
code
on
github.
So
it
is
it's
getting
there.
It's
improving,
but
I
think
what
bob
mentioned
of
how
it's
sort
of
it's
just
now,
starting
to
grow
so
yeah,
I'm
hopeful
that
it
becomes
a
thing
that
can
be
played
with
more
easily
in
the
not
too
distant
future.
As
more
people
pick.
G
G
A
Has
happened
is
they're
growing
so
fast
that
they
haven't
caught
up
with
some
of
that
documentation
and
they've
actually
expanded
that
team
quite
a
bit,
but
they're
still
growing
at
a
rate
where,
where
that
that's,
they
haven't
caught
up
with
a
lot
of
those
things.
So
at
some
point
I
expect
that
will
happen.
I
guess
it's
possible
that
they
could
continue
to
grow
at
an
astronomical
rate
and
it'll
be
a
while
before
we
catch
up.
But
at
some
point
I
imagine
it'll
slow.
G
A
bit,
I
think,
one
of
the
things
that
one
of
the
unsung
heroes
of
coho
documentation
is
nicole,
who
used
to
work
for
bywater
that
shane
yeah,
nicole
engard,
and
she
did.
I
mean
she
practically
wrote
the
entire
quahog
documentation
herself,
because
that's
all
she
did
when
she
would
go
out
on
training,
she
would
go
and
she
would
train
and
then
she
would
go
back
to
her
motel
room
and
write
documentation
all
night.
G
E
Yeah-
and
it
just
seems
like
some
of
the
structures
aren't
in
place
like
I
know,
I
talked
to
somebody
and
all
of
the
bug
tracking
is
happening
within
bywater
system,
so
I'd
love
to
see
that
sort
of
exposed
the
same
way.
Gohan
does
bug
tracking
and
I
know
that's
that's
just
part
of
the
growth
of
the
product,
but
it's
also
frustrating
for
people
that
don't
have
it
because
you
can't
see
inside
without
access.
G
I
think
that
would
be
something.
Maybe
you
and
I
could
say
to
bywater.
Is
you
know
we're
not
interested
in
it
until
we
can
see
how
the
bugs
are
tracked,
and
you
know
if
enough
people
say
you
know
we
want
to
see
the
community
and
how
the
community
works
before
we're
willing
to
to
to
adopt
it.
That
might
be
a.
A
A
A
F
C
B
A
We
we
largely
used
to
rely
on
the
documentation
that
existed,
but
that
is
in
I
mentioned
our
prison
libraries
earlier
they
their
clerks
are
all
are
all
offenders,
so
they
don't
get
access
to
youtube
and
things
like
that,
so
we've
been
having
to
create
our
own
content
and
have
it
funnel
through
their
the
the
systems
tech
department
to
like
land
on,
in
particular,
folders
that
they
have
access
to.
So
we've
been
getting
more
into
producing
that
content.
Lately.
C
Could
I
ask
one
more
question:
it's
not
really
a
consortium
question,
so
you
know
you're
talking
about
the
the
record
grouping
feature
that's
available
in
aspen.
I
that
an
immediate
concern
that
we're
going
to
have
is
just
on
a
very
limit.
Well,
it's
extensive
across
the
catalog,
but
it's
only
like
two
records,
so
you've
got
a
better
quality,
bib
record
and
a
lesser
quality
bib
record
and
you'd
like
to
overlay.
A
There's
a
merging
cohort,
it
depends
on
which
version,
because
I
think
some
of
those
are
more
recent
versions.
The
merging's
gotten
a
lot
better
and
easier
to
do,
but
yeah
you.
You
can
merge
just
off
a
search
if
you
search
by
like
a
title,
and
you
see
two
exact
things
you
can
check
box
them
and
do
a
merge
from
there
yeah
that's
easy
or.
A
A
C
G
I
have
51
libraries
and
a
lot
of
people
that
are
not
that
are
not
skilled,
librarians
they're
they're.
You
know,
a
lot
of
our
libraries
are
part-time
libraries.
The
director
is
a
18-hour
week,
employee
and
so
that's
seems
like
half
of
my
support
requests.
Are
you
know
somebody
added?
You
know
I've
got
six
records
for
this
new
book.
Can
you
merge
them?
G
I
do
a
lot
of
that.
That's
I've
been
off
since
last
friday
and
I
just
checked
my
email
and
I've
got
like
12
requests
for.
Could
you
merge
these
hopefully,
hopefully
like?
Six
of
them
are
all
for
the
same
record,
but
we'll
have
to
see
it.
My
it's
with
my
luck.
It'll
be
12
individual
merges
that
need
to
happen.
A
Yeah,
whenever
we
get
a
request
for
a
merge
somebody's
like
could
you
check
out
this
title
looks
like
there
might
be
a
merge,
and
usually
you
know
it's
like
oh
yeah
there's.
They
identify
two
things
that
could
merge,
but
there's
really
four
records
that
could
be
merged
and
then
there's
like
another
edition
that
could
be
merged
with
another
record,
and
then
the
audio
book
needs
to
be
merged
as
well,
and
then
you
kind
of
look
at
it
and
you're.
Just
like
okay
yeah.
A
G
A
G
Yeah,
I
have
the
merge.
The
merge
controls
are
all
hidden,
so
I'm
I'm
really
the
only
one.
The
knuckles
office
is
the
only
place
where
that
has
access
to
that.
Otherwise,
otherwise
there
would
be
one
record.
There
would
be
one
bib
record
for
huckleberry
finn
and
tom
sawyer,
but
with
all
of
the
all
of
them
on
one
record
or
things
that
in
translation
they
would
all
be
the
same
record.
Dante's
inferno
there
would
be
one
dante's
inferno.
It
doesn't
matter
who
the
translator
is
anything
like
that.
B
One
question-
and
I
could
have
asked
this
before,
but
I
forgot
the
answer:
do
you
share
online
resources
and
how
do
you
share
so
how
do
you
have
it
so
right
now
we
have
an
e-library
that
all
of
our
online
resources
are
that's
how
you
can
filter
them
out
in
the
search
results.
That's
how
we've
chosen
to
share
it.
Is
there
a
better
way
for
a
local
library
to
have
an
e-resource
that's
available
to
everybody.
B
G
A
That
situation,
so
so
this
is
how
we
use
aspirin
discovery,
because
some
libraries
have
like
cupola
and
most
don'ts.
Everybody
has
cloud
library,
but
only
some
have
overdrive,
so
you're
able
to
configure
that
per
url
per
each
location.
What
gets
seen
and
what
doesn't
so
that's
how
we
we
we
have
to
handle
that.
G
Yeah
now
that
would
be
nice
for
us
because
we
do
have
some
like
you
know.
All
of
our
libraries
have
hoopla.
Not
all
of
our
libraries
have
overdrive,
so
it
would
be
nice
to
for
the
libraries
that
do
have
overdrive
to
be
able
to
put
that
in
the
catalog
and
not
only
do
they
do.
Some
libraries
have
overdrive
and
sub
libraries
don't,
but
some
libraries
have
different
overdrive
collections
than
others.
G
A
G
One
of
the
things,
though,
that
we
try
to
do
you
know
I
that
is
one
of
the
things
I
like
about
the
coho
back,
and
you
know
our
philosophy
is
that
it's
all
shared
it's
all
stuff.
It's
all
about
sharing,
and
so
our
catalog
is
open
to
everybody
in
the
same
way,
and
I
think,
having
separate
catalogs
makes
things
more
complicated
for
the
for
the
basis
of
sharing.
G
That
would
be
an
issue
for
us
is
that,
for
years
and
years
and
years
and
years
and
years,
all
of
our
library
cards
at
all
that
almost
all
of
our
patrons
have
have
one
catalog
address
on
it
and
so
saying
to
some
people
saying
it
would
be
a
situation
where
saying
to
people
your
life,
the
catalog
is
the
address.
That's
printed
on
the
back
of
your
card
that
would
need
to
stop.
If
we
and
and
those
you
know,
150
000
people
that
already
have
cards
would
need
to
be
told.
G
E
D
This
is
a
first
for
us,
but
we're
going
to
be
an
early
adopter,
so
we're
doing
it
end
of
june
and
the
main
reason
we're
doing.
That
is
because
we
have
a
migration
that
happens
right
in
august,
and
so
we
wanted
to
get
them.
We
didn't
want
to
have
a
upgrade
right
after
they
migrated
and
so
we're
getting
to
do
two
two
new
things
for
me
this
year.
So
that's
that's
exciting.
A
Yeah
we've
done
early
adopter
before
we
had
one
bad
experience
that
wouldn't
necessarily
have
been
prevented.
Had
we
waited
just
because
of
the
way
we're
set
up
is
different
from
other
consortia,
so
it
still
might
have
happened
anyway,
but
but
mostly
it's
like
we,
they
don't
when
they
actually
go
over
some
of
the
training
on
new
features.
It
happens,
so
it
happens
after
you
would.
You
would
actually
have
it
live
on
production
and
that
just
doesn't
work.
We
don't
have
enough
staff
to
go
through
each
bug
and
look
at
each
each
thing.
A
A
D
D
G
E
A
Yeah,
our
big
thing
was
that
they
just
changed
the
way
that,
like
I,
was
mentioning
earlier,
how
slow
our
holds
load
when
there's
a
lot
of
items
that
just
has
to
do
with
them,
trying
to
load
that
in
a
different
way
that
had
some
appeal,
but
it
just
takes
more
resources
to
load
it.
That
way.
So
that's
what
you
know,
I'm
sure
who
whomever
was
testing
it,
wasn't
testing
it
on
a
record
that
had
80
items
attached
so
they're
like
hey.
A
G
On
old,
stable,
because
that
way,
we'll
add
six
months
to
work
out
all
the
bugs-
I
don't
know
if
jason
remembers
that,
but
we
had
every
day
I
had
to
go
in
and
generate
a
run,
a
report
to
see
who
got
fines
that
were
undeserved
yeah.
We
didn't
have
that
big
of
a
problem,
because
we
don't
use
grace
periods
that
much
every
single
library
at
the
system
I
worked
at
then
had
a
grace
had
had
fines
and
a
grace
period.
G
A
A
I
don't
know
off
the
top
of
my
head.
I
thought
I
had
it
on
my
personal
calendar,
but
it's
probably
on
the
quahog
calendar,
because
we
should
be
doing
every
other
month,
so
it
should
be
in
july.
Oh
there,
it
is
july
28th
same
time
same
link.
All
that's
the
same.
So
please
join
us
again
for
more
discussion.