►
Description
Leaders:
- Andrew Fuerste-Henry (Dubuque County Library District)
- Jason Robb (Southeast Kansas Library System)
A
So
admittedly,
I
haven't
prepared
much
for
this,
and
I
will
say
that
that
is
historically
accurate
for
web
dev.
We
don't
really
run
by
an
agenda
what
so
I'm
representing
Lucas
since
Andrew's.
Here
he
can
take
this
this
admin
stuff
so
for
webdub.
Typically
we're
talking
about
jQuery
hacks
PSS,
that
sort
of
thing
things
usability,
ux,
all
that
sort
of
stuff
filing
bugs
for
that
sort
of
stuff
and
then
workarounds
that
we've
done
on
on
those
things.
A
So
if
anybody
has
that
sort
of
thing
you
want
to
talk
about
well,
we
will
be
happy
to
entertain
topics
right
now.
We
are
running
over
on
time.
I
think
we
were
slotted
until
11
45,
so
I
will
remind
everybody
that
we
have
an
hour
block
after
lunch.
So
if
there
are
things
you
want
to
discuss
there
as
well,
we
can
come
back
and
reconvene
after
after
lunch,
I
see,
George
is
wandering
up
so
I'll.
Let
him.
B
Well,
I
just
wanted
to
say
a
good
example
of
something
that
the
web
dev
group
has
helped
with.
You
know
a
lot
of
times
we'll
get
together
and
and
we'll
say:
well,
we
don't
really
have
anything
planned
and
then,
over
the
last
couple
of
months,
Barb
Barbara
has
been
to
the
meetings
and
she
said
well
I'm
working
on
this
cover
flow
thing
and
I.
B
Don't
know
this
isn't
working
right
and
so
really
what
it
is,
is
it's
kind
of
been
a
working
group
where
people
somebody
will
bring
something
they're
working
on
on
on
doing
and
changing
and
it'll
be
like
four
or
five
of
us
sitting
around
going
well.
Have
you
tried
this?
Have
you
tried
that
and
then
Barbara
has,
you
know
been
applying
those
changes
to
what
she's
been
doing
and
that
kind
of
got
it
got
worked
out
so
well
that
she
was
able
to
do
a
presentation
on
it.
A
And
and
I'll
just
add
that,
like
Lucas
is
a
wizard,
you
all
know
that,
but
this
is
an
opportunity
to
sit
in
a
zoom
room
once
a
month
with
Lucas
and
have
some
of
that
rub
off
on
you.
So
I
encourage
anybody.
That's
interested
in
that
to
come
to
the
web
dev
meetings
and
participate
in
those,
and
those
are
the
third
Thursday
of
every
month,
so
Andrew
I'll,
let
you
take
it
over
for
a
little
while.
C
Sure
so,
since
admitted
reports
are
similarly
disorganized
and
broadly
chartered,
no
particular
agenda
there,
it
is
a
show
up
and
talk
about
things
that
you
are
doing
working
on
excited
about
challenged
by
with
regards
to
Administration
and
reports,
and
you
know
if
you've
ever
felt
like
koha
has
a
kind
of
rough
idea
of
what
belongs
in
the
administration.
Module
I.
Think
we've
got
kind
of
a
rough
idea
of
what
belongs
in
an
Administration.
C
Sig
can
be
kind
of
wide-ranging
I
was
you
know,
sitting
over
here,
waiting
to
to
start
and
thinking
about
Ray's
presentation
and
how,
if,
if
we
were
gonna,
have
something
run
over
it
eat
into
this
time?
His
was
a
great
choice,
because
it
is
absolutely
on
topic
for
what
we
want
to
talk
about
in
the
system.
Admin
reports.
Sig.
Are
you
doing
something
fun
with
your
data?
Do
you
want
to
show
us
your
your
project?
C
Do
you
have
something?
That's
not
quite
working
and
you're
hoping
we
could
help
you
with
I'm
sure
you've
all
figured
out
that
it's
there's
always
a
lot
to
talk
about
with
SQL
reports.
Somebody
has
some
SQL,
that's
not
behaving
itself
and
we
can
all
put
eyes
on
it
and
try
to
poke
it
into
behaving.
C
Yeah
I've
got
two
things
on
the
agenda
for
today,
which
are
just
bugs
that
I'm
personally
annoyed
about
that
I
want
to
wave
at
the
group
and
say
please
get
annoyed
with
me.
That's
always
a
part
of
these
things.
It's
a
good
thing
to
you
know,
get
everybody
aware.
A
I
I
think
it's
the
second
Tuesday
circulations
first
Tuesday
is
this
at
admin.
Second
Tuesday
and
Andrew.
You
can
feel
free
to
share
your
screen
if
you
want
to
yeah
whatever
you
need
yeah,
you.
D
A
C
So,
like
I
said
we're
not
highly
agenda
driven.
Here's
my
agenda
for
today,
which
is
full
of
blank
space
and
two
things:
I'm
gonna
go
into
bugs
because
that's
where
I've
got
stuff
and
I'm
going
to
tell
you
about
the
two
bugs
I'm
excited
about
in
sort
of
system,
adminy
things
and
then
open
to
y'all,
to
ask
if
there
are
things
that
you've
been
worried
about
or
interested
about
this
one
here.
C
This
to
me
makes
a
good
example
of
the
types
of
things
we're
talking
about
in
the
admin
Sig,
because
this
is
a
weird:
it
impacts
circulation,
but
it's
based
on
a
system
preference.
It's
a
lot
of
like
deep
system.
Behavior,
that's
going
to
matter
a
lot
to
like
six
libraries
in
the
world
and
not
anybody
else.
This
is
all
about
what
happens
when
an
item
gets
checked
in
whether
it
floats
or
returns
home
and
making
cohab
better
able
to
enforce
rules
about
how
that
works.
C
There's
nothing
I
like
I
personally
need
from
the
group
on
this.
That's
not
why
I'm
bringing
it
here,
I'm
just
sort
of
bringing
it
to
say,
hey
y'all,
this
exists.
Maybe
this
has
been
impacting
you
and
you
haven't
even
known
it.
Let's
make
a
little
stink
on
bugzilla,
get
some
attention
of
people
and
see
if
we
can't
get
it
moving
forward.
C
C
C
And
grab
my
sandbox
here
this
page,
it
has
a
handy
button
over
here
that
offers
to
cancel
your
hold
and
send
the
item
back
to
the
home
branch.
C
C
So
we
shouldn't
hard
code,
this
one
button
to
always
do
something
that
isn't
necessarily
what
we
want
again
I'm,
not
looking
for
the
group
to
do
anything
here
if
any
of
y'all
are
really
excited
to
go,
write
this
code
go
for
it
I,
just
mostly
I,
ran
into
a
thing
that
was
making
a
bit
of
a
headache.
In
my
my
system
and
I
wanted
to
share
with
the
group
in
case.
Anybody
else
could
benefit
from
it
or
had
some
great
idea
of
how
to
work
around
it.
While.
C
In
that
Spirit
does
anybody
else
have
system
admin
type
bugs
that
they've
been
keeping
an
eye
on
or
excited
to
see
are
finally
moving
forward
or
I?
Don't
just
want
to
talk
about
generally
or
I
should
say
bugs
that
y'all
have
been
really
wishing
would
be
filed.
We
could
file
some
things
together.
E
So
similar
to
the
one
you
just
talked
about
with
the
not
sending
it
back
to
home
away,
I,
don't
know
if
there'd
be
a
way
to
do
a
bug
to
address.
We've
had
several
people
who
have
placed
holds
on
things,
mostly
our
book
club
patrons,
and
somebody
else
gave
them
the
book
before
it
got
here.
So
it's
still
in
transit
and
so
they're
like,
oh
well,
when
it
gets
here,
just
send
it
back.
Well,
we
don't
really
have
a
way
to
put
it
in
there
that
I
know
of
to
be
like.
E
Oh,
when
this
gets
here,
just
send
it
right
back
because
it's
you
know
they're.
They
wanted
to
cancel,
but
if
we
just
cancel
it
when
it
does
it
when
it
gets
here,
it
shows
up
as
like
a
random
thing
or
if
it
gets
here,
we
just
put
it
on
the
whole
shelf,
because
we
don't
know
that
she
wants
us
to
send
it
back
so
I,
don't
know,
there's
something
we
could
do
about
that.
It
happens
quite
often
in
our
tiny
little
Library.
D
C
Seems
probably
pretty
doable,
but
not
a
not
a
question
I've
heard
before,
and
this
is
where
we
hope
that
somebody
else
in
the
group
says.
Yes,
my
library
does
basically
that-
and
this
is
how
we've
made
it
work,
because,
ideally,
we
don't
need
to
write
a
Dev
for
anything
ever
cohut
just
magically
knows
how
to
do
everything.
C
B
Jessica
is
at
one
of
my
libraries,
so
I'll
I've
asked
her
to
send
me
a
specific
example,
because
this
is
the
first
time
I've
heard
about
the
problem
from
her.
So
yeah.
C
C
Christopher
in
the
zoom
chat
said:
I
would
love
to
see
some
sort
of
compilation
of
preferences
that
are
Global
and
not
Consortium
friendly.
That
Dez
could
look
at
once
in
a
while
and
make
them
more
useful
to
consortiums.
C
Now
that
my
first
thought
on
that
is
that
kohai
us
does
have
also
a
consocial,
Sig
and
I.
Don't
know
that
we
need
to
get
into
like
special
interest
interest
group
Turf
battles,
but
yeah
that'd
be
the
sort
of
thing
that
we
could
work
as
a
Sig
to
make
a
list
to
establish
that
list
of
system
preferences
that
need
to
get
made
more
consortial
file,
an
Omnibus
bug
in
bugzilla
and
kind
of
track
that
work.
C
A
Already
I,
don't
I
don't
want
to
get
yelled
at
by
Liz
again
the
earlier
on
in
the
chat
we
did
have
one
question:
is
there
an
easy
view,
either
via
jQuery
system
preference
to
add
an
alert
or
notice
to
the
whole
confirmation
screen?
C
C
A
A
If
you
have
further
feel
free
to
expand,
oh.
C
C
B
So
I
I
guess
actually
I
was
about
to
say
I'm
wondering
if
what
Tim
is
interested
in
is
something
that,
if
they're
having
a
problem
where
patrons
are
leaving
that
page
without
clicking
confirm
hold.
If
there
could
be
like
a
warning
like
you
get,
sometimes
where
you
say:
oh
you're,
leaving
this
page
before
you're
finishing
the
transaction.
That
wouldn't
be
a
bad
idea,
but
then
Tam
here
says
that
we
need
to
alert
them
when
they
place
the
hold
that
it
might
be.
B
A
So
again,
yes,
it's
doable.
Yes,
we
could
probably
Workshop
that
in
a
regular
meeting
but
or
maybe
this
afternoon,
maybe
someone
wants
to
ride
diet
jquariance
into
Tampa
yeah.
C
C
A
C
D
I'll,
just
tease
him
to
talk.
What
happens
is
if
that
person
created
their
own
version
in
their
Library.
You
should
you
said
you
should
share
it
up
up
to
the
main
jaha.
So
yeah,
that's
the
story.
You
want
to
just
keep
it
alive
local
version
or
push
it
up
to
the
main
tree,
the
main
version
that
makes
it
yeah.
C
C
D
D
I
do
have
a
microphone,
it's
dangerous,
so
Rebecca's
question
about.
What's
the
best
way
to
restart
a
bug,
that's
stalled
out
in
the
community
and
I
was
like
and
everyone's
like
I.
Don't
understand
that
question,
but
I
think
what
she's
talking
about
is
when
it's
gone
into
discussion
or
having
some
kind
of
a
yeah.
A
stalling
problem
like
people
are
disagreeing
how
how
do
we?
How
do
we
convince
people
to
agree?
I,
don't
actually
have
an
answer
for
that
question,
but
I
just
wanted
to
make
sure
that
her
everyone
was
understanding.
C
And
then
she
gave
an
example
of
a
stalled
bug.
Looks
like
this
particular
one:
it's
not
in
discussion.
It
just
hasn't
moved
at
all
for
nigh
on
a
year
and
yeah.
That
will
happen.
I
guess
part
of
my
answer
to
you.
Rebecca
would
be
do
something
like
this
get
other
people
to
know
that
your
bug
exists.
C
So
hey
everybody
bug,
25901,
add
option
for
claims,
return
warning
threshold,
the
count
only
unresolved
claims
if
you're
using
claims
returned-
and
you
like
that-
little
pop
that
little
message
that
says
this
Patron
has
too
many
claims,
but
you
would
like
it
to
only
count
the
ones
that
haven't
been
resolved
come
over
to
bugzilla
make
a
stink.
C
To
my
knowledge,
though,
there
is
not
some
special
mechanism
of
like
a
place
to
put
a
bug
to
say
really
really,
please
developers
think
about
this.
One
aside
from
you
know
being
noisy
on
bugzilla
talking
to
any
developers
voting.
A
C
C
C
Okay,
yeah
I
mean,
if
you've
written
your
your
jQuery
locally
and
then
posted
up
a
bug
in
bugzilla
to
get
that
into
koha
proper
up
until
that
push
that
until
your
code
pushes
to
master
yeah,
it
would
need
to
get
updated
in
bugzilla
the
moment
your
special
jQuery
code
goes
into
koha,
though
then
it's
sort
of
the
communities
responsibility
to
make
sure
they
don't
do
anything
that
breaks
your
code,
because
your
code
is
great.