►
From YouTube: New Item Sharing Let Koha do the Heavy Lifting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
I
work
for
the
southeast
campus
library
systems,
which
is
a
15
County,
Regional
suspending
and
we
service
many
many
libraries.
Our
consortium
is
43
libraries
for
you
to
public's,
and
we
have
one
Community
College
Library,
which
always
makes
things
fun,
and
then
you
have
the
two
other
libraries
coming
up
soon.
We've
got
a
retrospective
conversion,
very
small
library.
A
Today,
I
am
talking
about
new
item
sharing.
This
is
probably
more
pertinent
to
a
consortium,
but
it's
still
an
interesting
thing
that
it
was
one
of
those
things
when
they
sent
out
the
show
us
something
you
didn't
ever
know
about
cocoa
pod.
So
for
me
it
was
the
whole
vault
policies
were
forbidden
when
I
started
my
dogs,
my
predecessor,
said
they
didn't
work
and
let
me
touch
them
and
then
a
few
years
down
the
road,
Heather
and
nettles
came
along
and
said.
Why
aren't
you
using
that?
This
works
perfectly?
A
So
that's
when
we
started
really
looking
more
into
that,
but
there
were
other
things
that
we
need
to
check
out
the
list
before
we
get
fully
using
it
with
full
potential.
So
as
far
as
our
collection,
we
have
about
twenty-five
libraries
to
have
questions
under
ten
thousand
items.
A
lot
of
those
libraries
don't
actually
actively
purchase
items
were
actively
contribute
to
the
consortium
so
that
when
they
do
get
money
to
get
new
items
they
just
don't
want
to
share
them.
They
want
them
on
the
shelves
for
their
patrons.
A
A
We've
got
a
few
really
big
libraries
for
us.
I
know
there's
like
huge
libraries
out
there,
and
then
we've
got
a
lot
of
small
libraries
and
a
few
medium
libraries
the
benefit
the
main
thing
our
consortium
does,
for
our
libraries
is
access,
so
those
very
small
libraries
getting
access
to
700,
sometimes
the
very
large
libraries
they're
getting
more
value
in
their
purchases,
not
just
staying
on
the
shelf.
It's
going
out,
it's
circulating
longer,
hitting
more
people,
so
in
the
in
that
gradient
there,
the
large
libraries
are
generally
willing
to
say
yeah
sure,
take
many
stuff.
A
It's
fine
I've
got
a
lot
of
other
new
stuff,
my
new
shelf.
It's
never
empty.
This
far
libraries.
On
the
other
hand,
they
want
that
browsing
the
shelf
and
as
usually
just
a
shelf,
so
when
that's
empty
and
their
beacons
come
in
they're
like
what
are
you
doing
with
your
money,
it
doesn't
show,
so
we
wanted
to
come
up
with
a
way
that
accommodated
those
small
libraries
while
still
being
fair
to
the
larger
libraries.
A
So
the
problems
that
we've
come
across
with
you
item
sharing
the
first
is
the
lack
of
local
priority,
which
is
something
that
has
been
solved
and
we'll
go
through
each
one
of
these
problems
and
how
we
kind
of
solved
it.
The
desire
for
local
browsing
shelves
again,
those
small
libraries
really
want
a
way
to
keep
all
their
stuff
in-house.
It
goes
against
our
mission
as
a
consortium,
but
we
still
want
to
accommodate
as
much
as
we
can
without
just
completely
exiling
language
so
that
they
don't
feel
like
welcome
in
the
consortium
anymore.
A
Lack
of
clarity
and
transparency
was
a
big
one,
so
we
have
the
rogue
libraries
that
just
don't
share
and
there's
never
gonna
share
their
new
stuff.
They
have
an
office
and
there's
all
their
new
chef
on
new
stuff
on
the
shelf,
and
then
they
have
a
little
box
of
cards
and
they're.
Just
writing
everything
down
and
that's
exactly
not
what
we
want.
So
one
thing
we
wanted
to
do
is
create
clarity
and
transparency
so
that
the
patients
are
aware
of.
A
A
So
we
do
have
policies
in
place
for
new
item
sharing
and
they've
evolved
over
time,
which
is
so
you'll
notice
in
my
presentation,
I'm
going
to
keep
the
problem
up
there
and
I'm
gonna
timeline
at
the
bottom,
because
it
is
kind
of
it's
been
tricky
for
me
to
track
so
I
just
wanted
to
have
all
along
the
presentation
and
if
there's
any
time
this
is
super
confusing.
Just
tell
me
to
stop
and
went
back
up
and
I
can
try
and
learn
what's
going
on.
A
So
as
far
as
the
solution
progression
goes,
we
started
with
a
written
policy
and
went
along
with
our
looted
art
consortium
started
in
2008
Banco
and
we've
been
through
two
major
migrations.
Technically
three
support
companies.
We
went,
we
started
at
ETFs
and
then
some
that's
happened
that
some
you
know
and
our
servers
are
made
with
them.
But
our
support
migrated
to
ETFs
Europe,
which
was
great.
They
were
great
people,
but
they
didn't
have
access
to
our
surgeries
and
the
time
difference.
So
in
2013
we
migrated
to
buy
water
and
everything
to
create
sets.
A
So
but
back
when
we
were
with
each
other.
We
had
written
our
our
Aussie
out
on
new
item
Shane
and
that
policy
relied
on
a
law
status
called
local
available
only
global
availability.
Only
and
that's
that's
what
we
use
for
the
longest
time,
also
in
the
Dark
Ages.
We
were
never
really
up
for
a
long
long
time,
so
we
didn't
ever
get
added
functionality
to
improve
this.
A
We
employed
those
Holtz
policies
that
I
said
we
didn't
really
know
works
and
then
the
final
piece
of
the
puzzle,
kind
of
was
automatic
so
to
break
that
down
a
little
more.
The
original
policy
would
look
with
a
Laird
Billy
only
was
the
non-shared
items
had
to
have
that
status.
So
any
library
wanting
to
keep
their
new
items
in-house
for
a
six-week
period,
which
is
what
our
policy
and
decide
is
on,
would
when
they
first
come
up,
I
didn't
put
it
in
what
that
did
as
a
lot
of
status.
A
It
restricted
holds
so
patrons
within
the
construction
consults
on
them
and
they
basically
created
a
dusty
shovels.
So
if
you
have
something
in
a
lot
status,
then
it
never
circulates,
then
it
just
sets
on
the
shelves.
Even
if
people
want
it,
the
other,
the
part
to
appease
the
people
that
did
show
the
new
items
was.
Our
policy
was
that
if
a
library
used
that
status
in
all
of
their
libraries
in
the
consortium
had
permission
should
not
share
their
new
life,
so
that
was
kind
of
the
reciprocal
I
love
borrowing
in
action.
A
A
It
just
didn't
cross
their
mind
to
go
in
and
change
it
or
they
were
intentionally
maliciously
doing
it.
We
can't
say
which-
but
there
were
lots
of
problems
with
this,
so
it
worked
on
the
surface,
but
it
didn't
really
work
under
and
aerialist
of
that.
So
the
misuse
of
the
status
was
one
of
the
major
problems.
People
would
just
put
anything
and
everything
in
that
status.
They
didn't
want
to
share
because
it
was
titled
local
availability.
A
Only
some
people
thought
that's
just
for
my
stuff
that
I'm
keeping
in
house
going
in
for
my
entire
genealogy
collection
and
local
availability
owned
where
we
actually
have
it
doesn't
circulate
courier,
but
they
just
didn't
understand
and
that
made
more
sense.
So
that
was
one
of
the
reasons
I
personally
didn't
like
manual
regulation
and
no
regulation.
That's
that's!
Basically,
what
happened
I
mean
people
would
put
their
statuses
on
and
just
weep,
so
holes
would
stagnate
now
using
a
law
status.
A
It
worked
sort
of
because
we
wanted
them
to
check
it
out,
put
it
on
their
browsing
shelf
a
picture
come
in
and
check
it
out
when
they
checked
it
in
the
whole
status
would
go
away
and
it
would
flow
into
the
halls.
So
if
there
were
was
a
big
shared
record
lots,
libraries
were
sharing.
There's
that
one
library
wasn't,
then
we
would
hope
that
with
that
hope
list
on
there
once
it
came
back,
they
would
just
send
it
into
the
flow
we
always
just
saying,
like
oh
honey
come
on.
A
The
problem
with
that
is
people
would
check
their
items
in
the
hold
would
pop
up,
and
then
they
immediately
back
in
place
the
status
on
again,
eventually
that
led
to
again
a
full
of
shelf
of
dusty
books.
Neath
the
hackls
people
wanted,
but
they
didn't
and
that's
directly
leading
to
subversion
of
sharing,
which
is
our
policy
and
our
mission
as
the
concern
and
then
again
there
was
no
way
to
reinforce
that
piece
in
our
policy.
A
A
The
supplicant,
this
library
system
and
the
Iowa
Public
Library
share
building,
and
we
also
shared
collection.
Sdk
has
a
fun
and
we
put
money
in
and
then
it
sets
on
the
shelves
of
gala
public
libraries.
So,
with
the
transfer
cost
matrix,
we
were
able
to
say
put
us
at
the
top,
but
I
will
at
the
top.
We
can
fill
all
the
requests
that
come
in
first
and
take
the
burden
off
the
other
libraries
and
then
from
there.
We
can
trickle
down
to
the
larger
libraries
on
the
original
graphic
on
you
stat.
A
So
the
bigger
libraries
are
getting
more
requests
from
the
smaller
libraries
and
that
kind
of
took
some
of
the
burden
off
of
filling
holes
from
the
libraries
and
wanted
to
keep
their
new
items
longer.
But
it
didn't
do
anything
like
the
so
this
is
just
a
rough
solution.
The
real
reason,
one
of
the
real
reasons
is
when
we
started
testing
local
folks
prioritization.
A
That
just
didn't
seem
to
work
right
until
we
didn't
stop
and
I,
don't
know
if
that's
above
or
if
it's
just
something
that
went
wonky
in
our
testing
I
know
that
every
time
I
tested
it
prior
to
engaging
the
transfer
cost
matrix,
it
would
the
hole
would
be
prioritized
correctly
and
then
the
wolf
to
refresh,
and
then
that
is
just
a
wacky.
So,
but
once
we
put
this
in
place,
it
works-
and
this
is
my
lovely
diagram
of
figuring
out
how
that
flow
of
award.
A
It's
posted
in
my
cubicle
as
a
constant
reminder
how
much
fun
that
was
so
a
local
whole
transition.
This
is
where
we
start
getting
into
the
actual
solutions
to
the
problem.
The
local
organization
is
one
of
the
greatest
things
we
work
insertion
in
our
situation,
so
what
it
does
is
it
takes.
It
looks
at
the
for
us.
We've
said
it
this
way,
so
give
priority
to
filling
holes
for
the
pickup
library
and
not
just
the
home
liner
in
the
item.
A
So
with
that
in
mind,
some
libraries
that
their
home
library
at
one
library
and
then
they
are
constant
users
at
another
one
and
they
always
want
to
pick
up
their
items
somewhere
else.
Maybe
they
work
in
one
town
but
live
in
the
other,
so
we
did
choose
to
use
the
pickup
library
rather
than
the
home
I
visit
patron
for
the
prioritization.
A
So
whenever
a
patient
places
the
hold
that
item
owned
by
the
home
library
is
going
to
go
wherever
that
Swiss
pickup
first
and
that
solves
our
problem
for
local
prioritization
people
get
what
they
want.
First
and
all
libraries
in
the
consortium
I
haven't
had
negative
feedback
on
that,
except
for
one
library.
A
Once
a
to
just
be
time,
limited
I
know,
there's
a
bug
out
there
that
could
make
that
possible
so
that,
for
certain
point,
new
items
will
no
longer
prioritize
like
this,
but
most
of
the
libraries
in
my
construction
love
this
they
whenever
they
want
their
item
to
come
in
their
patron,
they
just
put
a
hole.
It
doesn't
matter
where
it's
at
and
the
consortium
it'll
come
back
for
their
patron
first
and
prioritize
again
doesn't
go
totally
with
our
free
and
open
sharing
policies,
but
it
does.
It
did
seem
to
alleviate
a
lot
of
buzz
attention.
A
The
problem
with
that
is
a
lot
of
my
libraries,
the
ones
that
want
to
grow
themselves
didn't
want
to
mess
with
the
holes,
and
this
does
require
active
hold.
Please,
though,
if
you've
got
a
list
of
people
that
want
every
new
DVD
every
time
you
add
a
DVD,
you
have
to
go
in
and
put
a
hold
forth
application
so
that
it
cycles
through
and
prioritizes
at
your
location.
First
and
a
lot
of
my
library
is
saying:
well,
my
my
patron
just
comes
in
and
picks
it
up
off.
A
The
shelf
I
want
to
set
there,
and
then
they
tell
their
neighbor.
That
was
good
and
I.
Just
don't
do
Falls
so
again,
not
something
we
wanted
here,
but
it
is
a
reality.
So
this
didn't
fully
solve
all
of
our
problems,
so
both
policies
come
to
the
coming
to
play.
Next,
the
the
holds
policies
are
set
at
the
strict
client
page.
A
So
for
us
we
created
new
item
types,
new
new
item
types
so
that
we
could
designate
what
were
you
items
and
what
weren't
items
and
that's
what
drives
the
whole
policies.
There's
one
caveat
with
that.
If
you
have
two
item
for
the
same
item,
then
you're
going
to
have
to
search,
find
rule
lines
which
means
you're
going
to
have
to
duplicate
it
rule.
So
if
you
want
to
limit,
if
I
want
to
limit
visual
media
to
four
checkouts,
some
libraries
are
still
way
down
there.
A
So
it
basically
allowed
us
to
create
two
distinct
types
of
shapes.
So
we
have
the
immediate
sharers,
the
people
that
send
their
stuff
out
as
soon
as
they
get
it,
no
matter
who
wants
it
and
then
we
have
the
delay
shares
who
have
their
shelf
and
they
give
it
to
their
patrons
first
and
if
their
patients
don't
want
it,
then
it
shuts
on
their
shelf
until
the
six
pieces
up.
A
Another
thing
to
note
is
only
the
delay
chairs
need
that
eat
at
that
policy
set.
So
this
is
this
is
a
setup
for
one
of
my
delay
chain
libraries.
So
we've
got
one
of
the
rules
like
new
visual
media
from
the
home
library,
the
MS
sick
of
lugging
that
I've
ever
even
that
I
am
in
turn.
So
it's
not
super
clear
what
that's
doing
and
that's
probably
part
of
the
reason
why
we
just
avoided
it
for
so
long.
But
what
that
is
doing.
A
So
we
had
less
than
month
in
but
symbiosis
we
talked
about
mutualism,
we
talked
about
bees
and
flowers,
how
we
should
all
be
bees
and
flowers
how
to
be
benefits
and
the
fireman.
If
it's
from
the
relationship.
We
also
talked
about
parasitism.
We
talked
about
people
and
how
we
don't
want
anybody
to
be
in
this
IDO.
You
don't
want
anybody
to
be
a
victim
of
a
mosquito
and
everyone
in
the
consortium
should
be
reciprocating.
A
So
then
we
landed
on
commensalism,
which,
like
I,
said
we
would
rather
be
a
mutualistic
society.
We
want
everybody
to
benefit
from
everybody,
but
in
regards
to
new
new
items
sharing,
we
just
knew
that
wasn't
gonna
work.
There
were
too
many
factors
too
many
people
that
just
weren't
on
board,
so
we
landed
up
in
insulin,
which
is
the
shark
benefit
or
no.
The
shark
is
just
kind
of
there,
but
the
fish
benefits
from
the
charts
present.
A
So
that's
where
I
landed
on
sharpen
fish
and
it's
been
I,
don't
know
six
months.
Maybe,
since
we
put
this
into
place
and
every
time
I
trained
a
new
library
and
they're
like
the
Sharks
of
fish,
this
doesn't
make
sense.
So
then,
I
have
to
go
back
into
my
my
big
going
to
feel
about.
No
fish
are
friends,
not
food,
so
I'm
a
realist
analogy,
but
it
really
does
work
in
my
head.
A
A
Okay,
so
the
effects
of
the
whole
qualities
immediate
shares
the
Sharks.
They
gain
access
to
new
items
of
other
sharks.
So
that's
still
there
that's
oscillating
philosophy
in
coop
we're
getting
our
full
sharing
on
if
with
local
hole,
prioritization
the
Sharks
do
get
to
prioritize
their
own
little
shark
people
first,
but
as
soon
as
those
holes
are
gone,
it's
going
out,
it's
freely
shared
they
can
place,
holds
on
any
and
all
new
items.
There's
no
restriction.
A
The
problem,
the
only
kind
of
drawback
to
being
a
shark,
is
that
they're
all
dar
being
ignored
by
the
fish.
The
delay
chairs
the
fish,
on
the
other
hand,
keep
new
items
on
their
shelves
for
six
weeks,
so
they
get
their
local,
Brewers
and
shelf.
They
don't
have
to
worry
about
holes.
They
don't
want
to.
A
If
holes
get
placed
on
their
items,
they
don't
show
up
on
the
whole
queue,
which
was
a
big
thing,
because
one
of
the
other
issues
we
really
had
struggled
with
was
people
would
get
in
the
habit
of
just
ignoring
their
holes.
They're
like
I,
don't
share
my
new
items.
I'm
just
not
gonna,
hold
anything
new
and
then
at
some
point
they
don't
realize
that
it's
not
new
anymore,
and
it
just
sets
there
forever.
A
They're
not
going
to
see
the
holes
for
the
American
media
chairs
so
and
then
the
drawback
of
being
a
fish-
and
this
is
the
policy
enforcement
part
as
well-
is
that
they
can't
place
holds
when
and
that's
on
the
staff
side
and
that
okay,
so
when
a
patron
goes
on,
the
OPAC
tries
to
place
hold
on
an
item
that
the
fish
doesn't
have.
They
get
a
notice.
That
says-
and
this
is
a
little
root,
I
guess,
but
they
get
this
green
box.
That
says
your
library
has
elected
not
to
share
your
new
items.
A
So
that
means
you're
not
a
lot
of
place
hold
on
this
item.
New
items
come
off
in
six
weeks
and
please
contact
your
library
and
if
you
want
this
changed
so
there's
a
little
page
pressures
and
if
you
can't
tell
at
this
point,
we
are
fans
of
the
Sharks,
but
we
do
still
want
to
be
able
to
accommodate
because
wait,
I,
don't
know
we.
We
have
the
policy
in
place
and
things
change
over
time,
and
sometimes
we
feel
like
the
people
that
sign
up
at
the
very
beginning
aren't
getting
same
thing.
A
They
signed
up
for
and
I
know.
Other
can
sort
should
have
that
as
well.
So
I
don't
know,
I,
guess,
I'm
kind
of
a
softie
and
I
don't
just
want
to
kind
of
put
the
hammer
down.
The
other
problem
is
the
even.
If
I
put
the
hammer
down,
they
still
do
whatever
they
want.
So
putting
in
a
system
in
place
is
important.
A
A
Okay,
so
that
that
covered
up
to
now,
we've
knocked
out
the
desire
for
local
availability,
local
priority,
the
desire
for
local
browsing
shells
and
the
policy
enforcement.
So
now
I
wanted
to
tackle
fair
so
with
everything
kind
of
working.
How
I
wanted
in
the
background,
I
started
working
on
the
front
end
and
using
a
little
I
came
up
with
so
whenever
a
funny
vodka.
So
the
work
to
make
this
work.
A
Every
library
has
to
use
those
new
ID
types,
fish
or
shark,
so
whenever
they
had
something
they're
going
to
get
the
option
and
I
can
probably
show
you
my
other
setups
in
the
back
end,
but
that
we
demand
that
they
put
it
in
new
book
because
that's
what
actually
creates
the
barrier.
If
this
is
not
a
new
book,
it's
freely
sure
it
is
a
new
book
that
shark
share
of
the
fish
stuff.
A
A
We
did
so
it's
really
kind
of
annoying,
but
it's
a
little
circle
with
an
exclamation
mark,
and
then
you
get
my
leg
over
it,
the
patient
in
the
item
and
the
staff,
but
that
item
isn't
gonna,
be
paid
for
for
the
six
week
period
and
then
down
here.
It's
kind
of
hard
to
eat,
but
that's
the
nasty
message
I
was
talking
about.
So
it
says
that
your
library
doesn't
share
your
new
items,
so
you
can't
hold
on
this
item
and
for
that
one
it
just
tacks
on
to
the
Namibian
whole
message.
A
Okay
and
then
the
final
piece
of
the
puzzle
was
solved
with
our
latest
upgrade,
and
that
was
with
the
automatic
item
modification
school,
which
is
awesome.
If
you
don't
use
it,
you
shipped,
basically,
what
that
does,
if
you
can
tell
it
at
a
certain
age.
I
want
this
to
change
to
that.
So
for
us
that
certain
age
was
six
weeks
or
two
days
and
the
change
was
the
item
F.
So
we
want
the
new
audios
to
go
to
the
new
books,
but
that's
all
automated
now
in
the
past,
I
would
have
to
do
that.
A
A
So
I
highly
recommend
that
if
you
have
not
set
that
up
yet
for
things
like
this
one
other
note
on
that
is,
it
does
require
a
cron
job.
So
you
can't
just
go
in
and
start
expecting
him
and
then
our
revised
policy,
so
new
item
types
maintain
the
flow
of
sharing
while
giving
a
choice
and
that
that
was
one
of
the
main
goals
of
the
whole
I.
Don't
know
hog
revs
menu
year
long
process.
A
We
still
retained
the
six
weeks
limit.
We
did
briefly
discussed
it.
Doesn't
you
thought
users
group
to
see
if
people
wanted
it
changed
and
I'm
really
was?
Maybe
we
didn't
really
discuss
it?
We're
leaving
that
one
up?
We
know
we
asserted
that
it
was
six
weeks,
but
we
we
said
that
we
would
revisit
it
didn't
work
for
everyone.
A
Hello
and
then
this
is
basically
just
a
recap
of
everything
that
I've
said,
but
we
did
write
it
out
into
our
policy
so
that
it's
available
for
our
libraries
terrific's.
So
basically
it
just
gets
all
the
folks
and
I.
Don't
know
what
time
it
is,
but
I
might
be
well
show
it
that
they
may
have
questions
at
the
point.
I
guess
the
question
I
have
is
or
the
is
the
desire
of
a
library
sport
to
be
a
fish.
You
find
that's
usually
driven
by
library,
staff
or
library
trustees,
sometimes
with
the
board.
A
Sometimes
I
have
one
library
explicitly
singing
on
set
the
board
said
we
had
to
do
this
and
she
didn't
sound
too
keen
on
it,
but
the
board
demanded
it
now
other
libraries
that
it's
pretty
obvious,
that
barium
is
the
one
pushing
the
change
and
they
always
default
to
well.
This
is
best
for
my
people.
This
is
what
my
pictures
lock,
which
in
most
cases,
patients
don't
really
understand
what
it
all
means,
but,
but
you
got
the
bird
for
the
most
part,
I
think
it
is
the
librarians
driving
the
decision
over
the
board.