Closed rudouglas closed 2 years ago
Hi @rudouglas 👋 Thank you for filing an issue! We'll triage your issue and let you know if we have questions, and then route it to the appropriate team so we can get it solved.
tables updated. im going to update documentation as well as part of this ticket (since its not anywhere else 🙈 ).
gonna call this done since the criteria are met & sprint end. documentation is almost ready.
Background
Follow the instructions in the Readme to set up your environment. This sets up a local docker container for a PGAdmin instance to manipulate the DB.
In order to reduce code duplication and effort, we will be adding a new column called
project_id
to a couple of existing tables. This is so we don't need separate tables for each type of translation, and can re-use the same scripts with a little tweaking.Edit Tables
Adding
project_id
to the following tables is necessary for us to know whether a page needs to be sent to Machine or Human translation project in Smartling, and also identify how it's been translated when we download it.translations
jobs
We can do that in the PGAdmin console via the
Query Tool
:⚠️ SPOILER - Click to see image!
⚠️ SPOILER - Click to see SQL Code!
```sql ALTER TABLE IF EXISTS public.jobs ADD COLUMN project_id TEXT NOT NULL; ALTER TABLE IF EXISTS public.translations ADD COLUMN project_id TEXT NOT NULL; ```Edit Resource Creation Code
We will also want to alter the SQL code for the Terraform resource creation in creation_and_cleanup.sql, adding the following to the
CREATE TABLE translations()
andCREATE TABLE jobs()
functions:⚠️ SPOILER - Click to see Code!
- `project_id TEXT NOT NULL`Testing Scripts
🛑 You can use the MT Project ID for this but only test with a 1 word change, see here
The reason for this is we have a
2 million
word limit per year specifically for Machine TranslationAcceptance Criteria
note:
All Deven team members should be given access to AWS. - @zstixUseful Links