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.

Sign up for GitHub

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

Jump to bottom

Importing - 88: A new bitstreams are not sync with S3 - why? #597

Closed
milanmajchrak opened this issue Apr 8, 2024 · 1 comment
Closed

Importing - 88: A new bitstreams are not sync with S3 - why? #597

milanmajchrak opened this issue Apr 8, 2024 · 1 comment
Assignees
@MajoBerger
Labels
2024_BE need priority

Comments

@milanmajchrak
Copy link
Collaborator

milanmajchrak commented Apr 8, 2024 •
edited
Loading

Importing creates only Bitstream object with the metadata - synchronization with S3 must be done in other way.
@milanmajchrak milanmajchrak mentioned this issue Apr 11, 2024
Open
@MajoBerger
Copy link

When dump is imported, files are stored directly in /dspace/assetstore inside the container.
Therefore, from the point of view of python script import, they are already there. They are not uploaded by REST API.
Therefore, it makes sense that files are not in S3.

This behavior is expected and there is nothing wrong with this.

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

@MajoBerger MajoBerger

Labels
2024_BE need priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MajoBerger @milanmajchrak