In data venerdì 15 novembre 2013 18:14:57, Theodoropoulos Theodoros ha
scritto:
> 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? ;)
Hi!
It's a feature ;-) not a bug (OK maybe it's a bug in the documentation)?
bibupload --replace is really a replace, no matter what you think: if you pass
an empty record with FFTs it will drop the existing records (and all the
bibdocs attached) and replace with the empty record, executing the FFTs.
If you want to just drop the files you can use bibdocfile CLI first.
Alternatively you can send a bibupload --correct (with empty record, thus
corrcting nothing, and FFTs, thus correcting corresponding bibdocs.)
Cheers!
Sam
--
Samuele Kaplun
Invenio Developer ** <http://invenio-software.org/>
INSPIRE Service Manager ** <http://inspirehep.net/>
