#721: BibUpload: fix troubles with multiple 001 tags
------------------------+----------------------
  Reporter:  simko      |      Owner:  skaplun
      Type:  defect     |     Status:  assigned
  Priority:  blocker    |  Milestone:  v1.0
 Component:  BibUpload  |    Version:
Resolution:             |   Keywords:
------------------------+----------------------
Changes (by simko):

 * status:  in_merge => assigned


Comment:

 As you mentioned, on-the-fly allocation may be quite a dangerous default.
 For example, user mistypes 001 to contain 99999999 and bad things will
 happen to intbitset length.  (We used to have large holes in Aleph
 precisely due to similar mishap.)  To be on the safer side, it would be
 preferable to output an error as the default behaviour -- in which case
 users would have to create empty `bibrec` entries to push such dump-and-
 load jobs, as is the case now.

 In order to satisfy both user scenarios in a user friendly way, let us
 introduce a new CLI parameter called `--force` that would enable on-the-
 fly forcing of record IDs. (By default, the option would be off so that an
 error would be emitted.)  This would mean to wrap your changes into an if-
 else statement depending on the value of `--force`, so to speak. Please
 amend and please update the documentation as well.

-- 
Ticket URL: <http://invenio-software.org/ticket/721#comment:4>
Invenio <http://invenio-software.org>

Reply via email to