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

Content preview - S3 #505

Closed
3 tasks
milanmajchrak opened this issue Jan 29, 2024 · 0 comments · Fixed by #691
Closed
3 tasks

Content preview - S3 #505

milanmajchrak opened this issue Jan 29, 2024 · 0 comments · Fixed by #691

Comments

@milanmajchrak
Copy link
Collaborator

milanmajchrak commented Jan 29, 2024

  • the preview content should be in some another (new) table

When a zip file is added to the item, there is a Preview button. This button rolls down all zipped files, which are always generated by this action. We don't want that! In DSpace5, this content is in the metadatavalue table from which these values are only loaded by this action. We want to create a NEW TABLE. The values will be generated only once and then saved in this table. After the second click, the values will only be loaded from this table.

  • Design the new table, column names, and types.
  • When will the data be generated? By script, during startup, installation, or first click?

Useful notes: clarin-dspace.cfg -> file.preview.enabled = TRUE, MetadataBitstreamRestRepository = get FilePreviewContent.
ProcessInputstreamToFile

Research: The idea is to save FileInfo into database and make many2many relationship between FileInfo. For now I created new database object, but maybe the FileInfo can be database object.

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

Successfully merging a pull request may close this issue.

2 participants