# Editing Text and Linking Audio via Annotation Instructions **URL:** \ **Category:** Uncategorized\ **Tags:** usage, audio\ **Created:** [August 2, 2022, 5:44pm UTC](https://support.prodi.gy/t/editing-text-and-linking-audio-via-annotation-instructions/5841 "2022-08-02T17:44:55Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![jai](https://avatars.discourse-cdn.com/v4/letter/j/5f9b8f/32.png) [@jai](https://support.prodi.gy/u/jai)\ **Post date:** [August 2, 2022, 5:44pm UTC](https://support.prodi.gy/t/editing-text-and-linking-audio-via-annotation-instructions/5841/1 "2022-08-02T17:44:55Z")
Hi we are looking into different platforms for annotation and really like Prodigy from what we have seen so far. There are two features in which I was unclear if Prodigy could support: 1. Linking some specific audio per each document 2. Editing raw text in each document along w/ the annotation task (span categorization and relation labeling) Our use case is that we have some audio files and their transcriptions that we would like to do some span categorization and relation labeling on. However, sometimes the audio quality is poor so we would like our annotators to fix mistranscribed words hence the need to edit the raw text in each document and the ability to display the specific audio for each doc. Thanks ---
**Author:** ![ryanwesslen](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ryanwesslen/32/2969_2.png) [@ryanwesslen](https://support.prodi.gy/u/ryanwesslen)\ **Post date:** [August 2, 2022, 6:37pm UTC](https://support.prodi.gy/t/editing-text-and-linking-audio-via-annotation-instructions/5841/2 "2022-08-02T18:37:36Z")
hi @jai! Thanks for your question and welcome to the Prodigy community 👋 For audio transcription, you could use the [`audio.transcribe`](https://prodi.gy/docs/recipes#audio-transcribe) recipe. If all of your audio files are unique, you could load them along with the transcription as files like .jsonl. You may need to do a small amount of python pre-processing but [check out the file loader docs for audio](https://prodi.gy/docs/recipes#audio-transcribe). Just had a similar request earlier this week on how to handle a raw `.csv` file: > [@ASR text correct/edit recipe](https://support.prodi.gy/t/asr-text-correct-edit-recipe/5833/8): > > Take a glance at the documentation of [audio.transcribe recipe](https://prodi.gy/docs/recipes#audio-transcribe) details. Yep - your video could have the path/URL to your individual files (i.e., correspond to each row in your original .csv that is a unique audio cut based on start and end times). Then, you can add to your command the field-id where you can put the field name of your text text. Alternatively, the default is transcript so if you change the field name to transcript, by default, it would read that field without needing to be expli… > [@jai](#): > > Editing raw text in each document along w/ the annotation task (span categorization and relation labeling) You can combine [different recipes to create custom recipe/interfaces using blocks](https://prodi.gy/docs/custom-interfaces#blocks). So if you wanted, you could combine different interfaces like the `audio.transcribe` with the [`rel.manual`](https://prodi.gy/docs/recipes#rel-manual), which would enable labeling spans/relations. The one tricky part is that if the user had to correct to a transcription, you'd need to update (refresh) the text passed to the `rel.manual` after the user has used the textbox to correct the transcription. Does this sound right? For this, you'd likely need to use an [update / callback](https://prodi.gy/docs/custom-recipes#callbacks) using some JavaScript. There is an [example of something similar](https://prodi.gy/docs/custom-interfaces#javascript) where we show how you can use a button to change existing text to a different case. In theory, I suspect you could try to do the same with a text box that first provides the original transcription, then a user can edit/correct it. Then they could click the button to activate the call back which then updates the corrected transcript and resends to the `rel.manual`. I haven't tried this but would be interested to see if it's possible. Alternatively, perhaps the simplest solution would be to run this in two rounds. Round 1, you simply fix/correct transcriptions with `audio.transcribe`. Round 2, you use corrected transcriptions only in `rel.manual` and treat it like a typical span/relations annotation. I tend to prefer simpler tasks then trying to do everything at the same time, so I would likely choose this route. Thanks again for your question and let us know if you have further questions! ---
**Author:** ![jai](https://avatars.discourse-cdn.com/v4/letter/j/5f9b8f/32.png) [@jai](https://support.prodi.gy/u/jai)\ **Post date:** [August 3, 2022, 6:23am UTC](https://support.prodi.gy/t/editing-text-and-linking-audio-via-annotation-instructions/5841/3 "2022-08-03T06:23:04Z")
> [@ryanwesslen](#): > > The one tricky part is that if the user had to correct to a transcription, you'd need to update (refresh) the text passed to the `rel.manual` after the user has used the textbox to correct the transcription. Does this sound right? Yes thats correct. We can't go with the route of running multiple rounds because we don't want our annotators to correct everything in the transcription (there can be a lot); we only want them to correct them if they are relevant for span and relation labeling. I think the button to update text maybe the way to go then.