Closed christinach closed 1 month ago
@mzelesky and I reviewed the record history in Alma and the record was changed on: 7/25 at 10:22am eastern time 7/26 at 12:14pm eastern time This means that the record should have been published twice, once on 7/25th after 10:30am and once on the 7/26th after 12:15pm
@mzelesky looked through all the published files in alma and the only time we found the record was published was on 7/24th after 1pm. On 7/24th the record was still in the permanent location this is why it was indexed in Firastone$stacks.
The marc record in the main ticket comment was manually published by @christinach on 7/25th and it had the temporary location changes from alma.
@mzelesky updated the record on July 29th at 9:40am. We are waiting to see if the record will come in the next publishing job
Further investigation needs to happen in the actual publishing job in Alma. This is not a bibdata indexing issue
Expected behavior
Records in temporary locations besides
RES_SHARE$IN_RS_REQ
RES_SHARE$IN_RS_REQ` should be indexed with the temporary locaiton in holdings1_displayActual behavior
Records in temporary location: stokes$spir were indexed with the permanent location
After further investigation with @mzelesky this ^^ marc record was not exported in any of the publishing jobs after July 24th.
Steps to replicate
Impact of this bug
Users interested in the specific record think the record is in Firestone$stacks
Implementation notes
This was reported by Tracy H. in the catalog channel.
mms_id: 9941616013506421 mms_id: 99129005733006421