CDR Tickets

Will be discussed at next week's status meeting.

As I mentioned in the CDR meeting yesterday with regards to storage for the files, we do not need the files stored forever so we can implement a solution similar to what we have for storing the board meeting audio recordings. That is, have the program delete all files that have been stored for a period of time. I also want to mention that we are currently not storing the board meeting recordings in the CDR as we used to do. We decided to store them on as needed bases so there should be plenty of storage to go around 🙂.

As promised in yesterday's project status meeting, here is a proposed approach for this request.

• we will use a separate database table for the attachments, storing the English summary ID, the file bytes, the file name, and the date the file was registered for the job

• we will continue to support multiple attachments per translation job

• we will expand the existing translation job editing form, displaying attachments which have been previously posted for the job, each with a checkbox for dropping the attachment, along with the fields which are already in place for adding new attachments

• an attachment will be retained until explicitly dropped using the button provided for that purpose on the form, or when the job is dropped from the active queue, whichever occurs first

I have reviewed the approach above and it looks good to me. Thank you!

Here is a mockup of the revised form.

Looks good to me. Please change the word "drop" to "delete" from the instructional text.  Thanks!

Enhancement implemented on CDR DEV.

Verified on DEV. Thanks!

Please delete the extra word "all" in the first sentence of the interface as seen the screenshot you posted above?

Fixed.

Verified on DEV. Thanks!

Verified on QA. Thanks!

Closing this ticket for now as we can't test immediately. I will report if we run into any problems.