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
And similar lines in the other runners (in this case tika and siegfried),
Based on discussions with the team, I think we need this information to be exposed to the logging to be able to be better analysed down-stream. Will bring this offline to discuss more.
The text was updated successfully, but these errors were encountered:
since indexer errors are part of the indexer result structure, they are not yet logged. we have to decide whether we will log them where they appear (indexer) or just log the errors from the result structure
no errors found means, that there are no structural ocfl errors. eventually we should use a different wording
Given the command below, with gocfl compiled with extensions:
We see errors in the indexer packages
test_dir_xml1/v1/content/metadata/indexer_v1.json
:But the errors aren't making it into the logs here:
NB. we also exit okay with
no errors found
.Providing I am reading through the code correctly, it is written into the indexer file here:
gocfl/pkg/extension/NNNN-indexer.go
Lines 357 to 369 in 714abed
E.g. for convert, tt's first recorded in the indexing tool here: https://github.com/je4/indexer/blob/a02d015d6289f5687d43af935eb064ef104615a6/pkg/indexer/actionIdentifyV2.go#L139-L141
And similar lines in the other runners (in this case tika and siegfried),
Based on discussions with the team, I think we need this information to be exposed to the logging to be able to be better analysed down-stream. Will bring this offline to discuss more.
The text was updated successfully, but these errors were encountered: