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
In our multiple large import tests, we find that .odt files which are attached to every migrated work cause errors and incomplete ingests as CreateDerivative jobs are run on them. At this point, it's not clear if it is the attempt to create a thumbnail image or if text extraction is occurring when these jobs fail or cause the application processes to hang.
These files are important for preservation, but are always set to Private and will not be seen by end-users. We also anticipate that not many users would ever manually upload one of these files, as the majority of deposits are either PDF or standard MS Office files.
For this ticket, we want to investigate the level of effort to:
Exclude .odt files from CreateDerivatives jobs
Ensure that other types of plain text documents (.txt, .rtf) can still be submitted through normal manual deposit processes
The text was updated successfully, but these errors were encountered:
In our multiple large import tests, we find that
.odt
files which are attached to every migrated work cause errors and incomplete ingests as CreateDerivative jobs are run on them. At this point, it's not clear if it is the attempt to create a thumbnail image or if text extraction is occurring when these jobs fail or cause the application processes to hang.These files are important for preservation, but are always set to Private and will not be seen by end-users. We also anticipate that not many users would ever manually upload one of these files, as the majority of deposits are either PDF or standard MS Office files.
For this ticket, we want to investigate the level of effort to:
The text was updated successfully, but these errors were encountered: