Okay, I’m back from my vacation and checking on these. It appears that the predicate text I used for the Xbox One did in fact work … kind of. We have one item showing up now in Discover with that material type (https://tracpac.ab.ca/search/card?id=296fdf75-1d61-40a8-afdf-751d6150a807&entityType=FormatGroup). However, in Leap there are 236 records showing up with that format/material type. I compared two records - the one showing in Discover and another one, and can’t really see what’s different about them that’s relevant to the predicate text.
Here’s the predicate text: ((LDR/06 = ‘m’) and (ANY 006 WHERE (_ matches /^m.{5}q.{2}g/i)) and (ANY 007 WHERE (_ matches /^co/i)) and (008/23 = ‘q’) and (347$b = ‘Xbox one’))
I’m attaching screenshots of the two records - the one on the right is the one that is in Discover and the one on the left is the one only showing in Leap (when I link to the record in Discover it’s still just showing as Video Game).
You could try changing something in the bib record and saving it to cause it to get reindexed.
You would want to make sure the precedence of your TOM Rule is LESS than 9 because that is the standard Video game TOM rule precedence number, and the lowest number is supposed to “win”.
I agree with Wes’ first suggestion that this is an indexing issue with Discover. Once you’re done making changes in PolarisAdmin, you’ll likely need to do a full MARC Extract to get Discover synced.
Innovative responded to my ticket and said that it’s best practice to run a full extraction after applying custom TOMs. That seems to be doing the trick, but a full extraction takes a long time! It’s still in progress over 12 hours later. Thanks for all your help everyone.
This might come as a surprise, but extractions in Vega can get stuck without notice and appear to still be running. It might not hurt to ask Innovative to take a look. The response I got from them for the below issue was “If an extraction becomes either stuck or interrupted for one reason or another, then it is not unexpected for it to continue saying “In Progress” when really it is no longer processing.”
We have a huge database, so I’m not surprised at this! I had an extraction stuck in progress back in July and didn’t realize it until a week later, and no extractions happened because of it. I did an extraction for just the new and updated items for the week prior, and it took a long time then too. I’m curious to see how long this on takes - the ILS extraction bibs is currently sitting at 640,099 and still going.
