Data Portability - Revision history

User at 18:06, 12 January 2023

2023-01-12T18:06:19Z

User at 15:34, 26 October 2022

2022-10-26T15:34:13Z

User at 18:08, 17 October 2022

2022-10-17T18:08:25Z

User at 17:45, 17 October 2022

2022-10-17T17:45:33Z

User at 17:32, 17 October 2022

2022-10-17T17:32:15Z

User at 17:03, 17 October 2022

2022-10-17T17:03:44Z

User at 07:14, 16 October 2022

2022-10-16T07:14:23Z

User at 23:36, 15 October 2022

2022-10-15T23:36:44Z

User: Created page with "'''Content Coming Soon'''"

2018-12-19T23:28:16Z

Created page with "'''Content Coming Soon'''"

New page

'''Content Coming Soon'''

@@ Line 84: / Line 84: @@
 <div style="column-count:2;-moz-column-count:4;-webkit-column-count:4">
 *[[Big Data]]
 </div>

@@ Line 83: / Line 83: @@
 ===See Also===
 <div style="column-count:2;-moz-column-count:4;-webkit-column-count:4">
-[[Data Compatibility]]<br />
+*[[Big Data]]
-[[Data Access]]<br />
+*[[Big Data Integration]]
-[[Data Analysis]]<br />
+*[[Big Data Maturity Model (BDMM)]]
-[[Data Analytics]]<br />
+*[[Metadata]]
-[[Data Architecture]]<br />
+*[[Data]]
-[[Data Asset Framework (DAF)]]<br />
+*[[Data Access]]
-[[Data Buffer]]<br />
+*[[Data Analysis]]
-[[Data Center]]<br />
+*[[Data Analytics]]
-[[Data Center Infrastructure]]<br />
+*[[Data Architecture]]
-[[Data Center Infrastructure Management (DCIM)]]<br />
+*[[Data Asset Framework (DAF)]]
-[[Data Cleansing]]<br />
+*[[Data Buffer]]
-[[Big Data]]<br />
+*[[Data Center]]
-[[Big Data Integration]]<br />
+*[[Data Center Infrastructure]]
-[[Big Data Maturity Model (BDMM)]]<br />
+*[[Data Center Infrastructure Management (DCIM)]]
-[[Metadata]]<br />
+*[[Data Cleansing]]
-[[Data Collection]]<br />
+*[[Data Compatibility]]
-[[Data Compatibility]]<br />
+*[[Data Governance]]
-[[Data Consolidation]]<br />
+*[[Data Integration]]
-[[Data Deduplication]]<br />
+*[[Data Management]]
-[[Data Delivery Platform (DDP)]]<br />
+*[[Data Mining]]
-[[Data Description (Definition) Language (DDL)]]<br />
+*[[Data Monitoring]]
-[[Data Dictionary]]<br />
+*[[Data Munging]]
-[[Data Discovery]]<br />
+*[[Data Quality]]
-[[Data Driven Organization]]<br />
+*[[Data Reference Model (DRM)]]
-[[Data Element]]<br />
+*[[Data Security]]
-[[Data Enrichment]]<br />
+*[[Data Transformation]]
-[[Data Entry]]<br />
+*[[Data Visualization]]
-[[Data Federation]]<br />
+*[[Data Warehouse]]
 </div>

@@ Line 1: / Line 1: @@
-===What is Data Portability<ref>[https://www.integrate.io/blog/what-is-data-portability-and-why-is-it-important/ Defining Data Portabilit]</ref>===
+===What is Data Portability<ref>[https://www.integrate.io/blog/what-is-data-portability-and-why-is-it-important/ Defining Data Portability]</ref>===
 '''Data Portability''' is the concept that the users or owners of a given dataset should be able to easily move or copy this data between different software applications, platforms, services, and computing environments. The term “data portability” actually encompasses two related, but separate, issues:
 *First, organizations should be able to easily import and export the data they collect and store, converting between different formats and standards if necessary.
@@ Line 6: / Line 6: @@
 The rise of cloud computing services has heightened technical concerns about data portability. In particular, many organizations are worried about potential “vendor lock-in,” where users feel stuck or trapped with a particular IT provider because of the costs of migrating their data to another provider. For example, an IT provider may store data in a proprietary format that makes it difficult to convert to another, more usable format.
@@ Line 19: / Line 35: @@
 *the lawful basis for processing this information is consent or for the performance of a contract; and
 *when carrying out the processing by automated means (ie excluding paper files).
@@ Line 39: / Line 57: @@
 *For consumers, data portability lets people easily coordinate the personal data they keep on multiple social networking sites. On social networking sites, such as Facebook, LinkedIn, and Twitter, users can share their contacts, posts, photos, videos, sound clips and personal or professional information across the various platforms. In that way, users know their data is current and consistent, without having to modify the content on each service's site. Users can, of course, opt out of this data-sharing feature if they want to show different portfolios on different services.
 *In 2010, Facebook improved its data portability with a feature that lets users download all their network content as a single zipped file for viewing with a browser offline. This feature helps users to keep track of their data without fear that crackers might permanently alter or destroy it. The downloading feature backs up the data so it can be easily replaced in the event of a network failure causing data loss in the cloud. If the network has an outage or some other problem, users can simply upload their backed-up data to replace the damaged network data.
-*Data portability provides users of social networking services with added convenience when different services allow reciprocal access to first-party data. For example, a user on Facebook may import contacts from Google's Gmail email service. In a perfect world, all social networking services would allow users to freely and easily migrate data among them. Things haven't worked out that way. Instead, services sometimes take a territorial attitude toward user data.
+*Data portability provides users of social networking services with added convenience when different services allow reciprocal access to first-party data. For example, a user on Facebook may import contacts from Google's Gmail email service. In a perfect world, all social networking services would allow users to freely and easily migrate data among themselves. Things haven't worked out that way. Instead, services sometimes take a territorial attitude toward user data.
 *Without data portability, a person's data is accessible only through the platform where it is stored. Such a siloed approach to data can result in vendor lock-in, inaccessible data, and even data quality issues.
 ===Data Portability and the Cloud<ref>[https://www.talend.com/resources/what-is-data-portability/ Data Portability and the Cloud]</ref>===
-Data portability is crucial in the cloud. Before the cloud, most of  your personal data was on your hard drive: the only thing that had to care about was to use standard format for storing data, or importing/exporting them. But with the cloud, the data storage layer is not under your control any longer.  You not only need to import/export this data in a seamless way, but you have to move data through the cloud. Of course, this standardization principle applies to all kind of data, but in the case of personal data, those data movements must be driven by the data subject, rather than the data controller..
+Data portability is crucial in the cloud. Before the cloud, most of your personal data was on your hard drive: the only thing that had to care about was using a standard format for storing data, or importing/exporting them. But with the cloud, the data storage layer is not under your control any longer.  You not only need to import/export this data in a seamless way, but you have to move data through the cloud. Of course, this standardization principle applies to all kinds of data, but in the case of personal data, those data movements must be driven by the data subject, rather than the data controller...
 Think tanks and industry trailblazers have long collaborated to bring about benefits of standardization. One great use case is TCP/IP—the protocol upon which the internet agreed to grow. By standardizing data portability, new products can be developed around a universal method for plugging and unplugging user data.

@@ Line 6: / Line 6: @@
 The rise of cloud computing services has heightened technical concerns about data portability. In particular, many organizations are worried about potential “vendor lock-in,” where users feel stuck or trapped with a particular IT provider because of the costs of migrating their data to another provider. For example, an IT provider may store data in a proprietary format that makes it difficult to convert to another, more usable format.
@@ Line 13: / Line 34: @@
 [[File:Data Portability Reasons.png|500px|Reasons Data Should be Portable]]<br />
@@ Line 21: / Line 41: @@
 *Data portability provides users of social networking services with added convenience when different services allow reciprocal access to first-party data. For example, a user on Facebook may import contacts from Google's Gmail email service. In a perfect world, all social networking services would allow users to freely and easily migrate data among them. Things haven't worked out that way. Instead, services sometimes take a territorial attitude toward user data.
 *Without data portability, a person's data is accessible only through the platform where it is stored. Such a siloed approach to data can result in vendor lock-in, inaccessible data, and even data quality issues.
@@ Line 118: / Line 150: @@
 == References ==
 <references />

← Older revision	Revision as of 17:32, 17 October 2022
Line 12:	Line 12:


	+	[[File:Data Portability Reasons.png\|500px\|Reasons Data Should be Portable]]<br />

← Older revision		Revision as of 07:14, 16 October 2022
Line 7:		Line 7:

	== See Also ==		== See Also ==
−	*[[Data]]	+
−	*[[Business_Strategy\|Business Strategy]]
−	*[[IT_Strategy_(Information_Technology_Strategy)\|IT Strategy]]
−	*[[E-Strategy\|e-Strategy]]
−	*[[IT_Governance\|IT Governance]]
−	*[[Enterprise_Architecture\|Enterprise Architecture]]
−	*[[IT_Sourcing_(Information_Technology_Sourcing)\|IT Sourcing]]
−	*[[IT Operations_(Information_Technology_Operations)\|IT Operations]]
−	*[[Chief_Information_Officer_(CIO)\|CIO]]

← Older revision		Revision as of 23:36, 15 October 2022
Line 1:		Line 1:
	'''Content Coming Soon'''		'''Content Coming Soon'''
		+
		+
		+
		+
		+
		+
		+	== See Also ==
		+	*[[Data]]
		+	*[[Business_Strategy\|Business Strategy]]
		+	*[[IT_Strategy_(Information_Technology_Strategy)\|IT Strategy]]
		+	*[[E-Strategy\|e-Strategy]]
		+	*[[IT_Governance\|IT Governance]]
		+	*[[Enterprise_Architecture\|Enterprise Architecture]]
		+	*[[IT_Sourcing_(Information_Technology_Sourcing)\|IT Sourcing]]
		+	*[[IT Operations_(Information_Technology_Operations)\|IT Operations]]
		+	*[[Chief_Information_Officer_(CIO)\|CIO]]
		+
		+
		+
		+
		+	== References ==
		+	<references />