Closed sn0708 closed 5 years ago
This is coming on well, I think we need to make some of the rules conditional on the user and context inputs. For example have recipes filtered by whether the User has certain dietary needs. My only concern with this example is whether new people will just see Palisade as a filtering tool, and not get the FGS aspects. However I cannot think of a better example
We could drive the behaviour from user attributes, but I think we still need to tidy up the SimpleClientExample or refactor it so that its clearer how the elements interact. We could also add other examples to demonstrate FGS applications?
Having taken a good look at the data sets that are publicly available, I have come to the conclusion that we need to create our own fake data generator as none of the data sets have the volume, nested nature and being a dataset that you might realistically want to apply Palisade to protect. Therefore I think we need to fake some HR data which we can then generate as many records of data as we require for testing the performance of Palisade at scale.
merged into develop
branch to bring complex data packages up to latest codebase and add extra example files in Avro