1
00:05:09,899 --> 00:05:15,779
Am I get this right.

2
00:05:21,029 --> 00:05:22,319
I'll leave the hat, I guess.

3
00:05:28,320 --> 00:05:30,180
Do you know what border y'all
are going in.

4
00:05:31,980 --> 00:05:34,110
Yeah, me then Zeb and Natalie.

5
00:05:35,670 --> 00:05:36,270
Oh,

6
00:06:15,059 --> 00:06:18,029
tore out of the I left the
officer, I left the 230 but

7
00:06:18,239 --> 00:06:20,999
before that rain came in I
messaged Terry and I was like

8
00:06:20,999 --> 00:06:24,149
I'm gonna hit home before this
hits and then I'll finish the

9
00:06:24,149 --> 00:06:27,629
day at home. You know I knew
it'd be bad but I just didn't

10
00:06:27,629 --> 00:06:29,609
want to drive through it. I
didn't know it was gonna be like

11
00:06:29,609 --> 00:06:30,929
Wrath of gods or

12
00:06:32,310 --> 00:06:33,630
somehow was the drive.

13
00:06:34,350 --> 00:06:37,890
I was right ahead of it the
whole time. And I think it was

14
00:06:37,890 --> 00:06:40,740
worse, you know, as I got
further south, it was, it was

15
00:06:40,740 --> 00:06:43,950
worse in Baton Rouge and look
like. But I don't know did it

16
00:06:43,950 --> 00:06:46,680
look, did you notice it at all,
or did you have to drive through

17
00:06:46,680 --> 00:06:47,100
it.

18
00:06:47,820 --> 00:06:48,480
I left.

19
00:06:49,170 --> 00:06:53,670
About 315, I guess, whenever
whenever everybody on slack

20
00:06:53,670 --> 00:06:57,210
started saying that they got the
tornado alerts I was like okay

21
00:06:57,210 --> 00:07:02,040
I'm gonna go right. So, you have
a my drive is only about 10

22
00:07:02,040 --> 00:07:03,960
minutes so it was fine. No,

23
00:07:04,140 --> 00:07:06,090
I felt bad I was like oh I
should have told Laurie.

24
00:07:08,700 --> 00:07:11,520
I finished the day at home but
it was fine. We didn't get

25
00:07:11,520 --> 00:07:14,280
anything really. You yeah

26
00:07:18,480 --> 00:07:31,710
yeah we're gonna record it now.

27
00:07:34,200 --> 00:07:34,890
Hey, Mike.

28
00:07:52,019 --> 00:07:55,289
My section, I just timed myself
and it's only about 10 minutes.

29
00:07:55,649 --> 00:07:57,539
But I think, I think.

30
00:07:59,399 --> 00:08:01,589
Yeah, I'm actually under 15 so.

31
00:08:01,769 --> 00:08:06,569
Okay. So, I think we'll go.
We'll fill it in.

32
00:08:48,900 --> 00:08:52,170
I've been working on this
Middleton rename project last

33
00:08:52,170 --> 00:08:58,920
few days it was. I knew it'd be
involved but it's my mistake.

34
00:08:59,490 --> 00:09:05,940
Yeah. Before days, and seriously
is doing it. Hi. Okay. I've done

35
00:09:05,940 --> 00:09:08,910
it before, I feel like I could
have done it quicker myself but

36
00:09:11,400 --> 00:09:14,040
I don't know, I guess I was
interested to see how they do

37
00:09:14,040 --> 00:09:15,150
it. Uh huh.

38
00:09:16,680 --> 00:09:18,060
Just to make sure we're doing it
right.

39
00:09:19,409 --> 00:09:20,999
They offered to do it for free
so

40
00:09:21,149 --> 00:09:21,809
that's good.

41
00:09:22,890 --> 00:09:27,480
So well if they get it. Not
charted. So yeah, that was nice

42
00:09:27,480 --> 00:09:29,880
and then after that we didn't
even ask them, they just came

43
00:09:29,880 --> 00:09:32,490
out of blue. And I guess I'm

44
00:09:34,050 --> 00:09:36,720
Margaret Hansen was saw the
news,

45
00:09:38,100 --> 00:09:40,710
or I don't know if it was on
Twitter or the news or when she

46
00:09:40,710 --> 00:09:42,720
was like, I can help with this.

47
00:09:45,270 --> 00:09:45,990
Or her team.

48
00:09:46,320 --> 00:09:47,580
Yeah, well it's nice I

49
00:09:54,690 --> 00:09:58,830
was trying so hard to get my
picture to show up I don't know

50
00:09:58,830 --> 00:09:59,730
why it doesn't.

51
00:10:01,409 --> 00:10:02,909
I still haven't figured that out
either.

52
00:10:03,749 --> 00:10:07,139
I and sometimes it does and
sometimes it doesn't. And I

53
00:10:07,139 --> 00:10:08,249
don't know how to do it.

54
00:10:09,089 --> 00:10:12,779
I guess I have to go to the Zune
site. At some point and

55
00:10:12,779 --> 00:10:13,709
uploading a picture.

56
00:10:14,069 --> 00:10:18,059
I have uploaded the tanti any
day, whatever.

57
00:10:19,830 --> 00:10:22,830
I remember to comb my hair so
here I am.

58
00:10:27,869 --> 00:10:29,249
Happy Birthday z.

59
00:10:30,750 --> 00:10:31,590
Thank you.

60
00:10:34,979 --> 00:10:39,599
Thank you just just madly all of
them forgot. So what do you

61
00:10:39,599 --> 00:10:41,939
think I should do. Oh, I don't
know,

62
00:10:42,629 --> 00:10:43,259
forgot.

63
00:10:44,250 --> 00:10:50,130
I'm asking for a double play to
have gluten free treats. That

64
00:10:50,130 --> 00:10:56,250
sounds good. Yeah, way back, so
yeah make them pay up. Yeah,

65
00:10:56,580 --> 00:10:58,410
absolutely. That's my chance.

66
00:11:01,409 --> 00:11:09,149
So my system is very traditional
very traditional dessert, which

67
00:11:09,239 --> 00:11:14,249
we were decided to make because
a mother enjoys it a lot, so we

68
00:11:14,249 --> 00:11:17,879
wanted her to eat it too. So
that was nice. Those are little

69
00:11:17,879 --> 00:11:22,499
round balls. They didn't turn
out perfectly round and flat in

70
00:11:22,499 --> 00:11:27,149
certain places, but they were
tasty so I let it go to good.

71
00:11:30,269 --> 00:11:30,539
She

72
00:11:30,540 --> 00:11:34,470
let it go, but she made sure to
mention it to her this to BB

73
00:11:34,470 --> 00:11:36,810
right. Oh, gosh yes

74
00:11:36,810 --> 00:11:40,770
it was my one John's to say,
these are supposed to be round

75
00:11:42,870 --> 00:11:43,140
for

76
00:11:43,140 --> 00:11:46,740
you guys. Drop them from a
height so they landed in the pot

77
00:11:46,740 --> 00:11:48,780
with a toddler and became flat
at the bottom.

78
00:11:48,840 --> 00:11:49,680
Oh, no.

79
00:11:50,520 --> 00:11:52,140
Excuses, excuses.

80
00:11:53,520 --> 00:11:55,590
But if they were tasty I didn't
tell her that

81
00:11:56,190 --> 00:11:58,470
I'm scared to make macaroons for
you.

82
00:11:59,969 --> 00:12:01,619
They might not come out round.

83
00:12:03,809 --> 00:12:08,219
Hey, I'm willing to eat flat
balls, as long as they're tasty.

84
00:12:12,780 --> 00:12:16,050
The trick is, I was able to get
it yesterday.

85
00:12:19,349 --> 00:12:21,929
Thank you, coming to my zoom
thing again and see.

86
00:12:26,340 --> 00:12:29,730
Like I've had goat cheese on my
salad the last couple days.

87
00:12:30,450 --> 00:12:30,840
Good.

88
00:12:32,219 --> 00:12:35,999
Nice, nice. Yeah, I would do
that with like some walnuts.

89
00:12:38,190 --> 00:12:39,600
Premium some dried fruit.

90
00:12:40,170 --> 00:12:45,840
Yep, that's how I'm doing it the
the kale, sweet kale salad mix

91
00:12:45,840 --> 00:12:48,870
that they have at Sam's Club
that's on my weekly grocery

92
00:12:48,870 --> 00:12:51,630
list. The perfect tapping

93
00:12:52,590 --> 00:12:53,550
price. Thanks.

94
00:13:06,570 --> 00:13:07,530
starts at one.

95
00:13:13,590 --> 00:13:14,940
You got to be let in

96
00:13:17,669 --> 00:13:19,049
peanut gallery is over here.

97
00:13:19,139 --> 00:13:20,549
Are you gonna let her join us.

98
00:13:21,869 --> 00:13:26,849
Yeah, she's gonna have
headphones on. No comments. I

99
00:13:26,849 --> 00:13:29,579
made ask her questions there you
go.

100
00:13:34,559 --> 00:13:35,489
does not show.

101
00:14:08,759 --> 00:14:11,909
Do you know that's a very nice
big pot.

102
00:14:13,169 --> 00:14:14,219
Yeah, see.

103
00:14:20,940 --> 00:14:21,840
I think the United.

104
00:14:25,080 --> 00:14:28,500
Easy, you're your microphone is
kind of going in and out.

105
00:14:29,609 --> 00:14:31,019
Maybe. Let me

106
00:14:32,429 --> 00:14:35,009
find if I close my VPN, I get it
better.

107
00:14:36,840 --> 00:14:37,980
How's it now.

108
00:14:39,630 --> 00:14:41,520
Can you can you talk a little
more.

109
00:14:42,360 --> 00:14:46,530
How's it now TESTING TESTING
TESTING that was done.

110
00:14:47,789 --> 00:14:48,419
That's good.

111
00:15:06,809 --> 00:15:07,769
It's not popping.

112
00:15:09,450 --> 00:15:12,270
A few people connecting right
now so give them a another

113
00:15:12,270 --> 00:15:13,170
minute or two.

114
00:16:03,479 --> 00:16:36,029
Waiting for a few more. Is
anyone

115
00:16:36,030 --> 00:16:37,080
talking right now.

116
00:16:39,269 --> 00:16:43,829
Nope, nobody's talking Thank
you. We're waiting on, we're

117
00:16:43,829 --> 00:16:47,909
waiting for some more people to
come in. I see

118
00:16:47,999 --> 00:16:50,879
people who are connecting to
audio so once they're connected

119
00:16:50,879 --> 00:16:51,749
we'll get started.

120
00:16:56,940 --> 00:17:00,120
Should I had some background
music. Normally,

121
00:17:02,309 --> 00:17:06,629
I was just looking for a walk on
music for you, Mike. i, but I

122
00:17:06,629 --> 00:17:11,579
don't know my Grateful Dead song
catalog so I didn't know if walk

123
00:17:11,579 --> 00:17:15,239
me out in the morning was going
to be appropriate or not.

124
00:17:17,279 --> 00:17:19,469
About five bucks and my stops.

125
00:17:24,940 --> 00:17:28,930
Alright, it looks like
everybody's connected so I'll

126
00:17:28,930 --> 00:17:34,360
kick it off by just introducing
the today's topic and then

127
00:17:34,360 --> 00:17:40,090
reminding everyone of the last
session in this series which is

128
00:17:40,090 --> 00:17:44,020
next week. but today we're going
to talk about Loading Authority

129
00:17:44,020 --> 00:17:49,960
Records, and we have Mike Waugh,
and Zee Zee Solomon from LOUIS

130
00:17:50,320 --> 00:17:54,670
and Natty Natalie Palermo from
LSU Law are going to talk to us

131
00:17:54,670 --> 00:18:00,340
today, and then just a reminder
that next week. Wednesday at one

132
00:18:00,340 --> 00:18:06,160
o'clock, we have Khaleel L.
Bochy from SOWELA, and Rob

133
00:18:06,160 --> 00:18:09,400
Stevens from Nicholls who are
going to talk to us about tools

134
00:18:09,400 --> 00:18:13,060
for virtual outreach and
instruction. So I'll hand it

135
00:18:13,060 --> 00:18:13,960
over to Mike.

136
00:18:16,260 --> 00:18:19,860
All right, let me get started
with sharing the screen, you

137
00:18:19,860 --> 00:18:23,310
should be seeing a little slide
is that right.

138
00:18:23,760 --> 00:18:25,380
Yeah. Okay,

139
00:18:26,890 --> 00:18:33,010
so we're gonna we're gonna tag
team this. I'll start off with a

140
00:18:33,160 --> 00:18:37,720
short 10 minute. What are
Authorities and doing things and

141
00:18:37,720 --> 00:18:42,370
Authorities with Authorities and
Symphony Zee Zee's gonna follow

142
00:18:42,370 --> 00:18:47,170
up with talking about Loading
Authority Records. And then,

143
00:18:47,380 --> 00:18:53,050
Natalie will follow up the
cleanup hitter. We'll talk about

144
00:18:53,080 --> 00:18:58,630
authority load errors, and hint.
Handling deletions and changes.

145
00:19:02,110 --> 00:19:06,580
So there. Everyone knows me
right, Mike Waugh. Library

146
00:19:06,580 --> 00:19:12,220
Services Platform Administrator
at LOUIS. Before LOUIS I was a

147
00:19:12,700 --> 00:19:16,030
System Administrator at LSU for
five years and then I worked at

148
00:19:16,030 --> 00:19:20,890
the EBR PL. Before that for 10
years, never once held a

149
00:19:20,890 --> 00:19:29,440
cataloguing position. So caveat
emptor be beware here is I'm

150
00:19:29,440 --> 00:19:33,610
treading into territory I
normally don't tread but I am

151
00:19:33,610 --> 00:19:36,760
pretty good at given a
presentation, I think, and at

152
00:19:36,760 --> 00:19:43,390
reading documentation, so that's
why I'm here today. So first of

153
00:19:43,390 --> 00:19:46,990
all what is an authority I
wanted to start the presentation

154
00:19:46,990 --> 00:19:52,060
just from from square one. So
I'll be given kind of a 10,000

155
00:19:52,060 --> 00:19:56,470
foot, 45,000, foot view here. So
an authority would be the

156
00:19:56,470 --> 00:20:02,980
correct name or form of a name
or subject subject subdivision.

157
00:20:03,460 --> 00:20:07,300
As the slide says here. I don't
know which one would be the

158
00:20:07,300 --> 00:20:14,230
correct term for this. This one,
this nebulous one ebook. E dash

159
00:20:14,230 --> 00:20:18,730
book, electronic books, in some
ways, we're still trying to, you

160
00:20:18,730 --> 00:20:21,880
know, figure that out, out in
the real world, you'll see it in

161
00:20:21,880 --> 00:20:26,380
different places, so much like
you might have a style guide for

162
00:20:26,380 --> 00:20:30,160
publication that might give you
guidance about which one of

163
00:20:30,160 --> 00:20:35,680
these things to use in the
library, and our catalog. We

164
00:20:35,680 --> 00:20:38,560
need some sort of guidance as to
which of these terms is the

165
00:20:38,560 --> 00:20:43,630
correct one to use. So, So
that's what an authority, would

166
00:20:43,630 --> 00:20:49,540
be right, and authorities can
change over time. For example,

167
00:20:49,540 --> 00:20:54,670
we had a cookery for the longest
time was the authorized forum

168
00:20:54,670 --> 00:21:00,970
for any sort of cookbook subject
term. At some point in the past

169
00:21:01,000 --> 00:21:06,040
10 years it's switched over to
cooking, and millions of catalog

170
00:21:06,040 --> 00:21:09,280
records have to be updated with
that new terminology.

171
00:21:12,270 --> 00:21:13,560
Probably preferred.

172
00:21:16,199 --> 00:21:20,219
So then what is the authority to
control. What's the consistent

173
00:21:20,219 --> 00:21:23,579
use and maintenance of the forms
of the names. So this is the

174
00:21:23,579 --> 00:21:28,829
work that you do. In order to
keep your authorities, under

175
00:21:28,829 --> 00:21:32,279
control. Right. Otherwise, as
you're loading records as you're

176
00:21:32,279 --> 00:21:37,499
cataloging records, creating new
subject terms, new authors

177
00:21:37,529 --> 00:21:41,099
coming in. Authors changing
names and things like that.

178
00:21:41,579 --> 00:21:45,749
Like, like a garden, it's got to
get out of control, unless you

179
00:21:45,749 --> 00:21:48,119
put some control over it, you
got to weed your garden you got

180
00:21:48,119 --> 00:21:51,839
to weed your catalog, you have
to weed, your subject terms, you

181
00:21:51,839 --> 00:21:56,999
have to weed your authored
names. So, authority control is

182
00:21:56,999 --> 00:22:05,039
the name of the game here. So,
it's easy to get to get into the

183
00:22:05,039 --> 00:22:08,459
weeds per se, as far as whether
you're using the proper heading.

184
00:22:09,779 --> 00:22:13,559
But I think it's useful to
remember that the end goal

185
00:22:13,589 --> 00:22:17,879
really is to make searching in
your catalog easier for your

186
00:22:17,879 --> 00:22:21,929
user. So, as long as you kind of
keep that in the back of your

187
00:22:21,929 --> 00:22:24,809
head or once in a while kind of
put it into the front of your

188
00:22:24,809 --> 00:22:32,309
mind. I think it will serve as a
motivating force for you. For

189
00:22:32,309 --> 00:22:35,759
me, a good thing to do is to
kind of take a look at your

190
00:22:35,759 --> 00:22:40,289
catalog in the same way that
your users might, might see it.

191
00:22:42,449 --> 00:22:43,439
So,

192
00:22:45,629 --> 00:22:47,459
just to make a quick point about

193
00:22:49,250 --> 00:22:54,500
Authorities and Enterprise, one
we had the elibrary catalog. The

194
00:22:54,530 --> 00:23:00,140
authority database, and the
indexes were closely tied they

195
00:23:00,170 --> 00:23:04,160
often were the very same indexes
and searches that you would do

196
00:23:04,160 --> 00:23:07,670
in Workflows Symphony Workflows
would be the same as he would

197
00:23:07,670 --> 00:23:12,290
find in the public catalog,
elibrary with the broader

198
00:23:12,290 --> 00:23:16,910
adoption now Enterprise among
the LOUIS libraries, you'll find

199
00:23:16,910 --> 00:23:20,630
that it's not a one to one sort
of match.

200
00:23:21,989 --> 00:23:24,269
But, but it's still important

201
00:23:25,589 --> 00:23:27,209
show, so a couple examples here.

202
00:23:29,910 --> 00:23:35,190
This is a screenshot from the
Enterprise catalog, wherein.

203
00:23:36,030 --> 00:23:42,960
I've looked at the subject
facet. And I clicked this A to

204
00:23:42,960 --> 00:23:45,690
Z. I don't know if you can see
my cursor right here. Click the

205
00:23:45,690 --> 00:23:49,200
A to Z so I can alphabetize the
subject headings that are being

206
00:23:49,200 --> 00:23:54,540
used. and here we can see this
this is something that happens a

207
00:23:54,540 --> 00:24:00,570
lot. among a lot of our LOUIS
catalogs is we'll get subject

208
00:24:00,570 --> 00:24:07,110
headings that have slight
differences in this case this

209
00:24:07,110 --> 00:24:13,830
anaesthesia methods. One has a
period, one doesn't. Same here.

210
00:24:15,090 --> 00:24:19,200
Cats and cats and what that
means for the user is that if

211
00:24:19,200 --> 00:24:23,130
they do want to do a subject
search, usually typing it in

212
00:24:23,130 --> 00:24:27,030
they're going to find it but if
they wanted to narrow it down by

213
00:24:27,030 --> 00:24:28,170
selecting by

214
00:24:29,519 --> 00:24:32,429
hitting these checkboxes right
here and then doing include.

215
00:24:33,800 --> 00:24:37,130
You know, they have to have to
hit it twice right there. So you

216
00:24:37,130 --> 00:24:41,810
know might not seem like a big
deal but you know it's a lot for

217
00:24:41,810 --> 00:24:46,550
one it will make your list here
a lot shorter, but with some

218
00:24:46,550 --> 00:24:49,940
authority control. If you went
in and authorized these you

219
00:24:49,940 --> 00:24:54,560
could combine these terms, you
could verify your spelling's and

220
00:24:54,590 --> 00:25:00,860
make sure everything's neat and
tidy. Ah, oh the same screenshot

221
00:25:00,860 --> 00:25:07,190
just a little bit easier to see
bigger. This and better, better

222
00:25:07,190 --> 00:25:12,320
in there, in a seizure cats and
cats separately. These numbers

223
00:25:12,320 --> 00:25:15,290
on the side are the number of
records that have those subject

224
00:25:15,290 --> 00:25:23,390
terms. So oftentimes you'll see,
you'll see a subject term that

225
00:25:23,660 --> 00:25:29,330
only has one. You know usually
that's kind of a one off, sort

226
00:25:29,330 --> 00:25:38,750
of thing there. This. This is an
example that we hit a lot in in

227
00:25:38,750 --> 00:25:43,280
the public library sphere. But
this is taken from one of our

228
00:25:43,280 --> 00:25:47,090
academic libraries. The author,
looking at doesn't have to be

229
00:25:47,150 --> 00:25:50,720
just subject terms but author
names can kind of get out of

230
00:25:50,720 --> 00:25:54,680
control too so if you take a
popular author like James

231
00:25:54,680 --> 00:25:59,420
Patterson. And this is the
authorized heading right here

232
00:25:59,420 --> 00:26:05,150
with the 35 instances of James
Patterson. It's 1947 James

233
00:26:05,150 --> 00:26:09,710
Patterson, but it's a common
enough name, James and

234
00:26:09,710 --> 00:26:16,430
Patterson, that there are
dozens, in most catalogs, if,

235
00:26:16,460 --> 00:26:24,440
if, I'll say few dozens, if not
more, in, in these catalogs.

236
00:26:25,640 --> 00:26:30,860
James T there, James D, James
Dean Patterson seems to have a

237
00:26:30,860 --> 00:26:36,350
lot of records in our catalog.
So, you know, some of these,

238
00:26:36,380 --> 00:26:39,320
they're not together because
like this, James T right here

239
00:26:39,320 --> 00:26:45,410
has the extra, comma, but other
ones it's a little bit unclear

240
00:26:45,410 --> 00:26:53,090
about as to what the authorized
subject term might be RDA

241
00:26:53,090 --> 00:26:57,500
records, you don't notice have a
lot of will have this

242
00:26:57,530 --> 00:27:03,740
designation of what what their
role is author, in this case, so

243
00:27:03,740 --> 00:27:06,200
you might get some discrepancy
there and that's some cleanup

244
00:27:06,200 --> 00:27:11,810
that a lot of catalogers have to
do since those changes, those

245
00:27:11,810 --> 00:27:16,760
additional fields were added. So
ideally you would have this 1947

246
00:27:16,760 --> 00:27:20,750
and this 1947 James Patterson
combined. Same with these

247
00:27:20,750 --> 00:27:25,280
Williams here, and then notice
there's a James Patterson, we

248
00:27:25,280 --> 00:27:28,760
don't know who that is. So we
have to look at that record and

249
00:27:28,760 --> 00:27:32,240
figure out which of all these
James Patterson's might be the

250
00:27:32,240 --> 00:27:37,490
one that we're looking for. and
didn't didn't fall in

251
00:27:37,490 --> 00:27:41,090
alphabetically on the screenshot
but way up here, there's some

252
00:27:41,090 --> 00:27:46,070
James Patterson's flipped
around. Instead of Patterson

253
00:27:46,070 --> 00:27:50,900
James. So let me talk a little
bit now about the authority

254
00:27:50,900 --> 00:27:57,890
database. In Symphony, in
particular, so you know some

255
00:27:58,160 --> 00:28:02,420
Authority Database, simply is
just all of the Loaded Authority

256
00:28:02,420 --> 00:28:08,990
Records. Also within Symphony,
are these Authority Indexes, and

257
00:28:08,990 --> 00:28:13,430
the indexes can include the
authorized, and authorized

258
00:28:13,430 --> 00:28:18,170
headings and also improper
headings in Symphony, we tend to

259
00:28:18,170 --> 00:28:23,720
have two main indexes. One would
be the Library Congress Name

260
00:28:23,720 --> 00:28:27,620
Terms, and the other one would
be the Library of Congress

261
00:28:27,650 --> 00:28:31,550
Subject Headings. But that's not
to say that each library only

262
00:28:31,550 --> 00:28:34,490
has those two. A lot of
libraries have more than those

263
00:28:34,490 --> 00:28:39,560
two. And, for example, some
might have the Medical Subject

264
00:28:39,560 --> 00:28:43,010
Headings as a separate index,
the mesh and it makes it a

265
00:28:43,010 --> 00:28:47,210
little easier to control for
those things when they are in

266
00:28:47,210 --> 00:28:50,390
separate indexes you can keep
your Mesh headings which can, a

267
00:28:50,390 --> 00:28:52,700
lot of times be very similar to
your Library of Congress

268
00:28:52,700 --> 00:28:56,810
headings. You can keep them
separate and cleaned up.

269
00:28:58,439 --> 00:28:58,949
That way,

270
00:29:00,490 --> 00:29:05,470
kind of on the back end. Is this
something called a authority,

271
00:29:05,770 --> 00:29:10,900
thesauri plural thesaurus,
thesaurus nobody wants to say,

272
00:29:11,050 --> 00:29:15,130
so it's your, your chance to use
the word thesauri. In a

273
00:29:15,130 --> 00:29:21,100
sentence, but the authority
authority of the thesauri are in

274
00:29:21,100 --> 00:29:25,480
this should be plural right are
a separate file files that

275
00:29:25,480 --> 00:29:28,630
provide relationships between
terms and creates cross

276
00:29:28,630 --> 00:29:32,740
references. And so in Symphony
we have the author, title and

277
00:29:32,920 --> 00:29:38,140
subject thesauri you don't edit
them directly but you can. When

278
00:29:38,140 --> 00:29:41,560
you do things to the indexes and
databases. It will update

279
00:29:41,740 --> 00:29:49,570
thesauri. So a big part of
authority control is heading

280
00:29:49,570 --> 00:29:54,400
validation. And you can have
three types of heading

281
00:29:54,400 --> 00:29:59,500
validation in Symphony. You can
have a cross references only you

282
00:29:59,500 --> 00:30:05,020
can have case insensitive
checking where the case if it's

283
00:30:05,020 --> 00:30:08,890
upper or lower case doesn't
matter. And then you can have a

284
00:30:08,890 --> 00:30:16,000
case sensitive checking. So, for
case significance or case

285
00:30:16,000 --> 00:30:18,460
sensitive checking the
bibliographic headings you know

286
00:30:18,460 --> 00:30:21,730
they have to be exactly the same
I've got the example here of

287
00:30:21,760 --> 00:30:26,560
goat farming. Subject near and
dear to my heart. Goat farming

288
00:30:26,560 --> 00:30:29,680
with a capital F might come in
as the bibliographic subject

289
00:30:29,680 --> 00:30:34,780
term, it would not be considered
a match for the authorized goat

290
00:30:34,780 --> 00:30:40,270
farming with the small f. If you
had case sensitive checking. And

291
00:30:40,270 --> 00:30:47,050
I did a little server checking
and I found that all LOUIS sites

292
00:30:47,050 --> 00:30:51,310
are currently configured per
case sensitive checking. So, I

293
00:30:51,310 --> 00:30:56,560
was curious and had to know. So
that's good. So the way you do

294
00:30:56,560 --> 00:31:00,970
Heading Validation. Most of the
time, you're going to be in. In

295
00:31:00,970 --> 00:31:05,500
your Modified Title Wizard in
Symphony. And at the very top of

296
00:31:05,500 --> 00:31:10,360
it, top, maybe the second little
helper there is the validate

297
00:31:10,390 --> 00:31:14,710
headings helper. You click on
that helper and it's going to go

298
00:31:14,710 --> 00:31:20,050
through the record and validate,
all of the unauthorized headings

299
00:31:20,380 --> 00:31:25,600
that are in that record, you'll
be presented with some choices

300
00:31:25,600 --> 00:31:29,560
there, browse which is to search
the list of headings in

301
00:31:29,560 --> 00:31:34,030
alphabetical order, like any
browse list would be. You can

302
00:31:34,810 --> 00:31:37,450
get from lists, which is to
replace the heading that you've

303
00:31:37,990 --> 00:31:41,560
that you're looking at, with the
selected heading. The skip and

304
00:31:41,560 --> 00:31:44,770
skip rest. What that means is
that it's checking all of the

305
00:31:44,770 --> 00:31:48,580
unauthorized headings in that
record all at once, or one by

306
00:31:48,580 --> 00:31:52,990
one, you know for that whole
record. So you could decide to

307
00:31:52,990 --> 00:31:56,230
not decide and skip a heading,
and then move to the next one in

308
00:31:56,230 --> 00:31:59,410
the record. And then propose
means you want to make a new

309
00:31:59,410 --> 00:32:03,460
authority record based on the
heading. And here's a screenshot

310
00:32:03,460 --> 00:32:09,400
of that. There's the buttons on
the left. This was an you know

311
00:32:09,400 --> 00:32:12,670
when a heading is unauthorized
and Symphony. If you're in

312
00:32:12,670 --> 00:32:16,720
modify title. The name of the
wizard there, because this

313
00:32:16,750 --> 00:32:19,840
unauthorized question mark
unauthorized appears as a

314
00:32:19,840 --> 00:32:26,350
subfield next to it, you do not
see this unauthorized, then you

315
00:32:26,350 --> 00:32:29,470
can assume went to the next one,
you can assume that it's

316
00:32:29,470 --> 00:32:30,790
authorized at that point.

317
00:32:34,859 --> 00:32:35,549
So that's the.

318
00:32:37,070 --> 00:32:42,110
That was an author and this was
a subject heading, goat farming.

319
00:32:42,620 --> 00:32:49,850
And then if I wanted to. At that
point, get from list. I cut off

320
00:32:49,880 --> 00:32:54,470
the what I'm seeing in the
Browse list there. But then, if

321
00:32:54,470 --> 00:32:58,310
I were to look at this, the
authority.

322
00:33:00,839 --> 00:33:03,839
This actually this is why I'm
proposing one, I think.

323
00:33:05,700 --> 00:33:12,960
Anyway, the subject term is goat
farming and will this top part

324
00:33:12,990 --> 00:33:19,260
are the fixed fields and then
the fields below about explain

325
00:33:19,260 --> 00:33:24,180
what those are. Okay, so the
authority fixed fields. You can

326
00:33:24,180 --> 00:33:28,440
have an Authority Level.
Authorities can be authorized,

327
00:33:29,250 --> 00:33:32,580
or they can be provisional
typically you might mark one is

328
00:33:32,580 --> 00:33:37,230
provisional if you have a team
of people looking at it. You

329
00:33:37,230 --> 00:33:42,390
might have junior staff members,
checking these things and then

330
00:33:42,420 --> 00:33:46,080
marking authorities as
provisional, and then somebody

331
00:33:46,080 --> 00:33:50,310
can come back and check it
behind them and authorize it

332
00:33:51,030 --> 00:33:55,680
might be a way to do that. You
have different authority types,

333
00:33:56,880 --> 00:34:00,510
established heading, or the
establish heading and

334
00:34:00,510 --> 00:34:03,390
subdivision as an example
there's more values that are

335
00:34:03,450 --> 00:34:08,610
valid here but these are, you
know, the most common. That's

336
00:34:08,610 --> 00:34:12,390
what those letters and next to
it are the code for those. The

337
00:34:12,390 --> 00:34:18,870
name use these name use subject
uses zero use you kind of think

338
00:34:18,870 --> 00:34:22,680
of those three all at the same
time, 'A' means basically yes

339
00:34:22,680 --> 00:34:26,160
this is used for this thing it's
appropriate, or 'B' not

340
00:34:26,160 --> 00:34:30,810
appropriate. So here's a
screenshot of that. And I'm not

341
00:34:30,810 --> 00:34:33,210
going to list out every one of
the fixed fields, but I just

342
00:34:33,210 --> 00:34:37,920
wanted to pick those out as some
of the more interesting ones to

343
00:34:38,010 --> 00:34:38,760
look at.

344
00:34:40,110 --> 00:34:42,600
If you right click on any one of
those values.

345
00:34:43,889 --> 00:34:48,599
Right here. Whenever you were in
modified title, or when you're

346
00:34:48,599 --> 00:34:52,529
modifying authority. You will
get you'll be presented with a

347
00:34:52,529 --> 00:34:55,139
list of all the appropriate
values.

348
00:34:56,700 --> 00:35:00,780
With the code, and with, you
know kind of what it means.

349
00:35:04,020 --> 00:35:07,680
So that part below the fixed
fields where the you know the

350
00:35:07,680 --> 00:35:11,730
record fields themselves. You
know the established headings or

351
00:35:11,730 --> 00:35:16,680
the or the one xx personal name
would be 100. Subject authority

352
00:35:16,680 --> 00:35:21,180
be 150, there's more of them
there. But you know those are

353
00:35:21,180 --> 00:35:27,420
the big ones. The four xx are
called see from headings. These

354
00:35:27,420 --> 00:35:29,460
are the forms that have a
heading that aren't valid for

355
00:35:29,460 --> 00:35:36,390
use that, you know, 400 for the
personal name that 00 is name,

356
00:35:36,390 --> 00:35:41,880
you know, and then 50 for
subject for subject. So 450 In

357
00:35:41,880 --> 00:35:46,260
that case, and then the See also
headings. These are other

358
00:35:46,410 --> 00:35:49,560
established headings that are
related to this heading that

359
00:35:49,560 --> 00:35:53,490
you're looking at. And the same
sort of thing, you know, zero to

360
00:35:53,520 --> 00:35:59,880
500 would be personal name and
550 subject. There's more than

361
00:35:59,880 --> 00:36:04,320
one to six xx are notes, those
notes can be configured for, you

362
00:36:04,320 --> 00:36:10,170
know, staff use only or public
view, things like that. So

363
00:36:10,170 --> 00:36:13,230
here's an example just sort of
kind of a random one I was

364
00:36:13,230 --> 00:36:17,280
looking at to Chitimacha
Indians, as the established term

365
00:36:17,280 --> 00:36:23,130
150. These see from, you could
type in to your system Chitmacha

366
00:36:23,460 --> 00:36:30,150
Indians, and it would bring you
to this Chitmacha Indian, in a

367
00:36:30,150 --> 00:36:34,710
sense, and then. See also
Indians of North America,

368
00:36:34,740 --> 00:36:40,140
Louisiana. You know Chitimacha
Indians are, you know, a tribe

369
00:36:40,140 --> 00:36:42,780
from Louisiana. I mean,

370
00:36:45,840 --> 00:36:48,240
some useful reports that

371
00:36:49,560 --> 00:36:54,030
you might want to be aware of
the List Unauthorized Tags

372
00:36:54,030 --> 00:37:00,750
Report is a way to get a list of
all the unauthorized headings

373
00:37:00,750 --> 00:37:04,260
that you might have in your
system. If you haven't done this

374
00:37:04,260 --> 00:37:07,860
before it might be scary to look
at it. Just wide open so you

375
00:37:07,860 --> 00:37:10,620
might, you know, think of some
ways to narrow down the

376
00:37:10,620 --> 00:37:15,660
criteria. It's apparently an
informational report. Doesn't

377
00:37:15,660 --> 00:37:20,070
make any changes but it gives
you some ideas for things to

378
00:37:20,070 --> 00:37:24,210
clean up to authorize or Also,
if you're doing original

379
00:37:24,210 --> 00:37:32,130
cataloging. You might identify
some tags that you could propose

380
00:37:32,130 --> 00:37:39,420
to larger systems, NEKO, or
things like that, then another

381
00:37:39,420 --> 00:37:42,720
one to look at are these
authority headings without bibs,

382
00:37:43,020 --> 00:37:46,410
this would be authority headings
that don't have associated

383
00:37:46,830 --> 00:37:52,050
bibliographic records, also
known as a blind reference. It

384
00:37:52,290 --> 00:37:55,200
only, again, it's informational
it lists the records doesn't

385
00:37:55,200 --> 00:37:58,050
make the changes, but you can go
in there and delete the

386
00:37:58,050 --> 00:38:03,450
authorities. So that's my high
level view of Authorities in

387
00:38:03,450 --> 00:38:08,520
Symphony. I went to the Support
Center, SirsiDynix Support

388
00:38:08,520 --> 00:38:13,950
Center, and found a lot of
these, but good documents there

389
00:38:13,980 --> 00:38:14,880
and training.

390
00:38:16,680 --> 00:38:17,490
They've got

391
00:38:18,780 --> 00:38:21,090
a lot of things to read right
here, but also.

392
00:38:22,410 --> 00:38:26,790
This short Authority Control or
Working with Authority Self

393
00:38:26,790 --> 00:38:31,080
Paced this was about a 20 minute
20 to 30 minute class, I'd

394
00:38:31,080 --> 00:38:35,310
recommend that for anybody.
Especially now that Mentor is

395
00:38:35,820 --> 00:38:39,870
free training for most of us,
there's also this, it's a bit

396
00:38:39,870 --> 00:38:43,020
older, this Authority Control
Reference Manual but it seemed

397
00:38:43,020 --> 00:38:46,140
had the most detailed
information about the databases

398
00:38:46,140 --> 00:38:51,570
and indexes and thesauri. Inside
of Symphony. And then, of

399
00:38:51,570 --> 00:38:55,080
course, just a fun place to kind
of poke around, but it's you

400
00:38:55,080 --> 00:38:57,570
know a reference out of these
Library of Congress Authorities.

401
00:38:58,350 --> 00:39:02,670
So with that, I will turn it
over to Zee Zee

402
00:39:04,230 --> 00:39:06,990
to tell you about how we load
these records.

403
00:39:09,540 --> 00:39:12,000
And I don't think I have to do
anything I think Zee Zee you can

404
00:39:12,000 --> 00:39:14,910
just shift start sharing your
screen, or do I have to stop

405
00:39:14,910 --> 00:39:15,330
sharing,

406
00:39:15,570 --> 00:39:16,560
just stop sharing.

407
00:39:17,280 --> 00:39:18,930
Right now we got to find the
button.

408
00:39:26,430 --> 00:39:28,620
Look at the very top of the
screen.

409
00:39:29,580 --> 00:39:30,210
Oh, there it is.

410
00:39:31,500 --> 00:39:33,750
Oh, yay, I did it.

411
00:39:37,380 --> 00:39:42,660
Share screen, and to teach you
can see it.

412
00:39:45,960 --> 00:39:47,490
Can y'all see my screen.

413
00:39:48,840 --> 00:39:50,790
It's, it looks like it's
starting up.

414
00:39:51,960 --> 00:39:53,850
You see it now. Yeah.

415
00:39:56,780 --> 00:40:00,050
Good afternoon. I'm Zee Zee and
we're going to show you how to

416
00:40:00,050 --> 00:40:05,330
load a file authority records.
So, you can really use

417
00:40:05,330 --> 00:40:09,380
SmartVault to get authority
records, you can connect to OCLC

418
00:40:09,620 --> 00:40:15,740
or Library of Congress, or even
another site, the search box.

419
00:40:17,150 --> 00:40:20,540
Select record and drop it into
your catalog, but you can also

420
00:40:20,540 --> 00:40:25,100
subscribe to a party services
from a vendor, like SirsiDynix

421
00:40:25,130 --> 00:40:25,790
or Marcive

422
00:40:27,020 --> 00:40:28,880
So before I show you

423
00:40:28,810 --> 00:40:33,460
the details of how to load an
authority file. Let me just take

424
00:40:33,460 --> 00:40:37,960
a minute and give you a very
brief background of the options

425
00:40:37,960 --> 00:40:43,510
provided by both descenders. So
SirsiDynix offers two options,

426
00:40:43,570 --> 00:40:47,020
the full underlying the full
authority record the lightest

427
00:40:47,020 --> 00:40:50,290
party record but they also offer
the authority update service

428
00:40:50,290 --> 00:40:55,060
which is ongoing, it's hard to
book. So guys this session is

429
00:40:55,060 --> 00:40:59,050
being recorded, so you can go
ahead and read the details later

430
00:40:59,050 --> 00:41:03,730
on at your leisure. Marcive also
provides similar authority

431
00:41:03,730 --> 00:41:06,850
options. They have the
authority, update, which is

432
00:41:06,910 --> 00:41:11,200
ongoing authority work. And here
they provide you with overnight

433
00:41:11,200 --> 00:41:16,030
authorities, or monthly
notification service. And the

434
00:41:16,030 --> 00:41:19,840
point they try to make every
time is that they don't provide

435
00:41:19,840 --> 00:41:23,410
any light authority work,
everything is full level

436
00:41:23,410 --> 00:41:28,090
authority. And they also provide
some additional options here.

437
00:41:28,660 --> 00:41:34,930
That again you all can read the
details later on. We have the

438
00:41:34,930 --> 00:41:40,360
cost for both these vendors.
It's based on the number of big

439
00:41:40,360 --> 00:41:46,930
records in your catalog.
SirsiDynix will stand and reload

440
00:41:46,930 --> 00:41:49,630
the records for the initial
implementation, and they will

441
00:41:49,630 --> 00:41:53,860
also do it for the ongoing
authority work. But the best

442
00:41:53,860 --> 00:41:56,950
part with them is that they
resolve the unauthorized

443
00:41:56,950 --> 00:42:00,400
headings in your web records
that Mike was showing just now.

444
00:42:01,450 --> 00:42:06,130
Mark Guard for the initial
extract and reload. You have to

445
00:42:06,130 --> 00:42:10,450
be involved, or LOUIS was always
there to help you. And for that

446
00:42:10,450 --> 00:42:13,210
you can schedule the Gibbons
heading and he will text

447
00:42:13,210 --> 00:42:19,090
reports. But for the overnight
authorities and the update

448
00:42:19,090 --> 00:42:23,620
authority services. Most of the
time don't need to rebuild

449
00:42:23,620 --> 00:42:27,520
heading in text reports. The
good point with their services

450
00:42:27,550 --> 00:42:32,260
that they provide fifth party
records for any documents that

451
00:42:32,260 --> 00:42:36,520
you have in your catalog. So for
the sites that are using large

452
00:42:36,730 --> 00:42:40,180
loads of government documents.
This is really quite a boon.

453
00:42:42,070 --> 00:42:43,210
We have a

454
00:42:43,210 --> 00:42:45,340
question. Sorry to interrupt

455
00:42:47,320 --> 00:42:47,980
You want to add.

456
00:42:50,420 --> 00:42:55,610
Yes, from Louisiana Tech Dale
I'm sorry. Does it show that we

457
00:42:55,610 --> 00:43:02,360
have Marcive or not, is that
what I'm looking at. Are we okay

458
00:43:02,360 --> 00:43:07,010
so I guess, again I just hope
that I just started recently but

459
00:43:08,330 --> 00:43:13,010
it moved kind of quick to this
pandemic here but haven't got a

460
00:43:13,010 --> 00:43:16,460
chance to grab everything before
I went back home to Houston but

461
00:43:16,490 --> 00:43:22,520
anyhow. So Marcive do they have,
I guess, a schedule run with us

462
00:43:22,520 --> 00:43:25,370
to clean up the records at this
point or is it something I can

463
00:43:25,370 --> 00:43:28,040
look at a contract or how does
that work.

464
00:43:29,370 --> 00:43:33,690
So, I can send you the details.
At the end of the session. But

465
00:43:33,690 --> 00:43:37,710
yeah, not to contact them. Yeah,
you will have to send extract

466
00:43:37,710 --> 00:43:41,850
your records from the last time
the load and the cleanup was

467
00:43:41,850 --> 00:43:45,150
done, and they will be glad to
give you a price for that.

468
00:43:46,050 --> 00:43:50,580
Yeah, Yeah, again just coming in
there at this particular time in

469
00:43:50,580 --> 00:43:54,090
January in January, it's just
been a little bit of a challenge

470
00:43:54,090 --> 00:44:00,390
to see how far back, Louisiana
Tech has been in. I, since I've

471
00:44:00,390 --> 00:44:02,940
been there I've been trying to
clean it up as much as possible

472
00:44:02,940 --> 00:44:06,840
and there's just so much but I
do like what Mike brought up

473
00:44:06,840 --> 00:44:12,120
also some more cleaning up with
the unauthorized records. I'm

474
00:44:12,120 --> 00:44:16,020
sure we're going to find a few
of them out there in our systems

475
00:44:16,050 --> 00:44:21,150
but uh but if Marcive is doing
that. I think that takes care of

476
00:44:21,150 --> 00:44:22,440
some stuff for me as well.

477
00:44:23,669 --> 00:44:24,539
Yes, the way

478
00:44:25,979 --> 00:44:31,349
you have a charge for it. So, if
you open a task ticket for it.

479
00:44:31,529 --> 00:44:35,429
I'll be glad to get them to
identify when was the last load

480
00:44:35,429 --> 00:44:39,209
done for you all, and how much
would it cost to extract your

481
00:44:39,209 --> 00:44:41,219
records and clean it up all over
again.

482
00:44:41,789 --> 00:44:45,569
I deeply appreciate it I know
I'm still trying to grasp as

483
00:44:45,569 --> 00:44:50,969
much stuff with Louisiana Tech
and work, working from home it's

484
00:44:50,969 --> 00:44:55,529
been really interesting. So, but
I know those are some of the

485
00:44:55,529 --> 00:44:59,789
areas that I see that it was
needed to clean up a system but

486
00:44:59,789 --> 00:45:03,659
that's just any other libraries,
you can just keep on digging and

487
00:45:03,659 --> 00:45:06,119
digging and digging and find
something that needs to be

488
00:45:06,119 --> 00:45:09,719
cleaned up. Yeah, let us. Thanks
again for that. Yeah.

489
00:45:11,160 --> 00:45:16,830
So for SirsiDynix we have six
sites that are using services,

490
00:45:17,040 --> 00:45:21,480
five of them use the light
option, and only one slide that

491
00:45:21,480 --> 00:45:25,860
uses the full option, whereas
for Marcive we have nine sites

492
00:45:25,860 --> 00:45:32,070
using Marcive. And you'll notice
that LSU, and Louisiana Tech

493
00:45:32,070 --> 00:45:36,600
have reason default is for
government documents. So for

494
00:45:36,600 --> 00:45:40,200
them it makes perfect sense to
get free authority records for

495
00:45:40,200 --> 00:45:44,700
Google Docs also. Now, if any
other side is interested in

496
00:45:44,700 --> 00:45:48,540
getting authority records for
them, just send in a task

497
00:45:48,540 --> 00:45:53,370
tickets, and I'll be glad to get
the cost and the details from

498
00:45:53,370 --> 00:45:58,080
both vendors so that you can
make your decisions. Okay, so

499
00:45:58,080 --> 00:46:02,550
now moving on to how to load
authority records from Marcive.

500
00:46:03,000 --> 00:46:07,620
I am going to provide a lot of
screenshots, so that you can use

501
00:46:07,620 --> 00:46:13,770
this document later on and load
your authority files. So what

502
00:46:13,770 --> 00:46:18,240
does Marcive send you. They send
you an email that information,

503
00:46:18,660 --> 00:46:23,280
download. Record the file of
authority records are there to

504
00:46:23,280 --> 00:46:28,800
FTP, or you can use the browser
to download the files in the

505
00:46:28,800 --> 00:46:32,040
browser, it looks like this and
all you have to do is drag and

506
00:46:32,040 --> 00:46:35,430
drop them. But the important
thing to notice is the number of

507
00:46:35,430 --> 00:46:38,550
records in the file, because
this is the number you're going

508
00:46:38,550 --> 00:46:44,700
to track throughout the load
process. Load in authority file

509
00:46:44,700 --> 00:46:48,750
is really a three step process
you number one you have to get

510
00:46:48,750 --> 00:46:52,440
those hard to find, and you use
them archive email for that.

511
00:46:52,980 --> 00:46:57,600
Number two, you have to add it
to import it to the server, and

512
00:46:57,630 --> 00:47:01,200
I strongly recommend that
everyone get in the habit of

513
00:47:01,200 --> 00:47:05,010
loading to the tester. First,
and after that if everything is

514
00:47:05,010 --> 00:47:08,880
fine, move to production. To
import it or add it to the

515
00:47:08,880 --> 00:47:13,050
server you need to use the
utilities to that. And the third

516
00:47:13,050 --> 00:47:16,590
step is to load it into the
catalog using the report called

517
00:47:16,650 --> 00:47:22,320
authority load. So let's pretend
that I have received the email

518
00:47:22,320 --> 00:47:27,450
from Marcive. I've got my file.
It has four records, and I have

519
00:47:27,450 --> 00:47:31,260
saved it to my desktop. So now I
have to move to step number two

520
00:47:31,260 --> 00:47:34,860
which is added to this server
imported the file into this

521
00:47:34,860 --> 00:47:41,070
server using the utilities
toolbar to go to, utilities, and

522
00:47:41,100 --> 00:47:47,100
click on Marc Import to get the
criteria screen. Here is a

523
00:47:47,100 --> 00:47:52,680
better shot of that screen,
you're going to use. And you're

524
00:47:52,680 --> 00:47:56,130
going to use the gadget to
browse to the spot where you

525
00:47:56,130 --> 00:48:01,320
save the file. In my case, I
save the desktop, its

526
00:48:01,350 --> 00:48:04,860
destination feel that you need
to add a meaningful name,

527
00:48:04,890 --> 00:48:07,920
something that will make sense
to you, and this is the name

528
00:48:08,130 --> 00:48:10,920
that you're going to see when
you use the authority load

529
00:48:10,920 --> 00:48:15,630
report. So make it meaningful
sites, often use the month they

530
00:48:15,630 --> 00:48:19,350
received the data received, or
they put the initials of who's

531
00:48:19,350 --> 00:48:21,750
the person who's doing the load
just so that they can keep a

532
00:48:21,750 --> 00:48:26,490
track of it. Once you click
Import. You get a pop up that

533
00:48:26,490 --> 00:48:29,910
says, Are there any more files
to load the Marcive has got a

534
00:48:29,910 --> 00:48:34,950
large file broken into multiple
files. Please come back here

535
00:48:34,950 --> 00:48:38,490
browse to find number two, and
when it's important, it gets

536
00:48:39,180 --> 00:48:44,190
appended to file number one. If
you have only a single file and

537
00:48:44,190 --> 00:48:48,600
save, and the file will get
imported into the test server or

538
00:48:48,600 --> 00:48:52,230
the production server whichever
one you use, and you get the

539
00:48:52,230 --> 00:48:57,780
input log. This is a very good
visual for you. Go ahead and

540
00:48:57,780 --> 00:49:00,150
have a look at the number of
records converted, but the most

541
00:49:00,150 --> 00:49:03,990
important part is at the bottom,
which is how many records are

542
00:49:03,990 --> 00:49:08,490
processed, my file had four
records so great, everything has

543
00:49:08,490 --> 00:49:12,390
been loaded onto the server
successfully. So this means I

544
00:49:12,390 --> 00:49:16,680
can move on to step number
three, which is, add the records

545
00:49:16,860 --> 00:49:23,610
to my catalog, using the report.
So click on the reports tool

546
00:49:23,610 --> 00:49:29,520
bar. Come to the parties tab and
select the records report.

547
00:49:31,640 --> 00:49:38,120
In the authority data file tab.
If you can use the drop down to

548
00:49:38,120 --> 00:49:41,150
select the file that you had
just imported. Remember we gave

549
00:49:41,150 --> 00:49:46,100
it the name Authority Demo Four.
There it is. For more, if it's a

550
00:49:46,100 --> 00:49:48,830
brand new file that you're
getting from Marcive and

551
00:49:48,830 --> 00:49:52,880
selecting the Create. Most of
the time, Marcive will be

552
00:49:52,880 --> 00:49:56,840
sending you a mixed batch of new
records and updated records, so

553
00:49:56,840 --> 00:50:00,290
select Create an update. I think
this is the default, which comes

554
00:50:00,290 --> 00:50:07,370
anyway. The date catalog is as a
default set to the date of the

555
00:50:07,370 --> 00:50:12,590
load, but you can use the
gadgets to select the calendar,

556
00:50:12,830 --> 00:50:16,370
and any date that you want in
case you're tracking it for some

557
00:50:16,370 --> 00:50:26,150
reason. Now subfield five. This
is a neat feature for you. If

558
00:50:26,150 --> 00:50:31,160
you have in your existing
authority records. A note field,

559
00:50:31,190 --> 00:50:34,430
which you want to retain
something like Mike's that has

560
00:50:34,430 --> 00:50:40,580
no notes, how you earrings or
your classification practices,

561
00:50:40,760 --> 00:50:44,960
then all you need to do is put a
checkmark in this in this box

562
00:50:45,080 --> 00:50:52,430
and enter your OCLC code over
here to make it look like this

563
00:50:52,430 --> 00:50:57,830
you put a checkbox, you put your
OCLC code. Today, your existing

564
00:50:57,860 --> 00:51:02,600
authority record. If you have a
field with the same OCLC code in

565
00:51:02,600 --> 00:51:07,640
subfield file. This field now
becomes protected and it will

566
00:51:07,640 --> 00:51:11,390
not be overwritten with a new
authority record being loaded.

567
00:51:11,660 --> 00:51:15,020
Instead, it will get merged with
the new record that is

568
00:51:15,380 --> 00:51:19,520
overlaying, or it's a brand new
record. So once you have filled

569
00:51:19,520 --> 00:51:24,680
in the fields. Click Run now to
run your report. And once it's

570
00:51:24,710 --> 00:51:30,020
completed running, go ahead and
go to your finish reports. The

571
00:51:30,020 --> 00:51:32,480
first thing you're gonna do is
check the status, make sure it's

572
00:51:32,480 --> 00:51:36,410
okay there's no error, and then
view the report results, the

573
00:51:36,410 --> 00:51:42,170
load report results. So I can
see in this results that four

574
00:51:42,170 --> 00:51:45,290
records were read. Good. That's
the number I wanted and in my

575
00:51:45,290 --> 00:51:45,740
files

576
00:51:46,740 --> 00:51:51,240
there were no errors, zero
records were created, but four

577
00:51:51,240 --> 00:51:57,930
were replaced is good. So now my
authority load is done. This is

578
00:51:57,930 --> 00:52:02,550
it, you've loaded your authority
record, fine. But if you're like

579
00:52:02,550 --> 00:52:09,720
me, I'm always curious to see
and want to see. Did the records

580
00:52:09,720 --> 00:52:13,440
look correctly. What do they
look like. So normally I'd take

581
00:52:13,440 --> 00:52:17,040
a few records and spotted them
So scroll down and see the

582
00:52:17,040 --> 00:52:21,450
records that were loaded in my
test file, I have purposely

583
00:52:21,450 --> 00:52:25,500
loaded the name authority record
and the subject authority

584
00:52:25,500 --> 00:52:29,760
record. So to spot check them.
What I do is I look at the

585
00:52:29,760 --> 00:52:33,330
authority record number,
normally look at the last four

586
00:52:33,330 --> 00:52:38,490
digits, it's easy to remember.
So it's 1229. I swipe the title,

587
00:52:38,730 --> 00:52:44,400
and I go into my catalog toolbar
and modify authority and select

588
00:52:44,400 --> 00:52:48,540
the name index because this is a
name authority record based in

589
00:52:48,540 --> 00:52:53,370
my title selected from the hit
list and look at the details of

590
00:52:53,370 --> 00:52:56,700
the record the first thing I
check is, is the same authority

591
00:52:56,700 --> 00:53:02,670
record number, yes it is 1229,
and TA DA, there's my title. So

592
00:53:02,670 --> 00:53:06,780
for the subject authority
record. I do the same thing.

593
00:53:06,930 --> 00:53:14,160
Look at that party number 5525
swipe the title time, as, as the

594
00:53:14,160 --> 00:53:18,600
subject index, and the modifier
party paste in the title

595
00:53:18,780 --> 00:53:22,170
selected from the hit list.
Double check is the same

596
00:53:22,170 --> 00:53:28,050
authority number Yes, 5525. And
there it is. And that's it. Now

597
00:53:28,050 --> 00:53:31,680
I feeling satisfied, Marc
authority load was successful,

598
00:53:31,710 --> 00:53:35,580
everything looks good. So the
ideal scenario is that you have

599
00:53:35,670 --> 00:53:39,390
perfect records everything
matches, everything overlays,

600
00:53:39,450 --> 00:53:43,830
yeah right. Sometimes you're
going to get a load report which

601
00:53:43,830 --> 00:53:48,810
will indictate what you need to
do that certain records that are

602
00:53:48,810 --> 00:53:52,710
delete authority records need to
be removed. These will come in

603
00:53:52,710 --> 00:53:59,400
with the code D in position five
or the leader of the record. So

604
00:53:59,400 --> 00:54:04,170
you need to remove 'D'. And
you're going to get a list of

605
00:54:04,170 --> 00:54:07,890
records that require manual
intervention. Fortunately, we

606
00:54:07,890 --> 00:54:11,070
have manager who's going to tell
us how to take care of these

607
00:54:11,070 --> 00:54:15,420
errors. But before she does
that. Occasionally, once in a

608
00:54:15,420 --> 00:54:20,190
while. When you load that
authority file the load will not

609
00:54:20,190 --> 00:54:25,050
go through instant generate an
error. And it very clearly tells

610
00:54:25,050 --> 00:54:29,970
you, entry ID is not found the
entry ID number is this, and

611
00:54:29,970 --> 00:54:35,310
it's not found in this authority
format. And the reason is that

612
00:54:35,310 --> 00:54:39,090
the incoming record the file
that you're loading. It has a

613
00:54:39,090 --> 00:54:44,160
tag, which is missing and is
defined in this authority format

614
00:54:44,250 --> 00:54:49,830
policy to fix that you have to
go to the configuration toolbar.

615
00:54:50,220 --> 00:54:55,110
And since this tag is missing.
You have to add the tag create

616
00:54:55,110 --> 00:55:00,570
the tag. And once it's created,
you have to add it to this. This

617
00:55:00,570 --> 00:55:04,530
geograph format policy, the one
which is saying it's missing in

618
00:55:04,530 --> 00:55:08,520
this policy. So this is
something that normally the SIS

619
00:55:08,520 --> 00:55:12,450
admins, or the backup sis admins
will do, because they have

620
00:55:12,450 --> 00:55:17,400
access to the configuration
toolbar. I since we have three

621
00:55:17,400 --> 00:55:20,820
new sis admins, or new backup
sis admins, I'm going to show

622
00:55:20,820 --> 00:55:25,140
you how to do that, but please
remember, you can always open

623
00:55:25,140 --> 00:55:28,140
the task ticket, and I'll be
glad to take care of it for you.

624
00:55:29,410 --> 00:55:35,830
So to fix it. You go to the
format, it is missing so config

625
00:55:35,980 --> 00:55:40,180
authority format, select the
format in which it is missing.

626
00:55:40,690 --> 00:55:46,600
And by. And if you're like me,
you always click the increase

627
00:55:46,600 --> 00:55:50,230
tab and scroll down and double
check and say yeah, it didn't

628
00:55:50,230 --> 00:55:53,860
really missing. But if it is
missing you. The first step is

629
00:55:53,860 --> 00:55:57,610
you have to create that missing
tab, and for that you've been

630
00:55:57,610 --> 00:56:03,310
provided with a nice entry ID
helper. This cute looking a

631
00:56:03,310 --> 00:56:10,090
yellow labeled tab. So you click
it and it drops you into the net

632
00:56:10,450 --> 00:56:14,320
all the tags, which are
currently available for all the

633
00:56:14,320 --> 00:56:18,370
party format policies. So I
normally eyeball it and say

634
00:56:18,370 --> 00:56:22,300
yeah, sure enough, both 35 is
missing, I need to add it to

635
00:56:22,300 --> 00:56:28,690
create to click Create and enter
the name the description, and

636
00:56:28,810 --> 00:56:32,110
the rest of the region the
values, if it is for a single

637
00:56:32,110 --> 00:56:35,770
tag like we are doing just now
it's a single 35 tag, then the

638
00:56:35,770 --> 00:56:39,520
purpose should be authority. So
it looks like this, you enter

639
00:56:39,520 --> 00:56:43,630
the name to be very honest for
description you should go to LC

640
00:56:43,690 --> 00:56:47,290
authorities page and pick up the
correct description for the tag.

641
00:56:47,530 --> 00:56:50,500
I just added it here geograph
just to show that this is the

642
00:56:50,500 --> 00:56:55,480
one that we're missing in this
authority format policy. Once

643
00:56:55,480 --> 00:56:59,320
you save it, you come back into
the, your drop back into the

644
00:56:59,320 --> 00:57:03,970
entry list for the helper and
TA-DA, there it is good to see

645
00:57:03,970 --> 00:57:07,870
that it has been created. So
what you've done is that you've

646
00:57:07,870 --> 00:57:13,630
created the missing tag O34. Now
you need to add it to the format

647
00:57:13,630 --> 00:57:18,820
policy in which it is missing.
So for that, You have to go to

648
00:57:18,820 --> 00:57:24,070
the configuring configuration
authorities format geographic.

649
00:57:26,440 --> 00:57:30,220
Add the missing tab, and it will
have multiple fields where you

650
00:57:30,220 --> 00:57:34,960
need to add different values,
and the workflows had topic,

651
00:57:34,990 --> 00:57:39,460
defining format variations is
very clear cut and very helpful

652
00:57:39,460 --> 00:57:44,830
in what you need to add. So I go
to a target formatting

653
00:57:44,830 --> 00:57:48,580
configuration, pick up the
format where it is missing, and

654
00:57:48,580 --> 00:57:53,380
click Modify, this is the one
place that sites tend to make a

655
00:57:53,380 --> 00:57:56,680
mistake this by mistake click
Create. You're not creating a

656
00:57:56,680 --> 00:58:01,480
new format. You're modifying the
geographic format to add a tag.

657
00:58:03,000 --> 00:58:03,960
So when you click

658
00:58:05,640 --> 00:58:11,220
Modify, you can now click on the
drop down arrow and pick up the

659
00:58:11,220 --> 00:58:16,110
new tag you just created O34,
and enter the correct name which

660
00:58:16,110 --> 00:58:20,340
is coded cartographic
mathematically data. And the

661
00:58:20,340 --> 00:58:25,050
rest of the values, added using
the workflows help, and click

662
00:58:25,050 --> 00:58:31,410
Save. Done, your authority.
Missing tag has been added and

663
00:58:31,410 --> 00:58:35,010
now you can wait for a while to
run. Anytime you make changes to

664
00:58:35,010 --> 00:58:38,370
a config toolbar you need a
halting run, which takes place

665
00:58:38,370 --> 00:58:42,660
every night for everyone. And
then you can reload the file and

666
00:58:42,660 --> 00:58:47,280
you will not get this error. Now
there's one final optional step

667
00:58:49,860 --> 00:58:54,060
that now you are in config, you
are in this format, why not add

668
00:58:54,060 --> 00:58:59,010
this tag to the add authority
visit template. So that in your

669
00:58:59,010 --> 00:59:02,700
staff when they're in cataloging
when they're in authorities and

670
00:59:02,700 --> 00:59:05,670
they want to add an authority
record. for example, they're

671
00:59:06,210 --> 00:59:10,830
creating an authority record for
maps. They want to see the O35

672
00:59:10,830 --> 00:59:15,360
tag, the O34 tag, yeah, they can
add it. But if it's available

673
00:59:15,360 --> 00:59:22,050
it's one thing. And it's very
easy to add it. You go into your

674
00:59:22,050 --> 00:59:27,840
scene to grab authorities
policy. And in menu modify it,

675
00:59:27,990 --> 00:59:32,160
come down and look at what is
the template entries name, in

676
00:59:32,160 --> 00:59:36,690
this case is called your graph
dash T, T for template. So you

677
00:59:36,690 --> 00:59:39,810
stick in this scene the name.
Click on the

678
00:59:41,429 --> 00:59:42,629
entry ID helper

679
00:59:44,340 --> 00:59:48,480
and scroll all the way down all
the way down past the nine xx

680
00:59:48,480 --> 00:59:53,010
dots, that's when the templates
start showing up, and click on

681
00:59:53,010 --> 00:59:58,350
your geograph team, and modify
it. This will take you to the

682
00:59:58,350 --> 01:00:04,260
details of this template. Click
on the gadget, see the list of

683
01:00:04,260 --> 01:00:09,570
tags that are available. This is
currently in your. Add authority

684
01:00:09,600 --> 01:00:14,040
template. Now you pick up your
O34, and just add it over to

685
01:00:14,040 --> 01:00:18,840
this side, and click Save. Done.
All you need your hard round of

686
01:00:18,840 --> 01:00:22,680
the system for this entry to
display the format policy. And

687
01:00:22,680 --> 01:00:25,440
if you haven't reloaded the file
just yet, go ahead and reload it

688
01:00:25,440 --> 01:00:31,320
now. No more errors. So this is
how you load an authority file,

689
01:00:31,440 --> 01:00:36,150
and how you resolve the load
errors, now turning it back to

690
01:00:36,150 --> 01:00:40,890
Natalie, to show you how to
handle the other things. Let me

691
01:00:40,890 --> 01:00:45,570
stop sharing and Natalie it's
all yours.

692
01:00:47,969 --> 01:00:48,869
Okay,

693
01:00:55,260 --> 01:00:59,700
my slides will be created into a
task portal, Doc. So you should

694
01:00:59,700 --> 01:01:03,750
be able to see over there and
Laurie will also post the slides

695
01:01:03,750 --> 01:01:07,020
so that you can check it from
there also. Okay, um,

696
01:01:11,729 --> 01:01:12,479
see.

697
01:01:14,580 --> 01:01:16,110
I'm trying to

698
01:01:20,500 --> 01:01:26,380
yeah but I didn't see. Now I see
my. Okay.

699
01:01:27,850 --> 01:01:28,810
So can you see?

700
01:01:29,460 --> 01:01:30,570
yes. Okay,

701
01:01:31,350 --> 01:01:36,180
so I'm going to talk about the
authority load errors that

702
01:01:36,180 --> 01:01:40,620
indicate manual intervention may
be required. And I'll start with

703
01:01:40,620 --> 01:01:44,700
some disclaimers, I'm not an
expert on authority control in

704
01:01:44,700 --> 01:01:49,140
general or as it isn't
implemented in Symphony. And I

705
01:01:49,140 --> 01:01:52,740
can only offer limited
information in the time allotted

706
01:01:52,920 --> 01:01:56,250
I'm sharing how I handle errors
you may choose to handle them

707
01:01:56,250 --> 01:01:59,370
differently. My only
recommendation is that you do

708
01:01:59,370 --> 01:02:04,500
not ignore them. So we'll look
at when and why manual

709
01:02:04,500 --> 01:02:10,260
intervention may be required.
And I'll show examples of name

710
01:02:10,260 --> 01:02:12,930
heading that's been deleted a
subject heading that's been

711
01:02:12,930 --> 01:02:16,590
deleted and a heading change
from a one particular one xx

712
01:02:16,590 --> 01:02:20,010
field to a different one xx
field. And then I'll just

713
01:02:20,010 --> 01:02:23,550
mention that additional
information can be made

714
01:02:23,550 --> 01:02:30,780
available after the webinar. So,
when might manual intervention

715
01:02:30,780 --> 01:02:34,890
be required. Anytime a heading
has been deleted and that would

716
01:02:34,890 --> 01:02:38,880
be a name or a subject heading.
And when a heading is changed

717
01:02:38,910 --> 01:02:45,420
from a one xx to a different one
x x x. What I've seen mostly is

718
01:02:45,420 --> 01:02:54,900
110, that's changed to either a
111, a 130 or 151. Why would

719
01:02:54,900 --> 01:02:58,950
manual intervention be required.
So when a heading has been

720
01:02:58,950 --> 01:03:03,390
deleted the load report, only
removes the associated headings

721
01:03:03,390 --> 01:03:08,670
from the thesaurus. That's what
Mike mentioned earlier. So the

722
01:03:08,670 --> 01:03:11,610
headings are no longer
authoritative the authority

723
01:03:11,610 --> 01:03:16,710
record is not removed but
retained for reference. Hence,

724
01:03:16,740 --> 01:03:22,140
you get the message about manual
intervention being required the

725
01:03:22,140 --> 01:03:25,590
headings and the bibliographic
records are still linked to the

726
01:03:25,590 --> 01:03:29,820
wrong authority record which is
that deleted record. So manual

727
01:03:29,820 --> 01:03:34,620
intervention is required to
delete the authority record and

728
01:03:34,620 --> 01:03:38,580
correct the headings in the
bibliographic records. When a

729
01:03:38,580 --> 01:03:43,200
heading changes the load report
does not change Marc tags in

730
01:03:43,200 --> 01:03:47,100
bibliographic records so
therefore manual intervention is

731
01:03:47,100 --> 01:03:51,900
required. So again, we'll look
at three examples and we'll

732
01:03:51,900 --> 01:03:57,210
start with a deleted name
heading. So you'll see three

733
01:03:57,210 --> 01:04:02,820
lines in the load report log,
the first line is going to give

734
01:04:02,820 --> 01:04:08,280
you the authority ID, any
authority ID beginning with an

735
01:04:08,280 --> 01:04:13,440
end as a name heading, unless
it's no ID, and that indicates

736
01:04:13,440 --> 01:04:17,820
the authority record had been
deleted from the system prior to

737
01:04:17,820 --> 01:04:22,110
the authority load and actually
no ID can refer to a name, or a

738
01:04:22,110 --> 01:04:25,770
subject heading, and I can
provide information about that.

739
01:04:26,190 --> 01:04:29,910
Outside of the webinar. Then
you'll see a line telling you

740
01:04:29,910 --> 01:04:32,790
what the actual error is so in
this case heading has been

741
01:04:32,790 --> 01:04:35,670
deleted. And then the third line
is telling you that manual

742
01:04:35,670 --> 01:04:40,140
intervention may be required.
Again, I'll mention that the

743
01:04:40,140 --> 01:04:43,500
load report does not delete the
authority record it only

744
01:04:43,770 --> 01:04:47,220
replaces the existing one with a
record that's marked for

745
01:04:47,220 --> 01:04:52,440
deletion. The status will be
changed to deep or deleted and a

746
01:04:52,440 --> 01:04:57,390
note may be added in the six xx
field to explain the reason for

747
01:04:57,390 --> 01:05:01,530
deletion. So I usually start by
searching the authority file by

748
01:05:01,530 --> 01:05:07,410
the authority ID that you see
above. And here's an authority

749
01:05:07,410 --> 01:05:10,320
record it's a deleted one so you
can see the status has been

750
01:05:10,320 --> 01:05:14,640
changed to D for deleted, and
there's a 667 field that

751
01:05:14,670 --> 01:05:18,870
provides the reason for deletion
in this case, this was the last

752
01:05:18,870 --> 01:05:24,060
identity on an undifferentiated
record so it's been reported for

753
01:05:24,060 --> 01:05:30,420
deletion. So my next step is I'm
going to browse my catalogue to

754
01:05:30,420 --> 01:05:34,230
see how this heading is being
used in the case of a name

755
01:05:34,230 --> 01:05:39,960
heading, it can actually be used
as, you know, an author or

756
01:05:39,960 --> 01:05:43,710
subject, so you want to make
sure you browse both, I had

757
01:05:43,710 --> 01:05:46,650
already browsed the subject
index and didn't find anything

758
01:05:46,650 --> 01:05:53,970
so here I am browsing the author
index. I see this heading. And

759
01:05:54,090 --> 01:05:59,160
there's one title for that
heading sex crime and morality

760
01:05:59,160 --> 01:06:03,060
so I take note of the title and
the subjects because that's

761
01:06:03,060 --> 01:06:06,000
going to help me find my
matching authority record.

762
01:06:10,350 --> 01:06:14,460
So I'm browsing the LC name
authority index inside

763
01:06:14,460 --> 01:06:20,970
workflows. So I get two results.
The first one is the deleted

764
01:06:20,970 --> 01:06:24,780
heading and I know that because
there is no icon in front of it.

765
01:06:25,230 --> 01:06:29,610
So that's the one that needs to
be deleted Marcive has also

766
01:06:29,610 --> 01:06:35,760
delivered. Another heading. And
the reason is because the LCCN

767
01:06:35,760 --> 01:06:39,600
which is the Library of Congress
control a number of the deleted

768
01:06:39,600 --> 01:06:46,860
record appears in subfield Z of
the O one o field. And in this

769
01:06:46,860 --> 01:06:50,550
particular case this Sharon
Hayes, is the Deputy State Chief

770
01:06:50,550 --> 01:06:54,360
Information Officer for North
Carolina and it's probably not

771
01:06:54,360 --> 01:06:59,100
the author of the title Sex
Crime and Morality. So, you

772
01:06:59,100 --> 01:07:03,420
know, there are no other Sharon
Hayes, in my LC name authority

773
01:07:03,420 --> 01:07:07,860
index so I'm going to take a
look at OCLC's authority file to

774
01:07:07,860 --> 01:07:09,480
see if there's an authority
record that matches

775
01:07:10,050 --> 01:07:10,830
my title.

776
01:07:13,090 --> 01:07:18,430
So I've browsed the OCLC
personal names index, and this

777
01:07:18,430 --> 01:07:23,650
is what I get so I can see that
delivered authority record for

778
01:07:23,650 --> 01:07:28,060
Sharon Hayes, the deputy CIO and
that's the one we don't need,

779
01:07:28,390 --> 01:07:32,080
and the ones highlighted any one
of those could be the authorized

780
01:07:32,080 --> 01:07:36,670
heading that I need to match the
title in my catalog and Sharon

781
01:07:36,670 --> 01:07:39,850
Hayes the criminologist looks
like a good choice to check

782
01:07:39,850 --> 01:07:45,100
first so I do that. And this is
just part of the record it's so

783
01:07:45,100 --> 01:07:48,700
long I couldn't get it into a
screenshot, but I can tell that

784
01:07:48,700 --> 01:07:52,540
this is the authorized heading,
that's needed in my catalog How

785
01:07:52,540 --> 01:07:57,100
do I know that because the title
in our catalog appears as one of

786
01:07:57,100 --> 01:08:01,180
the source citations in the 670
field so this is the authority

787
01:08:01,180 --> 01:08:05,830
record that I need. And you can
also note that the heading I

788
01:08:05,830 --> 01:08:09,280
thought might be a match is
actually a C from reference, and

789
01:08:09,280 --> 01:08:13,810
that's one of those things that
Mike had mentioned. Also, there

790
01:08:13,810 --> 01:08:16,750
are two other C from references
that appeared in that browse

791
01:08:16,750 --> 01:08:23,170
list. And there's a 667. That
also includes the LCCN from the

792
01:08:23,170 --> 01:08:27,610
deleted authority record, and
I'll mention it also appears in

793
01:08:27,610 --> 01:08:31,510
subfield Z of the O1O of this
record but it's not included in

794
01:08:31,510 --> 01:08:36,520
the screenshot. So I'm going to
import this authority record

795
01:08:36,520 --> 01:08:41,110
from OCLC into our Symphony
authority file. I could wait

796
01:08:41,110 --> 01:08:45,430
around to see if Marcive would
deliver it, but I usually don't

797
01:08:45,430 --> 01:08:48,430
wait for that, even if they do
deliver it it's just going to

798
01:08:48,430 --> 01:08:55,000
overlay the one I import. So
I've imported it I've gone back

799
01:08:55,030 --> 01:08:58,450
and I'm browsing than the LC
name authority index in

800
01:08:58,450 --> 01:09:02,110
workflows so I can see now I
have the correct authority

801
01:09:02,110 --> 01:09:08,800
record Sharon Hayes. Born in
1958. I'm going to delete the

802
01:09:08,920 --> 01:09:12,220
highlighted records so the first
one is the one that's actually

803
01:09:12,220 --> 01:09:16,090
deleted so I call it the Delete
record and the other one is

804
01:09:16,090 --> 01:09:21,340
Sharon Hayes, Deputy CIO, I
usually refer to that as an

805
01:09:21,340 --> 01:09:24,490
extra record so I'm going to
delete both of those and then

806
01:09:24,490 --> 01:09:31,150
I'm going to correct the
bibliographic record. So,

807
01:09:31,180 --> 01:09:35,350
deleting the Delete record is
easy, just go ahead and delete

808
01:09:35,350 --> 01:09:41,170
it. For the extra records. I
actually record the LCCN before

809
01:09:41,170 --> 01:09:45,220
deleting it so that I can report
it to Marcive for removal from

810
01:09:45,220 --> 01:09:49,240
our history file. If I don't
report it Marcive will continue

811
01:09:49,240 --> 01:09:52,840
to deliver this authority
record, whenever it's updated

812
01:09:52,840 --> 01:09:57,190
and we don't need it, so you
don't have to report the deleted

813
01:09:57,190 --> 01:10:01,720
record you just report the LCCN
of any other authority record

814
01:10:01,720 --> 01:10:08,530
that you don't need in your
file. So here I corrected the

815
01:10:08,530 --> 01:10:14,290
heading. So, And if you
remember, I imported that

816
01:10:14,320 --> 01:10:19,720
authority record from OCLC so I
need to report that LCCN to

817
01:10:19,720 --> 01:10:22,930
Marcive so the record can be
added to our history file if I

818
01:10:22,930 --> 01:10:26,890
don't report it, Marcive does,
doesn't know that you know it's

819
01:10:26,890 --> 01:10:31,060
in my authority file and, you
know, they will not deliver the

820
01:10:31,060 --> 01:10:38,050
record whenever it's updated. So
that's a deleted name, heading,

821
01:10:38,140 --> 01:10:41,500
and for subjects, you're going
to see similar thing in the

822
01:10:41,500 --> 01:10:46,510
report log subject headings of
authority ID is going to begin

823
01:10:46,510 --> 01:10:51,220
with the letters sh again. The
report is not going to delete

824
01:10:51,220 --> 01:10:54,370
the record, just replaces it
with the record marked for

825
01:10:54,370 --> 01:10:59,020
deletion the status has changed
to D, and a note may be added in

826
01:10:59,020 --> 01:11:04,450
the 666 xx field to explain the
reason for deletion. And just as

827
01:11:04,450 --> 01:11:07,450
I did with the deleted name
heading I'm going to start my

828
01:11:07,450 --> 01:11:12,670
search and authority file by the
authority ID. So here's the

829
01:11:12,670 --> 01:11:16,660
authority record for the deleted
subject heading the status is D

830
01:11:16,660 --> 01:11:24,430
for deleted. The 150 heading,
that's the one that's no longer

831
01:11:24,430 --> 01:11:26,680
is going to be used it's no
longer going to be a subject

832
01:11:26,680 --> 01:11:31,660
heading. And there's a 682 field
indicating this authority record

833
01:11:31,660 --> 01:11:34,660
has been deleted because the
subject heading is covered by an

834
01:11:34,660 --> 01:11:37,840
identical name heading. And
that's because fictitious

835
01:11:37,840 --> 01:11:44,440
headings are now named headings
and that's due to REA. So

836
01:11:44,440 --> 01:11:48,760
Marcive delivered the authority
record for the identical name

837
01:11:48,760 --> 01:11:54,760
heading, and you can see the
LCCN for these deleted subject

838
01:11:54,760 --> 01:12:00,610
heading record. And now our
headings, a 100 a name, heading.

839
01:12:00,970 --> 01:12:04,720
And we'll assign that as a
personal name subject heading

840
01:12:04,750 --> 01:12:08,380
and 600 field and bibliographic
records.

841
01:12:11,240 --> 01:12:18,770
So I've corrected, have changed
the 650 to 600 field, and, you

842
01:12:18,770 --> 01:12:28,100
know, change the indicators as
needed. And the final example is

843
01:12:28,340 --> 01:12:32,930
a heading, that's changed from a
110 to 111 so a corporate name

844
01:12:32,930 --> 01:12:38,300
heading change to um, meaning
name, heading. You get a little

845
01:12:38,300 --> 01:12:42,230
bit more information in the
report log, you'll get the

846
01:12:42,260 --> 01:12:45,980
authority ID it'll tell you the
heading is changed, manual

847
01:12:46,010 --> 01:12:48,740
intervention is required and
it's actually going to show you

848
01:12:48,740 --> 01:12:54,650
the two headings. So this is the
authority record that's been

849
01:12:54,650 --> 01:12:58,880
changed the status is C for
changed, and you can see that

850
01:12:58,880 --> 01:13:02,270
the heading is now a meeting
name heading. You can see the

851
01:13:02,270 --> 01:13:06,410
former corporate name heading is
now a C from reference.

852
01:13:09,120 --> 01:13:13,350
And this is the bibliographic
record before. It's been

853
01:13:13,350 --> 01:13:15,240
corrected it's a 110.

854
01:13:17,339 --> 01:13:22,469
And this is after the heading
has been corrected. And I'll

855
01:13:22,469 --> 01:13:26,399
mention I do all of this
manually, you could use the

856
01:13:26,399 --> 01:13:31,379
validate headings helper. If you
choose that option I just prefer

857
01:13:31,379 --> 01:13:34,109
to do everything manually just
because it's the way I've been

858
01:13:34,109 --> 01:13:34,649
doing it.

859
01:13:36,600 --> 01:13:41,610
So that's a brief overview of
how I handle

860
01:13:43,280 --> 01:13:47,720
errors that might require manual
intervention and I just wanted

861
01:13:47,720 --> 01:13:50,810
to mention and I can provide
detailed instructions to LOUIS

862
01:13:50,810 --> 01:13:55,490
for, for all of this I will
mention that reporting additions

863
01:13:55,490 --> 01:13:59,150
and deletions to the Marcive
does involve a cost it's five

864
01:13:59,150 --> 01:14:06,290
cents per record or LCCN number,
and there's a particular format

865
01:14:06,350 --> 01:14:11,120
that you use to report that
information to Marcive and I can

866
01:14:11,120 --> 01:14:16,130
provide that. And I'm going to
go ahead and stop sharing so

867
01:14:16,130 --> 01:14:18,860
that we can entertain your
questions.

868
01:14:21,180 --> 01:14:29,460
I have a question on the, I
guess your Marcive use, which

869
01:14:29,460 --> 01:14:33,330
you prefer, I mean seem like you
prefer to do it beforehand and

870
01:14:33,330 --> 01:14:38,070
then let Marcive come in later
versus, I guess, depending on

871
01:14:38,070 --> 01:14:41,070
how many records you'd have I
guess, other places I worked at

872
01:14:41,070 --> 01:14:45,000
colleges they would use Marcive
to the full extent. I guess

873
01:14:45,000 --> 01:14:49,560
because they would budget, but
it seemed more efficient, you

874
01:14:49,560 --> 01:14:52,470
know to get it done and then we
come in after there and start

875
01:14:52,470 --> 01:14:56,400
cleaning up after, we'll see
some items but is that what I'm

876
01:14:56,400 --> 01:15:00,420
getting at you prefer to have
you do it personally or your,

877
01:15:00,450 --> 01:15:04,290
your technical service group,
and then use Marcive late I

878
01:15:04,380 --> 01:15:06,180
mean. Yeah, Marcive later.

879
01:15:06,600 --> 01:15:08,160
So, um.

880
01:15:09,300 --> 01:15:12,870
So Marcive has already processed
our file so I'm just keeping up

881
01:15:12,870 --> 01:15:17,100
with, with the monthly stuff.
Um, so I'm actually the person

882
01:15:17,100 --> 01:15:22,740
who does it. I, you know, we
send off our bib. records and

883
01:15:22,740 --> 01:15:25,740
have them corrected but there's
always going to be things that

884
01:15:25,740 --> 01:15:30,690
happen when you load authority
records on a monthly basis that

885
01:15:30,690 --> 01:15:33,630
you have to handle. And that's
what I'm doing,

886
01:15:33,000 --> 01:15:38,280
I get it. and then with the it's
always kind of question who

887
01:15:38,280 --> 01:15:42,600
works in the records and that
depth, meaning you use your

888
01:15:42,690 --> 01:15:46,320
career professionals or do you
feel more comfortable me doing

889
01:15:46,320 --> 01:15:51,930
it, I guess, a librarian doing
it, versus a copy cataloger or

890
01:15:51,930 --> 01:15:55,050
something or do you feel
comfortable, or how's it done,

891
01:15:55,050 --> 01:15:55,560
did you do

892
01:15:55,590 --> 01:16:00,810
so, I do it, I inherited it from
our cataloger who retired. Many

893
01:16:00,810 --> 01:16:07,530
years ago, and I just have not
had the time to show our current

894
01:16:07,530 --> 01:16:11,610
cataloger how to do it. You know
what I showed you was a very

895
01:16:11,610 --> 01:16:16,560
brief snippet of what I do I can
spend a whole day going through

896
01:16:16,560 --> 01:16:18,900
a report log, it can be that,
you know,

897
01:16:19,199 --> 01:16:20,099
okay. And that's

898
01:16:20,000 --> 01:16:25,220
how involved so I'm, I'm hoping
to pass this on or at least

899
01:16:25,220 --> 01:16:28,760
share it with our cataloger but
at this point it's just me.

900
01:16:29,300 --> 01:16:32,930
Believe me, I know where you're
at on that end, but yeah and

901
01:16:32,930 --> 01:16:35,750
that's one thing I'm
questioning, you know against

902
01:16:35,750 --> 01:16:39,500
just starting here, Louisiana
Tech and I know there's probably

903
01:16:39,500 --> 01:16:43,430
things to be cleaned up. But
again, getting the load up it

904
01:16:43,430 --> 01:16:46,340
makes more sense on our end it's
probably this makes sense on

905
01:16:46,340 --> 01:16:49,160
your end to do it that way so
we'll see what happens.

906
01:16:49,930 --> 01:16:54,430
And there's a there's a there's
a step that was before what Zee

907
01:16:54,430 --> 01:16:58,780
had shown Zee was showing us how
to load the records, yeah there

908
01:16:58,870 --> 01:17:03,400
is that from Marcive where you
export your bib records and send

909
01:17:03,400 --> 01:17:07,480
them to Marcive. And that's how
they tell which, you know, which

910
01:17:07,480 --> 01:17:12,040
records need to be updated. So,
you know, that's, you know,

911
01:17:12,040 --> 01:17:14,140
might be done at the beginning
of the month or the end of the

912
01:17:14,140 --> 01:17:17,200
month depending you know you
have some sort of schedule, and

913
01:17:17,200 --> 01:17:21,400
then some Marcive, you know,
we'll send you something that

914
01:17:21,400 --> 01:17:24,970
says that they you know they
process this, and then later,

915
01:17:25,000 --> 01:17:28,300
some, I don't know, I seem to
remember it taken about a week

916
01:17:28,300 --> 01:17:33,490
or two, you would get the
authorities to load. And then

917
01:17:33,640 --> 01:17:36,880
you, then you would follow is
what Zee had showed there.

918
01:17:37,270 --> 01:17:42,520
Yeah, yeah, I've never used a
Marcive and I guess a bigger

919
01:17:42,520 --> 01:17:46,840
project when we first at U of H.
When we started getting into RDA

920
01:17:46,840 --> 01:17:50,590
you know have we just started
dumping X amount of records to

921
01:17:50,590 --> 01:17:53,590
them, and getting them back and
started cleaning up, but that

922
01:17:53,590 --> 01:17:58,990
was scheduled in a long process,
and with me there I didn't know

923
01:17:58,990 --> 01:18:03,040
about the governor, government
documents on how well that's

924
01:18:03,040 --> 01:18:08,890
been, I guess, looked at or how
that's working right now I'm not

925
01:18:08,890 --> 01:18:12,850
familiar, on how it's working as
far as records, we'll

926
01:18:12,630 --> 01:18:19,260
find out. Yeah, and so Dale what
Marcive does is, first of all,

927
01:18:19,350 --> 01:18:22,830
even if you are going to do it
in the middle. When you extract

928
01:18:22,830 --> 01:18:27,780
your bib records and send it to
them, they will process the bib,

929
01:18:28,080 --> 01:18:32,460
bib records correct them all the
punctuation all the audio new

930
01:18:32,460 --> 01:18:37,560
fields and tags. And then they
make a copy of the authority

931
01:18:37,950 --> 01:18:41,910
that they create and keep it as
your history file. So any

932
01:18:41,910 --> 01:18:46,080
changes that come through. They
want it against the history file

933
01:18:46,080 --> 01:18:48,630
and that's when they said the
modification and changes that

934
01:18:48,630 --> 01:18:51,480
are taking place and that is
what Natalie is pointing out

935
01:18:51,690 --> 01:18:55,080
that she lets them know, so that
they update those history files

936
01:18:55,080 --> 01:18:57,330
and they don't keep sending you
the same record over and over

937
01:18:57,330 --> 01:18:59,190
again, making extra work for
you,

938
01:18:59,339 --> 01:19:04,139
and not getting double charts
kind of deal. Yeah, that makes

939
01:19:04,139 --> 01:19:07,079
sense. And again, I thank you
for your input on that.

940
01:19:14,440 --> 01:19:18,070
Any other questions. We've gone
a little bit over our time but

941
01:19:18,730 --> 01:19:20,770
we started slightly late too

942
01:19:27,590 --> 01:19:31,220
the good thing here is that this
presentation has been recorded.

943
01:19:32,360 --> 01:19:36,110
It was pretty information dense,
so congratulations if you were

944
01:19:36,110 --> 01:19:41,330
able to follow every step along
the way but you'll be able to

945
01:19:41,330 --> 01:19:48,230
refer to the documentation.
Probably going out with this and

946
01:19:48,230 --> 01:19:53,720
then, as well as the recording
itself. So, thank you so much

947
01:19:53,720 --> 01:19:57,770
for attending our Learning With
LOUIS and be sure to join us

948
01:19:58,010 --> 01:19:59,090
next time.

949
01:19:59,759 --> 01:20:01,079
All right, thank you all guys.

950
01:20:02,040 --> 01:20:02,580
Yeah.

951
01:20:03,660 --> 01:20:04,740
Thank you. Bye.

952
01:20:05,100 --> 01:20:08,310
Bye everybody. Hi.

953
01:20:11,090 --> 01:20:12,800
Thanks Natalie thanks, thanks
Zee.

954
01:20:13,550 --> 01:20:15,500
Thank you. Thanks, Mike. Thanks,
Zee