<?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>topic Re: Should I commit DAM metadata schema into Git codebase? in Adobe Experience Manager Assets Questions</title>
    <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-assets/should-i-commit-dam-metadata-schema-into-git-codebase/m-p/541208#M2540</link>
    <description>&lt;P&gt;Hi &lt;LI-USER uid="17533021"&gt;&lt;/LI-USER&gt;,&lt;/P&gt;
&lt;P&gt;In my opinion that is a good practice to keep your metadata schema configuration in git repository. I think that this is more application than content part. It's always good to have ability to track history of changes regarding metadata schema structure.&lt;/P&gt;</description>
    <pubDate>Wed, 17 Aug 2022 13:33:12 GMT</pubDate>
    <dc:creator>lukasz-m</dc:creator>
    <dc:date>2022-08-17T13:33:12Z</dc:date>
    <item>
      <title>Should I commit DAM metadata schema into Git codebase?</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-assets/should-i-commit-dam-metadata-schema-into-git-codebase/m-p/541175#M2539</link>
      <description>What is the best practice for DAM custom metadata schema and custom search forms. Do we commit the /conf/../dam/adminui-extension/metadataschema/.. into Git codebase and deploy through maven into AEM? OR do we treat metadata schema similar to /content and install the package manually on different environments?</description>
      <pubDate>Tue, 16 Aug 2022 23:38:16 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-assets/should-i-commit-dam-metadata-schema-into-git-codebase/m-p/541175#M2539</guid>
      <dc:creator>sarav-sgws</dc:creator>
      <dc:date>2022-08-16T23:38:16Z</dc:date>
    </item>
    <item>
      <title>Re: Should I commit DAM metadata schema into Git codebase?</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-assets/should-i-commit-dam-metadata-schema-into-git-codebase/m-p/541208#M2540</link>
      <description>&lt;P&gt;Hi &lt;LI-USER uid="17533021"&gt;&lt;/LI-USER&gt;,&lt;/P&gt;
&lt;P&gt;In my opinion that is a good practice to keep your metadata schema configuration in git repository. I think that this is more application than content part. It's always good to have ability to track history of changes regarding metadata schema structure.&lt;/P&gt;</description>
      <pubDate>Wed, 17 Aug 2022 13:33:12 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-assets/should-i-commit-dam-metadata-schema-into-git-codebase/m-p/541208#M2540</guid>
      <dc:creator>lukasz-m</dc:creator>
      <dc:date>2022-08-17T13:33:12Z</dc:date>
    </item>
    <item>
      <title>Re: Should I commit DAM metadata schema into Git codebase?</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-assets/should-i-commit-dam-metadata-schema-into-git-codebase/m-p/541545#M2546</link>
      <description>&lt;P&gt;sounds good. I too believed anything /content/ shouldn't go into git, but all rest folder should be committed. Was checking if there was opinion or reasons for otherwise.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Will commit and close this question.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Aug 2022 15:56:03 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-assets/should-i-commit-dam-metadata-schema-into-git-codebase/m-p/541545#M2546</guid>
      <dc:creator>sarav-sgws</dc:creator>
      <dc:date>2022-08-18T15:56:03Z</dc:date>
    </item>
  </channel>
</rss>

