[IMUG-L] Sierra 5.2, 5.3 known issue $i in Automated Authority Control Processing

[Rebecca Belford]

Greetings, Sierra users,

We are discussing our upcoming Sierra update from 4.1 and looking at moving
to version 5.2 but are aware 5.3 is an option. I was looking through the
known issues list for Sierra 2.0-5.2, and noted this one, which seems like
an awful lot of information that could get lost from 7xx fields:

When Automatic Authority Control Processing runs on an added entry field
that includes subfield i, the system updates the field and removes subfield
i. SIERRA-33592, added 2020-12-08, reported in version 5.1, resolved in 5.3.


I am reading this as somewhat limited in scope, i.e., subfield $i is
removed *only *when there's a "flip" generated by a match to a 4xx field in
an AR (as opposed to any time the process simply encounters $i). Anything
changes listed in the MCB get made via global update or ad hoc fixes from
single records. However, the other branches do not have the staff to keep
up with updates to the same extent and do rely on the automatic processing.
It seems like this could introduce inconsistencies within a single record
if some headings are flipped ($i removed) and some are not. Would this get
noticed by non-catalogers? I don't know. It also seems disheartening to
lose information like this.

I need to decide if anything about version 5.2 is sufficiently egregious to
recommend we go straight to 5.3.

Any experience/thoughts most welcome.

Thank you,
Rebecca

Rebecca Belford
Technical Services Librarian
Oberlin Conservatory Library
77 West College St., Oberlin, OH 44074
rbelford at oberlin.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osu.edu/pipermail/imug-l/attachments/20201215/f740ba23/attachment.html>