
►
From YouTube: Cataloging Special Interest Group - 5/7/2020
Description
Topic: Authorities
Chat Logs: https://drive.google.com/file/d/1RILU116djj34YumH7EMC256FKL2pzPO4/view?usp=sharing
B
See
as
we
are
recording
today,
but
please
feel
free
to
unmute
yourself
share.
Your
video
chime
in
I
was
thinking
of
showing
folks
a
couple
of
things
that
I've
discovered
that
could
be
useful
and
then
simply
open
it
up
for
questions
and
a
roundtable
discussion.
I
wanted
to
show
one
or
two
things
that
I
do
for
ongoing
work
for
my
cataloging
for
authority
control,
while
cataloging
and
then
I
think.
A
lot
of
us
are
also
looking
at
cleanup
and
so
then
look
at
a
couple
of
things
for
cleanup.
B
So
welcome
everyone
welcome
new
folks,
I
was
who've,
just
joined
us
I
was
saying
that
I'm
just
gonna
show
a
couple
things
I've
discovered
that
I
think
are
useful
for
ongoing
work
and
for
authority
control,
cleanup
projects
and
then
we'll
simply
open
it
up
for
discussion.
So
we
can
share
our
tips,
tricks
and
strategies.
B
We
don't
actually
have
the
annotated
Hobbit
in
our
maritime
history,
library,
but
I
have
very
tolerant
staff
and
they
know
that
if
they
run
across
anything
by
talking
in
the
catalog,
it's
a
record
I'm
playing
with
and
one
thing
that
I've
discovered
for
ongoing
work.
When
one
brings
in
a
record,
if
you're
working
in
the
basic,
editor
and
I
think
a
lot
of
people
have
run
across
this.
B
It
can
be
depending
on
what
your
settings
are.
It
can
be
difficult
to
add
a
heading
here,
that's
unlinked,
or
to
get
the
linking
going
or
to
search
the
authority
file
and
in
the
advanced
editor.
One
thing
I
really
like
is
a
keyboard
shortcut
right
here.
Ctrl
shift
L
link
field
to
authorities,
so
that
can
be
very
intentional.
C
C
B
B
B
A
B
B
Ahead
of
time,
I
got
a
lot
of
emails
from
people
mentioning
they're
working
on
Authority,
cleanup
projects
and
I
think
that
is
something
that
would
be
really
really
great.
To
talk
about
I'm
working
on
cleaning
up
our
database,
our
authority
file
is
an
absolute
mess,
so
my
first
goal
was
to
identify
which
records
are
good.
B
Nice
records
from
the
Library
of
Congress,
formulated
according
to
catalog
rules,
etc
and
which
one
which
ones
were
not,
and
we're
currently
working
on.
All
of
those
non-standard
authority
records
to
get
those
cleaned
up.
Once
we
get
our
authority
file
as
clean
as
possible,
then
we'll
work
on
linking
and
then
see
what
headings
we
have
left
in
the
catalog
that
are
unlinked.
There's
some
really
good
reports
on
the
coho
report,
wiki
for
getting
at
records
that
are
not
linked
in
the
authority
file.
A
A
D
A
B
A
A
B
B
That's
a
really
good
question:
I
find
merging
one
by
one
to
be
very
comfort:
tedious,
yes,
yeah
and
I
see
in
the
chat
that
other
people
are
merging.
That's
that's
what
I
do
when
I
discovered
them
I
haven't
done
a
systematic
report,
I'm
sure
there's
one
out
there.
There
might
be
one
on
wanna
if
your
cover
is
upgraded
enough
to
take
advantage.
I
think
we
have
1905
and
we've
set
it
up
to
share
reports
and
import
them
with
mana.
Oh
great,
my
cos
found
one.
She
says:
she's
tracking
down
the
link.
Now.
B
One
reason
I
still
like
contributing
to
the
coha
reports.
Wiki
is
that
you
can
just
take
a
look
with
mana.
Perhaps
other
people
have
found
a
different
way,
but
I
found
that
you
have
to
in
our
catalog
or
the
only
way
I
found
to
search,
it
is
to
say,
I,
want
a
new
report
and
then
to
actually
try
to
search,
whereas
it's
nice
and
the
coho
reports
wiki
to
be
able
to
see
the
whole
thing.
B
There
might
be
a
way
with
Mark
edit
to
if
you
can
export
all
your
authority
records
to
find
a
way
to
discover
the
duplicates
that
way
and
to
take
care
of
them
that
way
since
Marquette,
it
has
really
sophisticated
features
and
you
can
use
regex
with
it.
But
that's
a
skill.
That's
a
little
bit
beyond
me.
B
B
B
More
about
that
please
so
Copa
has
George
says
in
the
chat
that
the
mark
modification
templates
are
pretty
rudimentary.
Okay,
so
there's
a
new
feature
in
the
higher
versions
of
coha
for
a
bibliographic
mark
modification
and
they're
called
the
mark.
Modification
templates
and
one
reason
I
haven't
played
with
those
so
much
compared
to
Marquette
it
as
I
find
mark
edit
a
little
bit
easier
if
I
can
get
the
records
out
and
into
mark
edit.
B
B
And
raised
asking
is
anyone
using
an
overnight
Authority
service
such
as
mark
I've?
We
could
send
out
new
Biblio
at
night
and
receive
matching
authorities
back
in
the
morning,
but
as
we
are
using
the
basic
live
editor,
we
have
already
hunted
for
the
authorities
I'm
looking
for
a
better
workflow.
If
we
switch
to
the
advanced
editor,
how
would
that
work?
If
we
keep
the
heading
wrongly,
we
would
not
get
a
match.
That's
true!.
B
One
thing
I
found
is
that
a
lot
of
the
headings
that
we're
coming
across
that
are
non-standard.
When
I
look
at
the
bibliographic
records,
it
is
best
to
clean
them
up
with
a
human,
because
they
duplicate
other
headings
that
are
perfectly
standard
in
the
record.
So
one
thing
I've
found
is
that
if
we
can
take
the
time
to
actually
look
at
the
bit
records,
we
get
the
highest
level
of
control
and.
B
I
think
others
may
have
some
other
ideas,
but
one
thing
I
found
is
that
Marketa
is
one
way
to
download
Library
of
Congress
authority
workers
for
free
configuring.
The
Z
39:52,
the
Library
of
Congress
is
pretty
easy.
Also,
configuring,
the
Z
39:52,
the
Library
of
Congress
for
authorities
in
coha
is
really
easy
and
I
like
the
search
interface.
If
you're
searching
one
by
one
through
Z
3950
in
the
coha
interface
a
lot
better
than
the
market,
it
actually.
C
C
Oh
now
so,
oh
yeah,
but
when
I
get
to
the
authority
record,
it
has
a
different
number
but
from
the
the
loading
tool
I,
don't
see
a
way
to
tell
it
to
look
for
a
third
for
duplicates
without
having
it
kind
of
sit
there
and
blow
up
in
itself.
Does
anyone
have
that
problem
or
have
a
workaround?
I
I
do
get
tired
pulling
out
the
duplicates
Wow.
B
B
B
B
It's
it's
a
really
nice
display
in
Koha,
because
you
get
to
actually
see
the
headings
I
like
the
preview
and
at
this
point
I
could
import
it,
but
with
the
Z
3950
it
doesn't
do
matching.
It
only
does
matching
when
the
record
staged.
So
if
I
were
actually
doing
this
workflow
with
the
Library
of
Congress
at
this
point,
I
would
go
to
Marquette.
It
close
this.
B
B
It
worked,
and
this
is
showing
you
why
I
don't
like
this
interface
as
well.
I,
don't
see
the
same
information
I,
don't
see
the
heading
term,
so
one
thing
I'll
do
if
I
actually
want
that
record
is
when
I
do
the
mark
preview
I,
actually
grabbed
that
LC
control
number
from
the
o1o
and
I
can
search
for
that
and.
D
B
E
Is
Micah
hi
Micah,
so
just
update
people
Christopher
had
typed
in
the
chat
that
he
was
seeing
a
lot
of
duplicates
with
authors
and
things
so
I
asked
him
if
he's
on
his
libraries
on
elasticsearch.
Yes
yet,
and
he
said
yes,
they
are
so
I
just
wanted
to.
E
So
some
of
those
bugs
have
been
fixed
in
1911
and
even
more
of
them
are
getting
fixed
in
2005.
But
if
you're
on
1905
or
anything
earlier
and
running
elasticsearch,
my
recommendation
is
to
just
turn
off
the
linker,
to
auto
link
and
to
manually
link
when
you're
creating
your
records
when
you're
doing
your
cataloging.
B
E
Sure
I
can
try
I've
been
in
the
middle
of
trying
to
do
some
original
cataloging
for
the
first
time
in
a
very
long
time,
so
do
I
have
the
ability
to
share
a
screen.
I
think
you
should.
E
Will
so
you
know
Christopher
did
you
want
to
see
the
system
preferences?
Is
that
what
you
were
asking
about?
You're
nodding
thumbs
up,
okay,
so
I'll
just
switch
over
here
to
another
screen,
so
in
administration
in
the
global
system
preferences
on
the
authorities,
tab
there's
a
whole
section
here
called
linker.
E
There's.
Also
this
setting
right
here
the
auto,
create
authorities
when
editing
records.
I.
Have
this
set
to
do
not
generate
Authority
records
that
are
missing?
You
can
change
this
to
generate.
So
what
that
does?
Is
it
if
a
link
isn't
found,
it
will
automatically
create
an
authority,
but
I
don't
want
that
to
happen
because
we're
on
elastic
search
and
the
linkers
not
finding
matches
by
itself
very
easily.
So
we.
E
This
linker
keeps
tail
is
for
keeping
links
to
existing
authority
records
when
the
linker
is
unable
to
find
match.
So,
for
example,
if
you
you
know,
punctuation
is
different
in
your
bibliography
or
authority
record,
and
so
sometimes,
if
you
add
the
punctuation
into
your
biblioteca,
that
will
cause
the
linker
to
not
recognize
it
as
a
match
anymore.
So,
if
you
have
this
set
to
do,
it
will
retain
the
link,
when
you
add
the
punctuation,
so
that
they
stay
talking
to
each
other,
the
linker
module.
E
E
Basically,
what
this
does
is
it
would
look
at
your
width,
look
at
your
heading
and
if
it
did
not
find
a
link
on
the
whole
string
of
headings
all
of
the
fields
and
subfields,
it
would
chop
off
the
last
subfield
and
then
try
to
find
a
match
if
it
still
didn't
find
a
match,
it
would
chop
off
that
next
subfield
and
look
for
a
match
and
it
would
keep
doing
that
until
it
found
a
match.
So
I
have
found
that
broader
headings
does
work.
E
I
haven't
been
using
it
right
now,
because
our
records
are
still
in
need
of
cleanup.
So
I
want
to
clean
up
all
my
records
first
before
I
start
to
use
broader
headings,
and
then
the
linker
relink
option
is
to
relink
headings
that
have
previously
been
linked
to
Authority
records.
I.
Think
that's
when
other.
Do
you
remember
is
that
when
you
edit
to
an
authority
record
and
then
it
real
inks,
the
biblio
I,
don't.
E
Think
that's
I
think
that's
what
it
means
it's
when
you
make
so,
for
example,
if
you're
doing
a
merge
project
where
you're
merging
a
bunch
of
your
authority
records,
the
linker
relink
I
think
is
what
would
go
in
to
the
records
that
were
attached
to
the
other
authority
record
that
gets
merged
into
the
one
that
you're
keeping
and
it
real
inks
the
headings
in
that
record
to
the
to
the
new
merged
record.
I.
Think
what
that
is
so.
F
E
So
Nick
Clemens
has
been
working
on
it
at
Bywater
when
I
have
time
I
test
the
patches
that
he
writes
so
I
know
that
progress
is
being
made,
but
there's
still
there's
still
a
lot
to
be
done,
and
so
we're
we're
early
adopters
and
we're
gonna
be
moving
up
to
nineteen
eleven
next
week.
So
I
am
hoping
that
I'm
going
to
notice
some
significant
changes
with
some
of
this
authority
work,
because
a
lot
of
the
a
lot
of
the
patches
that
he's
written
have
not
and
able
to
be
back
ported
to
1905,
I.
Think.
F
It's
you
know,
showing
one
with
a
period
and
one
with
a
comma
and
and
to
me
that
that's
that's
a
big
issue,
because
you
know
when
somebody
is
trying
to
do
a
search
in
your
system,
they're,
seeing
a
name
and
they
click
on
that
facet.
They're
expecting
to
get
everything
with
that
name
and
obviously
you
know
if
Koha
is
seeing
it
differently
than
I'm
assuming
the
searchers,
seeing
it
differently
and
not
getting
all
of
the
the
author.
Because
of
that
punctuation.
E
So
some
questions
then
I
would
ask
would
be
like
how
is
that
facet
list
populating?
Is
it
populating
from
your
authorities
or
is
it
populating
from
like
the
elasticsearch?
The
contents
of
the
elastic
search
index
elastic
search
is
supposed
to
be
filtering
out
a
lot
of
that
punctuation.
When
it's
billed,
you
know
when
it's
building
that
that
index
so
I.
E
So
I
yeah
I,
don't
know
how
that
would
affect
it,
but
it.
The
facets,
are
being
built
by
your
authority
records
and
it's
possible
that
you've
got
because
of
the
auto,
create
authorities
and
having
a
linker
on
and
it
not
finding
matches.
It
could
create
new
authorities
for
each
different
punctuation.
E
E
So
this
is
a
result.
These
two
records
are
results
of
that
linker,
not
not
finding
not
looking
correctly
for
for
those
authority
records
and
not
realizing.
It
was
the
same
thing
here
is
a
case
of
I've
got
psychic
trauma
religious
aspects
Christianity
this.
You
know
it
has
all
of
this
information
with
it.
This
is
likely
a
record
that
originally
came
from
either
OCLC
or
Library
of
Congress.
E
This
one,
though,
is
the
duplicate
it.
It's
psychic
trauma
religious
aspects,
Christianity
period,
so
I
know
this
is
a
subject
example
and
not
an
author
example
like
what
you're
noticing
at
your
library,
but
if
your,
if
your
list
is
being
populated,
if
the
if
the
facet
list
is
being
populated
from
authorities,
then
that
would
be
an
example
of
how
multiple
entries
could
get
there.
E
Now
they
yeah
now
that
you're
on
elasticsearch
the
facets
list
is
actually
pulling
from
more
than
just
the
first
few
pages
of
your
search,
because
that
was
one
of
the
limitations
of
zebra
is
that
the
facet
list
could
only
be
populated
from
the
first
I,
don't
know,
60
or
80
search
results
and
now
with
elasticsearch.
It
can
pull
from
more
than
that.
I'm,
not
sure
what
the
limit
is,
if
it's
like
500
or
a
thousand.
But
it's
a
big
number
George.
F
E
F
B
B
C
Actually
does
anyone
know
when
I,
when
I'm
being
compulsive
and
I
go
through
and
pull
up
and
tell
it
to
start
with
a
and
give
it
a
name
and
I
go
through
the
first
50
pages?
Everything
is
in
alphabetical
order,
it's
fairly
simple,
to
see
if
there's
a
duplicate
heading,
but
when
it
gets
to
51,
it
starts
scrambling
the
letters,
and
so
you
get
things
from.
You
know
a
B
to
a
Z
and
it
doesn't
have
the
things
between.
So
is
this
have
I
done
something
horribly
wrong,
or
is
this
a
bug?
What.
C
C
G
I,
don't
I
don't
know
if
this
helps
when
you
were
talking
about
searching
authorities
when
you
do
I
think
within
Koha
right
you're,
getting
like
a
list
of
authorities
trying
to
get
things
on
the
same
page,
no
well
unrelated,
handy
tip
when
you're
searching
authorities
you
can
go
to
the
second
page,
and
then
it
gives
you
a
results
per
page
limiter
in
the
e
URL,
and
you
can
increase
that.
So
you
can
see
like
more
than
20
per
page.
G
D
G
So
up
in
the
in
the
URL
here,
let
me
start
over.
So
if
I
just
do
a
search
for
a
it's
giving
me
20
results
per
page
of
don't
look
at
my
authorities
because
we
don't
clean
them
up
very
often.
But
if
you
click
on
two,
then
you
can
see
that
the
URL
changed
to
include
results
per
page
and
it
includes
the
one
or
start
from
there.
So
if
I
change,
my
start
will
come
back
to
one
and
change
my
results
to
whatever
I
want
so
200
instead
of
20.
Oh.
G
It
lists
the
first
200.
Let's
just
need
to
be
settings
on
the
page.
I
agree
yeah,
it's
a
clunky
workaround,
but
it's
helped.
F
E
E
Yes,
so
I
posted
the
I
posted
the
link
in
the
chat
to
the
report
that
I
found
in
the
Quahog
wiki
that
identifies
duplicates
so
I've
been
I.
Don't
know,
I
feel
like
I'm.
Still
with
my
with
my
authority.
Cleanup
work
right
now:
I'm
still
kind
of
got
this
scattershot
approach.
I'll
do
one
thing
for
a
while
and
then
I'll
get
discouraged
and
a
little
bored
with
it,
and
then
I'll
shift
and
I'll
try
something
else.
E
So
it's
I
feel
like
the
duplicates.
Part
of
the
work
is
also
cleaning
up
authorities
because
we've
got
outdated
authorities.
You
know
where
the
the
terminology
has
changed
and
so
those
need
to
be
updated.
Then
we
had
the
punctuation
issues,
because
the
duplicate
authorities
report
works
great,
but
it
does
not
take
into
account.
Punctuation
I
still
have
to
go
in
and
identify
those
myself.
G
One
one
thing
that
we've
been
doing
and
we
don't
we
have
like
I
said
our
authorities
are
bad,
but
you
can
go
in
and
overlay
an
authority,
so
we
generate
a
list
of
things
to
work
on,
go
in
overlay,
the
Library
of
Congress
Authority
and
then
merge
down
all
the
bad
ones
into
that
overlaid
record.
It's
a
slow
clunky
process.
Yes,.
B
Well,
it's
been
an
hour.
This
was
a
great
discussion.
Everyone
and
I
would
encourage
everybody
to
keep
the
discussion
going
on
even
on
the
main
Kohala
list,
because
the
more
that
we
can
share
with
our
root
flows
in
places
where
the
developers
are
gonna,
see
it.
The
more
they're
gonna
understand
our
workflows
and
the
things
we
need,
but
we
also
do
have
the
cataloging
sig
email
list
among
ourselves
that
anyone's
welcome
to
join
any
any
last
comments
or
questions.
B
G
Let's
so,
basically
all
you
do,
is
you
pull
up
the
authority
you
want
to
edit
edit
here
and
then
up
here?
You've
got
a
search
for
Z
3950
button,
and
then
it
warns
you
that
it'll
overlay
it
fills
in
the
information
we
can
try
it
I,
don't
know.
I
just
picked
one
at
random.
Okay,
so
there's
there's
an
authority
record
there.
So
I
can
import
that
and
I
would
probably
look
it
over,
but
when
you
save
it
and
it
over
over
writes
what
was
there
before
with
the
better
data.