Import and export of data: Difference between revisions

Revision as of 16:05, 14 November 2020

Revision as of 12:05, 14 December 2020

Line 4:

Import and export of data shares semantic analogy with [[Cut, copy, and paste|copying and pasting]], in that sets of data are copied from one application and pasted into another. In fact, the [[software development]] behind operating system [[clipboard (computing)|clipboards]] (and clipboard extender apps) greatly concerns the many details and challenges of data transformation and transcoding, in order to present the end user with the illusion of effortless copy and paste between any two apps, no matter how internally different. The "Save As" command in many applications requires much of the same engineering, when files are saved as another file format.

The ability to import and export data (or lack of such ability) has large economic implications, because it can be resource-intensive to input data in non-automated ways (such as manual rekeying), and because lack of [[interoperability]] and [[data portability]] between systems unable to import or export data between each other causes [[stovepiping]] and, lack of opportunity and efficiencies such as those seen in, for example, [[mashup (web application hybrid)|mash-ups]], and may not suffice in its ability to search for information as enabled by tools such as <code>[[grep]]</code>.

[[File:Extract, Transform, Load Data Flow Diagram.svg|thumb|[[Extract, transform, load]] (ETL) - the typical import procedure into databases]]