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
Awesome work making this! I have a quick query on usage/working of the "For review" tab. I see that whenever a file is uploaded, no other user can access it except the user it is uploaded for. After annotating, The overall labelled file can be downloaded, but they cannot approved by on the UI (In the dashboard under projects).
Ideally, an annotation approver needs to go through the transcription/labels, and approve them for multiple transcribers/annotators. Is there a way to have any approver look at the annotation done on audio? Is there a way another user can review the annotations? am I missing something?
The text was updated successfully, but these errors were encountered:
Currently, our definition of reviewing was that user (who was assigned the audio for annotation) can mark the audio for review so that they can revisit the audio after potential discussion with the team. I understand your usecase which is something we used to do post annotation of the audio. I'm thinking of providing admin permission to view all audios including ones marked for review which should make this easier. Do you have a suggestion for this?
Hi MIDAS team,
Awesome work making this! I have a quick query on usage/working of the "For review" tab. I see that whenever a file is uploaded, no other user can access it except the user it is uploaded for. After annotating, The overall labelled file can be downloaded, but they cannot approved by on the UI (In the dashboard under projects).
Ideally, an annotation approver needs to go through the transcription/labels, and approve them for multiple transcribers/annotators. Is there a way to have any approver look at the annotation done on audio? Is there a way another user can review the annotations? am I missing something?
The text was updated successfully, but these errors were encountered: