Hello everyone,

Today I run a "bibupload -n -r xxx.xml" job with only FFT tags in order to 
enrich some of my records with fulltexts. Everything went fine (no errors/no 
warnings) but the affected records got replaced entrirely by 3 tags 
(001/005/856) wiping out everything else.

Shouldn't 'replace' mode (when used only with FFT tags) be smart enough and not 
touch (replace) the bibs? Reading the bibupload docs, I believed that I was 
allowed to use 'replace' mode with files...

Is this a known behavior (probably even fixed in a personal branch), or did I 
hit another bug? ;)

Cheers,
Theodoros

Reply via email to