Ivan Kurmanov writes
On Fri, Aug 21, 2009 at 6:10 PM, Christian Zimmermann<christian.zimmermann@uconn.edu> wrote:
Thanks! How do you force update? And how do we know whether there are other cases like this? Would they really sort out by themselves over time?
you force update by passing a number to updareq, i think it is documented, but i don't remember the details. there might be a lot cases like that -- you'd want to make sure something like 2 or 3 weeks is TOO OLD in RePEc::Index (not 2 or 3 months) and then make sure a general ("/") update goes through successfully. Then all such cases should be automatically sorted out.
Yes, it is the too_old parementer. By default it's a week, but this let to a lot of i/o, so I set it to something like a year in the crontabs. I am snowed under this week. I will look at the story next week. Cheers, Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel skype: thomaskrichel