►
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
A
A
What
if
we
do
you
configured
our
package
store?
Cisco
live,
not
neither.
We
had
to
tell
it
where
to
go,
get
so
hot.
We
got
the
key
security
even
make
sure
the
packages
haven't
been
tampered
with.
We
updated
the
existing
packages.
We
then
installed
in
the
rear,
DB
server,
which
include
and
client
installed
and
now
reactions
to
step
for
installing
kohat
any
night.
So
once
we've
got
cause
called
where
most
of
the
way
they've
got
a
number.
A
A
C
A
It
was
accommodating
the
new
operating
system
selection
of
1804,
but
the
older
version
did
not
have
platinum,
April,
5
default.
This
actually
takes
care
of
that
something
that
was
not
done
and
actually
memcache,
which
was
something
you
had
to
consider
manually
in
earlier
versions
of
software
and
no
actually
enabled
by
default,
and
you
don't
have
to
do
anything
to
get
that
meat
in
place.
A
A
A
B
A
A
A
A
B
So
after
before
the
next
session
after
this
will
be
the
roundtables
in
this
room
and
I
wanted
to
let
everybody
know
that
we
have
some
door
prizes,
we
will
be
doing
that
drawing
for
right
before
the
roundtable
start.
We've
got
a
brand
new
still
in
the
wrapper
Koha
u.s.
notebook
lived
in
the
wrapper
mint
condition
of
next
year,
we'll
be
able
to
sell
it
for
twice
with
it.
At
the
meeting,
we'll
also
have
a
coffee
cup
with
Koha
US
29th.
B
We
need
information
on
it
and
as
a
special
secret,
we've
got
a
lanyard
from
the
kohai
u.s.
2017
Coeur
d'alene
conference,
which
has
as
those
of
you
who
were
there
known
us,
drive
USB
Drive
I'll
give
those
away.
So
if
you
haven't
signed
up
for
the
door
prizes,
there's
a
canned
over
on
the
registration
table
and
there's
some
slips,
there
just
put
your
name
on
the
slip
and
stick
it
in
there
and
we'll
drop
of
those
in
a
while.
B
E
A
B
D
D
D
D
D
C
Colorado
that.
D
The
fact
that
that
raises
expectations
I
think
so
the
expectations
are
very
high
at
Colorado,
College
and
things
are
going
to
happen
and
they're
gonna
have
it
now.
Probably
the
most
unique
thing
is
that
we're
on
the
block
plan,
so
our
students
are
in
one
class
at
a
time
for
three
and
a
half
weeks
at
a
time,
and
so
everything
needs
to
happen
extremely
quickly
there,
because
if
you
live,
if
you
miss
a
day
or
you
know
day
and
a
half,
that's
like
this
in
the
whole
week
as
far
as
resource.
E
Migration
timeline
for
Montevallo,
we
began
looking
at
systems
for
pricing
in
January
2018
I
had
just
gotten
the
previous
summer.
We
had
switched
from
oclc's
WMS
they're
discovering
layer
to
EDS
for
our
discovery
layer,
and
so
some
of
the
changes
that
we
had
kind
of
made
prior
to
doing
this
sort
of
feed
into
what
we
were
doing.
We
at
that
time,
I
had
kind
of
realized
that
we
wanted
to
look
at
a
different
ALS
platform,
but
we
weren't
quite
ready.
E
D
Until
I
built
this
slide,
I
felt
like
ours,
was
the
fastest
possible
time
line.
So
this
is
interesting.
I
actually
started
in
January
2019.
So
so
you
started
looking
at
systems
to
talk
to
start
talking
to
administration
in
chem-20,
a
team
that
I
don't
think
they
started,
making
any
like
appointments
or
really
seriously
talking
to
people
until
October
November
and
then
made
the
decision.
D
E
E
A
little
more
detail
about
our
selection
process
first,
because
I
feel
like
that
was
really
one
of
the
most
important
pieces
for
us
pre-migration,
or
at
least
the
from
the
point
at
which
we
made
a
decision
through
the
day.
I
was
kind
of
all
blur.
Everything
went
really
really
quickly.
So
what
sticks
out
in
my
head
really?
Is
the
process
leading
up
to
selection
and.
E
Going
forward
so
just
to
give
you
some
background
again,
we
were
on
horizon,
and
that
was
the
ILS
that
we
were
using
and
we
had
it
locally
hosted
and
just
to
kind
of
give
you
an
idea
of
why
I
was
terrified
whenever
I
first
got
there.
Why
I
wanted
to
switch
ILS
is
immediately
was
because
it
was
looking
on
a
server
and
that
was
currently
running,
Microsoft
or
I'm.
Sorry,
Windows
2000.
It
was
on
a
class
black
and
we
were
running
into
issues
where
we
were
having
to
restart
the.
E
To
get
the
function
and
trying
to
get
reports
out
of
horizon
with
the
group
of
folks
who
haven't
like
really
had
the
time
to
dig
into
the
documentation
on
it
if
you've
ever
been
in
horizon
you'll
kind
of
know
what
I'm
talking
about
that
is
probably
the
least
user-friendly
iOS
I've
ever
seen
yeah
very
much
having
to
learn
a
whole
new
language.
Thank
you.
So.
D
E
So
that
kind
of
gives
you
a
little
bit
of
background
still
why
we
were
looking
to
so
we
did
go
and
look
at
the
obvious
options.
The
big
big
vendors
and
then
our
our
henna
preference
at
the
time
had
actually
mentioned
that
she
had
heard
from
the
Bywater
representative
a
year
before,
but
of
course
had
not
been
ready.
Don't
look
at
anyone
less
so
I
reached
out
to
that
person
and
got
them
in
the
mix.
E
So
we
evaluated
all
of
the
main
options
and
then
kind
of
narrowed
it
down
to
three,
and
we
were
looking
at
a
blue
cloud
overlay
with
30
and
as
kind
of
an
option
if
we're
going
to
stick
with
them.
We
looked
at
OCLC
dummy
on
us
because
we
had
just
recently
switched
over
it
into
process
for
I
ll,
so
we've
got
to
make
logical
sense
and
then
we
also
we're
looking
at
water.
E
We
did
some
site
visits
and
at
that
point,
after
the
site
visit
became
pretty
obvious
to
us
that
everybody
who
had
gone
actually
looked
at
east
systems
with
me
and
who
had
worked
specifically
in
the
iOS.
We
were
all
pretty
clear
on
one
thing
to
go:
it
seemed
the
most
user
friendly
as
well
as
easiest
for
us
to
make
the
transition
from
so
we
also
said
normally,
if
I
knew
Enterprise
when
we
discussed
some
kind
of
ideal
changes.
So
you
know
what
do
you
want
have
a
new
system?
What
is
it
that
it
currently.
D
E
Met
with
all
departments,
we
considered
additional
timely
changes,
like
say,
for
instance,
location
I,
didn't
type
changes.
These
are
things
that
hadn't
been
looked
at
new
years,
so
it's
always
good
to
kind
of
take
a
look
at
those
terminology.
Again,
you
know
our
students
know
what
the
sacs
mean.
So
do
we
need
to
look
at
changing
the
language,
so
other
things
that
we
did
that
were
preparation
for
migration,
we'd
switch
the
EDS,
and
luckily
we
had
kind
of
set
things
up
on
our
homepage,
so
that
you
really
have
a
dandy
to
get
to
the
ayahs.
D
E
E
It
was
not
easy
and
not
obvious,
so
we
decided
to
continue
to
kind
of
deal
with
that
that
setup.
While
we
do
the
transition
so
as
to
not
really
like
force
of
huge
change
on
work
agents
immediately
and
instead
we
targeted
our
most
active
patrons
and
made
sure
that
they
were
fully
aware
of
what
was
going
to
happen
and
what
changes
they
would
see.
And
then
we
also
sent.
E
D
E
E
So
we
definitely
had
some
minor
bumps
along
the
way.
Most
of
those
we
were
in
to
solving
that
first
week,
just
by
tweaking
singing
system
preferences
here
in
there,
I'm
just
system
doesn't
fight
behave.
The
way
I
expected
to
so
those
were
really
easy
changes.
One
thing
that
did
not
necessarily
go
well
that
kind
of
hit
a
selective
start
at
the
head
place
that
we
described
with
our
minds
were
not
right.
The
spreadsheet
that
we
used
to
export
at
a
head
prior
to
migration
had
such
high
body
knock
off
by.
E
E
So
sad
for
me
that
one
of
the
first
things
that
we
noticed
was
that
we
had
a
really
really
positive
reaction
from
our
major
patrons
and
our
student
workers
are
cheating.
Workers
were
thrilled
to
death,
to
be
off
of
price
picnic
and
also
to
be
on
a
web-based
system
that
meant
they
could
get
their
iPod
and
carry
it
around
the
library
to
do
all
sorts
of
things
that
we
usually
done.
As
far
as
inventories
concern.
So
talking
about
coming
out
steps
and
work
was
just
made.
Quite
a
few
people
got.
C
D
So
I
don't
know
about
because
it
haven't
my
experience
of
pre-migration.
It's
just
I
got
the
job
and
they
said
we're
doing
this,
but
there
I
know
there
was
a
selection
committee
formed
and
they
actually
ended
up
being
our
transition
committee
as
well,
and
so
I
got
them
over
representatives
from
each
of
the
departments
in
the
library,
with
the
hopes
that
they
were
disseminate
information
back
which
works
as
well
as
that
always
does.
When
you
form
a
committee
and
then
take
the
information
back.
D
One
thing
that
was
interesting
is
that
this
ILS
had
a
man''ôs
approval
from
all
of
the
library
staff,
which
I
didn't
think
was
possible
and
probably
won't
see
again.
The
structural
work
began
January
2019.
It
was
a
lot
of
identifying
issues,
so
they
had
been
on
the
millennium
system
since
2001
or
2006
I
can't
remember
but
Ohio,
and
before
that
they
were
just
on
whatever
it
was
prior
to
millennium.
So
a
lot
of
decisions
were
made
decades
ago
that
we
now
are
living
with
those.
D
One
of
the
most
maybe
unique
was
that
they
have
combined
all
of
the
item
and
collection
and
location
information
into
location,
which
is
that's
the
visa
needs
for
me,
and
so
getting
that
out
and
separating
that
out,
took
months
of
meetings
and
there's
things
like
that,
but
everybody
work
together
pretty
well.
The
department's
worked
with
us.
We
did
also
use
this
as
an
opportunity
to
create
policies
the
same
way
we
got.
D
We
made
a
major
change
so
that
our
faculty
and
staff
have
the
same
privileges
now
and
that's
something
that
probably
wouldn't
have
been
possible
without
just
disrupting
everything
as
far
as
getting
that
we
should
approve.
So
we
did
quite
a
bit
of
that
policy.
That's
the
water
hardest!
Long
I,
remember,
yeah,
still
working
on
cataloging
procedures.
D
That
is
one
thing
that
was
interesting
about
Colorado
College
is
because
it's
so
small
and
people
stay
there
for
so
long
that
they
have
basically
no
documentation
and
so
coming
in
as
a
new
person.
That's
both
terrifying
and
an
excellent
opportunity,
because
I
can
always
just
be
like.
Why
do
we
do
this?
This
doesn't
make
sense
to
me.
Explain
it
to
me
it's
a
and
they
can't
fall
back
on
documentation.
There
isn't
any.
So
there
were
a
lot
of
those
things
there
will
be
documentation
now
we're
starting
to
enter.
D
So
our
migration
was
extremely
quick.
This
part
part
of
it,
so
we
went
live
on
July
22nd
and
we
had
all
of
our
faculty
and
some
of
our
newer
students
on
campus
by
August
4th.
So
we
had
about
that
amount
of
time
to
get
through
all
the
problems
and
then
block
one.
So
the
start
of
our
semester
was
obvious
17
and
at
Colorado
College
you
get
I'm,
pretty
sure,
I
counted
it.
It's
nine
days
of
summer
between
the
end
of
the
last
summer
block
and
the
beginning
of
the
first
one.
D
So
we
try
to
jam
all
this
and
just
to
that
time
is
very
intense
one
of
the
things
that
really
helped
us
was
ending
acquisitions,
May
15th,
so
I
resisted
kinda
lots
of
time,
though
they
weren't
doing
any
rush
delivery,
and
then
we
stopped
cataloguing
processes
to
like
this.
So
those
two
departments
really
got
to
get
in
there
and
learn
the
system
and
do
the
work
in
a
way
that
other
departments
maybe
didn't
get
to
do
so.
I
thought
that
was
a
pretty
good
part
of
the
migration.
D
We
have.
What
worked
having
a
hosted
and
supported
solution
was
an
excellent
choice
for
our
very
diverse
City.
We
don't
have
the
staffing
there's
only
two
of
us
in
systems.
We
don't
have
the
ability
to
ensure
security
on
a
system,
there's
a
lot
of
things
that
we
can't
but
keep
us
from
self
hosting.
D
We
also
had
my
colleague
has
a
really
long
standing
relationship
with
IPS,
which
is
our
internal
or
our
university
college
party,
and
so
those
relationships
really
helped
because
we
knew
who
the
call
and
who
to
work
with
things
like
that.
We
also
have
excellent
communication
with
the
college
community
so
more
than
anywhere
else.
That
worked.
If
something
is
wrong,
the
professors
and
students
at
Colorado
College
will
tell
you
and
you'll
know
within
hours
and
that
I
think
that's
awesome,
sometimes
tiring
Barriss.
We
did
use
Basecamp
for
project
management.
D
I
use
this
primarily
for
two
do's
and
this
function,
and
not
only
to
tell
me
what
needs
to
be
done
as
Alyssa
do,
but
also
when
people
bring
a
complete
to
me
or
a
problem
or
something
they
want
me
to
look
at.
I
can
put
it
on
the
list.
They
have
this
list
and
they
can
see
that
at
some
point,
it'll
be
that
way
like
we've
done,
67
out
of
137.
D
If
these
post-launch
things
so
we
are
making
progress,
we're
still
holding
meetings
with
departments
on
an
ad
hoc
basis,
but
first
a
couple
months
we
held
meetings
of
the
departments
still
weekly,
so
that
helped
and
then
these
coha
open
labs
have
been
excellent,
where
we
just
set
up
a
time
where
in
computer
lab
and
people
can
come
to
us,
and
it
ends
up
being
problem
solving
that
is
collaborative
in
a
way
that
it
wouldn't
normally
be.
So
we
have
one
person
who
really
dug
into
serials
and
solved
a
lot
of
problems
so.
E
E
The
other
thing
that
I
would
like
to
note
is
just
that
kohai
in
general
and
I
mention
this
earlier
as
compared
to
other
that
we
had
looked
at
the
user
friendliness
of
the
system.
The
amount
of
time
that
we
got
out
of
the
training
for
student
workers
was
huge.
We
usually
spend
a
whole
day
doing
orientation
for
shooting
workers,
and
this
got
cut
down
to
a
half
day
for
us
just
to
get
them
trained
on
how
to
do
basic
search
functions
and
all
the
normal
basic
certified
student
work
with
you.
E
So
I,
so
what
didn't
work
well
or
is
not
yet
working
well,
so
that
both
my
supposed
to
be
serial
making
patterns
so
I'm
gonna
talk
about
that
just
for
a
minute,
because
that
was
probably
one
of
the
major
issues
that
we
ran
into
I'm,
not
a
serious
librarian
I've,
never
been
a
serious
librarian.
It
was
on
me.
You
set
up
the
prediction
patterns
and
do
the
first
prong
receiving
when
we
got
his
new
system
so
that
there
was
a
very
steep
learning
curve
for
me.
E
Having
said
that,
I
did
find
that
there's
I,
don't
again
have
my
background
in
this
is
hard
for
me
to
speak
as
compared
to
other
systems,
but
there
was
a
little
bit
of
flexibility
with
setting
up
the
prediction
patterns.
If
we
had
something
that
say,
we
got
10
issues
a
year
instead
of
12
year,
trying
to
get
that
set
up
on
the
right
in
there
hole,
that's
a
headache,
and
instead
what
we
kind
of
ended
up
settling
on
was
I
would
rather
have
it
notify
me
more
often.
E
Where
it's
a,
we
would
have
something
that
was
10
times
a
year.
I
was
knighted
after
12
times
a
year.
I
would
rather
get
notified
for
this
extra
two
times
than
not.
You
know
what
I
mean,
because
it's
easier
for
me
to
keep
track
in
my
head.
We
also
some
things
that
we
were
receiving
before
we
no
longer
received
and
then
said
just
like
basic
Holdings
notes,
like
hey,
we
have
to
last
300
notes
over
in
current
periodicals.
Instead
of
trying
to
receive
a
daily
newspaper
that
form
item.
E
D
It's
I
was
a
serious
librarian
way
and
they're
all
like
that.
For
us,
serials
protection
was
still
an
issue
by
the
person.
What
we
have
that's
in
charge
of
that
it's
like
a
preparation,
Rock,
sorry,
she
was
amazing,
and
so
she
had
everything
downloaded
it
in
spreadsheets
and
everything
about
a
timer
while
I.
So
it
actually
went
really
smoothly
because
she
put
a
ton
of
work
into
it.
D
And
so
these
are
our
major
issues,
the
first
one
that
many
people
that
internal
communication
wasn't
done
properly
again.
I
think
this
is
every
project
you
hear
this
and
every
project
I've
done,
maybe
I'm
just
bad
at
communication,
but
I
do
feel
like
because,
as
the
project
manager,
I
was
too
close
to
it.
Sometimes
I
thought
I'd
talk
to
people,
because
I
talked
about
something
for
three
weeks
straight
every
hour
of
my
day
and
so
I
assumed
it.
We
got
to
everyone
and
I
miss
it.
D
The
first
thing,
so
that's
something
I
think
we
could
have
used
better
use
of
Basecamp
for
this,
but
that's
yeah,
you're
working
on
it
communication
issues.
Sunday
has
integration
was
something
that
everybody
said
is
super
easy
right.
It's
only
super
easy
if
your
data
is
really
good,
so
we
found
out
that
our
data
was
not
really
good.
This
actually
I
can
tell
you
the
date
a
time
when
this
project
made
me
cry
and
it
was
caz
integration,
because
we
didn't
have
a
proper
match
point
and
getting
that
match.
D
Point
was
extremely
hard
with
the
data
that
we
had
and
a
lot
of
false
starts
and
thinking
we
had
it
solved,
and
people
actually
couldn't
log
into
our
system
for
the
first
two
weeks
that
it
was
up
so
yeah.
It
was
extremely
stressful,
but
once
we
got
our
data
to
where
it
needed
to
be
and
have
the
right
match
point
with
a
lot
of
support
from
a
lot
of
people,
you're
able
to
overcome
that
and
people
can
now
login
successfully.
D
D
The
take
home
here
is
probably
you
just
feel
a
little
bit
more
aggressive,
asking
questions
every
day
until
something
gets
all
I'm
at
labeling,
which
I've
done
a
little
bit
of
research,
and
it
also
is
kind
of
it's
just
hard.
E
E
D
D
Programs
to
handle
labor
within
it
and
it's
a
whole
thing
so
and
then
we
what
doesn't
work
yet.
Is
this
prospector?
That's
the
inReach
integration,
so
that
is
what
is
going
to
allow
us
to
join
the
Colorado
lines
of
research,
libraries
across
sectors
surface,
which
is
unmediated
aisle
within
the
state
of
Colorado,
and
it
works
really
well.
We
are
the
first
people
in
the
world
to
be
developing
this
API.
D
Well,
we're
not
they're
getting
the
developing
dollar
but
and
the
process
of
getting
the
agreements
is
taking
forever
we're
expecting
to
have
the
everything
signed
and
it
to
be
implemented.
January
2020,
that's
our
hope,
and
that
should
open
it
up
so
that
people
can
use
different
systems
like
there's
a
library
as
cu-boulder
is
now
like,
really
excited
about
the
API
being
used
in
any
way
because
they
can
then
connect
to
the
system.
We've
grown
almost
much
of
it,
but
it
gets
you
out
of
the
millennium.
D
D
A
B
B
B
B
B
B
A
C
B
All
right,
so
everybody
who's
suffered
through
this
long
and
we've
put
your
name,
everybody
didn't
have
their
name,
they
put
their
name
on
the
slip
of
paper
in
that
and
put
it
in
here.
So
here's
where
we
guys
we've
got
a
koha
us
2019
populace
a
Koba
us
2019
notebook
and
a
Koba
us
2017
lanyard
with
the
built-in.
B
D
B
A
B
B
B
C
A
B
Now
we're
on
to
the
round
tables
and
Lisette
has
was
it
Tomas
is
going
to
do,
is
going
to
participate
and
beat
the
round
table
about
api's,
that's
going
to
be
in
the
other
room,
so
anybody
that's
interested,
maybe
I
should
follow.
Was
that
over
the
other
room
and
they're
going
to
do
that
there
and
then
we've
got
reports.
B
Jason
and
I
were
going
to
work
on
leading
that
round
table
and
Jason
punches
hand
up.
Anyone
wants
to
talk
about
reports
head
over
where
Jason
is
and
then
user
interface
was
that
enter
or
Lucas
Lucas.
So
anybody
who
wants
to
talk
about
user
interface
over
and
over
and
hang
out
with
Lucas
and
we're
not
we're
not
doing
this
one
on
video,
so
you're
not
being
recorded,
feel
free.