►
From YouTube: Web Development Special Interest Group - 8/17/2023
Description
00:16:23 NEKLS Zoom 3 / George Williams: //Special functions - create variables for multiple uses //Special function BRANCHCODE var loglibbc = $(".logged-in-branch-code").first().text().trim(); $("body").addClass(loglibbc);
00:16:38 NEKLS Zoom 3 / George Williams: /* Remove sex radio buttons from LEAVENWRTH, BASEHOR, LANSING */.LEAVENWRTH #memberentry_identity.rows ol li.radio, .BASEHOR #memberentry_identity.rows ol li.radio, .BONNERSPGS #memberentry_identity.rows ol li.radio, .LANSING #memberentry_identity.rows ol li.radio, .PHAXTELL #memberentry_identity.rows ol li.radio, .PHSES #memberentry_identity.rows ol li.radio, .PHSHS #memberentry_identity.rows ol li.radio, .PHSMS #memberentry_identity.rows ol li.radio { display: none;}
00:17:10 Jason: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34356
00:17:27 Lucas Gass: having some connection issues
00:19:32 Jason: https://pastebin.com/ak0Quj8d
00:35:22 NEKLS Zoom 3 / George Williams: https://github.com/will1410/koha_staff_branding
00:40:26 NEKLS Zoom 3 / George Williams: https://pastebin.com/
00:40:40 Jason: https://pastebin.com/4fVcXcmv
A
A
You
had
it
early
okay,
so
we
were
before
we
started,
recording
just
talking
about
a
little
bit
about
what
we
thought
at
quack
on
and
Helsinki
I
had
mentioned
that
there
is.
There
was
a
session
on
HTML
customizations
that
was
interesting
and
sort
of
applicable
to
this
group,
so
they
showed
off
like
how
to
put
an
hours
widget
in
the
library
directory
in
the
OPAC.
They
also
showed
off
a
digital
resources
page
in
neopac,
and
those
are
some
of
the
things
that
we
were
planning
on
doing
with
the
pages.
B
A
A
B
A
C
B
Doesn't
disappear
right,
it's
just
not
visible
or
it's
not
changeable.
It's
not
it's
no
longer
editable.
It
still
appears
in
the
patron
record
I.
So
my
experience
with
this
is
with
with
phone
numbers
at
some
point
in
time
a
bunch
of
people
were
added
with
a
phone
number
one
of
the
you
know.
What
are
there
like
four
places
to
put
a
phone
number
and
a
patrons
record,
and
somebody
here
decided
we
should
only
have
two,
and
so
they
hid
the
the
third
one,
but
they
didn't
delete
all
the
data.
B
So
every
now
and
then
I
get
well.
I've
got
one
in
my
inbox
right
now,
where
somebody
sent
me
a
thing
saying
this
Patron's
got
a
phone
number
and
we
can't
delete
it.
You
know
it's
it's
there
and
and
then
I
have
a
a
response
like
a
canned
response
that
I
send
and
then
I
go
ahead
and
just
take
it
out
of
there.
I.
C
D
A
So
that
makes
sense.
I
have
that
I
have
some
code
set
up
for
the
street
number
field
for
the
same
purpose,
where
yeah?
If
there's
data
in
the
street
number
field
I
want
it
to
show
so
that
it
can
be
deleted
out,
but
otherwise
I
want
it
hidden.
So
I
I'll
just
leverage
that
same
code
for
the
gender
field,
so
hide
it.
If
there's
no
no
data
and
yeah
for
show
it,
but
don't
don't
let
it
be
set
if
there
is
or
unset
it.
If
there
is
data
Maybe
automatically.
A
B
A
Cannot
find
I,
don't
think
we're
gonna
do
that
we
haven't
gotten
to
that
point.
Yet
we
decided
that
if
it
was
there
prior
to
this
legislation,
then
we'll
fall
back
on
the
fact
that
it
was
populated
prior
but
I'm
I'm,
just
gonna
turn
it
off
and
see.
If
anybody
actually
complains
about
it
being
gone
or
not
or
even
notices,.
B
A
B
B
B
That
is
effectively
the
branch
code.
So
every
page
in
the
intranet,
if
we
look
at
the
the
body
tag
somewhere
in
the
body
tag,
there's
a
class
like
in
this
case
I'm
logged
in
currently
at
as
Prairie
Hills,
Sabetha
elementary
school.
So
I
add
this
thing
that
adds
a
class.
That's
the
branch
code
to
every
page
when
I'm
logged
into
the
internet.
B
But
that
uses
that
piece
of
you
know
you
have
to
have
that
piece
of
jQuery
to
create
the
class,
and
then
you
can
leverage
the
class
to
to
limit
it
to
those
branches
that
don't
want
it,
but
on
September,
1st
I'm
going
to
tell
them
and
our
our
next
next
search
catalog
meeting
is
August
29th
and
I'm
going
to
tell
them
that
on
September
1st
they
will
no
longer
be
able
to
enter
that
data
and
by
October
1st.
The
existing
data
will
be
deleted.
B
But
then,
after
that,
it's
just
not
going
to
be
there
and
I
think
there
will
be
some
pushback
on
it.
But
but
you
know,
particularly
after
you
know,
the
way
that
I'm
going
to
explain
it
to
them
is
that
you
know
right
now.
The
way
the
Kansas
law
is
written
is
if
you're
collecting
it
what
it's.
What
the
law
says
is
if
you're
collecting
that
data
it
has
to
match
their
biological,
the
biological
sex
on
their
birth
certificate,
which
would
make
libraries
responsible
for
every
time
somebody
gets
a
card.
B
They
got
to
look
at
their
birth
certificate
to
make
sure
they're
not
violating
the
law.
But
then,
since
Nichols,
since
northeast
Kansas
library
system
as
an
institution
is
the
person
that's
responsible
for
the
data.
That
means
that
if
eventually,
they
do
put
teeth
in
this
law
that
that
means
that
it
would
be
us
that
would
be
responsible
for
ensuring
that
the
data
is
properly
collected
or
face
the
consequences,
if
somebody
doesn't
collect
the
data
properly.
B
So
it's
a
risk,
it's
a
risk
to
the
library,
it's
a
risk
to
us
and
it's
a
way
of
the
State
trying
to
potentially
weaponizing
data
against
a
minority
group
which
is
kind
of
what
Chris
cormack
talked
about
in
his
discussion
of
data
sovereignty.
So
but
it
also,
you
know,
I
I,
when
we
had
the
circulation
meeting
a
few
weeks
ago.
There
was
the
discussion
about
you
know
the
gender,
not
the,
not
the
gender
marker,
the
pronoun
field.
B
B
A
I
guess
I
can
I
can
share
the
code.
I
can't
really
show
what
how
it
works.
I'd
have
to
find
somebody
with
the
street
number,
but
what
the
code
looks
like
so
my
street
number
cleanup
thingy
is
this:
where
it's
looking
at
it's
hiding
it
by
default,
and
then
it's
adding
a
clear
button
so
that
they
can
just
click
to
clear
the
field
and
then
down
here.
It's
setting
it
to
show
only
if
there's
something
in
that
field.
A
So
that
makes
it
so
that
when
anybody
goes
in
to
edit
an
account
with
the
street
number,
they
can
clear
it
out
and
save
it
and
then
the
next
time
they
go
back.
It's
not
there
anymore.
We've
done
the
same
thing
with
the
damage
status
because
we
did
away
with
damage
because
it
was
redundant.
So
if
anything,
old
data
was
populating
that
they
can
go
in
and
clear
it,
but
moving
forward,
we
just
use
withdrawn
for
damaged
items.
A
A
The
problem
I'm
having
him
with
it,
is
in
Firefox
and
only
on
our
current
version.
It's
sorting,
well,
no
I,
like
so
on.
Master
I
tested
a
Sandbox.
It's
sorting
by
that
column,
if
you
have
that
turned
on
so
giving
you
a
completely
useless
store
on
checkout
history
data,
because
it's
sorted
by
a
person,
a
staff
member's
name
and
that's
caused
some
confusion
from
my
library
as
to
like.
Why
is
there
old
stuff
showing
at
the
top,
so
I
wrote
some
jQuery
to
Resort
it
and
that
works
in
Chrome
on
live?
A
A
So
it's
one
of
those
like
really
frustrating
things,
but
I
don't
know
if
it's
just
because
production
is
a
different
point
patch
than
the
other,
like
the
tester.
That's
that's.
The
only
thing
I
can
come
up
with,
but
it
should
be
working
the
same
and
I
can
find
the
code
that
it's
just
a
simple
like
redraw
the
table
after
a
sort
thing
I
think
I
got
that
from
Barbara
that
got
it
from
Lucas
a
while
back
on
some
other
table.
A
C
A
D
D
Where
you
the
table,
just
you
know,
doesn't
sort
one
of
them.
I
want
to
change
the
sort
and
I've
tried
to
use
some
of
this
type
of
code,
and
it
doesn't
seem
to
make
any
difference
and
another
one
you
just
none
of
the
columns
sort
At
All
by
default
and
so
that
when
I'm
having
trouble
with
too
and
I
I,
don't
even
know
if
there's
bugs
out
there
yet
because
I
haven't
looked
but
yeah.
Some
of
the
Sorting
stuff
I
used
in
the
past
seems
to
not
now
work
on
some
of
the
tables.
A
D
D
B
D
So,
let's
see
so
this
is
the
screen
where
you
get
the
you
know
how
much
you
sold
in
cash
and
how
much
in
refunds
and
all
of
that
and
so
I
renamed
some
some
columns
to
help
staff.
So
this
would
be.
You
know
how
much
actual
cash
you've
got
in
the
drawer,
and
this
is
47
total
sold
two
dollars
of
it
was
cash
and
here's
refunds,
total
was
14.99
and
apparently
that
must
have
been
a
credit
refund.
D
D
You
know
they
want
to
see
outright,
how
much
cash,
how
much
credit,
how
much
total?
How
much
refunds
and
I
don't
know
if
I've
got
a
I?
Don't
have
a
good
one
here,
because
we
don't
agree
that
you
transactions
in
here,
but
is
it
ever
possible
to
either
like
add
a
column
in
the
table
or
add
a
calculation
of
something
and
put
it
in
there?
D
Well,
we
have
a
cash
register,
that's
from
like
1999.,
and
so
nobody
works
on
it
anymore
and-
and
you
know
it's
finally,
we're
been
asking
Finance
for
a
solution
and
they
never
came
up
with
anything.
So
finally,
we're
like
well
we'll
we'll
use
this
and
it's
going
to
work.
We
just
are
needing
to
get
it.
D
Of
how
much
you'd
spent
I
guess
out
of
your
total,
and
so
that
was
you
know
like
additional
data
that
didn't
exist,
and
so
I
was
thinking
you
know.
Maybe
there
was
something
I
could
do
to
give
staff
the
you
know
the
actual
numbers
instead
of
you
know,
looking
at
it
and
thinking.
Well,
how
much
was
this
and
and
it
it.
A
D
D
So
you
know
we're
reporting
on
on
all
of
our
cash
and
then
our
checks
and
then
our
credit,
and
then
we
have
refunds
and
they're
same-day
refunds
and,
after
the
facts,
refunds
that
have
to
have
a
cut
check
from
finance
department.
So
there's
actually
a
lot
more
to
the
reporting
part
of
this.
The
selling
part
of
the
POS
is
is
great,
but
the
reporting
part
is
a
little
more
involved.
B
The
best
way
to
deal
with
refunds
that
I've
ever
found
is
in
when
I
worked
at
Layton
County
Library,
one
of
the
members
of
that
Consortium
was
Clarkston
Washington
and
they
had
some
kind
of
legal
reason
that
they
just
were
forbidden
to
give
refunds
by
law.
And
so
when
somebody
said
you
know,
I
here's
the
book
that
I
just
paid
for
the
other
day,
they
would
say
we
are
forbidden
by
law
from
giving
you
a
refund
you're
out,
whatever
it
costs.
D
Would
be
nice,
we
have
a
patron
who
basically
comes
in
and
pays
for
stuff
all
the
time
and
then
finds
it
again,
and
they
partly
are
doing
that
because
they
want
to
get
past
the
block.
So
they
can
use
the
computers
so
they're
willing
to
just
pay
for
it
and
then
get
the
refund
and
it's
kind
of
like
yeah,
but
that's
kind
of
hard
on
staff.
So.
B
D
B
That
that's
that's
a
solution
there
yeah
when
I
worked
at
the
University
of
Idaho
library.
If
you
lost
an
item
and
it
didn't
have
a
price
in
it,
they
would
just
charge
you
195
dollars,
plus
plus
a
75
processing
fee,
and
they
would
bill
that
to
you
and
then
we
would
get
all
these
people
coming
in
going.
You
know.
I
I
owe
like
you
know
four
thousand
dollars,
and
then
we
would
just
be
able
to
save
them.
If
you
bring
it
back,
it
all
disappears.
B
All
you
got
to
do
is
bring
the
stuff
back
and
hold
its
peers.
You
get
this
notice,
you
know
as
soon
as
the
items
are
overdue,
you
get
billed
for
them,
but
as
soon
as
you
bring
them
back,
it
all
disappears.
It's
got
to
be
six
months
before
you
actually
have
to
pay
for
that,
and
so
then
all
those
things
would
come
back
the
next
day.
C
A
Notes
from
a
conference
there
was
an
interesting
talk
on
Aspen
and
Boca.
Okay
I,
don't
know
how
to
pronounce
it.
Okay,
I
think:
okay,
yeah,
so
bokeh
had
some
interesting
like
ideas
that
we
could
sort
of
maybe
leverage
for
web
design.
There
was
one
where
they
built
the
kizopax
I
wanted
to
look
at
that
a
little
bit
and
see.
A
I
was
sort
of
disappointed.
There
was
one
that
was
talking
about
building
tools
with
the
API
and
the
guy
just
kind
of
listed
all
three
things
but
didn't
didn't
have
anything
to
show
like
somebody
asked
if
the
code
was
available,
I
was
like
not
yet
so
that
was
a
little
disappointing,
but
hopefully
they
follow.
C
B
B
Yeah
I
guess
it
was
when
I
was
off
the
the
last
video
that
Christopher
and
I
did
is
the
one
about
the
about
the
customizing,
22,
11
11's,
look
and
all
that
work.
We
did
so
that
stuff
is
all
out
there
now
and
there
are
some
things
that
I
need
to
incorporate
into
that.
That
Christopher
has
found
some
places
where
the
colors
weren't
doing
what
I
said
they
were,
but
but
I've
got
that
up
on
running
on
our
test
system.
So.
A
C
B
B
A
B
A
I
do
remember
something
that
I
played
with
and
I.
Think
I
showed
this
off
at,
like
a
cataloging
cig
I
figured
out
how
to
reverse
engineer
the
population
of
information
from
Google
Books
in
purchase,
suggestions
in
the
OPAC
so
add
a
staff
member
wanting
that
added
in
the
the
staff
side
so
that
they
could
put
an
ISBN
in
a
purchase
suggestion
and
pull
some
data
when
they're
replacing
purchase
suggestions
on
behalf
of
the
the
patron
and
then
I
had
opened
a
bug
a
while
back
about.
A
So
I
added
this
button.
This
is
the
part
that
needs
created
up
next
to
the
ISBN,
so
I
can
put
it
in
ISBN
and
click
search
and
then
also
it
needs
like
feedback
and
junk
to
tell
you
that
actually
worked,
but
you
can
see
that
it
filled
in
an
author
filled
in
a
title,
some
of
the
publication
information
it's
really
hit
and
miss
what
Google
has
so
like
this
one
doesn't
have
paging
it's
just
a
zero
there,
but
it
and
it
brings
in
a
description
into
the
500.
No,
so.
C
A
A
C
A
And
then
I'm,
just
putting
all
that
information
into
different
variable,
so
I
can
insert
it
into
the
different
subfields.
So
I've
got
title
subtitle
if
it
has
one
authors,
publisher,
publish
date
and
page
count
and
I
try
to
do
height,
but
it
was
breaking
things
I.
Think
that's
why
that's
commented
out
like
I.
Don't
remember,
but
I
can
put
this
in
chat
if
you
want
to
play
with
it.
A
B
D
A
A
B
A
A
Of
stuff,
but
you
have
to
have
a
a
key
and
I
think
it
may
cost
or
something
like
it.
It
was
too
much
of
a
hassle
where
Google's
is
all
open
at
this
point
right
and
then
I
looked
at
library
thing
as
well,
because
that
came
up
at
the
catalog
or
meeting,
but
it
looks
like
they've
just
discontinued
their
apis.
As
far
as
I
can
tell
so
I
wonder
if
open
library.
C
C
Honestly
we're
doing
our
annual
reports
right
now,
so
we've
been
kind
of
hyper
focused
on
that
and
I
this
year
was
weird
because
we
switched
systems
in
the
middle
of
it
so
trying
to
figure
out
how
to
do
how
to
run
the
reports
in
the
first
place
in
koha
and
then
how
to
create
the
reports
correctly.
And
then
we
were
running
reports
and
thinking.
We
were
getting
the
right
answers
and
then
people
were
like
these
numbers
look
a
little
weird
so
having
to
re-re-create
the
reports.
Things
like
that.
C
So
a
lot
of
like
report
work
yeah
we
haven't
gotten
to
like
play
around
with
too
much
of
the
you
know
the
interface
and
the
way
it
looks
and
stuff
like
that
and
we're
still
waiting
on
getting
a
test
server.
So
I
think
maybe
we're
like
a
little
hesitant
to
do
anything
really
until
we
get
that
in
place
and
then
we
could
start
going
a
little
crazy,
but.
D
B
You
can
take
that
requirement
out
that
it
has
that
only
works
on
pages
with
a
class
of
XXX
and
then
and
then
you
don't
have
to
worry
about
screwing
everybody
up,
but
I'll
also
tell
you
that
the
library
I
used
to
work
at
we
didn't
have
a
test.
Server
either
and
I
would
just
break
stuff
and
people
would
say
people.
B
C
B
A
C
C
Or,
or
we're
waiting
for
ideas
of
like
automation
or
things
like
that,
you
know
I
think
we're
still
getting
used
to
koha
in
a
sense
that
we
don't
want
to
over
complicate
things
for
ourselves
just
yet
right
and
like
we
want
to
do
these
things,
but
we're
not
sure
where
to
start
or
like
what
our
biggest
pain
point
is.
Yet
you
know.
B
The
way
that
I
started,
making
changes
to
koha
was
with
the
simple
question
that
came
up
during
training
when
we
had
a
staff
member
at
the
training
that
asked
the
trainer
what's
a
surname
because
the
fields
and
cohorts
you
know
surname
first
name
and
I
said
you
know.
If,
if
this
person
who's
actually
fairly
smart
is
asking
the
question:
what's
a
surname,
then
there's
probably
other
people
that
don't
know
what
it
means.
C
Yeah
well
and
we
it's
we've,
had
plenty
of
suggestions
of
different
ways.
Things
can
be
worded
or
this
is
a
little
confusing
and
you
know
because
we
did
migration
and
then
we
weren't
getting
used
to
that.
Then
it
was
the
busy
summer
season
and
then
we
have
the
annual
reports
coming
up.
It
was
just
like
you
know.
We
felt
too
busy
to
actually
focus
on
any
of
these
suggestions.
So
it'd
be
a
good
idea
to
like
look
back
on
some
of
the
things,
because
at
first
they
were
definitely
like
plenty
of
yeah.
C
B
C
C
B
B
A
Yeah
and
I
I
like
to
like
triage
it
a
little.
You
know
the
more
complaints
I
get
about
it.
The
more
likely
I
am
to
try
and
focus
on
fixing
something
I
remember
our
our
very
first
piece
of
jQuery
was
written
by
Liv
when
she
worked
at
beckles
to
hide
columns
on
the
hold
cue
which
you
can
do
now
with
table
settings,
but
that
was
my
very
first
experience
with
that
system.
Preference.
B
D
B
A
A
B
Web
developers
issue
but
I
have
a
request
from
one
of
our
libraries
saying
they
deleted
a
bunch
of
stuff
in
batch
deletion
and
now
it
hasn't
been
deleted
and
so
I'm.
That's
what
I'm
supposed
to
work
on
after
lunch.
But
I've
got
a
physical
therapy
appointment
after
this
meeting
that
I'm,
probably
not
going
to
get
to
until
tomorrow.
So
but
it
was
one
of
the
days
during
I.
Don't
know
about
you,
guys.
B
B
Was
able
when,
when
Jesse
and
Kelly
and
Nick
were
there
and
Kyle
were
there?
I
could
see
them
in
the
room,
and
so
during
the
first
lightning
talks,
I
sent
a
slack
message
to
all
of
them.
Saying
be
sure
you
know,
one
of
you
should
get
up
and
and
mention
do
an
announcement
for
the
koha
US
conference,
and
so
they
did
that
during
the
first
lightning
talk
and
then
I
watched
the
second
lightning
talk.
My
back
has
been
really
hurting.
B
A
Yeah
I
took
I
I
got
up
early
into
numerous
naps
over
the
past
several
days,
but
I
think
it
was.
It
was
definitely
interesting.
I'm
glad
I
did
watch
it
and,
like
I
was
saying
that
the
dev
thing
earlier,
like
it
was
very
development
focused
it
felt
like
like
they
were
really.
He
was
really
pushing
the
Pearl
Community
to
like
collaborate
with
the
call
community.
C
B
A
B
B
A
B
You
know
and
I
might
actually
be
able
to
go
to
Wellington
in
2025,
because
it's
been
because
we
have
a
new
director.
Our
previous
director
Avery,
doesn't
know
this,
but
the
last
time
Nichols
sent
somebody
to
New
Zealand
for
a
conference.
They
ended
up
moving
there
and
so
my
our
previous
director,
wouldn't
let
anybody
go
to
International
conferences
for
fear
that
they
would
move
out
of
the
country
but
she's
gone
now.
We
had
a
new
director,
so
so
I
bet
I
could
talk
Mike
into
Wellington.