2012/1/6 Paul
<paul.a@aandc.org>
I have successfully use that script
to link authorities to biblio records after doing a migration. But the
way it works is to remove all links and recreate.
Not sure about the "recreate" bit...
Agreed. That's why I'm working on bug 7284.
Incidentally (this is for the whole list), I *always* run anything that is supposed to make bulk changes for the first time on a test database (preferred) or using some sort of "test" option. For
link_bibs_to_authorities.pl, that option is --test: "only test the authority linking and report the results; do not change the bib records." Is it slow and annoying? Yes. It is better than losing data? Oh my goodness yes. Having worked on a project where a cowboy decided to run a bulk modification script without testing first, I can speak with certainty about that ("Jared, why aren't there any records in the database?" is not something I ever want to hear again).
Its included for that use case.
Jared is working on a much better linking script and he gave you the
information how to change it.
Respectfully, it's included in the "current stable release"
with no warnings (3.6.1 was "current" when I installed it -- I
haven't verified 3.6.2.) and Jared's information came after "horses
and barn doors."
As it happens, you have encountered this problem at the right time. I have a working replacement linker script that needs testing, if you are so inclined. In pursuit of better results, I would be willing to host a copy of your bibliographic and authority databases so that you can look at the results of the revised linking. Note for the list: THIS OFFER IS OPEN TO ANYONE, first come, first served. I'd like to test over the next week or two, so anyone who's interested, let me know and (if I still have testing slots free) we'll arrange to transfer the files ASAP.
Its not a total screwup script, and
it didn't demolish the whole db, I think you would find people more
willing to help you, in their own free time, in their weekends if you
didn't come across so aggressive and accusatory in your
tone.
You may be glad to know that if bug 5683 were still an issue, your system would have been completely unusable, rather than simply unlinked.
Regards,
Jared