►
From YouTube: Consortia Special Interest Group - 9/24/2021
Description
Recorded during the Fresh Perspectives conference.
Chat logs:
06:23:01 Heather Hernandez (she/her): "Cataloging for consortiums?":)
06:23:30 Christopher Brannon: Consortiums for Cataloging
06:23:52 George Williams - NEKLS: I showed up at one meeting.
06:25:26 Michael Adamyk (CKLS): Heather’s ready for cataloging!
06:25:37 Heather Hernandez (she/her): Always ready for cataloging!!
06:27:57 Michael Adamyk (CKLS): I’d be interested in that too, Bob
06:31:37 Jason: https://wiki.koha-community.org/wiki/JQuery_Library#Show_Local_Copy_Status_in_Staff_Search_Results.2C_Hide_all_others
06:34:54 Heather Hernandez (she/her): ….aaaand back to cataloging!:)
06:35:22 Jason: https://github.com/bywatersolutions/koha-plugin-deduplication-tool
06:37:13 Christopher Brannon: OpacSeparateHoldings
06:38:38 Jason: https://wiki.koha-community.org/wiki/SQL_Reports_Library#Duplicate_ISBNs_Alternative
06:42:30 Heather Hernandez (she/her): Catalogers should use their powers for good instead of evil!!
06:50:46 George Williams - NEKLS: 2015 conference page
06:54:51 George Williams - NEKLS: http://web.archive.org/web/20150428062639/http://www.mercyhurst.edu/academics/library/2015-koha-north-american-users-group-conference
06:55:18 George Williams - NEKLS: Once again I have carpool duty so I'll log back in from home in about 30-40 minutes from home.
06:55:29 Michael Adamyk (CKLS): Bye George
07:13:05 Michael Adamyk (CKLS): I have to go, have a great weekend everyone!
07:19:15 Christopher Brannon: Thank you! This was fun. I definitely want to continue being part of this group.
07:19:53 Christopher Brannon: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19889
A
So
a
little
background.
We
had
been
running
some
meetings.
Well,
we
haven't
done
it
probably
about
eight
months,
but
we
weren't
getting
a
whole
lot
of
attendance.
There's
a
couple.
People
jason
was
a
regular
attendee
michael,
was
there
a
few
times,
but
for
whatever
reason,
we
weren't
getting
a
lot
of
attendance.
So
this
is
a
good
opportunity
to
see
if
there's
interest
in
discuss
in
having
these
meetings
return
at
the
time
we
were
doing
them
every
other
month.
A
George
did
show
up
at
one
meeting
that
is
correct
and
then
we
can
talk
also
spend
the
rest
of
the
time.
Also
talking
about
particular
challenges.
You're
facing
stuff
that's
coming
in
the
2011
update
that
might
be
of
impact
to
consortia
that
that
type
of
stuff,
so
I
guess
ultimate,
probably
a
good
place
to
start-
would
be
just
to
hear
if
there
are
people
who
have
questions
or
or
issues
that
are
concerning
them
that
come
up
in
that
multi-branch
type
setup.
B
The
first
one-
and
I
feel
like
it's
a
setting
that
I
just
don't
know
about
when
you're
searching
in
the
staff
interface
or
the
opac
in
no
pack,
if
you're
not
logged
in,
is
there
a
way
actually,
opec
you'd
have
to
be
logged.
In
sorry,
answer
that
question
in
the
staff
interface
is
there
a
way
for
when
I'm
searching
for
a
title,
that
my
library
search
results
are
first.
A
A
A
C
A
A
B
A
There's
probably
a
way
to
do
that
it
also.
The
other
factor
is
that
you
have
to
be
able
to
see
it
on
the
facets
and
that's
where
you
know
how
many
facets:
you're
showing
and
things
like
that
are-
are
relevant,
because
if
it's
not,
if
it
doesn't
pop
up
on
the
page,
then
the
jquery
doesn't
doesn't
highlight
it
like
that.
So
you
need
to
get
it
showing
first,
then
you
can
get
that
happening
now.
D
I
think
it
wouldn't
be
hard
too
hard
using
jquery
to
make
sure
that
there's
under
the
home
library
facet
that
there's
always
a
facet
for
the
library
that
you're
logged
in
at
by
getting
the
the
code
from
the
the
logged
in
page
and
putting
a
link
there.
That's
all
so
that
you're
always
see
that
link
for
a
home
library.
For
your
library,
one
of
the
things
that
I
saw
on
bob's
screen,
though
let
me
share
mine,
real
quick
that
I
don't
know
if
you
noticed.
D
D
D
But
if
we're
just
showing
the
local
copies,
it's
only
going
to
show
you
all
of
the
ones
from
the
other
libraries
are
hidden,
so
that
might
make
it
a
little
easier
for
the
staff
at
your
various
libraries
to
until
there
is
a
better
way
of
doing
it
to
help
them.
You
know,
make
it
easier
to
sort.
You
know
what
do
we
have
and
what's
local
and
what's
not
local.
D
Yeah,
it's
you
know
it's
something.
I've
got
working
on
my
system.
I
don't
know
that
I've
ever
had
to
update
it,
but
it's
certainly
something
that
it
wouldn't
hurt.
If
maybe
one
of
us
that's
using
it
went
back
and
reviewed
the
code
and
make
sure
that
the
the
code
that's
on
the
wiki
will
actually
still
work
in
a
current
version.
D
G
I
have
to
say
that
we're
we're
still
using
zebra
at
our
library
and
one
of
our
libraries
has
just
got
set
using
magic
jquery
that
someone
else
made
so
that
when
they
put
in
a
search,
their
items
always
hit
top
of
the
list
they
have
that
done
and
by
water
set
that
up
for
us.
So
if
that's
any
help
to
anybody,
it
can
be
done
and
on
the
opec
side
of
things
we
have
it.
A
A
H
E
G
We
do
have
that
we
set
it
so
that
the
first
search
you
always
do
is
for
your
home
library,
and
then
you
have
the
option
of
going
to
all
libraries.
After
that
we
have
a
horribly
a
horrible
catalogue
with
so
many
duplicate
records
that
patrons
often
miss
their
own
home
library
item
and
so
by
doing
it
that
way,
they'll
get
their
item
before
they
get
another
library.
G
A
It's
a
great
thing
if
you
ever
have
like
an
intern,
that's
a
great
project,
something
like
that.
That
doesn't
require
a
lot
of
training
but
gives
them
some
good,
hands-on.
Cataloging
experience
we've
done
that
before
we
don't
have
a
lot
of
our
libraries
where
I'm
super
comfortable
with
them
making
merges,
but
we
do
have
them
reporting
them
back
to
us.
A
E
We
did
a
deduplication
before
I
started
working
here,
which
was
also
before
we
were
bywater
customers
and
they
probably
wouldn't
have
let
us
do
it,
but
I
would
not
recommend
just
trying
to
do
a
full
system.
Dedupon
like
isbn,
because
that
didn't
work
I
mean
it
worked,
we're
still
cleaning
it
up
to
this
day.
So
I
would
err
on
the
side
of
caution
and
do
things
in
small
batches.
If
you're
gonna
d-do
things.
F
There
is
a
system
preference
just
for
the
opec
for
separating
the
holdings,
so
you
can,
if
you're
logged
in
that's
the
one
caveat
if
you're
logged
in
it
will
separate
holdings
from
one
branch
and
the
rest
of
the
the
branches
on
different
tabs,
it
would
be
nice
down
the
road
if
this
feature
incorporated
ip
addresses
that
could
help
parse
this
out.
So
you
didn't
have
to
be
logged
in
for
it
to
work,
but
right
now
it
only
works
if
you're
logged
in.
E
E
You
can
never
get
totally
accurate
on
on
reports,
but
he's
normalized
out
the
isbn
to
try
and
identify
possible
duplicates
and
then,
if
you
click
that
fast
merge
link
in
the
report,
it'll
take
you
straight
to
the
the
merging
tool
which
kind
of
speeds
up
the
process,
because
when
you're
merging
records,
usually
you
have
to
put
them
on
a
list
and
then
get
them
together
and
then
check
them
and
merge
them.
And
it's
a
clunky
process
for
sure.
E
G
E
It's
easy,
that's
what
my
head
is
always
complaining
about.
She's
like
it's
cataloging,
so
easy.
I
go
out
and
train
them.
They
know
what
they're
doing
it's
not
a
problem
and
then,
when
she
gets
back
and
runs
the
reports
they
didn't
listen
to
her
at
all.
So
I
would
say:
cataloging
just
in
general
is
is
also
on
this
list
of
consortium
problems
for.
A
A
A
We've
really
just
tried
to
simplify
things
as
much
as
possible,
so
that
we're
not
actually
trying
to
train
people
to
be
like
fully
knowledgeable
catalogers
just
get
the
copy
cataloging
down
and
then
when,
when
that
doesn't
apply,
then
we
can
provide
some
additional
help.
Some
additional
resources
that
type
of
thing-
and
I
do
think
we
we
do
see
less
problems
with
newly
cataloged
stuff
than
we
do
when
we
inherit
bad
cataloging
from
a
library,
that's
been
independent.
E
E
F
A
Way
worse,
so
one
thing
we
just
did
to
hopefully
discourage
dupe,
adding
duplicate
records.
Is
we've
actually
put
our
database
back
into
the
z3950,
so
you
will
see
if
we
have
a
title
in
there,
it
will
pop
up
in
the
search
and,
and
so
that
will
hopefully
indicate
that
maybe
you've
skipped
a
few
steps
and
you
need
to
go
back
and
just
find
the
the
the
record
in
the
system
and
not
actually
import
anything
since
it's
already
there.
A
G
Yes,
that's
an
ongoing
problem
with
us
as
well.
We
started
off
life,
we
use
the
transport
cost
matrix
and
then
we
went
to
the
static
queue
holds
and
they
were
ordered.
And
now
we've
gone
to
randomizing.
That
we've
only
just
started
that
this
this
month,
so
we're
we're
hoping
that
that
solves
some
of
the
the
problem
of
the
biggest
library
getting
all
the
holes
and
the
smallest
libraries
getting
no
holes.
A
A
So
so
some
libraries
don't
want
to
lend
some
things
that,
like
dvds
and
things
like
that,
that
are
really
popular.
So
we
have
to
make
sure
that
those
don't
get
that
the
patrons
of
the
libraries
aren't
lending
those
aren't
requesting
all
the
whole,
all
those
as
well,
and
so
we
have
a
very
complicated
branch
transfer
limits.
Matrix
going
right
now
that
yeah,
there
is
a
real
pain,
particularly
for
our
schools,
when
it's
time
to
turn
on
and
off
a
school
there's
a
lot
of
it's
not
just
like
a
button.
A
D
The
way
that
they
were
managing
libraries
getting
hit
harder
with
requests
than
others
is,
they
would
run
a
report
at
the
end
of
each
month.
That
said,
these
were
the
this:
is
the
ratio
of
net
borrowers
to
net
lenders
and
then
they
would
turn
that
that
list
upside
down
and
program,
those
in
so
the
next
month.
The
people
that
that
shared,
the
least
would
be
the
ones
that
would
be
at
the
top
of
the
holds
queue,
but
the
the
issue
with
that
is
number
one.
D
It's
a
lot
of
work
to
do
that
monthly
and
number
two.
Is
that
the
the
reason,
those
libraries
that
weren't
sharing
as
much
weren't
sharing
much
as
much
generally
was
because
they
didn't
have
anything
and
so
putting
them
at
the
top
of
the
queue?
Didn't
really
help
the
situation
any
and
currently
we're
not
using
the
transportation
cost
matrix.
I
can't
speak
right
right
now.
D
The
transportation
cost
matrix
we're
not
using
it,
because
we
have
a
similar
situation
with
with
that,
where
it's
all
the
big
libraries
would
be
hit
harder
by
the
transportation
cost
matrix,
because
you
know
where
we
are.
We've
got
all
of
the
population
in
one
corner
of
our
consortium
and
then
from
there
in
every
direction,
radiating
out,
it's
less
and
less
populous,
so
the
libraries
that
have
the
easiest
time
sharing
where
the
cost
would
be
lowest
to
share
things
among
each
other
are
the
ones
that
are
that
are
already
getting
hit
the
hardest.
D
So
it
would,
rather
than
making
it
easier
on
those
libraries
that
are
already
sharing
a
lot,
it
would
just
mean
that
they
would
be
sharing
more
to
use
the
cost
matrix.
So
we
found
that
the
random
randomization
is
the
most
fair
way
that
we've
come
up
with
in
our
geographic
situation,
to
to
make
it
fair
for
the.
F
Libraries,
eric
are
consortiums
a
little
bit
different
in
that
you
know
the
the
bigger
libraries
are
operating
more
often
and
can
fill
holds,
and
we
want
to
share
those
things
out,
but
several
years
back,
I
did
a
presentation
on
the
transport
cost
matrix
over
in
the
conference
over
in
pennsylvania,
and
I
don't
know
if
this
information
is
still
online
and
I
can
always
dig
up
the
the
information,
but
we
set
our
set
up.
Our
transport
cost
matrix
and
we
haven't
touched
it
for
years.
F
Everybody's
been
happy
with
with
how
it
works,
but
I
had
shared
a
spreadsheet
that
I
had
come
up
with
that.
Basically,
we
factor
the
cost
of
the
transport
on
more
than
just
distance.
You
know,
distance
is
one
of
the
factors
of
you
know
where
you
know
who
should
be
hit
up
for
that
item.
We
also
factor
in
you
know
how
frequently
courier
runs
at
different
locations,
because
we'll
have
libraries
that
are
open
two
days
a
week
and
it
doesn't
make
sense.
F
F
If
you
know,
we've
got
multiple
couriers,
we've
got
a
main
career
that
goes
out
to
most
of
our
branches,
but
within
some
of
those
outlying
branches,
they
have
a
sub
courier
and
if
they
go
through
a
sub
career,
then
that
knocks
them
down
the
list
even
more.
You
know,
so
we
figure
out
all
these
things
in
our
in
our
spreadsheet.
E
And
I'll
just
say
that
we're
also
a
transport
cost
matrix
consortium
and
I
did
use
christopher's
spreadsheet
to
get
that
set
up
initially
and
we're
doing
a
sort
of
the
same
thing.
I
can
show
you
what
it
looks
like
what
our
spreadsheet
looks
like
I've
got
that
pulled
up
over
here.
Ours
is
like
very
basic.
You
can
see,
there's
lots
of
it.
It
caps
out
at
four.
Zero
is
iowa
because
we're
the
system
center,
and
we
do.
We
are
the
800
pound
gorilla
or
whatever
bob
said.
So
we
have
a.
E
H
E
Large
libraries
are
ones
our
medium
libraries
are
twos
and
then
our
smaller
ones
are
threes
and
fours,
and
we've
calculated
it
based
on
their
courier
route
in
relation
to
each
other.
How
many
days
their
career
delivers
and
how
many
days
they're
open,
because
I
have
some
libraries
that
are
even
though
they
get
career
three
days
a
week,
they're
only
in
the
library
two
days
a
week,
but
it's
still
really
flat.
So
it
still
has
a
degree
of
randomization,
but
it
also
gives
us
control
over.
We
can
influence
a
little.
We
can.
E
We
can
put
us
at
the
top
and
then
I'll
put
the
burden
down
on
the
larger
libraries,
because
they
are
going
to
have
more
staff
in
a
larger
collection
to
fill
those
holds.
So
again,
just
like
christopher
was
saying
this
is
once
since
we've
implemented
it.
We
haven't
had
any
complaints,
so
it
has
helped.
We
also
have
the
whole
shark
and
fish
reciprocity
situation
going
on
for
our
new
items
which
works
we
do
have.
E
We
recently
discovered
that
one
of
our
libraries,
some
bad
things,
happened
there.
She
has
a
huge
collection
and
half
of
it
isn't
cataloged,
so
she
had
just
been
putting
cards
in
it
and
letting
her
own
patrons.
Have
it
so
we've
got
a
big
we've
got
some
cleanup
to
do
and
damage
control
to
do
there,
but
I
know
that
I
have
other
libraries
doing
similar
things
and
I
don't
know
how
to
get
get
that
fixed.
E
All
right,
so
what's
the
quick
and
dirty
the
so,
we
want
to
make
sure
that
it's
fair
for
our
libraries
when
they're
sharing
their
new
items.
So
we
have
a
policy
in
place
that
allows
them
to
either
choose
to
be
a
shark
which
lets
them
immediately
share
and
borrow
their
new
items
or
a
fish
which
lets
them
delay
the
sharing
of
their
new
items
outside
their
library
for
six
weeks.
So.
E
We
encourage
everyone
to
be
sharks,
because
that
gets
new
items
in
everyone's
hands
faster,
but
we
do
have
some
libraries
where
either
the
librarian
or
the
board
has
decided.
We
want
that
shelf
of
new
items
setting
in
our
library.
We
want
our
patients
to
have
it
first,
so
we've
used
the
holds
policies.
We
don't
use
the
branch
transfer
limits
like
bob
does
so,
but
we
use
we
have
hold
policy
set
up
and
then
some
extra
jquery
set
up
so
and
some
rude
messaging.
E
It
broke
along
the
way,
so
things
that
fish
libraries
do
manage
to
get
put
on
hold
for
shark
items,
do
show
up
on
the
holds
queue,
so
I've
had
to
go
through
and
just
hide
any
any
of
those
requests
on
the
holds
queue
so
that
we're
not
actually
filling
fish
holds,
and
I
have
a
presentation
I
did
on
this
in
coeur
d'alene.
If
you
need
to
see
it,
but
that's
that's
the
long
and
the
short
of
the
sharks
and
the
fishes
and
yeah.
F
We
had
a
similar
situation
where
libraries
were
withholding
stuff
for
their
their
patrons
for
for
a
long
time,
and
we
uncovered
that
you
know
we
found
out.
You
know
we
just
saw
some
weird
things
going
on
in
the
system.
It's
like.
Why
are
these
things
not
going
out
and-
and
we
had
this
big
discussion
in
our
consortium
and
we
really
had
to
get
on
the
libraries
about
you
know
what
this
we're
sharing
stuff.
This
is
the
policy
of
of
the
consortium.
F
You
know
you
know
to
share
these
things
and
we
we
had
to
address
that.
But
the
thing
that
really
helped
alleviate
that
was
when
we
adopted
the
the
local
holds
priority
system
setting
when
they
introduced
that
that
that
made
a
huge
difference
and
we
also
contributed
to
expanding
the
functionality
of
the
local
holds
priority.
F
But
that
made
a
huge
difference
and
it
gave
those
little
libraries
that
were
trying
to
let
their
patrons
you
know
get
the
stuff
that
they've,
just
added
to
the
system
gave
them
a
little
bit
more
authority
in
there
to
to
do
what
they
wanted
to
do
and
and
not
feel
like.
They
were
just
being
stomped
on
by
all
the
other
libraries
with
their
with
their
materials.
E
Yeah-
and
we
have-
we
have
an
informal
policy-
that's
basically
that
patrons
in
front
of
you.
They
picked
it
up
off
the
shelf,
give
it
to
them,
that's
terrible
customer
service
to
say
sorry,
that's
gotta
hold,
you
can't
have
it,
and
we
always
maintain
that
the
the
library
that
bought
the
book
can
check
it
out
to
one
of
their
patients
first,
even
if
there's
not
a
hold,
because
a
lot
of
my
little
libraries
aren't
putting
holds
on.
E
But
after
that,
if
they're
a
shark,
it
has
to
go
with
the
flow,
let
it
let
kohl
work
if
they
want
it
back.
All
they
have
to
do
is
put
a
hold
on
it,
because
we
do
use
localhost
prioritization
as
well,
and
that
did
smooth
things
out.
I
think
our
biggest
problem
is
the
stuff
happening
outside
of
kawa
that
we
can't
really
see,
but
we're
pretty
sure
is
happening
and
that's
more
of
an
administrative
thing.
We
need
to
have
a
policy
beat
down.
E
I
guess
we
also
don't
have
a
a
regular
participation
agreement,
which
is
something
that
we've
started
talking
about,
just
something
that
the
librarian
and
their
board
has
to
acknowledge.
Every
year
saying,
yes,
we're
part
of
a
consortium
and
that's
what
this
means.
It
means
that
we
have
to
share
95
of
our
stuff.
We
have
to
share
our
new
items
that
sort
of
thing,
so
we
we've
coasted,
we
do
coast.
F
Oh,
you
know
they're
up
next
or
you
know
they
should
be
getting
it
soon
and
they're
withholding
these
things.
So
you
know
causing
that
that
conflict.
You
know,
I
see
why
they
would
do
it
for
their
own
patrons,
but
when
they
do
that
within
a
consortium
they're
affecting
a
lot
of
people,
not
just
you
know
one
or
two
people.
A
A
I
There's
there's
something
in
the
new
update
and
I
don't
remember
the
exact
wording
about
the
finding
duplicate
patrons
and
having
a
a
pop-up
for
do
for
a
warning
for
duplicate
potential
duplicate
patrons
and
that's
something
that
we're
kind
of
curious
about
as
a
consortium,
because
most
we
don't
require
birth
dates
on
our
patreon
accounts,
that's
kind
of
a
privacy
thing,
but
the
problem
is,
we
also
don't
want
to
have
duplicate
patron
accounts.
People
can
share
their
accounts
between
libraries
and
so
we're
kind
of
right.
Now,
having
a
discussion
about
should
we
do?
I
We
need
to
require
the
birth
dates
and
things
like
that.
This,
the
new
feature
coming,
could
help
with
the
duplicate
patron
problem.
But
that's
we've
got
kind
of
a
users
group
of
a
few
of
our
librarians
that
we're
meeting
next
week
to
talk
about
that.
But
I'm
kind
of
curious
if
anyone's
anyone's
got
a
similar
setup
or
anything.
A
Well,
that
would
be
a
huge
problem
for
us
because
we
don't
share
any
patrons
because
we're
not
regional
enough
that,
even
though
some
libraries
are
within
driving
distance,
some
libraries
are
seven
hours
away
from
each
other.
So
we
don't.
We
don't
do
that
at
all,
but
because
there
are
some
libraries
that
are
kind
of
close
but
have
specifically
said
they
do
not
want
to
share
patreon
databases.
A
G
That
one
we
do
have
patrons
that
live
just
a
few
miles
away
and
we
have
shared
patrons
and
the
way
we
get
around
it
is
when
they
sign
up,
and
it
pops
up
the
message
that
you've
got
a
duplicate
patron.
We
ask
for
a
middle
initial,
which
then
makes
them
unique
to
each
each
library
again
with
the
monster
we're
horribly
independent
from
each
other.
J
J
J
E
I
E
A
So
one
thing-
that's
we
are
that's
being
added,
which
I
think
is
relevant
to
the
holds,
is
removing
items
from
the
holds
queue
after
it's
put
in
transit
and
george
had
mentioned.
They
have
their
randomized
holds
key
running
every
hour.
We
couldn't
do
that,
because
people
kept
on
pulling
stuff,
not
getting
it
checked
in
then
it
would
re-randomize
and
then
the
next
library
would
pull
a
bunch
of
stuff
that
was
already
in
transit.
A
I've
got
other
ones
that
I
thought
were
relevant
group
circulation
by
item
type.
I'm
pretty
excited
about
that.
Obviously,
in
a
consortial
setting
where
everybody's
doing
custom
things,
the
more
you
can
do
is
more
of
a
headache
for
an
administrator
but
certainly
allows
you
to
set
things
up.
So
I
think
that's
gonna
allow
less
areas
where
libraries
have
to
make
a
decision
between
giving
patrons
more
than
they
want
to
give
just
so
they're,
not
limiting
them
too
much.
A
So
I
haven't
looked
at
all
the
this
is
a
very
I'm
looking.
I
have
the
bug
open
now
and
there's
a
million
things
on
it.
So
I
haven't
looked
at
all
the
implications,
but
I'm
just
starting
to
see
how
that
will
be
helpful
in
organizing
making
sure
that,
like,
if
you
only
want
so
many
visual
medium
dvds
blu-rays
those
type
of
things
out
that
it's
going
to
be
limited
in
a
much
neater
way
than
we
currently
have.
E
E
I
was
trying
to
find
my
notes
from
upgrade
stuff,
so,
though,
I
think
one
of
the
only
ones
that
we
funded
this
coming
is
and
socially
related
is
the
addition
of
the
transacting
location,
the
checkout
location,
on
the
fines
page.
So
when
you
pull
up
a
fine
you'll
be
able
to
see
where
that
fine
is
actually
owed,
because
we
we
maintained
that
wherever
the
patient
was
standing
when
the
checkout
occurred
is.
J
A
Another
one
I
I've
noticed
that
isn't
necessarily
just
well
it's
consortial
in
that,
if
you're
doing
a
lot
of
resource
sharing,
this
is
important
and
staff
should
be
notified
that
a
transfer
has
been
completed
upon
check-in
because
right
now
it's
a
little
hard
to
train
on
that.
Without
that
satisfying
thing
that
when
you
check
something
in
and
it
changes
that
status
from
in
transit
to
available
when
it
just
says
not,
item
not
checked
out.
That
is
not
the
satisfying
thing
that
I
think
people
want
to
see.
A
E
E
Is
like
we'll
go
out
and
train
we'll
tell
them
that
then
we'll
come
back
and
we'll
find
that
they're
not
checking
things
in
that
came
in
on
the
career
anymore,
because
the
first
one
they
checked
in
said
not
checked
out.
So
then
they're
like
oh.
I
guess
I
don't
have
to
do
anything
with
that,
so
that
confirmation
is
huge
and
we've
needed.
J
Oh
yeah,
that's
I
always
get
asked
that
by
new
people
that
I'm
training,
even
you
know
I'll-
tell
them
I'll
explain
why
it
works
that
way
and
then
the
first
time
that
they
do
one
like
once
training
is
done.
They
always
ask
which,
like
I'm
always
glad
for
people
to
ask
questions
if
they're
not
sure
what's
going
on,
but
I
think
that'll
be
a
lot
clearer.
A
A
E
A
E
J
Is
it
something
that
like
continuously
goes
around
we're
using
it
for
new
books
right
now
and
it'll
automatic?
Currently,
it
automatically
puts
them
in
transit,
even
if
they're
checked
out
or
waiting
on
hold
for
somebody
or
just
sitting
on
your
shelf
they're,
just
in
transit
now,
which
is
very
annoying.
But
after
the
new
update
it'll
be
requested
for
transit
and
there's
a
new
report
built
in
that
is
transfers
to
send.
J
Which
will
then
say:
okay,
beauville
or
moscow.
You
have
to
send
all
these
items
to
beauville
and
it'll.
Tell
you
if
it's
on
the
shelf
or
checked
out,
but
also
I'll,
be
able
to
write
a
report.
That'll
work
better
because,
like
we
don't
care,
if
it's
on
loan,
when
it
gets
checked
in
it'll
route
properly,
so
we've
been
using
this
for
about
a
year
for
our
new
book
rotation,
we're
almost.
J
We
almost
have
all
the
old
stuff
on
it.
Actually
we
might
have
it
all
caught
up,
but
then
our
next
step
is.
We
have
av
rotation
where
we
rotate
cds
and
audiobooks,
and
dvds
and
blue
blu-rays
to
our
six
branches
in
the
consortium,
and
so
we
also
want
to
set
that
all
up
to
be
cyclical
and
run
automatically,
and
so
then,
just
like
every
week
you
run
the
report
and
see
what
needs
to
move
and
the
new
books
will
update
we'll
move.
J
F
J
J
F
But
there's
a
feature
in
the
2011:
that's
included
that
our
consortium
actually
paid
for,
and
I
talked
about
the
the
feature
of
local
holds
priority.
We
added
to
that
feature
so
that
local
holds
priority
allows
exclusions
right
now
it
doesn't,
and
you
know
there
are
a
few
libraries.
The
biggest
example
we
have
is.
We
have
a
few
libraries
that
that
do
hot
spots
and
all
of
our
smaller
outlying
libraries
don't
do
that.
F
So,
if
any
of
their
patrons
sign
up,
you
know
put
a
hold
on
those,
they
generally
don't
get
them,
because
we
we
have
patrons
that
regularly
check
out
or
place
holds
on
hot
spots,
and
so
you
know,
if
you're
at
one
of
the
libraries
that
that
carries
them
great
and
if
you're
one
of
the
outlying
libraries
you'll
never
see
them,
and
so
we
want
to
be
able
to
share
our
hot
spots.
So
this
feature
will
allow
us
to
exclude
these.
A
Excellent,
well,
I
think
we're
probably
at
time-
and
I
think,
there's
somebody
another
thing
after
us.
I
don't
want
to
dig
too
much
into
their
time,
but
I'll
put
my
email
back
in
the
chat.
Please.
Let
me
know
if
this
scintillating
discussion
is
what
you
want
more
of,
and
I
will
be
happy
to
set
up
find
some
meeting
space
in
the
coho
calendar.
That's
not
conflicting
with
anything
else,
and
we
can.
E
I
would
agree,
I
came
up
with
two
or
three
things
I
jotted
down
that
I'm
gonna
do
next
week.
I
I
will
you
know
me.
I
want
this
to
happen
anyways,
but
I
think
that
we've
proven
in
the
past
hour
that
there's
still
a
need
for
it.
It's
just
a
matter
of
finding
the
right
time
to
get
everyone
together.
Yeah.
A
Maybe
jason
and
I
will
put
our
heads
together-
look
at
the
calendar
and
maybe
in
a
in
november
we
can
find
something
to
see
what
happens
if
we're.
If
we
don't
have
all
the
attendees
here
joining
us,
but
we'll
we'll
give
it
another
go
yeah.
I
I
definitely
get
a
lot
of
these
conversations,
so
I
would
love
to
have
everybody.
That's
interested
come
together
and
do
this
again.