Open baltpeter opened 3 years ago
We can either purge them or keep them and create a flag that we could set on the record that would let the user know the company no longer exists/operates?
Both options are fine for me. I think it boils down to the question: Who is responsible for the data a company processed/collected after its shutdown?
I suppose most companies would delete their records, but what about those that don't? If there is still some data, we have a right to access it/correct/... it. But thats only really useful, if we can contact somebody responsible. From our point of view, we only have the contact information we already stored. That means a flag would make the most sense in these cases?
I think we agree that if there is still an entity that is responsible for some data, we should keep them in the database, regardless of whether they are still carrying out business under that brand or not. That's also pretty much what we're doing already by adding (formerly)
to the respective runs
entry.
But I think it's good to formalize this as an official policy here.
The next question then is when we consider a company to be closed. There's often cases where for example the website goes offline but the company still exists. As a measure to decide that, I'd propose to look at the official company registers and check whether the company is still listed as active.
That of course only works if the company is in fact listed in an official register. Not sure what to do otherwise.
Now, with regards to companies that we have determined to be actually closed, I don't know whether keeping them in the database (with a flag) would really serve any purpose. If the company is really closed, it's unlikely that you would still reach anyone through the old contact details. In some cases, there may be an insolvency administrator/liquidator or something like that, that now becomes the controller (and in that case, we should list them) but that is not always the case.
I suppose most companies would delete their records, but what about those that don't? If there is still some data, we have a right to access it/correct/... it. But thats only really useful, if we can contact somebody responsible.
Definitely. But unfortunately, I really don't see a way for us to determine who the responsible entity is unless one of us is affected and wants to put major work into finding that out. And in many cases, it's probably going to be a natural person rather than a company, which makes this even more difficult. :/
A few example of companies that I am not quite sure what to do with:
Another thing to consider: By deleting a company, we invalidate the links to it, including the ones in My requests. I'm really not a fan of that*.
Considering that, I might lean more on the side of keeping the records with a flag but not showing them in the search and lists.
Side note: In #1168, I am deleting a few defunct companies. As we haven't decided on anything else yet, I'll keep doing that for now. Should we decide to keep the records after all, it's easy enough to restore them.
Considering that, I might lean more on the side of keeping the records with a flag but not showing them in the search and lists.
I think it would also be a good idea to provide a way to redirect defunct records to other ones. Not sure what a nice way to implement that would be yet but I have seen quite a few companies that have been merged with or bought by others. For those, I have listed the old company as (formerly)
on the other one but it would also be nice to redirect the existing record there.
We decided that:
runs
array with the addition of a (formerly)
merged into a larger company
or defunct
)(formerly)
Do we translate that?
How do we want to deal with companies and services in our database that have since been closed?
I'm mostly opening this issue to remind us that we should adopt a policy for that. If anyone has any thoughts, I'd be glad to hear them!