<?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 Multiple owner of Feature Dataset in Data Management Ideas</title>
    <link>https://community.esri.com/t5/data-management-ideas/multiple-owner-of-feature-dataset/idi-p/940778</link>
    <description>&lt;P&gt;Only the owener of feature datset can grant priviliges, alter the schema, enable versining etc..&amp;nbsp;&lt;BR /&gt;In big projects where the owner might be unavailable and changing feature data set schema, like adding layers , or grant privilages might required, its good to have more than a user who can do this, not only the Owner of feature data set.&amp;nbsp;&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;&lt;!--  content transformation source ID: 087E0000000PLjV  --&gt;</description>
    <pubDate>Tue, 30 Aug 2022 00:58:44 GMT</pubDate>
    <dc:creator>aymansalah</dc:creator>
    <dc:date>2022-08-30T00:58:44Z</dc:date>
    <item>
      <title>Multiple owner of Feature Dataset</title>
      <link>https://community.esri.com/t5/data-management-ideas/multiple-owner-of-feature-dataset/idi-p/940778</link>
      <description>&lt;P&gt;Only the owener of feature datset can grant priviliges, alter the schema, enable versining etc..&amp;nbsp;&lt;BR /&gt;In big projects where the owner might be unavailable and changing feature data set schema, like adding layers , or grant privilages might required, its good to have more than a user who can do this, not only the Owner of feature data set.&amp;nbsp;&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;&lt;!--  content transformation source ID: 087E0000000PLjV  --&gt;</description>
      <pubDate>Tue, 30 Aug 2022 00:58:44 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/multiple-owner-of-feature-dataset/idi-p/940778</guid>
      <dc:creator>aymansalah</dc:creator>
      <dc:date>2022-08-30T00:58:44Z</dc:date>
    </item>
  </channel>
</rss>

