►
From YouTube: Merging Data | S3E14
Description
Don't make a mess of your bib records or patron records. Clean up the clutter and the duplication by merging records. George walks us through both processes with ease.
Contents:
0:00 - Title
0:27 - Intros
2:36 - Merging Records
13:28 - Merging Patrons
20:22 - Bug 20271 - Deletion Tables
Additional Resources:
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20271
Music: https://bensound.com/
Text -to-speech: https://wideo.co/text-to-speech/
Audio Effects: https://zapsplat.com/
Visual Effects: https://flexclip.com/
A
B
D
Video
is
sponsored
by
koha
us
your
place
to
look
for
all
things
Co-op,
whether
you're,
just
starting
out
with
tohog
or
you've,
been
with
Kohan
for
a
while
koha
us
is
a
great
place
to
find
resources,
learn
new
tips
and
techniques
or
connect
with
other
users
and
libraries.
Koha
us
provides
excellent
information,
both
original
and
curated
from
around
the
internet,
including
the
terrific
every
other
day
training.
Videos
you'll
also
find
several
special
interest
groups
to
connect
with,
as
well
as
our
general
monthly
meeting
Where
We
Gather.
To
talk
about
the
latest
Kohan
news.
D
You
should
also
check
out
the
koha
U.S
annual
conference
held
at
various
locations
around
the
U.S.
This
is
a
great
opportunity
to
meet
with
other
users
face
to
face
and
build
your
Kohan
Network,
as
well
as
new
friendships
and,
of
course,
don't
forget
about
the
great
presentations
koha.
Us
is
also
actively
involved
in
the
koha
community
by
contributing
towards
new
developments.
D
If
you
are
interested
in
contributing
towards
koha
U.S
funded
developments
join
the
koha
U.S
memberships.
Your
annual
membership
builds
the
funds
to
sponsor
new
developments
in
the
community
and,
as
a
member,
you
also
help
shape
koha
us
with
your
membership
votes
and
receive
a
discount
on
the
annual
conference.
You
can
also
contribute
towards
developments
through
a
direct
donation
or
by
purchasing
some
great
koha
us
merchandise,
through
our
threadless
accounts
visit
us
at
kohaus.org
to
find
out
more.
C
C
So
people
were
going
crazy
with
merging
things,
and
so
we
took
that
away
from
everybody
and
instead
what
happens
is
when
they
want
to
merge
something.
They
send
me
an
email
with
a
couple
of
with
the
URLs
of
the
two
things
that
they
think
ought
to
be
merged
and
I
go
ahead
and
merge
them.
So
if
it's
Justified,
if
merging
them,
is
Justified,
so
just
the
other
day,
I
got
a
request
from
one
of
our
libraries.
C
They
said
that
there's
this
Edition
in
the
system
and
there's
this
Edition
in
the
system
they're
both
the
same.
They
both
appear
to
be
the
same.
They've
got
the
same.
Isbn
This
Record
looks
a
little
bit
better
than
this
record.
This
one
is
probably
a
pre-pub,
so
the
my
process
for
merging
them
is
I
actually
have
a
list
and
I
add
them
to
the
list,
and
there
are
other
ways
to
merge
things.
But
this
is
the
process
that
I
have
and
then
I
opened.
C
I
open
the
list
that
I've
put
them
both
on
and
I
select.
All
the
one
owned
by
Paola
is
the
one
that
I
think
is
the
better
book,
the
better
record
and
so
I
checked
the
check
boxes
there
and
I
click
on
merge,
selected
and
I
tell
it
that
this
is
the
one
I
want
to
keep,
because
that's
the
biblio
number
for
the
one
that's
owned
by
Piola.
C
You
can
change
the
framework
here
if
you
want
to
do
that,
but
then
I
click
on
next
and
it's
going
to
show
me
the
complete
record
for
the
source.
This
is
the
reference
and
this
is
the
destination
record,
and
so
this
is
the
one
that
all
of
this
stuff
should
be
exactly
the
same
and
then,
if
I
click
on
this
one,
this
is
the
one
that
I
didn't
like
that
record.
C
C
If
I
just
yeah,
if
I
wanted
to
add
any
of
this
information
here
like
if
I
I,
don't
know
what
the
050
is,
it
looks
like
some
kind
of
maybe
Library
of
Congress
call
number
and
082
is
the
Dewey
Decimal
number,
but
maybe
I
decide
that
this
is
I.
Don't
like
this
050
or
I
want
to
add
both
of
them.
If
I
click
on
that,
then
that
one
will
move
over
here
and
if
I
click
on
it
over
here,
it'll
uncheck
it
so
anything
I
want
to
take
off
this
record.
C
I
can
just
check
the
like.
If
I
wanted
to
drop
this
655
I.
Could
click
on
that
and
I'll
take
it
off
of
there
and
if
there's
anything
over
here,
I
want
to
add.
If
I
check
on
the
check
box,
it'll,
add
it
to
the
new
record
and
honestly,
in
this
case,
though,
I
don't
see
anything
in
this
brief
record
that
I
want
to
keep
on
the
on
the
final
record.
So.
B
B
C
It's
a
really
good
way
of
doing
it.
It
shows
you
every
field
in
the
mark
record
and
it
gives
you
the
opportunity
to
merge
them
and
so
that
now
both
of
the
items
that
were
on
that
are
now
on
the
new
record
and
if
I
go
back
and
try
and
reload
this
one
that
I
didn't
like
the
one
that
we
got
rid
of.
It
just
says
that
biblio
no
longer
exists,
but.
D
B
I'm,
not
a
catalogger,
but
it
makes
it
look
easy,
but
I
do
see.
The
concern
about
you
know
have
giving
people
that
option
and
they're
not
paying
attention
to
the
actual
items,
whether
or
not
they're
the
same
additions
and
and
actually
copies
of
books,
and
so
that's
that's
rather
important
if
you're
going
to
merge
Fields.
C
B
C
C
Surprise
me,
but
again,
I've
never
had
a
problem
with
that.
Currently
we
don't
use
the
Acquisitions
module
here
other
than
the
suggestions
portion
of
the
Acquisitions
module
and
I'd
like
to
say:
I've
never
made
a
mistake,
merging
records,
but
oh
yeah
I
have
some
pretty
big
ones.
Actually,
that's
one
of
the
nice
things
about
having
a
test
server
that
doesn't
have
the
that's.
That's.
C
With
the
production
system
is
when
I
have
made
a
mistake,
I'd
have
been
able
to
go
to
the
test
system,
pull
the
record,
I
wanted
and
fix
it,
but
one
of
the
number
one
ways
because
I
use
the
list
to
do
merges
one
of
the
number
one
ways
I
have
made
mistakes
is
after
I've
finished
a
merge.
I
have
to
remember
to
go
to
the
list
again
and
remove
all
the
items
for
all
the
titles
from
the
list,
because
that's
the
the
way
that
I've
made
mistakes
in
the
past
is
I've.
E
C
Yeah,
usually
usually
totally
unrelated.
So
but
that's
you
know,
there
are
other
ways
to
get
to
the
merge
you
could.
If
you
do
a
cataloging
search,
you
can
click
on
the
check
boxes
and
find
the
merge
button.
That
way,
that's
one
of
the
ways
that
we
have
hidden,
because
it's
easy
to
hide,
hide
that
and
take
away
that
that
essentially
takes
away
the
merge.
C
B
Yeah,
certainly
something
that
you
want
to
be
very
mindful
of
of
who
gets
permission
to
do
that
yeah.
You
know
how
good
of
a
catalog
or
are
they,
and
you
know
mindful
of
details,
but
you
know
also,
you
know,
keep
in
mind
all
the
nuances
of
bibliographic
records
and
what
they're
tied
to
because,
yes,
they
are
tied
to
holds.
They
are
tied
to
Acquisitions
if
you're,
using
acquisite,
Acquisitions
they're
tied
to
they're
tied
to
lists
yeah
in
some
ways.
C
C
You
know
and
the
reason
that
we
don't
let
everybody
have
that
that
you
know
currently
only
I
have
the
ability
to
merge.
Things
is
because
we
are
the
reason
we
have
duplicates.
A
lot
of
the
time
is
because
a
lot
of
our
catalogers
are
also
the
director
at
the
library
they're
at
and
they're.
Also
the
janitor
and
they're,
also
the
circulation
desk
person
and
they're.
C
Also
the
person
that
mows
the
yard
at
the
library
we
have
a
lot
of
really
small
libraries
and
cataloging
is
rarely
somebody's
only
job,
except
for
our
five
or
six
very
biggest
libraries.
Almost
everybody
that
does
cataloging
is
doing
multiple
jobs
at
the
library,
and
so
they
might
not
be
as
good
at
it
or
as
well
trained
or
as
experienced
as
as
people
at
some
of
our
other
libraries.
B
Right
and
when
you
have
a
when
you
have
a
Consortium
where
different
libraries
have
different
catalogers,
they
all
have
different
cataloging
styles
and
so
yeah.
There
can
be
some
inconsistencies
in
between
them.
You
know
between
them
and
between
your
your
staff,
members
and
small
libraries
that
have
those
many
hats
that
don't
touch
cataloging.
All
that
often
so
yeah
I
guess
you
know
yeah,
it
does
make
sense
to
have.
You
know
maybe
have
in
a
large
environment
like
that.
Have
somebody
be
the
the
key
point
for
certain
tasks.
C
C
C
C
Person
yeah
they're
close
enough,
that's
usually
the
number
one
reason
we
merge.
People
is
because
somebody
at
one
Library
somebody's
gone
to
Richmond
and
created
a
library
card
there
and
then,
a
year
later
they
go
to
use
the
library
in
Ottawa,
which
is
just
down
the
road
and
somebody
at
one
of
the
two
libraries
when
they,
the
person
from
Richmond,
doesn't
realize
that
they
can
use
their
Richmond
library
card
in
Ottawa
and
they
go
to
the
desk
and
they
say
I
need
a
library.
B
C
What
I
find
is
that
it
has
to
be
a
really
really
really
close
match
if
the
first
name
and
the
last
name,
you
know
if
somebody
makes
a
typo
or
if
they
put
a
one
of
them,
has
a
middle
name
and
the
other
one
has
a
middle
initial.
Even
if
they're
the
same
person,
the
matching
has
to
be
really
really
really
tight
for
koha
to
warn
you
yeah.
C
So
we've
I've
checked
the
box
for
Daryl
Frosty
and
for
Gilbert
Frosty,
and
then
up
here,
you'll
notice.
There's
merge
selected
patrons
at
the
top
of
the
page.
It
won't
show
up,
it
won't
be
enabled
until
you've
actually
clicked
on
two
patrons,
but
you
check
those
check,
boxes
and
click
on
merge
and
it's
going
to
give
you
some
of
the
basic
information.
You
know
the
name
date
of
birth,
category
and
library
and
expiration
date
and.
C
To
select
one
of
those
to
be
the
patron
that
you're
going
to
keep
right
so
maybe
Gilbert
Frosty
came
in
and
he
said
well,
you
know,
my
middle
name
is
Daryl,
you
know
and
I'm
the
same
person.
They
have
the
same
birthday
so
which
cut
you
got
to
ask
the
patron.
You
know
which
one
of
these
two
accounts
do
you
want
to
keep
which
card
number?
Do
you
want.
A
C
Keep,
and
so
let's
say
we
choose
this
one,
so
what
it's
going
to
do
is
it's
going
to
take
all
of
the
information
from
Daryl
that
isn't
on
Gilbert's
and
push
those
two
together?
So
if
Daryl
Frosty,
if
that
account,
has
fines,
it'll
pull
those
into
the
Gilbert
Frosty
account
if
it
has
anything
that
isn't
filled
out
in
Gilbert's
account
it's
going
to
transfer
that
data
to
those
same
fields
in
or
in
Daryl's
account
it'll
transfer,
those
to
Gilbert's
account
in
those
same
Fields,
but
Gilbert
is
the
one
that
will
be
kept.
C
So
it's
going
to
lose
the
card
number
it's
going
to
lose.
The
name
it'll
lose
the
date
of
birth.
If
it's
different,
it's
going
to
lose
the
patron
category
and
it's
going
to
lose
the
library
everything.
That's
that
there's
already
a
field
filled
out
in
in
Gilbert's
account
it's
going
to
lose
those
from
Daryl's
account.
So.
D
C
C
B
Right
early
early
on
when
we,
when
this
feature
came
out,
we
had
to
disable
it
because
we
were
running
into
issues
where
we
tried
to
merge
patrons
and
we
had
certain
attributes
that
should
not
be
repeated.
And
when
you
merged
the
records,
it
was
duplicating
those
and
we
have
jQuery
written
around
it
and
it
was
causing
some
weird
anomalies
and
I
had
to
go
into
the
patron
record
and-
and
there
were
some
work
around
ways
to
get
rid
of
those
extra
Fields.
B
But
it
you
know
if
I
wasn't
around
the
patron
record,
had
issues
and
staff
couldn't
move
any
further
with
it
and
so
yeah
that
that
was
a
problem
and
so
later
on.
They
addressed
that.
But
then
they
kind
of
crippled
the
merge
feature
because
they
were
saying
well,
if,
if
it
has
fields
that
you
can't
duplicate,
we're
just
not
going
to,
let
you
merge
them
right
and
that
that
was
frustrating,
and
so
they
finally
got
to
this
point.
B
Where
it's
going
to
have
you
select
the
the
record
where
it's
going
to
keep
that
stuff
and
that
in
that
process
it
is
going
to
keep
the
stuff
the
the
those
non-repeatable
fields,
from
whatever
record
you
choose
to
make
the
priority
right
so
that
you
know
it's
come
a
long
way,
but
you
know
I'm
hoping
that
down
the
road
they
they
can
make.
This
work
a
little
bit
more
like
merging
bibliographic
records
and
where
they
show
you
all
the
fields
right.
These.
A
B
B
Yeah,
that's
that's
ideal.
In
in
any
merging
situation,
you
know
being
able
to
see
what's
going
to
go
on
and
be
able
to
cherry
pick,
the
more
accurate
information
from
from
each
you
know
all
the
stuff
behind
the
scenes
outside
of
the
record
it
handles.
Well,
you
know
it's
it's
doing
what
it's
supposed
to
do,
but
within
the
records
that's
a
little
goofy
still
and
needs
Improvement
cool,
but
yeah
has
come
a
long
way.
B
I
know
that
there
are
some
bugs
in
the
work
and
I'll
have
I'll,
have
a
a
bug
number
pop
up
here
talking
about
it,
but
there
is
a
bug
in
the
process
that
we're
having
discussions
on
right
now,
where
I
think
it's
taking
koha
in
the
right
direction.
Right
now,
making
modifications
deletions
are
still
kind
of
tricky,
and
you
know
whether
it's
deletions
or
modifications
some
of
those
things
you
can't
undo.
B
This
bug
that
is
being
discussed,
they're
discussing
doing
some
things
differently
right
now,
when
you
do
a
deletion
in
koha,
it
will
take
that
information
and
move
it
over
to
a
deleted
table
right
in.
In
some
cases,
there
are
some
deleted
tables
where
that
information
is
migrated
over,
but
we
lose
a
lot
of
connections
between
that
information
and
data.
We
want
to
retain
yeah.
B
In
koha-
and
you
know
some
of
the
issues
around
that
is
number
one-
it
keeps
cohab
bloated
and
you
have
to
do
some
maintenance
now
again
on
on
those
tables,
because
those
are
easy
to
forget
and
that
those
tables
can
build
and
build
a
build,
and
when,
when
you
migrate
over
to
those
tables
again,
like
I
said,
you
lose
a
lot
of
links
that
were
important
and
right.
Yes,
you're,
maintaining
that
information
in
those
deleted
tables,
it
doesn't
make
un.
B
B
We
can
still
go
back
to
who's
responsible
for
it
last,
and
it
could
still
be
linked
in
the
in
in
records
the
way
we
need
them
to
be
linked,
and
you
know
we're
not
breaking
things
along
the
way
by
moving
this
data
around
or
removing
it,
and
you
know,
of
course,
we
still
have
the
you
know
the
issue
of
when
the
stuff
gets
cleaned
up.
I
think
that
kohas
good.
It
has
some
good
safety
measures
that
we
still
keep
in
place
where
we
don't
remove
this
stuff.
C
C
C
That
you
can
have
your
support
company
Runner.
You
can
run
that
will
delete
the
things
on
the
deleted,
biblios
and
deleted
items
and
a
lot
of
those
other
tables
after
a
certain
amount
of
time.
But
you
know
it
would
simplify
a
lot
of
things
if,
if
they
just
stay
there,
we
have
all
of
our
things.
So
once
something
moves
to
the
deleted
items
or
the
deleted
bibliodes
table,
it
stays
there
for
13
months
and
then
after
13
months
it
gets
deleted.
C
But
there's
a
lot
of
history
that
gets
deleted
too,
but
it
would
simplify
a
lot
of
things
if,
instead
of
items
and
items
table
and
delete
and
I
stable,
if
there
was
just
one
table
and
the
items
table
indicated
whether
something
was
you
know,
active
or
not
active
and
then
after
a
certain
amount
of
time
being
inactive,
then
they
could
be
deleted.
It
would
just
be
one
less
table,
you
know,
and
there
are.
D
B
I
I
do
encourage
those
of
you
watching.
If
you
go
to
the
bug
and
check
it
out,
comment
on
it,
I
think
one
of
the
biggest
hurdles
or
for
this
particular
project
would
be.
You
know,
funding
for
it,
because
it
is
going
to
be
a
major
shift
in
koha.
In
my
opinion,
because
it's
a
it's
a
database
restructure
and
you
know
the
question
is
for
me
the
biggest
hurdle
would
be
okay.
Well,
we
can
add
this
this
column
in
this
flag.
You
know
we
we
have
to.
B
We
have
to
point
everything
to
that.
That
has
to
do
with
deleting
and
merging
at
at
that
point,
but
we
also
have
the
the
issue
about
the
data.
That's
already
in
the
deleted
tables.
What
happens
to
that?
Can
we
can
we
put
that
back
in
amongst
all
the
other
data,
because
you
know
those
links
have
already
been
broken,
and
so
the
question
is
how
to
make
that
transition.
Frankly
to
the
other,
that's
that's
going
to
be
a
big
challenge,
but
I
see
this.
B
Is
you
know
you
know,
we've
got
that
hurdle
that
the
programmers
have
got
the
developers
have,
but
the
other
hurdle
is
funding.
I
I
see
that
one's
gonna
probably
take
a
lot
of
time
and
work,
and
so
I
would
encourage
those
those
libraries
that
are
interested
in
in
the
concept
of
this.
You
know
particularly
to
retain
those
links
and
make
it
easy
make
it
so
that
we
can
work
towards
a
koha
where
we
could
undelete
things
down
down
the
line.
B
If
you,
if
that's
something
that
sounds
really
appealing
to
you,
maybe
we
gather
together
and
contribute
towards
this
in
some
way.
I
I'm,
you
know
I'm
hoping
that
some
vendors
would
put
this
in
a
some
sort
of
crowdfunding
kind
of
a
situation
where
we
can
all
contribute
towards
it
and
work
toward
towards
getting
this
done,
because
I
think
this
is
going
to
be
a
huge
asset
to
koha
down
the
line.
B
B
B
You
know
we're
trying
to
do
statistics
on
things
that
have
been
added
and
withdrawn
and
that's
complicated
when
you
have
to
go
between
those
two
tables,
because
you
have
to
consider
the
things
that
were
added
at
in
a
certain
time
and
they
might
have
been
deleted
at
that
point
too
or
within
that
right
now,
and
so
you
have
to
go
back
and
search
both
of
those
and
man.
It
is
not
fun
having
to
do
that.
C
No,
that's
I've
got
a
lot
of
reports
that
are
that
they
have
to
look
at
both
of
those,
because
you
know,
if
you
know
a
monthly
report,
you
know
something's
added
on
January
1st
and
then
it's
but
it's
deleted
before
January
31st.
It's
hard
to
count
that
in
an
end
of
the
month
statistically,
but
this
would
simplify
a
lot
of.
B
That
yeah
take
a
look
at
that
that
bug
and
please
participate
in
it.
At
least
you
know
comment
in
it
if
you
like
them,
if
you
like
the
direction
of
that
bug,
please
you
know,
add
a
plus
one,
but
add
your
comments,
your
thoughts
to
that
it's
in
discussion
and
I
would
like
to
see
it
move
forward
from
discussion
to
development.
B
If
you
can
contribute
funds,
maybe
comment
in
there.
You
know
that
you'd
like
to
contribute
towards
it,
but
I
really
think
that
that
would
be
a
fantastic
development
for
Gohan
yeah.
All
right,
well,
good
discussion.
You
know
for
an
impromptu,
topped
it
topic.
So
thank
you.
George
for
sharing
your
knowledge
on
merging
all
right,
we'll
see
you
next
time,
we're
ready
for
it.