Friday, November 29, 2019
Brexit, your business and data: Personal-data transfers | Lexology
My comment: Comprehensive discussion of Brexit impact on matters of GDPR
> Brexit, your business and data: Personal-data transfers lexology.com/library/detail… via @lexology #GDPR #DSGVO #DataProtection #DataPrivacy #Datenschutz #Brexit
Labels:
Brexit,
Data Privacy,
Data Protection,
DSGVO,
GDPR
Thursday, November 28, 2019
Schweizer Hotelbuchungsplattform verletzt die DSGVO-Informationspflicht in Österreich | Lexology
Mein Kommentar: Hilfreiche, ausführliche Auslegung und Anwendung der
DSGVO auf (Nicht-EEA-)Organisationen mit EEA-Markt, am konkreten
Beispiel > Schweizer Hotelbuchungsplattform verletzt die DSGVO-Informationspflicht in Österreich lexology.com/library/detail… by @BuehlmannRA & @reinle_michael via @lexology #DSGVO #Datenschutz #GDPR #DataProtection #DataPrivacy
Labels:
DataPrivacy,
DataProtection,
Datenschutz,
DSGVO,
GDPR
Wednesday, November 27, 2019
CCPA Global Checklist | Lexology
CCPA Global Checklist lexology.com/library/detail… by @HopkinsCarley's @ChiaraPortner & Céline M. Guillou via @lexology #CCPA #GDPR #DataPrivacy #DataProtection
Labels:
CCPA,
DataPrivacy,
DataProtection,
Datenschutz,
DSGVO,
GDPR
Understanding Regulation of Cookies | Lexology
Understanding Regulation of Cookies lexology.com/library/detail… by @StellaDante via @lexology #Cookies #GDPR #CCPA #DataPrivacy #DataProtection
Guidelines on the long arms of the GDPR | Lexology
My comment: Interesting clarifications rg. the GDPR's territorial scope
(not only for New Zealand orgs)! > Guidelines on the long arms of the
GDPR lexology.com/library/detail… by @BuddleFindlay via @lexology #GDPR #DSGVO #DataProtection #DataPrivacy
Monday, August 18, 2014
When is the BEST time for a Data Quality Review? | Roshan Joseph (via LinkedIn)
Follow the LinkedIn discussion
My comment
While position 5 (NOW!) is the "correct" answer, I like to add "Merger & Acquisition" as a triggering event (variation / combination of pos. 1 to 4).
My comment
While position 5 (NOW!) is the "correct" answer, I like to add "Merger & Acquisition" as a triggering event (variation / combination of pos. 1 to 4).
With an upcoming M&A transaction, a data quality review prepares for
the audit that is an indispensable part of the due diligence. Both
(all) involved organizations should undergo a data quality review to
especially know about the mergability of the parties' data before taking
the final decision.
Labels:
Data Quality
Monday, June 2, 2014
Tool to Track Which Databases Keep Customer Data | LinkedIn Group: Master Data Management Pros
Follow the LinkedIn discussion
My comment
I suggest you to use a professional data and process modeling tool suite.
The data modeling tool component will allow you to have an inventory of the data, i.e. which fields (particularly: customer data) reside in which database. Typical use of the data modeling tool could be:
Ideally, the tool suite will be integrated, i.e. database fields that are captured in the database reverse engineering step (using the data modeling tool) can be linked to the fields found in the analysis of the data flows (using the process modeling tool) and vice versa.
How you apply the modeling tool suite in detail will certainly depend on the mid and long-term goals of your organization, e.g. merging/replacing application systems, evaluating new software packages, changing platforms, going mobile etc.
Considering any of these targets combined with your initial question, I recommend you to check out the SILVERRUN Professional & Enterprise Series at www.silverrun.com . (In the spirit of full disclosure: I represent Grandite, the maker of the SILVERRUN tools.)
Please do not hesitate to contact me for further information directly, you will find my coordinates in "Contact Info" of my LinkedIn profile.
My comment
I suggest you to use a professional data and process modeling tool suite.
The data modeling tool component will allow you to have an inventory of the data, i.e. which fields (particularly: customer data) reside in which database. Typical use of the data modeling tool could be:
- Reverse engineer each database, i.e. automatic transfer of the database structure to a graphical/textual representation in the data modeling tool.
- (Since even (semantically) same fields will have different physical names in different databases...) Link synonyms to a common business name, e.g. "cust_name" and "cli_nam" could both represent "customer name".
- Add/modify any other crucial description that may be missing/incorrect.
- Integrate the database models into subject areas (A subject area will give you the synchronized business view of how e.g. a customer is - and perspectively should be - described in your organization, e.g. by customer first-name, customer family-name, customer date-of-birth, etc.)
Ideally, the tool suite will be integrated, i.e. database fields that are captured in the database reverse engineering step (using the data modeling tool) can be linked to the fields found in the analysis of the data flows (using the process modeling tool) and vice versa.
How you apply the modeling tool suite in detail will certainly depend on the mid and long-term goals of your organization, e.g. merging/replacing application systems, evaluating new software packages, changing platforms, going mobile etc.
Considering any of these targets combined with your initial question, I recommend you to check out the SILVERRUN Professional & Enterprise Series at www.silverrun.com . (In the spirit of full disclosure: I represent Grandite, the maker of the SILVERRUN tools.)
Please do not hesitate to contact me for further information directly, you will find my coordinates in "Contact Info" of my LinkedIn profile.
Subscribe to:
Posts (Atom)