From 36d5632150d774cb874b620354cebebe99d8cc7c Mon Sep 17 00:00:00 2001 From: mribary <m.ribary@surrey.ac.uk> Date: Fri, 18 Dec 2020 22:12:16 +0000 Subject: [PATCH] Graph update --- Ddf_documentation.md | 2 +- SQL_documentation.md | 2 +- sql/README.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/Ddf_documentation.md b/Ddf_documentation.md index a2ec98b..409fcb0 100644 --- a/Ddf_documentation.md +++ b/Ddf_documentation.md @@ -6,7 +6,7 @@ The documentation describes the creation of the core dataframes of the `pyDigest The dcumentation follows the order of output files stored in the prject's `dump` folder. The title of individual steps include the method and the name of the output file in the format of `[Method] > [outputFile]`. The `[Method]` is either (1) manual or (2) executed in Pyhton files which are stored in the `script` folder. The `[Method]` and `[outputFile]` correspond with elements in `Ddf_flowchart`. These steps document the data manipulation pipeline from the raw text of the _Digest_ to its [relational database](link). - + 1. Manual editing > ROMTEXT.txt diff --git a/SQL_documentation.md b/SQL_documentation.md index b379a19..22a7c5d 100644 --- a/SQL_documentation.md +++ b/SQL_documentation.md @@ -16,7 +16,7 @@ The core structure of the `digest` database is drafted in the yEd graph editor a The graph below is a visual representation of the tables in the database. Each table includes an "id" as primary key (PK) and one or more foreign keys (FK) which point to the "id" columnn of a different table. It is by foreign keys that the tables are chained together in many-to-one relationships. The entity boxes for the tables include the names and datatypes of the columns where "tinyint" and "smallint" are two types of integer, "varchar" is a limited length, while "text" is an unlimited length text type. The three colours indicate the three different sources from which the tables are created. Tables in shaded blue are created from the same source as the core "text" table, i.e. the _Digest_ text as presented in Amanuensis, but they were separated to structure the information. - + 3. `D_sql_create_tables.py > digest_skeleton.db` diff --git a/sql/README.md b/sql/README.md index 9c39701..f12b8a9 100644 --- a/sql/README.md +++ b/sql/README.md @@ -78,7 +78,7 @@ The "bko" table presents information related to the theory about the _Digest_'s The graph below is a visual representation of the tables in the database. Each table includes an "id" as primary key (PK) and one or more foreign keys (FK) which point to the "id" columnn of a different table. It is by foreign keys that the tables are chained together in many-to-one relationships. The entity boxes for the tables include the names and datatypes of the columns where "tinyint" and "smallint" are two types of integer, "varchar" is a limited length, while "text" is an unlimited length text type. The three colours indicate the three different sources from which the tables are created. Tables in shaded blue are created from the same source as the core "text" table, i.e. the _Digest_ text as presented in Amanuensis, but they were separated to structure the information. - + ### 3. Sample SQL queries -- GitLab