<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>idea Metadata for domains in Data Management Ideas</title>
    <link>https://community.esri.com/t5/data-management-ideas/metadata-for-domains/idi-p/1023825</link>
    <description>&lt;P&gt;Domains have the fields 'Code' and 'Description'.&lt;/P&gt;&lt;P&gt;We experience that different users have different perceptions of the different entries in domains. Therefore we think a more detailed explanation, than the one suitable for the 'Description' field, could assist users in selecting the appropriate values.&lt;/P&gt;&lt;P&gt;This kind of detailed explanation would be suitable for metadata.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Therefore my idea is to enable metadata for domains in ArcGIS similar to the way metadata works for featureclasses.&lt;/P&gt;&lt;P&gt;The kind of geodatabase domains discussed here are the ones accessible via Data » Domains in ArcGIS Pro.&lt;/P&gt;</description>
    <pubDate>Thu, 18 May 2023 19:22:50 GMT</pubDate>
    <dc:creator>JohnZachariassen</dc:creator>
    <dc:date>2023-05-18T19:22:50Z</dc:date>
    <item>
      <title>Metadata for domains</title>
      <link>https://community.esri.com/t5/data-management-ideas/metadata-for-domains/idi-p/1023825</link>
      <description>&lt;P&gt;Domains have the fields 'Code' and 'Description'.&lt;/P&gt;&lt;P&gt;We experience that different users have different perceptions of the different entries in domains. Therefore we think a more detailed explanation, than the one suitable for the 'Description' field, could assist users in selecting the appropriate values.&lt;/P&gt;&lt;P&gt;This kind of detailed explanation would be suitable for metadata.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Therefore my idea is to enable metadata for domains in ArcGIS similar to the way metadata works for featureclasses.&lt;/P&gt;&lt;P&gt;The kind of geodatabase domains discussed here are the ones accessible via Data » Domains in ArcGIS Pro.&lt;/P&gt;</description>
      <pubDate>Thu, 18 May 2023 19:22:50 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/metadata-for-domains/idi-p/1023825</guid>
      <dc:creator>JohnZachariassen</dc:creator>
      <dc:date>2023-05-18T19:22:50Z</dc:date>
    </item>
    <item>
      <title>Store additional information in coded value domains</title>
      <link>https://community.esri.com/t5/data-management-ideas/metadata-for-domains/idc-p/1170945#M2209</link>
      <description>&lt;P&gt;It would be handy if we could store additional information/columns in GDB domains. So that we could use that additional data in SQL queries, reports, labels etc.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;CODE [domain coded value]&lt;/LI&gt;&lt;LI&gt;NAME [domain description]&lt;/LI&gt;&lt;LI&gt;Additional field: DETAILS&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 05 May 2022 04:52:48 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/metadata-for-domains/idc-p/1170945#M2209</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2022-05-05T04:52:48Z</dc:date>
    </item>
    <item>
      <title>Re: Multi-column domains - Status changed to: Needs Clarification</title>
      <link>https://community.esri.com/t5/data-management-ideas/metadata-for-domains/idc-p/1170947#M2210</link>
      <description>&lt;P&gt;Thanks for submitting the idea&amp;nbsp;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/351335"&gt;@Bud&lt;/a&gt;&amp;nbsp;We're going to need some additional details to understand what you're looking for here. Can you describe the problem you're trying to solve along with any examples you might have?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 05 May 2022 02:33:44 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/metadata-for-domains/idc-p/1170947#M2210</guid>
      <dc:creator>KoryKramer</dc:creator>
      <dc:date>2022-05-05T02:33:44Z</dc:date>
    </item>
    <item>
      <title>Re: Store additional information in coded value domains</title>
      <link>https://community.esri.com/t5/data-management-ideas/metadata-for-domains/idc-p/1171052#M2211</link>
      <description>&lt;P&gt;Thank you for providing additional details, Bud.&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;HR /&gt;So that we could use that additional data in SQL queries, reports, labels etc.&lt;UL&gt;&lt;LI&gt;CODE [domain coded value]&lt;/LI&gt;&lt;LI&gt;NAME [domain description]&lt;/LI&gt;&lt;LI&gt;Additional field: DETAILS&lt;/LI&gt;&lt;/UL&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;So for your additional queries, reports, labels, etc. you want to run those directly against a domain table?&amp;nbsp;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 05 May 2022 13:20:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/metadata-for-domains/idc-p/1171052#M2211</guid>
      <dc:creator>KoryKramer</dc:creator>
      <dc:date>2022-05-05T13:20:13Z</dc:date>
    </item>
    <item>
      <title>Re: Store additional information in coded value domains</title>
      <link>https://community.esri.com/t5/data-management-ideas/metadata-for-domains/idc-p/1177260#M2212</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/129401"&gt;@KoryKramer&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes.&amp;nbsp;&lt;/P&gt;&lt;P&gt;In Oracle, we can select the domain data from the XML system tables as follows:&lt;/P&gt;&lt;PRE&gt;select
    substr(extractvalue(codedvalues.column_value,'CodedValue/Code'),1,255) as code,
    substr(extractvalue(codedvalues.column_value,'CodedValue/Name'),1,255) as description
from
    sde.gdb_items_vw i 
join 
    sde.gdb_itemtypes it 
    on i.type = it.uuid, table(xmlsequence(xmltype(definition).extract('/GPCodedValueDomain2/CodedValues/CodedValue'))) codedvalues 
where
    i.name = 'PIPE_MATERIALS'&lt;/PRE&gt;&lt;P&gt;So we can already use the domain data in&amp;nbsp;queries, reports, labels etc.&lt;/P&gt;&lt;P&gt;But what we can't do is store additional information/columns in the domain.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 25 May 2022 16:29:08 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/metadata-for-domains/idc-p/1177260#M2212</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2022-05-25T16:29:08Z</dc:date>
    </item>
    <item>
      <title>Re: Store additional information in coded value domains - Status changed to: Open</title>
      <link>https://community.esri.com/t5/data-management-ideas/metadata-for-domains/idc-p/1177261#M2213</link>
      <description>&lt;P&gt;Thanks for the clarification, Bud. Re-opening the idea.&lt;/P&gt;</description>
      <pubDate>Wed, 25 May 2022 16:32:06 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/metadata-for-domains/idc-p/1177261#M2213</guid>
      <dc:creator>KoryKramer</dc:creator>
      <dc:date>2022-05-25T16:32:06Z</dc:date>
    </item>
    <item>
      <title>Re: Metadata for domains</title>
      <link>https://community.esri.com/t5/data-management-ideas/metadata-for-domains/idc-p/1385854#M2348</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/129401"&gt;@KoryKramer&lt;/a&gt;&amp;nbsp;I would love to also get a new field for 'sort order' so that we aren't stuck using the Code and Description and ascending and descending order.&amp;nbsp; I'd like to be able to control the sort order of domains based on what is most common option at the time (which might change periodically in some applications).&amp;nbsp; I'm not seeing this ask anywhere yet.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Feb 2024 04:55:54 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/metadata-for-domains/idc-p/1385854#M2348</guid>
      <dc:creator>cspielman_bouldercounty</dc:creator>
      <dc:date>2024-02-23T04:55:54Z</dc:date>
    </item>
    <item>
      <title>Re: Metadata for domains</title>
      <link>https://community.esri.com/t5/data-management-ideas/metadata-for-domains/idc-p/1385874#M2350</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/754049"&gt;@cspielman_bouldercounty&lt;/a&gt;&amp;nbsp;I would suggest you submit a separate idea for that.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Feb 2024 05:49:05 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/metadata-for-domains/idc-p/1385874#M2350</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2024-02-23T05:49:05Z</dc:date>
    </item>
  </channel>
</rss>

