table status of tul before and after vanilla import #144
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem description
Check if all data was imported after the vanilla import.
Analysis
The vanilla import is not using a pump. Run the import based on the import instructions: Migrating DSpace to a new server and check database consistency.
Solution
We ran the vanilla import based on the instructions and created scripts to capture the database status before and after the import.
The differences before and after the import are as follows:
Database difference:
bitstreamformatregistry: 12 surplus
checksum_results: 1 surplus
fileextension: 13 surplus
metadatafieldregistry: 5 surplus
metadataschemaregistry: 1 surplus
schema_version: 6 surplus
Differencesare because DSpace7 contains more default data. All tables from DSpace5 exist in DSpace7.