Suggestion:
Publish a clear statement to address the previously lost Member Group data and content/web site pages. Commit to ensuring that data will be transferred appropriately in any future systems migration.
Category on Map Diagram:
COLLABORATION
Instructions:
Please complete Add New Comment section fields as requested below:
FIELD | REQUESTED INPUT |
Your name: WILL BE PUBLISHED |
With your name ! |
Email: WILL NOT BE PUBLISHED |
With your email – this will not be made public |
Homepage WILL NOT BE PUBLISHED |
LEAVE BLANK |
Subject WILL NOT BE PUBLISHED |
LEAVE BLANK |
Comment WILL BE PUBLISHED |
Please type JUST ONE these three response options on the first line.AGREE DISAGREE REFER REFER is to be used to either get more information, or if you like the principal, but have concerns about the implementation. Then from the second line onwards please add any personal comments if you would like to. |
Comments
REFER
Submitted by Carol Long on
REFER
BCS should apply appropriate practice and comply with DPA and GDPR. Additional statements may be inappropriate.
REFER
Submitted by Julian Schwarzenbach on
REFER
This should be future practice, but I would question the value/ impact of such a public statement
AGREE. Wasn't the migration
Submitted by Christopher Lawrence on
AGREE. Wasn't the migration tested beforehand?
REFER
Submitted by John Rendall on
REFER
I was only aware of a MG data transfer when my list-server mailing lists stopped working (...not at the same time, either!) i.e. I was not aware, in advance, that this was to happen. Similarly, I was not aware that any data had been lost.
I agree that there will be little to be gained by making a public statement (i.e. washing our dirty laundry in public), unless this contravened GDPR (in which case it should have been notified to the Information Commissioners Office (ICO) already), however I agree that this needs to be committed to going forward. We are supposed to be *The* Institute for IT, its not very good publicity if we can't get our own house in order.
Agree
Submitted by Fred Long on
Agree
This should be commonplace for an organisation such as the BCS.
REFER
Submitted by Kylie Fowler on
REFER
Don't see much point doing this for past issues (unless it's a formal apology for the problems caused) but yes for future issues.
Refer
Submitted by Claire MacManus on
Is this not a requirement already?
AGREE - it is essential that
Submitted by Martin Beer on
AGREE - it is essential that member groups know what is and is not available.