morning!

planning, meetings, supporting lusers (not a fan of the word but answering the same question for three times makes me bitter)

writing code for compliance to GDPR!

i have a question, actually

for things that are IDs in my system, when exporting the data, can I keep stuff expressed as an ID or do i have to translate what the id means? Practical example: a user chooses in his profile that they are a "unicorn" but that value is represented in my system as 123. When exporting their data do i have to show Unicorn or can I keep 123 (and the mapping 123 -> Unicorn is only in my system)?

@helios Is your question related to having the right to see your information? In that case I think you should make some effort to make the data understandable to the user.

yes it is for that purpose

mogguh

@helios you can keep naming it either 123 or unicorn.. it's not about the actual numbers/ids, but whether you can possibly corelate it to just a single person

@lmergen it's for the data portability, not for identifying or not

you mean the data export stuff ?

yep

as far as i can tell, no one truly knows the answer to this question

ah, ok, as i imagined 🙂

and i say this as someone who had to go through this process before 🙂

the way i was adviced, was that you can perfectly normalize this stuff

so keep calling it 123

but you need to have a lookup table somewhere

you can't obscure the data

i had the mapping id->name easily available so i just used the names in the export

but hell, no one knows

yeah, i imagine

afternoon

@joost-diepenmaat we tend to use UGT here: http://www.total-knowledge.com/~ilya/mips/ugt.html

so goodnight from me 😉

but what if you enter and leave the same channel multiple times a day :thinking_face: