Of course there could be other options, depending on your definition for gender. That’s not the point. The idea is that we would have these fixed options. When we record this in a table of a database, the value assigned to gender can only be one of these 4 values. So we say that the data domain for the gender column is “male”, “female”, “non-binary”, or “not specified”.<\/p>\n GENDER_TABLE<\/strong><\/p>\n<\/th>\n<\/tr>\n<\/thead>\n\n MALE<\/p>\n<\/td>\n<\/tr>\n FEMALE<\/p>\n<\/td>\n<\/tr>\n NON-BINARY<\/p>\n<\/td>\n<\/tr>\n NOT SPECIFIED<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n From a data governance perspective, data domain means something else. Here, a data domain is “a logical grouping of items of interest to the organization, or areas of interest within the organization”.<\/p>\n You can think of data domains as high-level categories of data for the purpose of assigning accountability and responsibility for the data. By the way, a data domain is also called “subject area”, or a “data concept” so you might encounter either. Within data governance, they both refer to the same thing. <\/p>\n Just to note that some are refer to the data domain to mean the same thing as a data set. That’s not accurate as a data domain can contain multiple data sets as long as those data sets represent the same area of interest within the organization.<\/p>\n If this is still clear as mud, let’s look at some examples. <\/p>\n An average organization would have anywhere between 5-10 AND they aren’t always these, though these are usually the most common ones. In the end it really depends on the industry that you’re part of.<\/p>\n Let’s look at some industry specific data domains. <\/p>\n In the education sector, you might have:<\/p>\n In the healthcare sector, you might have:<\/p>\n In the insurance sector, you might encounter:<\/p>\n In any of these sectors you could also have some of the previous data domains as well. So for example, I’m sure that all 3 sectors would all have “Location”, “Transaction”, and “Legal” as data domains.<\/p>\n There’s also the concept of a data sub-domain. Typically each data domain will have anywhere between 3 to 10 data sub-domains.<\/p>\n What is a sub-domain? It’s simply a way to divide that data domain even further into other categories.<\/p>\n There are some considerations, though:<\/p>\n Data sub-domain examples<\/p>\n Let me provide you with some sub-domain examples to some of the data domains mentioned above.<\/p>\n Customer<\/strong><\/p>\n Vendor<\/strong><\/p>\n Location<\/strong><\/p>\n What you should remember is that these data domains, and sub-domains, are a way of grouping the most important data of an organization and they go across business units & systems. So for the same domain you might have different stakeholders from different lines of business and departments and the data can be found in different systems, can be produced by different systems, or consumed by different systems.<\/p>\n That being said, the reality can also be a bit more complicated and when data doesn\u2019t perfectly slot into one subject area or another, data can be associated with more than one domain. This is not a recommended approach, but it sometimes is unavoidable.<\/p><\/p>\n","protected":false},"excerpt":{"rendered":" Determining your data domains is an important part of your data strategy. So what is a data domain? It actually can mean a couple of things, depending if we look at it from the point of view of data management and database management, or if we look at it from the point of view of […]<\/p>\n","protected":false},"author":1,"featured_media":3612,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[2],"tags":[],"class_list":["post-3604","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-data-governance","post-wrapper","thrv_wrapper"],"yoast_head":"\n![\"\"](\"https:\/\/i0.wp.com\/www.lightsondata.com\/wp-content\/uploads\/2021\/11\/MALE-FEMALE-NON-BINARY-NOT-SPECIFIED.jpg?resize=300%2C300&ssl=1\" "\\"data")
<\/span><\/p>\n\n\n
\n \n \n \n \n \n \n \n \n \n Data domain (data governance)<\/h2>\n
Data domain examples<\/h2>\n
\n
\n
\n
\n
Data sub-domain<\/h2>\n
\n
\n
\n
\n
Conclusion<\/h2>\n