Skip to content

Commit 1b9f2eb

Browse files
author
Tim Band
committed
Response to Stef's comments
1 parent eff4cc1 commit 1b9f2eb

1 file changed

Lines changed: 7 additions & 6 deletions

File tree

docs/source/overview.rst

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -63,11 +63,11 @@ the sensitive data can be read. Information Governance oversight happens at the
6363
of this process to decide if this obfucated summary can be released out of the private
6464
network.
6565

66-
The Repopulate process happens outside of the private network and outside of the remit
66+
The Repopulate process can happen outside of the private network and outside of the remit
6767
of Information Governance. This is important! The act of turning reduced
6868
obfucated data into a larger quantity of randomized data is *not* a privacy-sheilding
6969
process! By this time all the actual privacy-sheilding has already happened and
70-
the Information Governance has already been applied.
70+
the Information Governance restrictions have already been applied.
7171

7272
Reduction techniques
7373
--------------------
@@ -131,7 +131,8 @@ because the same amount of data is output as was input.
131131
Datafaker's Operation
132132
=====================
133133

134-
Datafaker is based on the Alan Turing Institute's SqlSynthGen tool.
134+
Datafaker is based on the Alan Turing Institute's
135+
`SqlSynthGen tool <https://github.com/alan-turing-institute/sqlsynthgen>`_.
135136
SqlSynthGen implements all three operations of Reduce, Obfuscate and Repopulate.
136137

137138
Datafaker builds on SqlSynthGen by automating the specification of the Reduce
@@ -178,9 +179,9 @@ Datafaker make-tables phase
178179
``datafaker make-tables`` makes a file called ``orm.yaml`` that describes the structure of the source database.
179180
This is part of the Reduce phase, but this file is used in every other Datafaker phase.
180181
By describing the structure of the database, no private data is leaked.
181-
However it is not impossible that, in describing the structure of some commercial
182-
database, some commercially-sensitive information could be leaked.
183-
In such a case, the file is alterable by hand as long as the YAML structure is maintained.
182+
However, if part of a commercial database's schema is considered commercially sensitive,
183+
this information would be leaked in the ``orm.yaml`` file.
184+
It may be possible to alter this file by hand to remove the sensitive information as long as the YAML structure is maintained.
184185

185186
Datafaker configuration phase
186187
-----------------------------

0 commit comments

Comments
 (0)