Sometimes the BNF data has blocks or regions labelled as "tables" which then contain parts labelled as "images" which don't have coordinates or corresponding information in the ALTO.
This can sometimes lead to content items of type table having a "coordinates" field in the canonical, but having "null" as value, instead of actual coordinates, and somewhat acting as image regions.
This should be fixed, and can be done easily by identifying cases when the table/image confusion takes place and not adding coordinates and iiif_links when the CI's type is table.
In addition, one should ensure that the "image" parts within articles or logically segmented blocks are treated correctly, and should add the pOf field.
Sometimes the BNF data has blocks or regions labelled as "tables" which then contain parts labelled as "images" which don't have coordinates or corresponding information in the ALTO.
This can sometimes lead to content items of type table having a "coordinates" field in the canonical, but having "null" as value, instead of actual coordinates, and somewhat acting as image regions.
This should be fixed, and can be done easily by identifying cases when the table/image confusion takes place and not adding coordinates and iiif_links when the CI's type is table.
In addition, one should ensure that the "image" parts within articles or logically segmented blocks are treated correctly, and should add the
pOffield.