This is an automated notification sent by LCG Savannah.
It relates to:
task #6202, project CDS Invenio
==============================================================================
LATEST MODIFICATIONS of task #6202:
==============================================================================
Update of task #6202 (project cdsware):
Assigned to: None => skaplun
==============================================================================
OVERVIEW of task #6202:
==============================================================================
URL:
<http://savannah.cern.ch/task/?6202>
Summary: treatment of empty files/fields should be
configurable
Project: CDS Invenio
Submitted by: simko
Submitted on: 2008-01-21 11:19
Should Start On: 2008-01-21 00:00
Should be Finished on: 2008-01-21 00:00
Category: BibUpload
Priority: 5 - Normal
Status: None
Privacy: Public
Percent Complete: 0%
Assigned to: skaplun
Open/Closed: Open
Discussion Lock: Any
Effort: 0.00
_______________________________________________________
Currently bibupload reports an error ("Cannot parse MARCXML file") if the
input file does not contain any record, or if a record is empty. This error
makes bibsched not to run any other scheduled bibupload jobs in the queue,
waiting for manual problem resolution.
The reason behind this philosophy was basically worries of the kind "what if
input file was wrongly created?". But ideally these worries should be
configurable in order not to bother sites like Indico Search that have known
empty input files coming from harvested sites, indicating no problem, so no
error reporting is wanted (a warning perhaps would be good) and the queue
should not get stopped because of that.
Solution: introduce an internal bibupload's config variable such as
CFG_BIBUPLOAD_TREAT_EMPTY_RECORDS_AS_ERROR, with default being False, most
probably.
(Ditto for a possibility to silently ignore empty fields/subfields that IIRC
are allowed by the MARCXML schema specification but that are currently
treated as error by bibupload. See also some slight differences between
MARCXML schema and the MARCXML DTD we are using for RXP validating parser.)
_______________________________________________________
Carbon-Copy List:
CC Address | Comment
------------------------------------+-----------------------------
2195 | -UPD-
1576 | -SUB-
==============================================================================
This item URL is:
<http://savannah.cern.ch/task/?6202>
_______________________________________________
Message sent via/by LCG Savannah
http://savannah.cern.ch/
