►
From YouTube: TTEOT Training Video - S3E3 - Patron Validation - Part 1
Description
You know, I just pour my heart into Koha. I don't ask for a lot. But when I do, it would just be nice to get some validation. What? You hear me? You really do care about our data? It's so NICE to be validated! In fact, let's start a small series on patron data validation.
Contents:
0:00 - Title
0:32 - Intro
2:40 - KohaCon22
4:40 - koha-US 2023 Conference
7:00 - What is Patron Validation?
9:10 - The Original Code
11:20 - Existing Validation
13:07 - The New Improved Code
14:15 - RegEx
15:58 - RegEx Tester
17:03 - Getting Started with Validation
40:40 - Wrap Up
Music: https://www.bensound.com
A
A
Hello,
everybody
I'm
George,
Williams
I
am
the
next.
B
B
A
And
today
we're
going
to
start
talking-
probably
three-part
set
of
videos
about
Patron
validation,
how
to
set
up
validation
to
make
sure
that
fields
are
being
filled
in
properly
when
you're,
creating
more
editing
patrons.
We
are
a
part
of
the
education
Committee
of
koha
us
and
you
can
find
our
website
at
koha.us.org.
A
A
Most
of
the
you'll
find
the
title.
The
name
of
the
presenter
links
to
all
the
video
recordings
and
if
there
are
slides
available,
you'll
see
a
little
little
red
or
I
guess
it's
kind
of
a
greenish
yellowish
icon
over
here
for
the
for
the
presentations
that
we
have
slides
for,
or
extra
content
for
Beyond,
just
the
video
recordings.
So
and
again
you
can
find
all
of
that
at
koha-us.org,
so
be
sure
to
go.
A
Look
at
that
and
while
you're
there,
if
you
go
to
the
learn
page
and
go
to
video
playlists,
that's
where
you'll
find
all
of
our
videos
from
this
training
series
series
that
we've
been
doing
for
over
two
years
now.
So
there's
a
lot
of
stuff
here
we
are
currently
in
season
three,
but
there's
also
season
one
season.
Two
there's
links
out
to
buy
water
solutions.
Monday
minutes
leaks
links
out
to
Deep
dive
by
buy
water
solutions.
A
We
need
to
get
some
of
those
other
those
other
things
in
there,
because
there
were
some
good
video.
There
was
one
presentation
at
koha
Khan
about
I,
don't
remember
the
name
of
it,
but
there
was
somebody
in
Asia.
That's
doing
some,
some
good
cool
Quahog
videos,
so
we'll
try
and
get
a
link
to
that
on
there,
too
yeah
Christopher
is
going
to
do
the
bulk
of
the
work
on
on
talking
about
validation,
I,
guess
I've
got
one
more
thing
to
say
about
the
koha
conference.
A
If
you
came
to
the
koha
conference-
and
you
haven't
done
it
yet
go
to
this
link,
there's
a
QR
code
here,
scan
it,
go
to
the
link
and
fill
out
the
survey
and
tell
us
how
you
like
koha
Khan.
If
you
didn't
go,
watch
all
the
videos
and
then
send
us,
you
know,
watch
them
all
in
one.
Go
start
to
finish,
get
a
big
bowl
of
popcorn
watch
them
all
and
let
us
know
how
we
did
at
that
link
there.
A
B
I'm
gonna
I
think
something
that
surprises
me
in
that
in
that
and
you
you
were
commenting
on
that
before
we
started
recording
was
you
know,
people
commenting
about
why
we
didn't
do
this
or
why
this
or
what?
Whatever?
In
you
know,
really
it
all
comes
down
to
people's
involvement
in
in
the
conference
and
planning
you
can
submit
a
request
to
to
be
a
host
location.
B
If,
if
you
don't
like
the
locations,
you
know
put
your
place
up
for
forbid
as
hosting
the
conference
location
or
you
know,
if
you
don't
like
a
topic
or
you're
wondering
why
something
was
included,
and
you
think
it
should
be
submit
a
proposal
for
for
a
presentation.
We
would
love
to
have
more
people
present.
You
know
their
thoughts
on.
You
know
how
they're
using
Kohan
and
really
that's
what
we
want.
So
if
you
find
something
lacking,
please
participate
and
add
to
it.
Yeah.
A
The
way
that
the
Quahog,
the
koha
US
Conference
location
is
chosen
is
it's
voted
on
by
the
koha
U.S
members.
So
if
you
want
to
come
to
the
Kauai
us
Conference
next
year,
and
you
want
it
to
be
some
place
that
you
want
to
go,
you
know
if
you
or
if
you
wanted
to
be
at
your
library,
you
know
submit
a
proposal,
though
there's
always
that'll
be
information
available
on
the
koha
koha-us.org
on
our
website.
A
It
seems
like
we
usually
do
the
voting
for
locations
and
it's
gonna.
It's
you
know
it's
we're
in
October
right
now,
but
it's
gonna
be
January
September
or
January
February.
When
we
start
thinking
of
where
we're
going
to
be
having
our
conference
in
in
August
and
August
or
September
next
year.
January
is
when
we're
going
to
start
asking
people
if
you
want
to
host
this,
send
in
a
proposal,
so
it
if
you,
if.
A
Koha
U.S
conference
in
your
library.
It's
not
that
far
off
when
you're
going
to
have
to
come
up
with
the
with
the
proposal
so
and
the
easiest
way
to
find
out
more
information
is
to
come
to
a
koha
us
meeting.
There
are
the
second
Wednesday
of
every
month.
The
way
you
find
out
is
you
go
all
the
way
to
the
bottom
of
the
page
and
here's
our
upcoming
events
for
our
calendar.
We
have
a
meeting
on
the
next
meeting
will
be
October
12th
at
10
30
a.m.
B
B
All
right
well
we'll
go
ahead
and
get
started
here,
so
we're
going
to
talk
about
Patron
validation
for
for
two
or
three
episodes
here,
and
the
goal
of
this
Gohan
has
slowly
evolved
over
the
years
and
has
learned
how
to
to
improve
things
along
the
way.
But
one
thing
that
we've
been
doing
since
we
got
started
back
in
2012
I
believe
is:
we've
we've
slowly
added
bits
and
pieces
to
jQuery
to
improve
Patron
validation.
B
One
of
the
things
that
that
we
kept
running
into
was
you
know,
staff
would
enter
things
slightly
different
or
there
would
be
mistakes
made,
and
so
we're
we're
working
to
improve
Patron
data
entry
so
that
that
information
is
more
consistent
and
we
don't
have
to
go
back
and
clean
up
stuff
if
there's
mistakes
made
and
we
have
functionality
that
depends
on
things
being
entered
correctly.
It's
not
going
to
it's
not
going
to
break
it.
B
So
having
that
consistently
correct
information
entered
into
the
patron
Fields
is
critical,
especially
things
like
you
know,
I
mean
if
you
can
stick
a
space
in
a
a
patron
field.
You
know
how
much
is
that
going
to
throw
off
searches
and
complicates
sorting?
That's
for
sure.
Yes,
exactly
so
you
know,
consistency
is,
is
really
important,
so
we've
I
I've
found
some
information
out
long
ago
and
I
can't
remember
the
the
original
Source
but
long
ago,
I
found
some
validation
code
and
we
have
tweaked
it
over
the
years.
B
I've
had
to
make
modifications
through
various
upgrades
in
in
Kohan
I'll
point
one
of
those
out
in
today's
episode,
but
we've
had
to
make
modifications,
as
koha
has
evolved
over
the
years.
So
we've
maintained
this
code
and
you
know
we'll
keep
this
up
in
the
in
the
library
for
everybody
to
get
to.
A
So
I'm,
looking
here,
I
remember:
I
was
using
this
I
I'm,
not
currently
using
Patron
validation
at
my
current
job,
but
I
did
use
it
the
last
job
and
I
just
did
a
quick
look
and
there
is
a
in
the
koha
on
the
koha
wiki
in
the
jQuery
Library.
There.
B
A
An
old
set
of
validation
rules
from
Paul
Landers
at
Texas,
Tech,
University,
Health,
Sciences,
Center
and
I
know
that
that's
where
I
base
the
the
stuff
that
I
used
to
do
with
validation.
A
I
think
it
is
because
I
think
we
talked
about
it
at
the
time
and.
B
I'll
I'll
refer
to
that
that
original
code
in
our
notes,
I'll
link
to
that.
But
you
know
since
since
that
was
posted,
there
have
been
some
changes,
especially
with
the
the
button.
The
save
button
that.
A
A
B
Validation
make
ensures
that
information
is
consistently
entered
so
that
you
know,
if
you
know,
we've
had
some
staff
that
entered
last
names
in
all
uppercase.
You
know
screaming
at
you,
we've
had
patrons
or
we've
had
Patron
names
that
had
spaces
in
the
wrong
places.
B
B
First
of
all,
there
is
some
validation
that
is
at
work
here
in
the
patron
entry
form.
George
pointed
that
out
to
me,
we've
we've
had
some
code
in
place,
so
you
know
we
have
not
I,
have
not
gone
through
here
and
and
checked
to
see
the
changes
that
have
been
made
over
the
years,
but
he
pointed
out
to
me
that
that
now
email
addresses
are
being
validated
to
make
sure
that
something
is
properly
formed
in
there.
B
So
if
I
were
to
put
just
something
random
in
there,
it's
already
complaining
about
it
says
please
enter
a
valid
email
address.
So
it's
letting
me
know
that
I
have
a
bad
email
address
and
it's
not
letting
me
save
until
I
have
something
correct
in
there.
So
I'll
just
put
that
back
where
it
was.
A
Yeah
I
think
that
was
a
change
in
the
HTML
in
the
in
the
HTML
standards.
Is
they?
If
you
add,
if
you
have
an
input
type
and
if
you
have
an
input
and
you
give
it
the
type
email,
then
HTML
automatically
validates
for
the
typical
parts
of
an
email
address
which
is
great
so.
B
A
It
wasn't,
it
wasn't
as
much
of
its
the
idea
that
some
koha
developer
came
up
with.
It
was
a
an
idea
that
the
people
that
that
did
the
standards
for
HTML
yeah
made
a
modification
there
at
the
basic
HTML
level.
Yeah.
B
So
you
know
there
are
some
improvement
improvements
that
are
being
made
along
the
way,
as
you
know,
as
we
get
further
and
further
into
HTML
and
and
and
koha
itself,
but
still
some
things
that
that
we
can
improve
on.
So
the
first
thing
that
I
want
to
point
out.
Let
me
let
me
go
over
to
my
code,
so
we're
not
going
to
do
all
of
this
today,
but
you
know
you
can
have
quite
a
lengthy
amount
of
code
just
for
validation
and
that's
that's.
B
This
is
basically
our
validation
segment
that
we
have
here
and
I
will
I
will
point
out
a
few
key
things
that
that
in
the
in
the
structure
here
we
we
have
a
message
that
we're
going
to
display
when
you
try
to
save
your
information,
and
so
we
start
out
with
a
blank
message
and
as
it
goes
through
validating
different
pieces,
it
will
add
to
that
message.
So
it'll
add
components
of
a
message
where
you
know
it's
trying
to
remind
us
about
spaces
or
formatting
or
or
such
so
it'll.
B
Add
to
that
that
variable
message
and
then
we
all
also
grab
different
components
that
we're
checking
against.
So
we're
setting
variables
against
different
fields
that
we're
checking
we'll
have
regexes
that
we
use
to
do
a
lot
of
this
validation.
So
I
have
some
case.
Sensitive,
regexes
and
I
have
some
case,
insensitive
regexes
that
will
will
validate
against
and.
A
B
Regex
is
short
for
I,
think
regular,
Expressions
yeah
and
if
you
search
for
regex
and
I'll
I'll,
add
some
links
to
the
the
video
and
post
this
linking
to
some
sources.
But
regex
is
just
basically
looking
for
patterns
in
whatever
you're
testing
against
to
see
if,
if
there's
a
match
or
if
this
not
a
match
in
some
cases,
so.
A
A
How
it
matches
for
email?
It
knows
that
there's
supposed
to
be
something
followed
by
an
at
symbol,
followed
by
something
else,
followed
by
a
DOT,
followed,
by.com
or
dot
org,
or
you
know
something
what's
supposed
to
be
there
right,
so
it
can
match
against
a
pattern
rather
than
matching
against
an
exact
set
of
an
exact
match
and.
B
Regex
is
really
great,
but
it
also
can
be
a
little
tricky
yeah.
There
are
a
lot
of
nuances
to
to
using
reg
X,
so
we'll
we'll
include
a
source,
some
materials
that
you
can
look
at
to
brush
up
on
regex
and
also
an
online
tester,
which
is
really
handy.
I
use
it
all
the
time
to
test
my
patterns
to
see
if
it's
coming
up
with
the
results
that
I
want
and
then
then
incorporate
that
input
to
my
code.
B
But
regex
has
been
very
handy
for
validation,
so
so
you'll
Define
some
patterns
to
test
against
and
then
you'll
actually
do
your
tests.
If
it
doesn't
pass
your
test,
it
will.
Then
we
add
to
the
message
you
know
telling
it
What
what
the
problem
is.
So
I've
got
lots
of
tests
here
that
I
that
I
test
fields
for
and
then
down
towards
the
bottom.
B
We
have
where
it
displays
the
alert.
So
it
basically
puts
an
alert
modal
on
the
screen
telling
you
those
that
message
that
you've
built
based
off
of
the
different
results
of
your
tests
and
then
at
the
very
bottom
I
I
have
where
we've
changed
the
the
save
button
and
that's
key
to
this,
and
then
we're
going
to
start
off
with
that.
B
B
One
reason
we
have
to
modify
the
save
button
is
it
doesn't
have
all
the
components
I
need
in
order
to
to
enable
disable
the
button
to
trap
those
validations
I
need
something
to
trigger
the
event
to
say,
hey,
validate
and
check
this
information,
and
then
you
know,
put
up
the
alert
and
prevent
it
from
submitting
if
it
isn't,
yeah
isn't
valid,
so
so
I've
had
to
modify
the
save
button
So.
Currently
on
the
save
button,
let's
see
here
where
is
it
it's
right
here?
B
This
has
changed
a
bit
from
the
three
point:
X
version
of
koha,
because
in
the
past,
when
we
would
save
the
button
was
just
in
the
form
and
if
you
scrolled,
it
would
go
off
the
page
and
at
some
point
they
Incorporated
the
floating
confirmation
buttons,
the
the
save
and
cancel
buttons
so
that
it
stays
on
the
screen,
no
matter
where
you
are
in
the
the
form
which
is
nice,
but
we
had
to
make
modifications
for
that
small
change.
B
So
so
we
have
the
save
button
here
and
what
we're
doing
is
we're
adding
some
elements
to
it,
we're
hiding
the
save
button
or
in
in
this
case,
in
our
case
it
we're
actually
deactivating
it
so
that
it
isn't.
It
doesn't
work
until
validation
is
passed,
but
we
we
have
some
elements
that
are
that
are
changed
on
here,
so
we're
replacing
it
with
we've
got
a
name
called
validate,
that's
associated
with
it
and
we're
incorporating
it
on
click
and
one
reason:
we've
replaced.
I
replaced
the
button.
B
Instead
of
adding
these
elements,
I
tried.
Adding
these
elements
in
the
past
and
I
wasn't
able
to
actually
modify
the
existing
button,
which
is
really
strange,
I,
don't
know
if
it
had
something
to
do
with
when
it
was
constructed
in
the
code
generation,
but
I
I
was
having
trouble
with
just
adding
these
elements
to
an
existing
button.
So
I
ended
up
using
a
replace
with
to
replace
the
button.
I
rebuilt
the
button
based
on
what
was
already
there
and
then
I
added
the
elements
that
I
needed.
B
Put
that
piece
in
there
I'll
save
that
and
now,
if
I,
so
here's
our
here's
our
button
here
it
doesn't
have
that
name
and
it
doesn't
have
that
on
click
I'm,
going
to
refresh
this
screen
now
and
we'll
inspect
the
button.
That
is
there
and
now
we
have
it
with
the
the
validate
name
and
we
have
it
with
the
on
click
function.
So
it's
going
to
return
a
function
called
Patron
validate
now.
If
I
use
this
now,
it's
it's
going
to
nothing's
gonna
happen.
Nothing's.
A
B
B
I
like
to
Define
these
things
before
you
actually
have
an
unclick,
so
I
have
an
unclick
that
is
asking
for
this
validation.
So
it's
always
a
good
idea
to
Define
that
function
before
you
have
buttons
that
call
for
it,
because
if
it
isn't
completed-
and
you
click
on
that
for
some
reason,
if
you
have
slow,
slow
bandwidth
and
you
click
on
that
and
that
function
hasn't
been
defined
yet
then
you
can
run
into
some
problems
so
always
Define
your
functions
before
you
define
where
it
can
be
accessed.
B
B
Here,
no,
it's
not
doing
that!
That's
right!
Okay!
So
there's
the
close
of
the
function
so
defines
Patron
validate
as
a
function
and
then
we're
going
to
Define
what
that,
what
that
all
does
and
that,
basically,
it's
going
to
Define
all
the
guts
of
our
function.
Now
one
of
the
last
things
that
it
needs
to
do.
B
A
A
B
So
my
modified
save
button
is
here
and
if
I
click
it,
it
should
save.
So
now
it
now
it
works
just
like
it
always
has,
but
now
we
can
add
other
functionality
to
that
function
in
order
to
accomplish
some
things,
so
we're
going
to
start
off
with
some
basic
structure
here.
So
one
of
the
first
things
that
we
need
to
do
is
we
need
to
Define
a
variable
that
will
hold
the
whatever
message
it
needs
to.
You
know:
shoot
back
like
you've
got
spaces
here.
You've
got
you
know
this
in
here.
B
And
that's
not
going
to
do
anything
just
yet
now
we
need
to.
We
need
to
Define
some
variables
that
we're
going
to
check
and
right
now,
I'm
going
to
get
my
variable
section
of
where
I
link
up
variables
with
specific
fields
and
right
now
we're
only
going
to
focus
on
the
surname
so
I'm
going
to
grab
that
for
today's
video
formatting
here.
B
B
A
B
Fingers
there
come
on
copy
I
like
to
have.
B
A
B
I've
got
two
variables
with
the
regex's
in
them.
These
These
are
sick
case
insensitive.
This
first
one
is
checking
for
spaces
now,
I
could
I
can
deal
with
spaces
in
a
couple
ways
this.
This
is
looking
for
basically
leading
and
trailing
spaces.
I
could
have
used
a
trim
on
this
and
just
cut
it
out
completely,
and
you
know
at
some
point.
I
may
just
consider
doing
that,
but
you
know
I
figure
if
the
the
staff
are
regularly
doing
this.
B
If
they're
copying
things
from
one
place
to
another,
you
know
sometimes
you'll
get
spaces
in
there
and
I
want
staff
to
be
in
the
habit
of
you
know
entering
things
correctly,
even
in
places
where
I'm
not
validating.
So
this.
B
This
helps
me
build
in
a
good
habit
for
the
staff
by
you
know
pointing
out:
hey
you've
got
spaces
at
the
beginning
or
the
end
of
of
this
field,
so
they
need
to
be
able
to
it
need
it
gets
them
on
point
to
watch
for
these
kinds
of
things,
rather
than
just
relying
on
the
program
to
do
it
itself
right.
B
So
the
first
regex
is
looking
for
spaces.
The
second
one
and
I
and
I
Define
these
separately,
because
I
can
reuse
the
space
reg
if
against
several
Fields.
B
Fields
right
this
one
so
I
have
the
space
reg
now
I
have
a
surname
reg,
which
is
looking
to
see
if,
if
they're,
actually
using
letters
and
not
numbers
in
a
name,
they're
not
putting
some
weird
characters
in
the
name.
So
the
only
thing
that
I'm
allowing
in
the
field
is
letters
and
then
a
a
hyphen
or
an
apostrophe,
because
you
have
beans
like
O'brien
or
you
have
hyphenated
last
names,
and
so
it's
it's
just
making
sure
that
that
all
of
this
is
Kosher
for
a
last
name.
A
B
Prince
okay,
so
yeah,
so
those
are
the
two
tests
that
I'm
doing
on
this
particular
case
today.
So
that's
going
to
grab
those
variables
now
I
have
to
actually
perform
the
test.
So
I've
got
a
section
down
here
that
does
the
validation
so
I'm
going
to
grab
these
two
tests.
So
we
we
have.
We
have
we've
defined
the
regexes.
Now
we're
going
to
test
against
those
those
regexes.
So.
B
Okay,
so
this,
if
statement
is
going
to
test
for
invalid
characters
and
then
it's
going
to
have
another
test
that
tests
for
the
space
okay,
see
if
there's
any
spaces
in
it,
and
that
should
be
well
okay,
that
that
should
be
it
but
it'll
test.
But
nothing's
going
to
to
happen
with
that
message:
I'm,
defining
a
message
I'm,
adding
to
the
message.
So
it's
it's
testing.
It's
testing
this!
It's
if
it's
not
passing
this
test,
meaning
that
this
particular
variable.
So
here's
the
variable
that
I'm
testing
and
here's
the
test
I'm
testing
against.
B
B
That's
the
basic
structure
there
and
if
it
doesn't
pass
it's
going
to
take
that
message
variable
and
it's
going
to
add
to
it
because
I
can
have
you
know
several
things
go
awry
in
one
form.
So
it's
going
to
take
that
message.
If
the
message
is
going
to
equal
itself,
plus
this,
it's
going
to
add
a
last
name-
contains
invalid
characters,
I'm
adding
a
break
so
that
it
goes
to
another
line
in
the
message.
So
that's
what
those
slash
ends
are
for
right.
B
B
Excuse
me
and
then
it's
going
to
test
the
surname
against
the
the
space
test
to
see
if
there's
Extra
Spaces
and
if
there
are
it's
going
to
add
a
message.
A
space
has
been
found
at
the
beginning
or
end
of
the
field.
Okay,
so.
B
So
then,
at
the
very
end
of
our
function,
after
all
its
testing,
there
was
another
if
statement.
So
this
is
where
you
were.
You
were
talking
about
right,
the
if
else,
yes,
the,
if
else
so
we're
going
to
add
this
condition
here
that
will
display
the
alert
so
I'm
going
to
add
this
and
then
I'll
have
to
modify
what
I
put
in
there.
B
B
B
B
B
B
So
now,
if
my
surname
starts
with
a
space-
and
you
know
you
can
see
how
easy
it
is
to
not
see
that
space
I'm
going
to
save
and
it's
going
to
pop
into
this
message,
last
name
contains
invalid
characters.
A
space
has
been
found
at
the
beginning
or
end
of
the
field.
So
basically
it's
telling
me,
you
know
hey
it's,
it's
an
invalid
character.
It's
not
one
of
the
characters
that
that
is
defined
so
right,
but
specifically
it's
saying
space
has
been
found.
So
that's
why
I
put
that
in
those
in
parentheses
there.
B
B
If
I
do
something
weird
like
I
put
some
other
character
in
there,
I'm
going
to
say,
save
last
name
contains
invalid
characters.
Okay,
that
wasn't
that
wasn't
acceptable.
So,
but
maybe
her
name
is
oh
Frosty.
A
B
B
B
And
I,
don't
think
in
this
validation
I
think
this
this
we
can
do
in
another
episode.
It
doesn't
validate
whether
or
not
it's
capitalized
or
not.
I
do
have
that
in
our
system.
Some
people
may
or
may
not
want
to
go
that
far.
But
you
know
this
gives
us
a
good,
a
good
beginning
of
validation.
I,
don't
think
this
one,
this
test
tests
against
perhaps
either
yeah.
B
A
Yeah,
you
should
be
able
to
set
up
a
pattern
to
match
any
field
that
you're
dealing
with
and
make
it
you
know
whatever
you
want
it
to
be.
If
you
want,
if.
A
To
be
in
a
specific
format,
you
can
do
that
yeah.
That
was
one
of
the
things
when
I
was
using
validation.
My
last
job,
that
was
one
of
the
things
that
we
had
at
doing,
was
making
sure
that
all
phone
numbers
had
three
digits,
a
dash
three
more
digits
a
dash
and
then
the
final
four
digits
and.
B
B
A
Anything
could
come
after
those,
so
I
could
set
it
up.
It
didn't
have
to
be
exactly
10
digits
with
the
dashes.
It
could
be
10
digits
with
the
dashes,
and
then,
after
that
you
could
put
an
extension
number
or
you
could
put
a
leave
a
in
parentheses.
You
could
write
messages
or
you
know
you
could
add
anything
after
the
part
that
I
wanted
to
validate
right.
The.
B
Phone
numbers
were
were
especially.
A
B
A
B
A
B
B
And
you
know
it
was
important
for
us
too,
because
I've
actually
made
some
modifications-
and
maybe
we'll
do
this
in
another
video.
Some
at
some
point,
but
I've
made
some
modifications
where
we
do.
We
we
do
SMS
and
you
have
to
enter
a
phone
number
and
I
have
a
a
link.
Next
to
the
SMS
field,
where
you
enter
the
phone
number
for
for
texting
where
you
can
actually
copy
the
phone
number
into
that
field,
and
but
that
phone
number
has
to
be
entered
a
very
specific
way
for
the
SMS
field.
B
It
has
to
be
entered
with
a
plus
one
and
then
all
the
digits,
without
any
hyphens
or
or
spaces
happening
in
there.
So
basically
I
cut.
You
know
if
if
they
know
that
that's
the
the
number
that
they
want
to
use
for
SMS,
they
can
copy
it.
What
it'll
do
is
it'll
copy
that
into
that
field
and
because
it's
properly
formatted
it
knows
to
strip
all
the
hyphens
out
of
there
and
add
a
plus
one
in
front
of
it
and
put
it
in
that
field.
B
So
it
makes
it
really
easy
for
them
to
enter
that
SMS
number.
If
they've
already
entered
it
in
the
phone
number
field
to
begin
with
so
cool
so
yeah,
you
know
the
validation
really
stream
helps
to
streamline
some
processes
down
the
road,
even
if
you're
not
using
that
at
this
point,
you
know,
you
know,
make
sure
you
know.
If
you
do
it
now,
you
want,
you
won't,
have
to
go
back
and
clean
it
up
later,
which
is
really
nice.
B
So
that
is
it
for
this
week
and
we
will
continue
on
the
series
will
will
show
some
other
validations
that
we
can
do
on
our
Patron
entry
form
in
upcoming
episodes,
cool.
B
If
there
are
consistent
pieces,
if
there
are
consistent
things
between
all
of
your
libraries,
like
phone
numbers,
have
to
be
formatted.
This
way
you
can
at
least
do
that
you
can
at
least
validate-
and
you
know
you
know,
push
for
consistency
in
the
areas
that
are
consistent
among
all
your
libraries,
I.
A
Think
that
was
one
of
the
big
reasons
is
I.
Think
we
have
one
Library
where
they
don't
use
any
phone
numbers.
It's
a
school
library
and
you
know,
and
so
I
think
I.
Remember
that
being
an
issue
is
that
I
would
need
to
write
the
validation
in
such
a
way
that
phone
numbers
weren't
required
at
that
place
at
all.
So.
B
Right-
and
you
know,
the
validation
doesn't
necessarily
require
the
the
validation
that
we're
using
isn't
doesn't
make
the
field
a
requirement.
So.
A
B
A
B
Right
well,
we'll
see
everybody
again
in
two
weeks.
Oh
don't
forget!
If
you
enjoy
our
videos,
please
go
to
our
YouTube
channel
I.
Believe
it's
youtube.com,
Slash
koha,
us
no
hyphen.
Is
that
correct.
B
So,
okay,
but
look
for
kohai
us
on
YouTube
at
the
very
least
and
subscribe
to
our
playlist.
We
have
a
playlist
specifically
for
these
videos.
You
can
subscribe
to
them.
You
can
like
our
videos.
Let
us
know
that
that
you're
enjoying
our
videos
at
the
very
least
by
liking
them
there
or
comment
on
them.
You
can't
do
that
on
kohai
dash
us
dot
org,
but
you
can
do
that
on
our
YouTube
channel
and
we'd
like
to
have
feedback
about
what
you
think
about
our
videos.
B
If
you
have
questions,
if
you
found
errors,
if
they
found
ways
to
improve
things
or
if
there's
a
particular
topic
that
you
would
like
feel
free
to
comment
but
check
us
out
on
YouTube
and
we'll
see,
everybody
in
two
weeks
see
you
later.