Our data comes from a relational database (postgres).
The anonymized data needs to be converted to an object form so that it is self contained and does not rely on any external lookups.
This already happens to some extent because our DTO's are constructed from a JPA entity which is an object created from links to multiple table relationships.
So, for example, a country field of a candidate (eg location or nationality) appears in the DTO as a country property with an id field and a name field.
For the anonymized data, the id is meaningless to anyone external (being a random internal database primary key of the Country table). We also need the two character ISO code (as well as the name for convenience) in the anonymized data.
Another example is occupations where, for external use, we need the ISCO08 code.
[ ] Add standard constants to existing DTO's - eg Country 2 character ISO code and Occupation ISCO code. This is little extra overhead and will be generally useful
Our data comes from a relational database (postgres).
The anonymized data needs to be converted to an object form so that it is self contained and does not rely on any external lookups.
This already happens to some extent because our DTO's are constructed from a JPA entity which is an object created from links to multiple table relationships.
So, for example, a country field of a candidate (eg location or nationality) appears in the DTO as a country property with an id field and a name field.
For the anonymized data, the id is meaningless to anyone external (being a random internal database primary key of the Country table). We also need the two character ISO code (as well as the name for convenience) in the anonymized data.
Another example is occupations where, for external use, we need the ISCO08 code.