AWS and data blob, assistance required. -- 2

Preferred language: Ruby, Python, or JavaScript Storage: AWS S3 Framework: Rails, prepared to change this to better integrate with AWS S3 and and other required users. Also: Lambda, REST API Required: login/logout functionality, including email verification for new accounts, email/password resets, (without using gmail or facebook or AWS) different levels of permissions (user/team member, leader (of members and their groups), administrator (of one or more Leaders), web site administrator. password security, white lists, security protocols to improve form security, etc. . friendly URL User and manager data held: first name last name username tasks allocated (by leader and/or admins) submissions (stored on s3) – recordings and details (date, user etc.) TRANSCRIBE AWS lambda results (stored different s3) - results from recording (json) callable once available and requested email password Levels of users: 1. Guest – no login, small trial from set examples. 2. Member (of team) 3. Leader (of team) 4. Administrator (of team) 5. Site Administrator (for everything) Main process of site> Site Administrator: 1. Can add members, leaders and administrators 2. Can change all passwords/users 3. Can set tasks 4. Can view completed tasks Administrator (team): 1. Can add Members and Leaders and change their details (manually or by uploading a list of names and respective emails – CSV or txt) 2. Can set tasks for LEADERS and/or all of a TEAMS MEMBERS (under them) 3. Can review progress of members tasks 4. Can review tasks set and task completion (transcriptions) of all LEADERS and MEMBERS under their level. Leader (of team) 1. Can add MEMBERS (not other Leaders) (manually or by uploading a list of names and respective emails) 2. Can set tasks to specific and/or all of their members – by drag and drop text, doc, pdf, jpg or html and choosing which members must do the task 3. Can review progress of members tasks 4. Can review task completion (transcriptions) of all their team members Member: 2. Selects a task from their provided options (if any given by their Leader) 3. Turns on ‘onboard microphone’ (permissions required) 4. Records audio – the recording can be paused, continued, stopped 5. Audio made available for them to review/listen to before submitting 6. The member may record again, as multiple recordings pop up as the recording is stopped/finished. 7. The member then chooses which recording is to be SUBMITTED (saved to s3 bucket) 8. Saved recording is saved to the S3 bucket, with the users name, member number, task details, in the file name for retrieval etc. 9. The users file is TRANSCRIBED (AWS Transcribe using Lambda) 10. The TRANSCRIBED file is returned to a different s3 bucket to the first (there should be identifying elements in the file name, including name, member number etc. 11. The transcription (JSON) should be available to the members on their ‘completed task’ page. (the results should also be available to the Admin/Leader. Guest: Similar to Member, without login, and only three tasks to choose from – set by Administrator. Notes: AWS has provided generic lambda to move the files between the buckets via Transcribe. S3 buckets need to be secure – they can not be completely open to the public, only those using the site – of the relevant authority. Audio format must be in WAV or mp3. The time to Transcribe varies before the results are passed to the S3 bucket, a symbol should appear in the Members/Leaders account to show that a file is being processed and, eventually, when it is available. Tasks set by the Leader and/or Administrator should be able to be dragged and dropped or selected and submitted. No content as such to be added yet, we require the CRUD functionality for the Member/Leader/Administrator/Site Admin, but requires ability to resize for different devices. Members signed up by Leaders/Administrators/Site Admins or casually. Files attached show recording require