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 is described with patch #4 in this google sheet, there is a problem with the logic separating the identified regions into content-items in the BNL data.
Given that the content-items are created and remerged in the importer's code, some problems most probably stem from there.
The goal is thus to re-think the implementation of the logical construction of content items in the BNL importer.
Note that this will most probably break current content-item IDs for all concerned BNL data.
Ideally, this is also done when ingesting the updated OCR for the BNL data.
The text was updated successfully, but these errors were encountered:
New information on this issue:
It has been found that the version of the data visible on the interface is actually not the version of the data in the S3 of the last release documented, but a prior version.
It may be that the problem with the BNL article reconstrution had indeed been fixed and that it would not be necessary to fix it.
However, this probably means that there will be a break in the content-item Ids
As is described with patch #4 in this google sheet, there is a problem with the logic separating the identified regions into content-items in the BNL data.
Given that the content-items are created and remerged in the importer's code, some problems most probably stem from there.
The goal is thus to re-think the implementation of the logical construction of content items in the BNL importer.
Note that this will most probably break current content-item IDs for all concerned BNL data.
Ideally, this is also done when ingesting the updated OCR for the BNL data.
The text was updated successfully, but these errors were encountered: