#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:
------------------------+----------------------
Comment (by skaplun):
Mmh...
I have a small doubt. I would be against storing as 1234, because that
would create a hole in the system. Although... maybe this would be exactly
the desired behavior. And we might be even be safe on this by updating on
the fly the auto_increment index of the recid.
But storing it to 345 is misleading, because user has explicitly set the
001.
Spitting out an error and not allowing this situation wouldn't help,
because the user might really want to put the record in 1000 (imagine if
he is re-loading an Invenio instance from an MARCXML dump). The user would
not have a chance to do this.
So finally I think I am going to implement an on-the-fly allocation of
recid.
Would you agree?
--
Ticket URL: <http://invenio-software.org/ticket/721#comment:2>
Invenio <http://invenio-software.org>
