Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BCUL] - Reingest years 1866 and 1867 of TouSuIl #132

Open
piconti opened this issue Jul 30, 2024 · 1 comment
Open

[BCUL] - Reingest years 1866 and 1867 of TouSuIl #132

piconti opened this issue Jul 30, 2024 · 1 comment
Assignees

Comments

@piconti
Copy link
Member

piconti commented Jul 30, 2024

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.

@piconti piconti self-assigned this Jan 15, 2025
@piconti
Copy link
Member Author

piconti commented Jan 15, 2025

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant