Re: Bibupload/FFT only, replacing Marc records

[Theodoros Theodoropoulos]

Thank you Sam for the clarification (btw, I 'fixed' my records by just 
re-uploading[1] the marc, so no problem there).
Bibdocfile is a powerful module and definitely my best friend in this 
case, however, I indeed find bibupload documentation a bit misleading on 
this matter.


As bibupload is a module widely used by people and that this issue could 
potentially lead to temporary loss of marc data (you don't always have 
the xml of the records to 'fix' them and reverting all of them into a 
previous revision is a bit 'tricky'), I will submit a ticket (of 
'trivial' priority) so that -when time for the documentation updates 
comes- you also update the relevant part of the -otherwise clear and 
extensive- bibupload documentation.


Cheers,
Theodoros


[1] Using bibedit list-revisions followed by --revert-to-revision for 
these records would be a 'cleaner' alternative, but I also found the 
opportunity to do some trivial batch changes to the marc, so reuploading 
was a better solution in this case.


On 15/11/2013 10:01 μμ, Samuele Kaplun wrote:

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

Re: Bibupload/FFT only, replacing Marc records

[Samuele Kaplun]

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 ** 
INSPIRE Service Manager ** 

Bibupload/FFT only, replacing Marc records

[Theodoropoulos Theodoros]

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