<?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: Studio and DAM in Nuxeo Forum</title>
    <link>https://connect.hyland.com/t5/nuxeo-forum/studio-and-dam/m-p/323683#M10684</link>
    <description>&lt;P&gt;Would it make sense for Studio only to override standard document types once the Studio user determines that they need to be overridden, rather than overriding them by default?&lt;/P&gt;</description>
    <pubDate>Thu, 11 Sep 2014 18:14:30 GMT</pubDate>
    <dc:creator>dweisinger</dc:creator>
    <dc:date>2014-09-11T18:14:30Z</dc:date>
    <item>
      <title>Studio and DAM</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/studio-and-dam/m-p/323681#M10682</link>
      <description>&lt;P&gt;Just a note that may save you some time if you're using both Studio configurations and DAM...&lt;/P&gt;
&lt;P&gt;I found that after deploying the Studio jar file on the server that assets of Doctype 'File' were no longer included in the list of DAM assets.&lt;/P&gt;
&lt;P&gt;DAM expects an asset to have the facet 'Asset' assigned to it, and doctype 'File' normally will unless you deploy a Studio jar with default settings.&lt;/P&gt;
&lt;P&gt;Within Studio, under Content Model -&amp;gt; Documents -&amp;gt; File under facets you'll need to manually assign the 'Asset' facet to 'File' and any other doctypes that you want to use with DAM.&lt;/P&gt;
&lt;P&gt;DAM contributions in the file dam-core-types-contrib.xml try to append the 'Asset' facet to 'File', but the Studio file definition later overwrites it with the settings from Studio which doesn't have 'Asset' set by default.&lt;/P&gt;
&lt;P&gt;Don't know if it is possible, but if Studio can know that the target system has DAM deployed, the 'Asset' facet should be automatically assigned to non-folder doctypes.&lt;/P&gt;</description>
      <pubDate>Sat, 06 Sep 2014 20:28:35 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/studio-and-dam/m-p/323681#M10682</guid>
      <dc:creator>dweisinger</dc:creator>
      <dc:date>2014-09-06T20:28:35Z</dc:date>
    </item>
    <item>
      <title>Re: Studio and DAM</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/studio-and-dam/m-p/323682#M10683</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;</description>
      <pubDate>Thu, 11 Sep 2014 09:25:06 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/studio-and-dam/m-p/323682#M10683</guid>
      <dc:creator>Anahide_Tchertc</dc:creator>
      <dc:date>2014-09-11T09:25:06Z</dc:date>
    </item>
    <item>
      <title>Re: Studio and DAM</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/studio-and-dam/m-p/323683#M10684</link>
      <description>&lt;P&gt;Would it make sense for Studio only to override standard document types once the Studio user determines that they need to be overridden, rather than overriding them by default?&lt;/P&gt;</description>
      <pubDate>Thu, 11 Sep 2014 18:14:30 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/studio-and-dam/m-p/323683#M10684</guid>
      <dc:creator>dweisinger</dc:creator>
      <dc:date>2014-09-11T18:14:30Z</dc:date>
    </item>
  </channel>
</rss>

