Hello,
Our implementation team couldn’t help with this issue we’re getting, so trying out here 
We’re getting Marc Validation errors in the Tag 655 $2 cstr
cstr is our code both for the California Digital Library and our MARC institutional code.
Ideas?
Thanks, Tina
Pretty sure the list of acceptable ones are basically hardcoded. Here is an idea you can vote for: Validate controlled thesauri (650 or 655 _7 $2) – Innovate with us
After Wes said he thought they were hardcoded, I thought I’d have a look to see if I could figure out where they might be coded… I think these Source codes are all stored in the MARCCatSourceTermsCodes table. It’s pretty expansive, but there are entries for “lcgft” and “lcsh”, so it seems like this is the right place. What’s strange though is there’s a column named LocallyDefinedFlag, which suggests to me that there should be a way to define a local entry for this table… I’ll have to poke around a little more to see if I can figure out how, but if this jogs anyone else’s memory, please share!
Good sleuthing!
Yeah, in fairness, “hardcoded” was a bit of a nebulous term on my end. It would really be more accurate to state “not changeable via the admin UI or other user-accessible configuration changes.”
You’re right in that many times the adjustments can be made by manipulating tables behind the scenes, and sometimes that is the process that gets rolled out by Polaris themselves in upgrades from version to version as things are officially adopted into standards.
Also, sometimes the database structures, especially in a system that is almost 30 years old with over 1,000 tables, can hint at plans or experiments that may have never come to fruition or could be on their way in a future release. Maybe this is one of those cases!
