Conversation
docs/source/overview.rst
Outdated
| of this process to decide if this obfucated summary can be released out of the private | ||
| network. | ||
|
|
||
| The Repopulate process happens outside of the private network and outside of the remit |
There was a problem hiding this comment.
| The Repopulate process happens outside of the private network and outside of the remit | |
| The Repopulate process can happen outside of the private network and outside of the remit |
docs/source/overview.rst
Outdated
| of Information Governance. This is important! The act of turning reduced | ||
| obfucated data into a larger quantity of randomized data is *not* a privacy-sheilding | ||
| process! By this time all the actual privacy-sheilding has already happened and | ||
| the Information Governance has already been applied. |
There was a problem hiding this comment.
| the Information Governance has already been applied. | |
| the Information Governance restrictions have already been applied. |
docs/source/overview.rst
Outdated
| However it is not impossible that, in describing the structure of some commercial | ||
| database, some commercially-sensitive information could be leaked. |
There was a problem hiding this comment.
| However it is not impossible that, in describing the structure of some commercial | |
| database, some commercially-sensitive information could be leaked. | |
| However, in describing the structure of some commercial | |
| database, some commercially-sensitive information could be leaked (i.e. columns and their linkages. |
There was a problem hiding this comment.
Just thinking this sentence doesn't make any sense even with the clarification. How can the schema be sensitive? I've tried DuckDuckGoing for this and it's a really hard thing to search for. I tried asking Duck.ai and it's even more useless than you'd think. So, I think rather than strengthening this sentence, let's delete it unless we can come up with an actual commercial database for which the schema itself is commercially sensitive.
There was a problem hiding this comment.
oh this is a genunine thing. We can't publish Epic column names and table names for caboodle/clarity because they state its their IP and they aren't afraid to use lawyers
Mermaid diagrams can be embedded in docs Table CSS fixed
Does this work?
tim-band
force-pushed
the
overview_documentation
branch
from
910c6fc to
1b9f2eb
Compare
2 participants
Uh oh!
There was an error while loading. Please reload this page.