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

Jhove errors - migrating a large number of historical files #916

Open
JuliaWahlund opened this issue Mar 12, 2024 · 2 comments
Open

Jhove errors - migrating a large number of historical files #916

JuliaWahlund opened this issue Mar 12, 2024 · 2 comments
Assignees
Labels
P1 High priority issues to be scheduled in the upcoming release question

Comments

@JuliaWahlund
Copy link

Hello!

My name is Julia Wahlund and I work as a product manager at the National Library of Sweden. We are currently in a migration project where we are migrating a lot of digital files to our preservation platform. While we are doing this, we are validating our files using JHOVE. We have encountered some issues previously that we have fixed, but now we have more issues with files not being able to validate.

We have divided it up into files that can be opened/rendered and files that cannot be opened.

Errors for files that CAN be opened are:

  1. 2311331 JHOVE_ERR: "Not well-formed" : "File is too short"
  2. 974933 JHOVE_ERR: "Not well-formed" : "No TIFF header: ¢_"
  3. 974937 JHOVE_ERR: "Not well-formed" : "Premature EOF"
  4. 2311324 JHOVE_ERR: "Not well-formed" : "No TIFF header: r"

Errors for files that CANNOT be opened are:

  1. 2278540 JHOVE_ERR: "Not well-formed" : "No TIFF header: 8B"
  2. 2023591 JHOVE_ERR: "Not well-formed" : "Type mismatch for tag 36864; expecting 7, saw 2"
  3. 2311329 JHOVE_ERR: "Not well-formed" : "Unknown TIFF IFD tag: 34152"
  4. 974935 JHOVE_ERR: "Not well-formed" : "Unknown data type"

Do you have any suggestions on how to fix these files? Last time we had an error for not well formed tiffs, we resaved them after talking to some experts within digital preservation area and then they validated. And then we saved some preservation metadata for this action. But these errors are hard to find information around, so we are not so sure what we can do about it.

Looking forward to hearing from you,

Best regards,

Julia Wahlund

@JuliaWahlund
Copy link
Author

My bad. It is the other way around on the errors. So first title and section should be "cannot be opened" and the second title and section should be "can be opened"

@GeorgiaMoppett
Copy link
Contributor

Hi Julia,

Thank you for your logged issue! We're having a look at this now, and will follow up soon.

@GeorgiaMoppett GeorgiaMoppett self-assigned this Mar 28, 2024
@GeorgiaMoppett GeorgiaMoppett added question P1 High priority issues to be scheduled in the upcoming release labels Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 High priority issues to be scheduled in the upcoming release question
Projects
None yet
Development

No branches or pull requests

2 participants