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

table status of tul before and after vanilla import #144

Merged
merged 2 commits into from
Jun 24, 2024

Conversation

Paurikova2
Copy link
Collaborator

@Paurikova2 Paurikova2 commented Jun 24, 2024

Phases MP MM MB MR JM Total
ETA 0 0 0 0 0 0
Developing 3 0 0 0 0 0
Review 0 0 0 0 0 0
Total - - - - - 0
ETA est. 0
ETA cust. - - - - - 0

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.

@Paurikova2 Paurikova2 linked an issue Jun 24, 2024 that may be closed by this pull request
@Paurikova2 Paurikova2 requested a review from MajoBerger June 24, 2024 06:44
Copy link
Contributor

@MajoBerger MajoBerger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we wanted to see differences between databases. I suggest modifying db.status() method slightly to obtain dictionary (or similar) and comparing those, e.g. with https://stackoverflow.com/a/50912266

@Paurikova2 Paurikova2 requested a review from MajoBerger June 24, 2024 07:28
@Paurikova2 Paurikova2 merged commit 96a2fbd into main Jun 24, 2024
1 check passed
@Paurikova2 Paurikova2 deleted the tul_table_difference branch June 24, 2024 08:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Check Database consistency on TUL dump
2 participants