►
From YouTube: Acquisitions Special Interest Group - 4/21/2020
Description
Chat logs:
00:19:41 jennie evans: YES
00:19:45 jennie evans: STRONGLY AGREE
00:19:51 Barbara Johnson: does multiple order receiving have a bug #?
00:20:05 Victoria Escobar: Yaay, I've been waiting for that!!!
00:20:24 Nick Clemens: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8179
00:20:54 Nick Clemens: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20212
00:21:21 Nick Clemens: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18731
00:26:11 Nick Clemens: http://localhost:8080/api/v1/.html
00:27:19 Laura (MCC): Wondering about blanket po integration
00:27:28 Margaret hade: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13325
00:35:19 Victoria Escobar: How is the development going for being able to close multiple invoices at the same time?
00:37:07 Victoria Escobar: Great, thank you.
00:41:20 Laura (MCC): sounds good
00:46:39 Jason Robb: https://docs.google.com/document/d/1t706ZWK6TTpedd0zOa4dltn2DW2i5Z1C5Vr03hsrk2o/edit?usp=sharing
00:49:19 Laura (MCC): thanks Nick
00:49:31 jennie evans: thanks, nick!
00:52:41 Barbara Johnson: Bedford might be able to help a little
00:54:09 Laura (MCC): Do we know how many libraries use acquisitions
00:54:22 Margaret hade: http://devs.bywatersolutions.com/#
00:57:47 Laurie McKee: I've done one.
00:57:51 Barbara Johnson: I think I've done 3. It's exciting.
00:58:28 Laura (MCC): Might that be something we want to do in a meeting or does that not make sense
00:58:29 George: I've done a bunch
00:59:54 Jason Robb: http://koha-us.org/kohathon-2020/
01:01:00 jennie evans: that's the best way to get more viewers--with mystery
01:01:58 Laura (MCC): We are all working from home
01:02:08 George: Things are peachy
01:02:24 Barbara Johnson: Some staff working at library, some from home. Doing deliveries of holds.
01:02:26 jennie evans: we are all still coming in here too
01:02:29 Judy: Los Gatos is closed. Everyone working from home.
01:02:31 jennie evans: well, 7 of us
01:02:48 Laurie McKee: We're going in alternate days.
01:03:14 Victoria Escobar: We are all working from home, not placing orders, using money for cloudLibrary
01:03:38 SAMSUNG-SM-G950U: Snow College library is also alternating days, in addition to some work from home
01:03:45 Laura (MCC): what state are you
01:03:50 jennie evans: she's in TX
01:04:08 jennie evans: lol
01:04:13 Laura (MCC): lol
01:04:15 George: That's all you need to say
01:06:39 Laura (MCC): Is Kohathon all online
01:07:36 Jason Robb: http://koha-us.org/kohathon-2020/
01:07:47 Jason Robb: bitly.com/kohausYT.
01:07:50 Jason Robb: bitly.com/kohausYT
B
I'll
start
over
and
I'll
try
to
be
more
succinct
this
time,
so,
at
least
from
a
developer
perspective,
what
I
really
see
happening
in
acquisitions
right
now.
The
big
thing
that
we
are
working
on
is
kind
of
moving
everything
into
the
api's.
Tomas
has
been
doing
a
lot
of
work
with
this,
while
integrating
with
gobe
and
allowing
integration
with
other
systems.
B
So
the
reason
we
want
to
move
to
use
the
Koha
api
is
that,
right
now,
when
you
go
to
acquisitions-
and
let's
say
you
go
to
the
acquisitions
homepage,
we
start
pulling
in
all
of
the
order
information
totaling
everything
up
getting
the
budget,
information
and
kind
of
building
these
tables
out
of
it.
The
same
similar
things
happen
when
you
go
to
receive
an
order,
we
sort
of
go,
get
all
your
open
orders,
get
all
the
information,
then
funnel
it
into
the
page.
B
The
nice
thing
with
the
API
is
it
kind
of
uses
a
different
workflow
where,
instead
of
having
to
load
everything
at
the
start
of
the
page,
we
go
and
we
load
the
page
and
then
we
can
start
getting
the
orders
and
processing
them
into
the
page
so
that
you
don't
have
to
wait
so
long
for
everything
to
show
up.
You
can
sort
of
see
it
as
it's
coming
in
and
if
you
make
any
changes
or
filter,
we
don't
have
to
reload
the
entire
webpage.
B
We
can
just
reload
that
one
little
kind
of
specific
part
of
it,
so
those
are
the
big
things
I
have
in
my
queue
and
I'm
working
on
acquisitions
multi
receipt
so
that
you
can,
when
you're
receiving
you
can
receive
several
items
at
once,
instead
of
having
to
receive
one
at
a
time.
That
is
a
tricky
issue
just
because
kohai
is
not
built
that
way
currently
and
there's
a
lot
of
information
that
you
need
to
put
while
receiving
an
order.
But
those
are
like
big
previews
of
what's
coming.
So
what
other
questions
do
you
have
I?
B
A
A
B
So
much
like
the
bug
number
form
multi
receipt,
which
is
a
very
old
bug
number
that
we
kind
of
inherent
it
until
it's
done.
We
don't
actually
put
a
lot
there,
so
you
may
have
to
wait
a
little
while
to
get
that
kind
of
update,
but
the
other
ones
there's
bug
0
1,
which
is
just
called
slowness
and
acquisitions,
and
that's
kind
of
the
large
where
a
lot
of
these
changes
are
happening
and
I'm
trying
to
see
the
other
book
is
pushed.
So
it
doesn't
come
up
with
my
initial
search.
B
And
then
they'll
be
tangential
bugs
from
all
of
those,
and
there
has
been
I
know.
Kyle
is
still
working
on
the
EDI
plugins
and
doing
stuff
martinet
PT,
FS,
Europe
I.
Don't
believe
he
has
any
bug
numbers
yet,
but
they
are
working
on
improving
kind
of
a
lot
of
the
core
EDI
code
which
will
just
bring
along
with
it
more
of
those
kind
of
acquisitions
cleanup
and
changes
and
things
that
people
want
to
see
and
I'm
gonna
are.
We
is
this
strictly
a
u.s.
group,
or
is
this
a
wheat
worldwide?
Here
we.
C
B
A
I
know
I'm
just
gonna
ask
about
a
bug
that
we're
interested
in
and
hopefully
other
people
will
it'll
stimulate
some
ideas
too.
There's
a
connection
between
acquisition
or
its
acquisitions
and
the
purchase
suggestions.
When
you
do
non
EDI
ordering
there's
a
way
to
connect
the
purchase
suggestion
to
the
order
and
then
the
patron
can
get
notified.
You
know
during
the
process
when
the
thing
comes,
but
right
now,
if
we
place
EDI
orders
that
isn't
a
connection.
B
Don't
have
any
specific
updates
on
that
one
right
now
again,
it
is
in
the
works
and
it's
sort
of
there.
There
was
a
lot
of
waiting
while
Tomas
worked
on
the
end
points,
because
we
kind
of
want
everything
to
use
these
end
points.
So
that's
really
been
the
linchpin
of
this
to
get
his
work
on
top
of
it
rather
than
sort
of
building
on
the
existing
systems
and
having
to
change
things
or
end
up
facing
the
same
problems
that
we
already
have.
D
C
B
So
the
API
essentially
just
gives
a
standard
way
for
people
to
interact
with
the
kohat
database.
It
allows
for
outside
systems
to
make
you
know,
standard
request
to
Koha
and
say,
like
I,
want
to
get
acquisitions
information.
I
want
to
change
acquisitions
information
patron
information,
it's
sort
of
the
whole
database,
it's
just
a
different
way
of
interacting
with
the
database,
so
that
you
can
directly
make
these
requests
and
get
objects
and
do
things
to
them.
B
It's
a
benefit
for
integrating
with
outside
partners
so
that
they
can.
You
know,
use
these
standard
requests
that
they
already
have
to
do
to
do
what
they
expect
to
do
and
then
internally,
to
Koha.
It's
helpful
as
I
said
before,
because
it
lets
us
interact
with
the
data
without
having
to
load
everything
into
the
webpage.
It
lets
just
load
it
a
little
more
dynamically
and
make
these
requests
a
little
bit
simpler
and.
B
We
have
been
building
the
restful
interface
for
some
time
and
it's
really
kind
of
picking
up
steam
now,
so
most
of
the
developments
that
you're
going
to
see
are
going
to
come
with
these
API
as
well
right
now,
and
if
any
of
you
are
curious,
you
can
actually
go
and
see
like
what
endpoints
are
built
in
your
current
system
and
everything
like
that.
Let
me
just
put
a
little
link
in
there.
Just
replace
that
localhost:8080
you
see
if
I
can.
B
A
Just
I
don't
know
if
anybody
else
has
questions,
one
bug
that
this
group
has
sort
of
been,
which
you
know
negotiate.
You
know
pooling
our
thoughts
on
and
getting
different
ideas
and
trying
to
create
something
that
all
of
us
can
benefit
from
is
Lexi
one
three
three
to
five
and
that's
the
tracking
function
for
the
budget
modules,
and
we,
you
know,
we
kind
of
came
up
with
some
ideas
and
I
know
that
I'm
guessing
it
was.
You
were
part
of
the
discussion
too.
We've
got
some
basically
came
back
with
three
phases.
B
A
B
You
know
the
specific
use
case
that's
asked
for
and
how
it
might
be
used
elsewhere,
as
well
as
kind
of
what's
going
to
need
to
exist,
just
to
get
it
through
that
community
process
and
doing
it
in
a
way
that
generally
were
writing
code.
That
is
going
to
be
reusable
and
extensible.
Where
we
can,
you
know
it's
always
better
to
abstract
or
to
pull
something
out.
B
Make
it
work
in
a
bigger
fashion,
then
then,
focusing
in
on
one
real
specific
thing,
because
that
gets
us
into
the
trouble
that
we
have
a
lot
of
times
where
we
have
this
code.
That
is
really
specifically
written
and
the
next
time
you
try
to
do
something
with
it.
It's
not
as
flexible,
so
we
always
want
to
make
sure
things
will
be
flexible,
so
yeah,
so
the
first
two
parts
of
it
are
the
are,
or
at
least
the
first
part
of
it
is
very
small.
That's
just
adding
the
logs.
B
This
is
because
we're
adding
not
just
that
logging
to
it,
but
adding
reasons,
and
we
don't
actually
like
funds
as
they
stand
right
now.
They
don't
have
kind
of
any
of
this
information
stored
in
them.
They
are
just
a
number
kohat
like
when
you
order
something.
We
don't
actually
subtract
that
from
the
fund
anywhere.
We
always
do
that
on
the
fly.
So
all
of
your
totals
are
always
calculated
at
the
moment.
B
A
D
Yeah
I've,
what
we
have
is.
We
have
blanket
POS
in
our
our
budget
whereby
we
say
we're.
Gonna
spend
two
thousand
dollars
for
ebook
content
and
I
I,
put
it
into
my
system
and
then,
as
invoices,
sort
of
or
charges
are
expended,
I
want
to
like
track
what
is
happening
so
that
people
know
how
much
is
left
with
the
with
the
funds
and
there
are
sort
of
a
workaround
that
everyone
sort
of
talked
about,
but
it's
not
explicitly
discussed
and
people
use
blankets.
E
C
D
Our
previous
systems,
like
the
two
or
three
systems
we've
had
before
all,
had
something
built
in
specifically
for
blanket
POS,
so
we're
relatively
new
in
Kohala
last
two
years,
so
having
an
ability
to
do
that
so
that
we
can
track
how
much
I
mean
we
can
log
in
to
our
other
systems.
But
this
is
just
a
quicker
way
if
it's
built
in
we've
sort
of
like
worked
around
it,
but
there
would
be
something
more
implicit
that
would
be
nice
to
have
it
included.
Yeah.
B
B
So
a
lot
of
this
stuff,
you
do
have
to
explain,
and
we
have
to
understand,
but
I,
don't
know
that
anyone
is
working
on
that
and
it's
not
something
that
has
that
has
been
brought
up
to
me
before
it
does
sound
like
something
that
it
would
be
possible
to
do.
We
have,
in
the
past,
talked
about
having
child
orders,
but
I
think
that
still
is
not
sort
of
the
same
thing.
So
yeah
I
don't
know,
but
that
sounds
interesting.
B
B
At
least
you
know
invoice
that
mm
and
then
just
record
an
invoice
adjustment
for
each
order
that
comes
in,
although
the
totalling
might
still
get
weird
there,
but
there
I
think
you
could
at
least
you
can
at
least
have
it
tracked
that
way
and
then
use
a
report
to
give
you
those
correct,
totals
of
what
is
left
out
of
that
mm,
maybe
not
natively
in
Koha.
But
it
would
give
you
the
ability
to
add
an
individual
line
for
each
order
and
then
use
a
report
to
get
your
numbers
right.
D
B
B
A
A
Okay,
I
think
I
think
maybe
a
good
place.
The
next
step
that
we
need
to
do
is
maybe
open
a
bug
just
and
describe.
You
know
exactly
the
function
that
we
want.
That
way.
You
know
we
can
like.
We
did
with
the
this
last
one.
You
know
get
firmed
up,
how
we
want
it
to
function
as
far
as
librarians
doing
the
work
and
and
then
we
can
see
if
there's
libraries
that
are
willing
to
support
the
development
of
it
and
see
what
we
can
get
going.
A
B
Looking
for
see
this
isn't.
Their
problem
is
that
this
is
my
developer
brain
I'm,
just
like
I
start
playing
with
this
I'm
like,
oh,
maybe
you
could
just
have
a
basket
that
is
like
pre
encumbered,
and
so
you
say
this
basket
numbers
mm
and
then
you
just
add
your
items,
and
it
will
tell
you
when
that
baskets
out
of
money,
but
you
guys
you
guys,
should
figure
out
what
you
want
before
you.
Let
us
go
play
and
be
kind
of
how
to
do
it.
A
A
A
That's
something
I'm
curious.
You
know
for
people
that
do
EDI
if
they're
interested
in
that,
if
I'm
curious
Nick,
if
you
think
that's
a
big
ask-
or
you
know,
since
we've
got
the
function
in
there
for
the
orders
and
talking
to
the
vendor
already,
is
it
just
a
matter
of
figuring
out
how
to
identify
a
canceled
order?
I
would.
B
Say
for
that
question,
you're
gonna
need
to
invite
Kyle
to
this
meeting.
Well.
I
have
worked
a
lot
of
the
acquisitions
in
Quahog
code.
All
of
the
EDI
stuff
is
Kyle's
project,
so
he
has.
He
would
be
the
one
who
would
know,
but
I
have
not
heard
it
come
up
before,
which
does
not
mean
that
it
hasn't
come
up
before.
Okay,
because
he
deals
with
EDI.
A
A
C
Think
Nick
brings
up
a
good
idea:
it'd
be
nice
to
get
the
developers
who
are
working
on
acquisitions
to
stop
by
this
meeting
occasionally
and
check
in
with
them.
We
can
give
them
a
real-time
feedback,
and
if
you
get
some
questions
answered,
so
we
can
check
with
Kyle
and
maybe
edible
to
Martin
or
Jonathan
for
some
months
out
in
the
future
and
see
if
we
can
make
this
a
regular
thing.
A
C
B
If
anything
is
in,
they
need
sign-off
stage,
and
you
want
to
sign
off
on
it.
You
can
either
do
it
yourself,
I
those
inboxes.
We
are
also
always
happy
to
help
either
demo
those
bugs
or
do
something
to
you
know,
to
get
your
sign-off
and
help
move
it
along.
We
really
love
to
see
librarians
involved
and,
as
I
always
say,
your
opinions
carry
a
lot
more
weight
than
my
opinion,
especially
in
the
QA
stage.
B
Workflows
tend
to
be
very
different
between
public
and
academic
and
then
us
versus
worldwide
libraries.
So
it's
always
good
just
to
get
that
kind
of
opinion
in
perspective
so
that
we
know
if
something
has
gotten
too
specific
or
just
if
we're
going
in
the
right
direction
with
anything
and
those
are
the
big
places.
If
you
want
to
get
real
involved.
You
know
if
you're
someone
tactical
like
George
and
you
want
to
or
Jason
even
and
you
want
to
join
the
QA
team
and
be
out
there
signing
off
on
bugs.
B
That's
always
really
appreciated
and
we're
glad
to
help
you
get
what
you
need
to
do
things
like
that
out
there
well
I
mean
I'm
gonna
call
you
out
my
name's
guys
come
on.
I
can
see
I'm,
not
all
that
technical,
but
just
in
that
you
know
anything
that
you
see
that
you
do
have
questions
about,
don't
hesitate
to
ask
us.
B
We
are
available
in
slack
and
if
you're,
not
part
of
the
Bywater
partners,
we
are
available
in
IRC.
You
can
find
us
and
ask
us
questions
about
anything.
We're
always
happy
to
talk
and
help.
We'd
rather
have
attention
on
our
bugs
that
you
know
it
says
that
we
need
more
work
and
not
have
any
attention
at
all.
A
A
A
A
Fortunately,
you
know
I
I,
think
what
we
have
been
trying
to
do
with
the
133
to
5
is
kind
of
what
you've
described
it
was
in
discussion,
so
we
kind
of
got
together
and
and
worked
out
what
we
wanted.
You
know
different
libraries,
giving
their
input
and
stuff
so
now
we've
got.
We've
got
something
concrete
that
you
get,
that
developers
can
look
at
and
say
hey.
This
is
what
what
we
need
to
do.
A
A
In
in
the
agenda,
I'd
listed
all
the
acquisition
bugs
that
need
sign-off
I'll
figure
out
how
to
get
it.
Access
to
everybody
there
and-
and
like
you
said,
if
people
need
help
signing
off,
sometimes
the
acquisitions
bugs
can
get
a
little
complicated
because
you
need
you
know
to
have
all
these
baskets
set
up
which
the
sandboxes
don't
have
anything
set
up
in
them.
A
A
Yeah
we
can
help
each
other
out
with
this,
and
definitely
you
know
contact
the
developers
I've
I've
signed
off
on
a
few.
Now
it
was
hey,
you
know,
got
my
feet,
wet
and
I.
Think
I've
signed
off
on
two.
Now,
it's
very
exciting,
but
the
same
boxes
are
pretty
straightforward
to
use
and
there
is
the
YouTube.
You
know
there's
a
video
that
shows
you
just
exactly
how
to
walk
through
the
whole
process.
It's
very
helpful
when
I
came
across
the
field,
I
was
uncertain.
What
to
put
in
there.
A
A
A
B
A
A
A
Yeah
this
is
part,
one
would
be
the
log
modifications
to
the
funds,
so
that
would
be
add
an
option
to
include
fun.
Changes
into
the
action
logs
would
come
in
at
a
cost
of
one
thousand
two
hundred
and
fifty
dollars,
not
bad
part.
Two
is
build
the
functionality
and
interface
to
modify
phone
funds,
as
your
document
indicates
a
new
area
to
modify
amounts
from
in
to
active
funds,
with
a
reason
for
change.
That's
where
the
rubber
hit
the
road
$7,500.
A
For
that,
and
then
part
three
is
see
the
history
of
the
fund,
which
is
create
a
history
table
on
the
page
and
populate
with
the
information
log.
So
that's
that
little
table
that
we
put
in
so
that
you
can
see
what
what
had
happened
in
the
past,
what
the
changes
were,
and
that
was
a
cost
of
one
thousand
two
hundred
and
fifty
dollars
so
for
doing
the
math.
That's
a
total
cost
of
$10,000.
For
that
update,
which
is
a
little
bit
more
than
I
thought
it
would
be.
But
my
first
thought
is
to.
A
Submit
that
to
the
development
committee
and
see
if
we
can
get
that
part
of
it
done
the
one
thousand
two
hundred
and
fifty
dollars
see
if
we
can
get
that
done
so
thoughts
on
that.
Does
that
seem
reasonable
to
do
you
just
submit
to
get
the
part
one
and
then
we'll
have
to
look
at
the
7,500
section,
which
is
really
the
meat
of
what's
going
on
and
I?
B
A
There's
a
little
note
in
here
that
says:
there
are
two
areas
that
make
this
development
complex.
The
first
is
the
creation
of
a
new
interface
to
modify
the
amounts
and
display
the
log
data
changes.
The
second
is:
writing
the
logic
in
the
code
to
transfer
funds
transfers
in
quotes.
This
requires
back
in
logic
and
processing.
If
you
want
just
to
add
or
subtract
amounts,
transfers
would
be
a
two-step
process.
A
Part
two
would
decrease
to
$5,000
instead
of
the
7,500.
So
that's
something
to
think
about
too.
Instead
of
having
the
ability
to
transfer
from
one
screen,
you'd
have
to
add
for
one
amount
and
then
go
to
another
screen.
You
know,
whichever
other
fund
and
subtract
from
that.
That
would
reduce
the
cost
by
$2,500,
so
we
can
kind
of
okay.
A
A
F
C
C
F
C
A
A
So
we
need
to
get
in
there
too.
We
need
to
make
sure
we
get
our
our
logs
as
well.
Okay,
that's
probably
maybe
the
best
way
to
chip
away
at
this
is
to
create
three
bugs
for
each.
You
know,
part
1,
part
2,
part
3,
and
then
then
we
can
put
the
funding.
You
know
we
can
see
what
happens
with
the
Development
Committee
and
then
just
put
put
it
out
there
for
funding
to
see
what
we
can.
We
can
do
with
that.
A
A
A
D
F
A
C
A
A
So
that's
great,
and
that
would
be
a
really
good
agenda
item
and
and
I
do
want,
while
I'm
thinking
about
this
I
do
want
to
put
in
a
plug
for
Kohath
on
which
is
Thursday
of
this
week
and
Jason
gets
pale
when
you
see
lots
of
work
going
into
that,
encouraging
you
to
check
out
the
agenda.
That's
on
the
kohai
us
web
page
and
just
there's
going
to
be
a
keynote
speaker,
speaker
and
I.
Forget
I
want
to
say
it's
I,
don't
remember
what
it's
it's
earlier
in
the
process
around.
It's.
E
A
A
A
A
A
Okay
Barbara
says
some
staff
working
at
the
library
some
from
home
doing
deliveries
of
holds
okay
and
Jeannie.
We
are
all
still
coming
in
here,
too.
Okay,
all
right,
all
seven
of
us,
okay,
Los
Gatos,
is
closed.
Everyone's
working
from
home
Laurie
is
we're
doing
we're
going
in
alternate
days.
Okay,
that's
it's
really
interesting
to
see
all
the
different
ways
that
people
have
approached
this.
We
started
off
doing
curbside.
Then,
when
our
governor
said
stay
home,
stay
state
yeah
tried
to
say
that
stay
home
stay
safe.
A
We
decided
enticing
people
to
come
out
and
get
their
library
materials,
probably
wasn't
in
the
spirit
of
what
was
going
on.
So
we
stopped
that.
But
now
the
governor
is
trying
to
restart
things
again
so
Friday
and
we
will
be
in
retail.
Business
can
open
as
a
curbside
kind
of
thing.
You
know
so
we're
going
to
start
curbside
back
up
again
on
Friday,
okay,
so
snow
college
library
is
also
alternating
days.
In
addition
to
some
work
from
home.
A
You
that's
all
I
need
to
say
right
so
anyway,
if
there
is
any
any
questions
on
the
kohai
us
website
on
the
the
sig
page,
the
special
interest
group
page,
you
can,
if
you
talk
with
other
people,
there's
a
join
button
there
now
to
join
a
google
group,
which
is
what
everybody
else
all
the
other
SIG's
are
doing.
So
we're
gonna.
Try
this
again,
that's
a
place
to
ask
questions
in
between
meetings
and
discussions.
So
I
think
one
of
the
things
that
we
want
to
discuss
and
we'll
get
a
discussion
going
is
the
blanket
pio.
A
F
A
C
Just
on
the
Google
group
part,
if
you're
pretty
antithetical
to
Google
or
you
don't
haven't
you
meal
anything
like
that.
Rhonda
and
I
can
always
add
your
email
directly.
So
you
can
just
use
it
like
any
of
the
other
listservs.
Where
you
see
something
you
respond
and
then
you
can
send
it
to
I.
Think
its
acquisitions
SI
g
at
kohai,
us
org,
correct
me.
If
I'm
wrong.
F
C
F
F
We're
streaming
it
all
live
to
YouTube
and
we're
breaking
it
up
into
three
chunks
or
there'll,
be
three
different:
youtube
links,
you'll
click
throughout
the
day
and
I
will
have
more
information
about
that
coming
out
soon
and
I
hope,
since
it's
Thursday
but
yeah
watch
for
that,
and
of
course,
since
it's
being
streamed,
live
it'll
have
will
have
the
vods
the
videos
recordings
of
it
as
well.
So
if
you
missed
something,
you
can
always
go
back
and
watch
it
later.
F
F
Yeah
I
mean
we've
got
this
page
that
I
linked
earlier,
which
is
has
a
schedule
on
it.
We
will
get
those
links
at
it
to
the
YouTube.
Also,
if
you
subscribe
to
our
You
Tube
channel
you'll
get
notified
when
we
go
live
and
when
the
link
changes,
I
had
a
period
there,
somehow
that'll
get
you
Charlie
YouTube
page
and
you
can
subscribe.