Difference between revisions of "Catalog"

From wiki
Jump to navigation Jump to search
 
(3 intermediate revisions by the same user not shown)
Line 8: Line 8:
 
* Makes data easily accessible
 
* Makes data easily accessible
 
* Allow users to self-serve
 
* Allow users to self-serve
== Why data Catalog ==
+
== Why Data Catalog ==
 
In an enterprise vision, we would like to minimize the number of data silos, get a faster access to what matters most, and function as a single source for better doing.<br>
 
In an enterprise vision, we would like to minimize the number of data silos, get a faster access to what matters most, and function as a single source for better doing.<br>
Data-driven culture empowers users with getting access to their data source. <nowiki><br></nowiki> With this, the growing numbers of cloud applications, privacy regulations and security rules are making it more difficult to effectively secure and govern data.<nowiki><br></nowiki>
+
Data-driven culture empowers users with getting access to their data source.  
 +
With this, the growing numbers of cloud applications, privacy regulations and security rules are making it more difficult to effectively secure and govern data
  
 
Therefor, a Data Catalog is needed to:
 
Therefor, a Data Catalog is needed to:
Line 17: Line 18:
 
* Reduce the cost of data redundancy and hoarding.  
 
* Reduce the cost of data redundancy and hoarding.  
 
* Better linkage between the technical value of metadata and the business value.  
 
* Better linkage between the technical value of metadata and the business value.  
== data Catalog Architecture ==
+
== Data Catalog Architecture ==
coming soon
+
 
 
== List of Stakeholders ==
 
== List of Stakeholders ==
 
coming soon
 
coming soon
== data Catalog Team ==
+
== Data Catalog Team ==
 
coming soon
 
coming soon

Latest revision as of 08:31, 19 September 2018

Data Catalog

Data catalog is an organized service that allows users to centralize metadata and learn more about their data sources which help organizations achieve more values from their assets.

Following are some advantages to centralizing metadata:

  • Consistency and accuracy across the department/government
  • Better data congruency, quality and structure
  • Makes data easily accessible
  • Allow users to self-serve

Why Data Catalog

In an enterprise vision, we would like to minimize the number of data silos, get a faster access to what matters most, and function as a single source for better doing.
Data-driven culture empowers users with getting access to their data source. With this, the growing numbers of cloud applications, privacy regulations and security rules are making it more difficult to effectively secure and govern data

Therefor, a Data Catalog is needed to:

  • Spend less time searching for data and more time using it to gain insight
  • Have a better/safer access to data through governance. Departments have a hard time finding data and controlling who has access to it.
  • Reduce the cost of data redundancy and hoarding.
  • Better linkage between the technical value of metadata and the business value.

Data Catalog Architecture

List of Stakeholders

coming soon

Data Catalog Team

coming soon