CDR Tickets

Will we be able to make a clean switch to the new numbering system, or will there be a batch using the old arbitrary numbering system still in the pipeline, ~oseipokuw?

We can make a clean switch. That is, I will not generate a new spreadsheet on PROD until this modification has been released.

Good. Here are the tasks which will need to be performed for this ticket, then.

1. Add generation of filenames with the new naming pattern to AudioRequestSpreadsheet.py

2. Change the expected filename pattern in the FtpAudio.py download script

3. Change the expected filename patterns in GlossaryTermAudioReview.py

4. Change the expected filename patterns in LoadGlossaryAudioFiles.py

5. Archive sets created with the old naming schema (using the file sweeper)

6. Perform end-to-end testing of the entire workflow pipeline

✔ Add generation of filenames with the new naming pattern
✔ Change the expected patterns in the download script
✔ Change the expected patterns in the review script
✔ Change the expected patterns in the import script
✔ Archive sets created with the old naming schema

I have added the following spec to the file-sweeper specifications on DEV and I ran a sweep job to archive sets which used the older naming pattern. We'll need to do this on all the tiers.

  <SweepSpec Tiers="PROD STAGE QA DEV">
    <Name>Archive legacy audio files on all tiers</Name>
    <Action>Archive</Action>
    <InputRoot>/cdr/Audio_from_CIPSFTP</InputRoot>
    <InputFiles>
      <File>Week_???.zip</File>
      <File>Week_???_Rev?.zip</File>
    </InputFiles>
    <OutputFile>/cdr/Audio_from_CIPSFTP/JobArchive/LegacyAudio</OutputFile>
    <Oldest>2</Oldest>
    <Youngest>1</Youngest>
  </SweepSpec>

Modifications installed on DEV.

Verified on DEV. Thanks!

Verified on QA. Thanks!

Verified on PROD. Thanks!

Verified on PROD.  Thanks!