Issue: Complex JSON -> RPC -> Redux -> Ui data handling

[oenu]

Duplicating state from json -> sqlite -> redux was a massive headache that should be avoided

My proposal is using Realm to store the data in a fast and local mongoDB instance, then each audio file can have multiple 'jobs' attached to it as documents, each with collections of 'lines' from the script. These could be added from multiple streams without having to worry about attribution or FS collisions.

Realm (as a database for fast mobile development) has the ability to be queried from the render process.

Steps to implement

• Test Realm connection
• Design Database Schema
• Init database
• Hook up stdio
• Remove redux functions
• Migrate pages to request driven rendering

[petersterne]

How long will this take you to implement?

[petersterne]

@oenu I know you looked into using Realm DB and found it wouldn't be feasible. Should we close this issue or do you still want to find another way to handle the transcription database?