On Wed, Feb 16, 2011 at 6:36 PM, Dan Scott <[email protected]> wrote: > A simple/simplistic way to fix this in the short term would be to run > (after importing all of your bib records): > > UPDATE biblio.record_entry SET tcn_value = id; > > I would consider this a bug, though, as the expectation when you set > "Cat: Use internal ID for TCN value" to TRUE is for that to be the case > no matter how you get the records into the system. In which case, a > minor tweak to the maintain_901 or maintain_control_number triggers > should suffice (maintain_901 because it occurs before > maintain_control_number, although perhaps that order should be > reversed anyway to ensure that maintain_901 inserts the correct values > in the correct spots...)
Okay, I have committed a fix for this behavioural inconsistency as part of the maintain_901 trigger to trunk and backported it back to rel_2_0 so that it will be part of the 2.0.2 release, whenever that occurs. -- Dan Scott Laurentian University
