►
From YouTube: Koha Documentation Webinar
Description
Watch as the education committee members discuss how to add information to the Koha Community Manual!
A
Oh
hi
everyone,
my
name
is
Jessie
Zahra
and
I'm.
The
education
chair
for
kohai
us
and
I
also
work
at
buy
water
solutions.
As
the
marketing
and
outreach
coordinator,
we
are
doing
a
series
of
continuing
education
for
kohai
us
as
part
of
the
education
committees
role.
Here,
we've
done
a
few
in
the
past
basics.
On
SQL
some
we
have
a
jQuery
class
coming
up
next
week
and
we're
going
to
continue
to
roll
those
out.
As
as
we
move
forward
this
summer,
please
feel
free
to
use
the
chat
box
to
ask
questions.
A
If
you
have
a
microphone
I'm
totally.
Okay
with
you
asking
questions
as
we
go
along,
we
are
recording
this
session,
so
you'll
be
able
to
go
back
and
you
know
watch
certain
sessions
as
we
walk
through
I
am
gonna,
be
very
hands-on,
so
we'll
go
through
the
whole
process
of
where
the
documentation
you
know
instructions
are
the
wiki.
What
the
community
uses
to
keep
track
of
places
where
we
need
to
see
changes
as
well
as
what
the
documentation
team
uses
to
keep
track
of
new
release
information.
A
So
we'll
go
out
and
go
through
that
whole
process,
then
we'll
go
into
get
lab
and
we'll
actually
go
through
and
edit
and
update
the
manual
I'm
gonna.
Keep
it
very
basic
today,
so
we'll
just
make
edits
to
the
the
document
itself
and
then
we'll
push
those
through
and
get
and
and
then
we'll.
You
know,
leave
some
time
up
and
for
Q&A
and
I
figure.
A
We
could
go
a
couple
weeks
and
maybe
you
let
everybody
get
their
feet
wet
and
then
maybe
we'll
do
like
an
advanced
documentation
and
the
next
month
or
so,
and
we
could
all
meet
back
again.
If
you
have
questions
and
maybe
go
through
like
adding
images
as
well.
So
let's
jump
right
in
so
good
morning.
Everyone
and
thanks
for
joining
us.
A
So
today,
I'm
gonna
talk
to
you
a
little
bit
about
Quahog
documentation.
So
for
those
of
you
that
have
been
in
the
Quahog
community
for
many
years,
you're
well
versed
with
how
amazing
the
Quahog
Manual
is.
There
is
a
documentation
team
in
the
community,
that
is,
that
volunteers,
every
release,
and
so
those
individuals
help
steer
the
new
release,
information
that
comes
out
so
with
each
release.
You
know,
there's
updates
to
the
manual
for
new
enhancements.
A
Any
type
of
bug
fixes
anything,
that's
essentially
new
in
the
system
and
then,
of
course,
there's
always
maintenance
to
the
manual
where
librarians
can
share
information
about
specific
workflows.
They
have
or
things
that
would
make
it
easier,
and
so
that's
why
it's
so
important
for
not
only
users
to
you
know,
give
feedback
form
the
manual,
but
it's
really
important
for
individuals
to
share
information
about
workflows,
and
this
is
where
people
you
know
will
come
in
and
kind
of
see
what
other
libraries
are
doing.
So
I'll
talk
a
little
bit
about
that
as
well.
A
So,
let's
jump
right
in
so
you're.
Probably
thinking
like
where
do
I
start
I
really
want
to
get
involved.
What
are
the
first
steps
that
I
need
to
take
so
think
about
documentation
that
you
have
have
you
created
anything
for
your
frontline
staff?
I
remember:
I
started
out
as
an
educator
here
at
Bywater
solutions
and
I
still
do
trainings
and
a
lot
of
my
libraries
would
create
internal
documentation,
whether
it
was
for
frontline
staff.
Folks
in
the
back,
you
know
that
would
make
it
easier
for
them.
That
is
great
information
that
you
can
start
with.
A
If
you
want
to
share
that
information
with
the
community,
we'll
go
into
the
manual
and
I'll
kind
of
talk
about
that
in
a
little
bit,
but
think
about
some
of
the
documentation
that
you've
created
internally,
you
know
for
libraries
that
are
coming
in
to
Quahog
to
see
that
information.
It
would
be
extremely
Val
for
those
libraries,
you
know
giving
them
a
good
start,
so
think
about
anything
that
you've
created
for
frontline
staff.
You
know
easy
circulation,
you
know
start
to
finish.
Changing
things
to
lost.
A
You
know
anything
like
that
would
be
a
good
start,
technical
information
so
part
of
that
implementation.
Go
back
to
your
migration
and
think
about
you
know
what
things
were.
You
know
what
things
made
it
easy
for
you
to
get
started
any
workflows,
I,
always
think
about
acquisitions.
The
were
cataloging.
A
You
know
the
interfaces
in
Quahog
when
a
user
is
first
starting
or
maybe
they're
new
they've
been
a
librarian
for
a
long
time,
but
you
know
they've
only
had
experience
with,
let's
say:
Searcy
dynex
or
you
know,
tribal
I
or
fall
at
you
know
coming
in
and
starting
with
that,
cataloging
module
could
be
a
little
bit
different
for
them.
So
any
type
of
you
know,
workflow
information
that
you
have
would
be
great.
I
just
received
an
email
yesterday
from
a
librarian
who
she
said:
we've
you
know
we
just
hired
a
new
cataloging
librarian.
A
Do
you
have
any
basic?
You
know
videos
or
tutorials
on
just
you
know,
regular
cataloging.
You
know
using
the
Z
3950
server,
bringing
that
information
in
editing
the
record,
adding
a
new
item
so
I
always
think
about
like
workflows
that
are
great
for
your
library,
that's
the
kind
of
stuff
you
want
to
see
in
that
in
that
documentation
and
then,
of
course,
like
cheat
sheets
I'm,
gonna,
I'm
gonna
call
out
two
of
our
team
members
here
that
are
on
both
Jason
Robb
and
Lizette.
A
They
have
created
some
great
cheat
sheets
that
are
available
on
the
kohai.
Us
website-
and
you
know
think
about
those
cheat
sheets
that
you
may
have
created
if
documentation
lives
there,
that
you
think
would
be
beneficial
for
other
community
members
to
see.
Those
are
the
kind
of
things
you
want
to
want
to
share.
A
Okay,
the
Koha
community,
so
the
how-to
documentation
really
lives
all
on
the
wiki.
There
are
some
great
pages
on
there
about
on
how
to
begin
the
editing
process,
creating
a
gitlab
account
and
really
going
in
there.
So
you
can
feel
comfortable
to
edit
the
system
if
the
documentation
has
really
become
easier
over
the
years
for
folks
that
have
been
with
Koha
for
a
long
time.
A
Nicole
was
the
documentation
manager
for
a
long
time,
and
she
maintained
that
and
after
she
transitioned
on
to
a
new
wall,
the
documentation
team
grew
to
multiple
people
that
started
editing
the
manual
and
their
goal
has
really
been
to
make
it
as
easy
as
possible
or
they
go
in
and
make
those
edits.
So
we'll
go
through
that
process.
A
Bugzilla.
A
lot
of
you
are
familiar
with
Bugzilla.
You
know
if
you're
going
to
look,
for
you
know
errors
that
you're
finding
in
the
system
or
any
type
of
enhancements
that
are
coming
out.
The
koha
documentation
team
also
uses
Bugzilla
to
look
for
sections
in
the
manual
that
need
to
be
updated.
So
like
existing
things,
where
there's
maybe
a
missing
section
in
the
manual.
If
there's
a
system
preference,
that's
not
updated.
If
there's
a
you
know
something
may
be
in
circulation,
that's
not
listed
clearly,
that's
where
anyone
can
go
in
essentially
submit
a
bug.
A
You
know
and
keep
track
of,
that.
The
koha
documentation
team
uses
Tegea
to
keep
track
of
new
release
notes.
So
anything
that's
coming
out
in
the
next
release
right
now
we're
preparing
for
the
2005
release,
which
should
be
out
in
the
next
week
or
so,
and
that's
where
the
documentation
team
keeps
track
of
all
that
information.
A
Okay,
if
you
are
interested
in
providing
feedback
or
really
getting
involved
with
the
documentation
committee,
the
next
community
meeting
is
on
June
4th.
The
meetings
take
place
in
the
IRC
channel
and
on
the
wiki
there's
an
agenda
with
more
information
about
what
we'll
discuss
at
that
next
meeting.
So,
like
any
type
of
updates,
we
usually
look
at
the
tasks
that
are
listed
in
both
Bugzilla
and
Tegea
to
see
what
we
can
tackle
and
then,
of
course,
coming
up
with
ideas.
A
All
right,
so
my
next
step
is:
let's:
let's
explore
I'll
walk
you
through
the
whole
process
of
adding
documentation
to
the
manual
and
also
I,
do
have
a
list
of
all
the
resources.
So
this
is
these
are
all
the
links
I'm
about
to
show
you.
This
slide
will
be
on
the
kohai
u.s.
website
and
I'll,
send
it
out
to
a
list
of
our
on
the
kohai
u.s.
listserv
too.
A
So
for
those
of
you
that
may
want
to
share
it
with
your
staff
members,
okay,
so
the
first
thing
I
want
to
talk
about
is
on
the
coha.
Wiki
and
I'll
put
this
in
the
chat
box
too.
So
if
anyone
wants
to
follow
along
with
me,
you
can
so
this
page
real
the
outlines
getting
started
with
the
whole
process
of
editing
the
manual
you'll
see
here,
there's
a
the
first
section
is
really
like
new
writers
start
here.
A
A
There
is
an
extensive
to-do
list
in
Bugzilla
which
will
hit
next.
So
you
can
see
like
where
there's
information
that
we
actually
need
in
the
manual
today
I'm
gonna
focus
my
documentation
on
elasticsearch.
There's
elasticsearch
is
pretty
new
to
Koha
the
last
two
or
three
releases.
People
have
been
more
and
more
enabling
elastic
in
their
site,
so
we
have
some
really
good
documentation.
Now
that
we
can
add
to
the
manual
so
as
more
individuals
start
enabling
it
they
can
see
it.
A
So
we're
going
to
use
that
today
and
as
we
scroll
down
a
little
bit
further
in
the
wiki,
it
actually
really
walks
you
through
this
and
I'll.
Tell
you
I
always
keep
this
open
in
another
tab,
even
when
I'm
going
through,
because
they're
pretty
specific
about
how
they
want
you
to
essentially
when
you're,
making
a
change
in
the
document
they'd
like
us
to.
Essentially
you
know
when
we're
creating
it
make
a
message,
so
they
know
exactly
what
we're
changing
so,
whether
it's
you
know
something
in
administration
and
serials.
A
You
know
also
a
comment
as
to
why
we're
making
the
change.
So
you
know
maybe
an
introduction
of
a
new
system
preference.
It
may
be
adding
a
image
to
an
existing
workflow.
That's
in
there,
it's
just
easier
for
those
that
are
essentially
making
the
merges
into
the
master
document,
so
they
can
easily
find
what
they're
looking
for
in
the
manual.
A
So
you
know
giving
as
much
information
as
possible
and
of
course
we
do
that
as
librarians
already
so
this
is
a
great
page
to
like
keep
open
when
you're,
when
you're,
going
through
and
again
I'm,
not
gonna,
hit
adding
screenshots.
Today
we'll
do
that,
like
maybe
in
our
next
webinar,
when
we're
a
little
more
advanced
but
we'll
go
through
this.
It
shows
you
how
to
add
screenshots.
They
even
have
like
step-by-step
instructions
in
here
with
screenshots
and
and
how
to
do
that
process.
So
this
is
a
really
good,
a
really
good
place
to
start.
A
The
next
thing
I
want
to
show
you
is
in
Tegea
now
this
is
again.
This
is
another
place
where
we
keep
track
of
essentially
the
new
release
or
the
next
release.
That's
coming
out
and
information
in
there,
so
you
can
see
David
named
and
Caroline
are
both
two
active
members
of
the
quahog
documentation.
Team
I.
Think
Caroline
is
the
current
chair
of
the
co-head
documentation
committee,
but
this
is
a
great
place
where
you
can
see
anything
that's
coming
out
in
the
new
release
and
where
things
need
to
be
added.
A
The
next
thing
we'll
take
a
look
at
is
bugzilla
and
if
you
joined
us
for
the
virtual
hackfest,
the
first
part
of
our
virtual
hackfest,
we
really
focused
on
like
searching
in
Bugzilla,
to
look
through
for
information
to
see
like
what
needs
documentation
when
you're
looking
for
bugs
or
you're
performing
a
search
in
the
system,
you
can
actually
search
by
keywords
than
by
component.
So
there
is
a
component
for
documentation
which
allows
you
to
just
search
for
things
that
have
been.
A
A
You
can
take
a
look
at
that
now.
You
can
perform
this
search
from
scratch
as
well.
So
if
we
go
into
search,
you
can
do
an
advanced
search
and
kind
of
narrow
it
down,
but
here's
a
good
place
to
start.
So
if
you're
like,
where
do
I
even
start
with,
you
know
adding
things
you
can
take
a
look
here
and
see,
what's
you
know
missing
or
what
needs
to
be
explained
in
a
little
more
depth,
you
know
or
if,
like
a
system,
preference
is
missing.
A
This
is
a
really
nice
place
to
start
so
again,
today,
I'm
gonna
focus
on
the
elasticsearch
part
of
the
manual.
So
this
was
a
book
that
that
I
I
filed
a
little
bit
ago.
Just
mentioning
that
we
need
to
add
some
documentation
about
elasticsearch
in
the
manual
and
also
in
administration
for
a
search
engine
configuration.
So
this
is
a
great
place
to
start.
If
you're,
not
sure,
you
know
what
you
need
to
do
and
you're
looking
to
get
your
feet
wet.
This
is
a
perfect
spot.
It's
you
can
kind
of
just
scroll
through
and
see.
A
You
know
what
information
is
in
there
like
for
those
of
you
who
may
work
in
acquisitions
all
the
time.
You
know
it
says
that
we
need
some
manual
screenshots
and
description
in
acquisition
order,
lists
in
a
basket.
They're
saying
that
you
know
this
one
is
outdated.
So
you
know
this
is
a
good
place
to
kind
of
check
and
see
if
there's
something
in
your
area,
that
you
work
in
your
library
that
needs
to
be
essentially
updated.
A
I'm
gonna
jump
over
to
the
manual
really
quick
here,
because
I
do
want
to
talk
a
little
bit
about
this,
so
I'm
gonna
start
just
at
the
Quahog
community
page
now,
you're
probably
accessing
the
manual
from
maybe
your
staff
client.
Maybe
you
do
have
it
bookmarked
on
your
browser,
but
if
you're
starting
from
scratch,
you
can
come
to
the
Quahog
community
page
and
click
right
on
documentation
that
will
take
you
into
the
current
or
the
stable
version
of
the
manual.
So
you'll
see
here
right
now
we're
we
have
the
1911
manual
up
front.
A
I'm
gonna
jump
into
the
HTML
version
and
just
talked
a
little
bit
about
how
the
manual
is
set
up
for
those
of
you
again
who
have
been
on
Koha
for
a
while
prior
to
I,
don't
know
I
say
it
was
maybe
about
three
years
ago.
I
think
that
the
the
documentation
changed
format.
This
new
format
is
really
nice,
because
you
can
know
you
have
a
quick
search
bar
over
there
on
the
left
hand,
side
prior
to
that,
you
had
to
do
like
a
either
a
controller
or
command
F
to
find
something
on
the
page.
A
But
this
is
really
a
nice,
a
nice.
You
know
starting
spot
where
you
can
come
in
and
search
for
something
in
the
manual.
So
again,
I'll
use
my
elastic
as
an
example.
If
I
do
a
search,
it'll
bring
back
any
hits
that
it
finds.
So
in
this
case,
it's
telling
me
one
is
in
the
global
system:
preference
where
you
can
set
your
search
engine
options
to
either
a
zebra
or
elastic,
and
then,
of
course
the
other
one
is
in
administration
where
we
actually
start
talking
about
the
search
engine
configuration.
A
So
you
know
if
you're,
if
you
want
to
see
what's
existing
in
there,
this
is
usually
what
I
do.
I
usually
come
in
and
I
take
a
look
at
the
manual
first,
because
it's
it's
a
little
easier
to
read
it
here.
You
know
see
what
screenshots
are
in
the
system
and
then
go
into
into
get
lab.
Now
you
do
have
a
table
of
contents
over
here
on
the
left
hand
side,
so
you
know
once
you're
dropped
into
your
specific
destination.
It
may
be
short.
It
may
be
a
little
long.
A
In
this
case,
administration
is
huge,
of
course,
so
I
can
see
right
over
here.
On
the
left
hand,
side
that
search
engine
configuration
so
I'm
going
to
jump
on
that,
and
then
that
takes
me
right
into
this
section.
So,
basically
right
now,
there's
just
a
brief
introduction
of
that
search
engine
configuration
here
in
the
in
the
system.
So
what
we're
gonna
do
today
is
we're
gonna,
go
into
get
lab
and
we're
going
to
make
some
edits
and
add
a
little
more
information
to
that
search.
Engine
configuration
I.
A
Just
see
we
have
a
chat.
David
also
made
a
comment
that
in
Bugzilla
there
is
also
a
link
on
the
footer
of
the
homepage,
where
you
can
link
out
to
see
the
documentation
open
issues.
So,
let's
we'll
jump
back
to
the
home
page
Oh
down
here
and
you
can
see
right
here,
documentation
listed
so
yeah,
there's,
there's
great
places
where
you
can
can
take
a
look
at
that
information
and
Before.
A
A
Okay,
so
now
we're
going
to
jump
into
get
lab
and
again,
if
you're,
following
along
with
me
and
you're
on
that
editing
the
koha
manual.
Remember,
if
you
don't
have
a
gap
web
account,
you'll
want
to
come
in
and
create
one
first,
and
there
is
a
link
to
we
in
here.
So
you
can
register
and
then
you'll
once
you
do
register
and
create
an
account.
Then
you'll
want
to
go
directly
to
that
Koha
manual,
project
and
and
click
fork.
A
Now,
I've
already
done
those
those
processes,
I've
had
an
account
for
a
few
years,
so
you'll
want
to
you'll
want
to
walk
through
that
process.
So
once
I
get
into
the
koha
manual
you'll
notice
over
here,
on
the
left
hand,
side
I
I,
have
a
link
that
tells
me
I
am
in
the
koha
manual.
I
can
also
look
up
top,
which
tells
me
again
my
profile
is
my
Jessica's
arrow,
the
koha
manual,
and
then
I
can
come
in
and
start
looking
for
that
information.
A
Now
the
Koha
manual,
once
you
get
in
there,
you're
going
to
look
for
the
folder
called
source.
That's
going
to
have
the
breakdown
of
all
the
information
for
each
section
in
the
manual,
so
you'll
see
that
folder
for
images
and
as
I
scroll
through
you
can
see
some
of
those
sections
of
the
manual,
so
acquisitions
administration,
cataloging
circulation
and
so
on.
So
again,
today,
I'm
going
to
focus
on
administration
and
we're
going
to
update
the
section
in
the
manual
for
elasticsearch.
A
So
once
I
select
that
administration,
it
will
take
me
into
of
you
the
manual
where
I
can
actually
see.
I
always
say
this
is
like
a
read,
friendly
view.
So
before
we
get
into
the
markup
where
we're
gonna
edit
it,
you
can
quickly
take
a
look
to
make
sure
you're
in
the
right
location.
So
this
is
me
these
are
just
some
like
helpful
hints.
A
For
me,
what
I
usually
do
is
I
keep
the
manual
open
in
another
tab
or
another
window,
so
I
can
just
make
sure
that
I'm
in
the
right
section
of
the
manual
so
again
I'm
starting
in
administration
and
of
course,
the
first
thing
there
is
gonna,
be
basic
parameters
just
like
it
is
in
your
staff
client.
So
that's
just
a
helpful
tip
tip
for
me.
You
know
to
make
sure
I'm
in
the
right
location
so
as
I
scroll
through
you're
gonna
want
to
make
sure
that
you're
editing
the
right
location.
A
A
So
I
want
to
give
a
shout
out
to
David
because
he
helped
me
get
transitioned
back
into
editing
the
manual
because
I
hadn't
done
it
in
so
long.
So
to
all
my
listeners
out
there
don't
get
nervous.
If
you
need
help,
you
know
jump
into
IRC
or,
of
course,
to
buy
water
slack
if
you're
one
of
our
partners
and
in
IRC
you
can
actually
come
in
here
and
jump
into
the
coho
channel
and
ask
questions.
Everyone
is
always
willing
to
help
so
Caroline
who's.
A
The
current
chair,
her
handle
is
Caroline
and
David
is
also
on
the
call
and
he's
a
great
resource
to
start
with
I
think
he's
diamond
so
again,
just
a
great
place
to
start.
If
you
get,
you
know,
if
you
get
stuck,
you
can
come
in
and
ask
a
question.
Oh
look,
I
see
David
just
popped
in
there,
so
David
nint.
So
you
know
this
is
a
great
way
Lizette.
Thank
you,
hello
from
the
documentation
webinar.
You
know
this
is
a
great
place
to
come
in
and
ask
for
help.
Don't
be
shy.
A
I
ask
for
help
all
the
time,
even
all
of
our
educators.
We
all
do.
We
were
just
talking
about
talking
with
Carolyn
this
morning
to
ask
her
some
questions,
so
you
know
don't
hesitate
to
ask
for
her.
The
Quahog
community
is
always
willing
to
help
you
so
again
now
what
I'm
gonna
do
is
I'm
gonna,
scroll
down
and
I'm
gonna.
Look
for
that
elasticsearch
for
me,
I'm
going
to
do
that!
I
always
do
a
ctrl
F,
because
I
want
to
make
sure
I'm
in
the
right
location.
A
So
this
jumps
me
exactly
down
to
my
line,
so
I'm
gonna
hover
with
my
cursor
over
here
and
let's
talk
a
little
bit
about
the
formatting
in
here
so
depending
on
what
you're
editing
in
the
manual,
if
you're,
making
a
new
section
like
if
something
was
added,
there's
very
specific
instructions
that
you
want
to
follow
for
what
you're
adding
in
there
and
I'm
gonna
pull
up
just
another
page.
Here
there
is
a
page
on
the
manual.
That's
called
get
guide
for
documentation
and
I'm
gonna,
pull
that
over
real
quick.
A
This
will
actually
walk
you
through
essentially
some
setup
in
the
system.
So
like
again,
if
you're
fixing
a
mistake
or
changes
in
the
manual
there's
some
documentation
here
on
what
you
need
to
do,
you
know
capitalizations
where
things
need
to
be
capitalized
in
there.
You
know
examples
of
what
you're
changing
to
the
manual.
A
This
essentially
is
telling
us
like
what
the
header
is
or
what
the
heading
is
for
that
breaking
the
page,
so
like
the
search
engine
configuration
and
then
a
break
to
the
acquisitions
module.
So
if
we
go
back
over
here
and
actually
look
at
it
in
the
manual
you'll
kind
of
understand
what
it
does
again,
this
is
super
helpful
for
me
to
look
back
and
forth,
so
you
can
kind
of
understand
and
what
the
structure
is
in
the
manual.
A
So
here
you
can
see
that
you
know
search
engine
configuration
and
then
it
jumps
into
acquisitions
and
then
currencies
and
exchange
rates.
So
now,
when
we're
looking
at
it
here,
you
can
see
that
so
that's
kind
of
where
that
break
is
the
search
engine,
configuration
acquisitions
and
them
that
currency
and
exchange
rates.
So
you
can
kind
of
understand.
You
know
how
how
it
breaks
down
the
next
thing.
You'll
see
here
is
the
essentially
the
heading
so
again,
there's
that
search
engine
and
then
the
brief
description
of
that
information.
A
I'll,
give
you
another
helpful,
tip,
I,
usually
start
or
have
a
separate,
like
text
editor
open.
So
if
you're
worried
about
like
punctuation
or
you
want
to
read
it
over
or
checking
your
spelling,
I
usually
type
it
over
in
another
like
text
window
or
a
Google,
Doc
I
usually
use
a
Google
Doc,
and
that
way
you
can
copy
and
paste
it.
And
you
know
if
you're
working
on
something
and
you
don't
finish
it
right
away
or
you
know
the
phone
rings
or
somebody
comes
up.
A
You
know
and
asks
you
a
question
if
you're
back
in
the
library,
you
know
that
way,
you're
at
a
good
point
where
you
can.
Essentially
you
know,
keep
that
information
in
your
Google
Doc
and
keep
editing
it
and
then
come
back
to
get
lab
and
do
it.
So
this
is,
you
know
these
are
just
helpful
tips.
You
know
that
have
helped
me
that
way.
If
you
come
back,
you
know
it's
an
easy
way
to
find
it.
So
now,
I'm
gonna,
I'm
gonna,
come
over
here
again
and
I'm.
A
Just
gonna
hit
that
hard
return
and
I'm
gonna
add
a
little
information
in
about.
Essentially,
you
know
setting
up
that
search
engine
configuration
so
just
context
into
what
we're
doing
here.
I
see
a
few
people
on
here
who
already
are
on
elasticsearch
elasticsearch
is
replacing
or
a
new
option
for
the
zebra
indexer.
A
So
in
administration
you
can
first
in
your
system
preference
once
you
enable
elasticsearch
when
you
enable
it,
it
will
populate
a
new
section
in
administration
called
search
engine
configuration
and
that
allows
you
to
go
in
and
essentially
set
up
the
mapping
for
relevancy
within
that
within
your
elasticsearch.
And
what
I'll
do
is
I'll
just
open
this
up,
so
you
can
see
what
I'm
explaining.
A
So
it's
not
such
a
thinking
about
it
for
those
of
you
who
aren't
on
elastic
yet
so
again,
so
I'm
in
administer
and
when
I
come
down
to
under
it
right
under
cataloging
you'll,
see,
there's
a
new
link
here
and
that
search
engine
configuration
when
I
click
on
that
link.
It
then
takes
me
into
a
new
screen
where
I
can
see
some
of
my
mapping
or
search
fields
and
additional
information
like
bibliographic
records
and
authorities.
A
A
A
Now
these
I
actually
have
a
few
tips
to
share
with
you
too,
for
this,
because
David
actually
shared
these
with
me,
you'll
notice,
I
have
some
contractions
in
here,
like
your
instead
of
you
are
and
David
shared
that
it's
good
to
keep
things
very
straight
forward,
because
it's
easier
for
translation
when
I'm
moving
forward.
So
if
you
have
something
like
don't
or
aren't-
or
you
are
try
and
change
that
in
so
it's
easier
for
translation
for
the
rest
of
the
community
out
there
if
they're
translating
this.
A
So
what
I've
done
is
now
I've
gone
in
and
I've
added,
like
the
tabs
that
are
labeled,
that
they
see
once
they
click
on
that
search
engine
configuration
and
they
can
see.
You
know
that
information
in
here
and
then
just
a
little
more
information
about
you
know
what
they'll
see
when
they
get
in
there.
So
I'm
just
gonna
edit.
Some.
A
And
just
so,
it
explains
it
so
usually
when
we're
trying
to
enter
in
information,
try
and
make
it,
as
you
know,
clear,
as
possible
to
the
end-user.
You
know
what
they'll
see
on
that
page,
anything
where
they
need
to
either
click
a
drop
down
menu
or
maybe
enter
in
a
value
or,
for
example,
like
if
there's
a
place
where
maybe
you're
talking
about
collection
codes.
You
know
you
can
say:
collection
codes
can
be
edited
in
authorized
values.
A
You
know
think
about
ways
that
you're
teaching
individuals,
you
know
where
they
can
find
things
in
the
cohosh
system.
You
know
this
is
always
a
really
good
way
to
help
them.
Learn
the
system
and
really
you
know,
get
that
information
out
there
Heather
just
asked:
is
there
a
style,
guide
or
somewhere?
That
tells
us
if
it's
UK
or
us
Spelling's
are
preferred
Heather?
Yes,
there's
actually
we'll
see
how
who
quickly
gets
it
in
there?
There
is
one
that
has
a
glossary,
so
let
me
see
I
think
I
changed
it
somewhere.
Let
me
make
two
seconds.
A
Here
we
go
so
it's
called
terminology,
and
this
I'll
put
this
link
here
in
the
the
channel
in
the
chat
here
we
go
actually
David
shared
me
share
this
one
with
me
too.
This
is
a
good
place
where
you
can
see
like
where
it
talks
about,
and
this
was
the
first
one,
because
sometimes
people
do
say
Authority
record
and
and
not
Authority,
and
actually,
if
you
go
down
a
little
bit
like
authorized
it
with
the
Z
versus
authorized
with
an
S.
So
you
know
this
is
a
great
place
also
to
have
this
open
or
bookmarked.
A
So
you
know
what
to
use
like
bibliographic
record,
not
Biblio,
and
things
like
that.
So
yes,
this
is
a
great
place
also
to
keep
bookmark
to
you
know
to
see
what
what
it
is.
I'm
I
will
tell
you
I'm
always
you
know
this.
This
one
is
always
like
check
in
or
check
in
without
a
hyphen.
You
know.
So
these
are
things
and
if
you
forget,
don't
worry,
you
know
like
it'll
get
double-checked
but
like
this
is
a
good
thing
to
bookmark
that
you
can.
A
You
know
take
a
look
at
to
see
how
to
talk
about
it.
For
example,
hold
you
know
using
hold
and
not
reserve
a
request.
This
is
a
great
place
to
show,
because
you
know
at
times
it
does
get
confusing
like
I
always
think
issue
is,
is
totally
confusing
because
you
have
the
issues
table
and
then
you
also
have
you
know
serial
issues.
So
you
know
this
is
a
good
place
to
kind
of
check
to
make
sure
you're
using
the
right
terminology
when
you're
when
you're
updating
the
manual.
So
you
know
thanks
Heather,
for
asking
that.
A
A
A
So
once
you've
added
in
you
know
some
of
your
information
and
you
feel
like
you're
at
a
good
spot.
The
thing
you're
going
to
do
next
is
we're
gonna
scroll
down
a
little
bit
to
the
bottom,
and
this
is
where
you're
going
to
see
a
box
for
commit
message
and
essentially
you're
your
target
branch.
So
within
one
of
the
the
tabs
here
your
that
I
showed
you
earlier.
There
was
one
for.
A
Let
me
pull
it
over
my
get
guide
and
this
actually
shows
you
what
you
want
to
put
in
those
messages.
So
if
you
are
in
Bugzilla
and
there's
a
Bugzilla
number
that
you're
updating
or
Tegea
number,
you
want
to
enter
that
information
in
and
then
a
short
title.
So
in
my
case
I
think
I
have.
I
still
have
that
book.
Zillah
open,
I'm
going
to
go
back.
One
screen-
and
I
know
I
had
one
in
here
for
elastic.
A
So
I
could
enter
in.
You
know
this
particular
bug
within
within
the
system.
So
I
can
add
in
that.
If
I
follow
the
get
guide
here,
you
also
see
a
little
information
about
what
else
we
want
to
put
in.
Just
like
a
very
short
title.
So
I
can
say
you
know
adding
more
description
to
the
elasticsearch
configuration.
A
So
you
know
just
mentions-
maybe
it's
just
a
short
paragraph
describing
it
and
why
that
particular
information
was
was
made
to
to
the
manual.
So
I
updated
a
little
bit
of
the
mapping
information
once
the
user
gets
into
that
search
engine
configuration
down
at
the
bottom.
The
next
thing
we're
gonna
do
is
hit
that
commit
changes
and-
and
that
will
take
us
to
our
next
screen,
where
you'll
get
a
little
message
saying
that
your
changes
have
been
successfully
committed.
A
A
You
know
high
five,
everyone
out
who
there,
who
might
be
following
Oh,
both
David
and
and
Caroline,
made
comments.
So
if
you're
using
the
web
version,
you
can
make
several
changes
under
the
same
commits.
So
you
know
if
we
also
wanted
to
update
something
else
in
administration.
We
could
do
that
and
mention
it
in
the
commit
message
and
Caroline
mentioned
that
there
are
a
couple
people
that
have
access
to
the
pushing
them
through.
So
you
know,
that's
really
great.
You
can
do
that
multiple
times.
You
know
everyone
spread
out
all
over
the
world.
A
So
when
you
get
that
in
usually
it's
really
really
quick.
I
usually
see
a
quick
turnaround
with
the
day
or
two
that
that
information
has
gotten
in.
So
you
know
now
that
I've
done
this
I
can
wait
until
we
see
that
push
come
through,
we'll
see
what
it
looks
like
and
then
we
can.
You
know,
start
looking
for
our
next
piece
of
information
to
start
updating
that
information.
A
Oh
John
asked
did
I
see
correctly,
that
you
were
adding
hard
returns
to
longer
lines.
I
usually
do
there's
a
when
you're
editing,
something
there
is
an
option
up
top
that
does
a
soft
wrap
and
maybe
Caroline
or
David.
If
you
have
a
better
a
better
option,
I
just
like
to
see
what
it
looks
right
away.
I
know
if
you
don't
do
a
hard
return
at
all
I
think
it's
okay
in
the
manual
but
I
like
to
see
what
I'm
writing
right
away
so
I.
A
Okay,
Heather
asks
if
we
have
ideas
about
expanding
and
improving
sections
where's
the
best
place
to
float
those
ideas
or
feedback,
yeah
IRC
or
the
Kohala
serve
Heather
or
if
you
can
make
you
know
the
next
documentation
meeting
it's
in
the
IRC
Channel
on
on
June
4th
I
think
that's
a
that's
a
great
one!
Yeah
and
both
David
and
Caroline
just
said
the
documentation
list
or
if
you
have
a
question
or
something
isn't
clear,
definitely
jump
on
the
IRC
meeting
or
the
or
the
mailing
list.
D
A
John
has
a
question:
is
it
necessary
to
push
or
pull
content
through
SSH
and,
if
so,
should
we
use
RSA
or
8255
one
nine?
That's
a
great
question
and
I'm
gonna
defer
to
either
Caroline
or
David
I
I
not
pushing
or
pulling
through
SSH,
but
yeah
David
says
we'll
take
contributions
in
other
formats.
Yeah.
A
E
C
C
A
A
A
A
A
Well,
I
want
to
thank
everyone
who
joined
us
today
for
coming
to
the
Quahog
documentation,
I
hope
it
was
helpful
and
that
you
can,
you
know,
get
in
there
and
start
trying
things
out
and
Carolyn
said:
don't
worry
about
making
errors,
we're
all
learning
together
and
that's
the
absolute
truth.
I
I
did
one
yesterday
and
David
was
super
helpful
to
help
me
like
make
some
changes
to
things,
and
you
know
walk
me
through
the
process.
So
don't
worry
everyone's
out
here
to
help.
A
If
you
have
questions,
ask
at
any
time-
and
we
have
an
Education
Committee
meeting
next
week
and
I
mean
I
hope
to
do
one
of
these
again,
where
you
know,
maybe
next
time
we'll
go
through
adding
an
image
to
the
manual
a
little
more
advanced.
So
for
those
of
you
that
joined
us
today,
you
know,
get
your
feet
wet,
try
making
some
and
then
the
next
webinar
will
go
through
adding
images
or
screenshots
that
you've
taken
to
add
to
the
manual.
A
Okay,
wonderful!
Thank
you
so
much
everyone
I!
Thank
you
big!
Thank
you
to
Caroline
and
David
and
Lisette
and
Jason
for
coming
in
and
helping
us
all
today.
Thank
you.
Thank
you.
So
much
and
again,
if,
if
you
need
help
with
anything,
please
reach
out
on
either
IRC,
you
know
we're
an
email
and
we'll
be
glad
to
help
have
a
wonderful
weekend.
Everybody
thank
you.
So
much.