content-analysis-on-aws

content-analysis-on-aws copied to clipboard

.//deployment/media-insights-stack.yaml:605: # TODO: Update cors config per: https://docs.amplify.aws/lib/storage/getting-started/q/platform/js#using-amazon-s3

brandold

tl;dr - don't let your stack name contain "aws" --- The `MieCognitoDomain` step had a with `"Domain cannot contain reserved word: aws (Service: AWSCognitoIdentityProviderService; Status Code: 400; Error Code: InvalidParameterException;...

hakanson

Add front-end validation for image assets. Currently, we only validate video assets.

ianwow

Create "NightsWatch"-esque Github Actions test job for CAS

ianwow

The transcribe stage of the video workflow fails when processing long videos (> 1 hour) with the following error: `...r', 'MetaData': {'transcribe_error': 'An error occurred (BadRequestException) when calling the StartTranscriptionJob...

ianwow

Some of the languages supported by transcribe and translate are not listed as options in the workflow configuration form shown on the Upload view. Please check with the service docs...

ianwow

**Describe the bug** The bad-words package used to detect profanity in the transcript only supports english, and consequently causes confusion when it falsely labels non-english transcripts as profane. Therefore, the...

ianwow

The upload form needs to allow users to select a source language for the transcribe operator. It currently assumes that is english.

ianwow

Users need to be able to find assets by searching for their filenames. Currently they can't do that.

ianwow

Every workflow listed in the the Upload view will send a request to get its status at the same time. This won't scale very well. Something should be done to...

ianwow