The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
That's what I've said before: We should be able to move posts between forums ourselves!
Anything that is unrelated to elephants is irrelephant Anonymous - The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944 - I'd just like a chance to prove that money can't make me happy. Me, all the time
We used to have a table (SQL) to store forum members - active or inactive...
Now we added the ability to define a group of members (mostly on role base) with a single line...
The next step was to declare a view that expands those lines with group on them to be back to the one-line-one-member situation...
Why in the elephanting elephant the view has a filter for active members only!!!
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
So for us British, European, maybe even US folks at least, we have something called the Data Protection Act, which ultimately means we "should" be careful with other peoples data and not retain it longer than we need. The thing is, as a software developer, do we know who is responsible for the data contained within the database driven apps we release?
I would say it's whoever owns the app?
What about building apps in-house? The Chief Exec?
Each organisation is obliged to appoint a DP officer who is responsible for policing the systems and procedures in use. But ultimately if there is any breach of the law the organisation as a whole tends to be held responsible. For corporate bodies that means the directors/management, and for charitable bodies it is the trustees.
This general concept is discovered frequently in the group I work in.
We collect operating data, not necessarily personal data, from various pieces of equipment, sensors, meters, etc. And we keep that data... seemingly forever.
We do have some regulatory requirements to hold certain data for 'X' number of years; after that time period, we can LEGALLY dispose/delete the data.
If we delete the data as we are allowed to do, then, in the event of a legal action, we cannot provide data we don't have - which may benefit the company.
However, from the perspective of seeing how something performed over time, we may need more than 'X' number of years of data to see a long term trend... think of very large turbines for example. They may have a service life of 20 to 30 years.
So... it is an interesting topic to say the least.
Where I work its in house development of Insurance back office system. We hold regular audit reviews by each department team leader(s).
Our parent company then on top of that have Yearly company audits and then Group Internal Audits every 2 years repeating depending on how you fair with the audit.
We also have security audits on top of that which look at the access of property / systems etc.
Every day, thousands of innocent plants are killed by vegetarians.
Last year we were tasked with reverse engineering a legacy app, we could not find anyone willing to admit they owned the data and that was from the POV of we want to fix this for you, not you f***ed up and we want to put your ass in a sling.
So I guess DP was low on their priority list (there was no personal data involved).
Never underestimate the power of human stupidity
Last Visit: 31-Dec-99 18:00 Last Update: 14-Jun-21 18:41