You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As already discussed with Theophile, there were a few duplicated issues in the BCUL data, for which the duplicated identifier was not valid anymore (removed form the API).
Most of them had been identified during the canonical (or rebuilt) ingestion, but three were remaining in TouSuIl (Le Touriste - la Suisse Illustrée).
The issues are the following:
287545, 1866-09-01
287530, 1866-08-01
287477, 1867-02-01
Unfortunately, they were processed after their correct counterpart, so the page files were overwritten with faulty information.
Fixing them by hand is possible, but could be prone to errors.
It seems more adapted to re-ingest the two specific years of the BCUL data as part of the next ingestion, to ensure this problem is fixed.
Currently, the issues were simply ignored from the MySQL ingestion.
The text was updated successfully, but these errors were encountered:
Since more BCUL data has arrived and will be ingested, it can be practicle to re-ingest these two years of TouSuIl at the same time.
Action points for this issue would be:
check if the issue IDs listed above are among the ones filtered when ingesting BCUL data and if the problem has been fixed on BCUL's side (see echange of emails)
reingest these years and ensure the problem is fixed
As already discussed with Theophile, there were a few duplicated issues in the BCUL data, for which the duplicated identifier was not valid anymore (removed form the API).
Most of them had been identified during the canonical (or rebuilt) ingestion, but three were remaining in
TouSuIl
(Le Touriste - la Suisse Illustrée).The issues are the following:
Unfortunately, they were processed after their correct counterpart, so the page files were overwritten with faulty information.
Fixing them by hand is possible, but could be prone to errors.
It seems more adapted to re-ingest the two specific years of the BCUL data as part of the next ingestion, to ensure this problem is fixed.
Currently, the issues were simply ignored from the MySQL ingestion.
The text was updated successfully, but these errors were encountered: