Issue Number | 4618 |
---|---|
Summary | Audio import creating duplicate records |
Created | 2019-05-17 12:51:31 |
Issue Type | Improvement |
Submitted By | Osei-Poku, William (NIH/NCI) [C] |
Assigned To | Kline, Bob (NIH/NCI) [C] |
Status | Closed |
Resolved | 2019-10-01 12:49:43 |
Resolution | Won't Fix |
Path | /home/bkline/backups/jira/ocecdr/issue.244284 |
The audio import tool we use for importing audio pronunciations appears to be creating and linking multiple media records to glossary terms. On May 10, 2019 a user ran the report by accident (I run this report exclusively and thought that no other CIAT user had access) and imported audio files contained in the Week 132 file . Multiple media docs were created and all the different media docs were linked to the glossary terms (I am not sure if the user tried the import multiple times or not). After the first link (which was correctly made publishable), subsequent links created invalid glossary term versions so the current version is invalid and multiple media documents are linked to the glossary terms. Could there be a problem with the permissions in the CDR ? I just made a change to one of the accounts but saving it produced a python script error. I will create a new ticket for this issue.
Examples:
1. 796814 - TRK protein family - Glossary term
Media documents created and linked to the glossary term above.
CDR0000797972
CDR0000798023
CDR0000798138
2. CDR0000796908 - trunk - Glossary term
Media documents created and linked to the glossary term above.
CDR0000797969
CDR0000798020
CDR0000798176
CDR0000798135
I'm looking at the log file for the audio import and can see that there have been a few program errors during the last import job. Some of these appear to be related to incorrectly named audio files. For instance, the spreadsheet is listing the CDR-ID 784947 but the audio file has been named 784987_en.mp3 (same for ES version).
There are two additional errors but I'm unable to identify their cause from looking at the log file and spreadsheet.
I'm closing this ticket.
As discussed at our last CDR meeting, I've created a new ticket for the error message I've noticed in the logs not related to running this tool twice.
Elapsed: 0:00:00.001365