You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: