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

incorrect mapping between bitstreamforamt and fileextension #157

Closed
Paurikova2 opened this issue Jul 10, 2024 · 0 comments · Fixed by #162
Closed

incorrect mapping between bitstreamforamt and fileextension #157

Paurikova2 opened this issue Jul 10, 2024 · 0 comments · Fixed by #162
Assignees

Comments

@Paurikova2
Copy link
Collaborator

Paurikova2 commented Jul 10, 2024

We have two tables:

  • bitstreamformatregistry: id, mimetype, short_description, ...
  • fileextension: id, bitstream_format_id, extension.

The mapping between these tables is by bitstreamformatregistry id. The attribute short_description is unique.

Problem: In DSpace 7, new records were added to the bitstreamformatregistry table. We imported bitstreamformatregistry but without fileextensions. If data already exists in the database (short_description is not unique), the database throws an exception and we log the info. However, there are records where short_description values differ only in lower/upper case.

Problems:
Records in bitstreamformatregistry are imported without fileextensions.

Question:

  • Should we have a unique mimetype?
  • What if one mimetype in DSpace 5 had different extensions than in DSpace 7?

Test:
We need to validate the mapping, not only the id, but all columns must be correct because of the implicitly imported data!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment