Publication log and report contradict each other after canceled publication

[matdillen]

I published a new version of an existing dataset on our IPT server. This new publication was going to fail, because there was a delimitation problem (field quotes had the wrong symbol). Hence, I canceled it, fixed the problem and published again. This time the publication was successful, as indicated in the publication log. The update has also been ingested by GBIF.

However, the publication report still indicates this version as failed due to fatal error. Additionally, while the IPT window where the publication process can be followed initially showed the (successful) log, it later replaced this by the (unsuccessful) report. This lead me to think the second publication failed as well, although this was not the case and investigating the GBIF monitoring tools supported this.

The timestamp of failure in the report seems to suggest the first (faulty) publication process may not have been cancelled, although this could not possibly take 30 minutes. It may have taken the timestamp from the successful process or only wrapped up the faulty process after the succesful one.

Dataset: http://apm-ipt.br.fgov.be:8080/ipt/resource?r=botanical_collection

Publication report:

Publication log:

Archive generation started for version #1.17
Start writing data file for Darwin Core Occurrence
No lines were skipped due to errors for mapping Darwin Core Occurrence in source dwcfilecorrected2021-02-101051am
No lines were skipped due to errors for mapping Darwin Core Occurrence in source dwcfilecorrected2021-02-101051am
No lines with fewer columns than mapped for mapping Darwin Core Occurrence in source dwcfilecorrected2021-02-101051am
All lines match the filter criteria for mapping Darwin Core Occurrence in source dwcfilecorrected2021-02-101051am
Data file written for Darwin Core Occurrence with 1796902 records and 42 columns
Start writing data file for Darwin Core Identification History
No lines were skipped due to errors for mapping Darwin Core Identification History in source dwcidentification2021-02-101047am
No lines were skipped due to errors for mapping Darwin Core Identification History in source dwcidentification2021-02-101047am
No lines with fewer columns than mapped for mapping Darwin Core Identification History in source dwcidentification2021-02-101047am
All lines match the filter criteria for mapping Darwin Core Identification History in source dwcidentification2021-02-101047am
Data file written for Darwin Core Identification History with 320440 records and 5 columns
Start writing data file for Simple Multimedia
No lines were skipped due to errors for mapping Simple Multimedia in source simplemultimedia-2021-02-10_14-16
No lines were skipped due to errors for mapping Simple Multimedia in source simplemultimedia-2021-02-10_14-16
No lines with fewer columns than mapped for mapping Simple Multimedia in source simplemultimedia-2021-02-10_14-16
All lines match the filter criteria for mapping Simple Multimedia in source simplemultimedia-2021-02-10_14-16
Data file written for Simple Multimedia with 1393256 records and 8 columns
All data files completed
EML file added
meta.xml archive descriptor written
Validating the core file: occurrence.txt. Depending on the number of records, this can take a while.
? Validating the core basisOfRecord is always present and its value matches the Darwin Core Type Vocabulary.
? Validating the core ID field occurrenceID is always present and unique. Note: the core ID field is required to link core records and extension records together. 
No lines are missing occurrenceID
No lines have duplicate occurrenceID
✓ Validated each line has a occurrenceID, and each occurrenceID is unique
No lines are missing a basisOfRecord
All lines have basisOfRecord that matches the Darwin Core Type Vocabulary
5677 line(s) use ambiguous basisOfRecord 'occurrence'. It is advised that occurrence be reserved for cases when the basisOfRecord is unknown. Otherwise, a more specific basisOfRecord should be chosen.
✓ Validated each line has a basisOfRecord, and each basisOfRecord matches the Darwin Core Type Vocabulary
Validating the extension file: identification.txt. Depending on the number of records, this can take a while.
? Validating the ID field occurrenceID is always present in extension data file. 
✓ Validated each line in extension has an ID occurrenceID
No lines in extension are missing an ID occurrenceID
Validating the extension file: multimedia.txt. Depending on the number of records, this can take a while.
? Validating the ID field occurrenceID is always present in extension data file. 
✓ Validated each line in extension has an ID occurrenceID
No lines in extension are missing an ID occurrenceID
Archive validated
Archive has been compressed
Archive version #1.17 generated successfully!