Publish DAM Metadata?

Just a thought ...
If you upload an image to the DAM, set some metadata, and publish, is there anyway to access the metadata from the Publish instance?  Is there a URL for xml which is accessible?
Thanks!

I am not quite sure understand your problem correctly and looks like you are looking for http://<host>:<port>/<patch of assets>/_jcr_content/metadata.xml example:-[1]
[1] http://localhost:4503/content/dam/geometrixx/drm/no-drm.jpg/_jcr_content/metadata.xml

Similar Messages

  • Publish Discoverer Metadata, possible ?

    Hi all,
    simple question:
    Is it possible to publish Discoverer Metadata to the Users ? If yes then please describe how or point to a document as I haven't been able to find any related information about this.
    It would seem natural to be able to publish it as it is the centralised metadata repository so I guess that I have been just looking in all the wrong places :-)
    - Kalle

    See if these links help
    http://www.oraclenerd.com/2010/10/discoverer-to-obiee-migration-utility.html
    http://obiee101.blogspot.com/2008/08/obiee-migrating-oracle-bi-discoverer-to.html
    There are also commercial solutions to the migration
    HTH
    Srini

  • Publish Persistent Metadata breaking instances in .swc export?

    I'm trying to export publish persistent metadata from JSFL in flash pro.. 
    If i export as a swf file it works as expected.. the metaData is available...
    Now, if i export an swc instead.. it will make the instance holding the metadata into NULL,
    and thereby also removing it from the stage. The name exists but it is no longer is a child.
    Surely this cant be correct behaviour? Can anyone confirm this is a bug in Flash Pro? (Using Fl pro CC 2014.1)
    jsfl code:
    element.setPersistentData( "testvalue", "string", "test123" );
    element.setPublishPersistentData("testvalue", "_EMBED_SWF_", true);
    fl.getDocumentDOM().setPublishDocumentData("EMBED_SWF", true);

    Nothing.... guess i have to report it in the bugbase just then

  • View metadata near his image in a html file?

    Hi
    I am new to this board,
    I wanted to ask if there is a way to publish the metadata of an image, (or filtered metadata), into a html file, (for expample near the image).
    It want to publish photos with some of the metadata of it made readable on an easy way...
    Thank you in advance for looking at my problem
    Erwin

    Within Bridge you can select a batch of images and convert them to a Photoshop Web Photo Gallery.
    You can customize the page templates that Photoshop uses. I've not seen any documentation for metadata but some of the templates display caption, copyright, etc. Try searching or asking on the Photoshop forum.

  • Introducing Custom Metadata property through a package

    Hi,
    I want to introduce a new custom metadata property for my assets which could be displayed in the DAM metadata UI of an asset as below. I can see some steps mentioned to do this in http://dev.day.com/docs/en/cq/current/dam/how_to_edit_metadata.html. However I want to do this through a package that I am developing. Hence whenever my package is installed in CQ some custome metadata properties must be automatically regisitered for all assets.
    To summarize I have following queries:
    How to create/register custome metadata proerties for assets in a package using CQ APIs ?
    Once a custome metadata prperty is registered how to update its value using Asset API ?
    Appreciate any help here!

    Check http://www.wemblog.com/2013/01/how-to-associate-cug-with-dam-asset-in.html is that helps.
    Yogesh

  • Flex sdk incremental build will lose swc information

    I have a mxmlc ant task job like this
            <mxmlc 
            file="${trunk_dir}/main/src/main.mxml"
            output="${local_tmp}/app/bin/main.swf"
                      >    
                <load-config filename="${basedir}/flex-config-sea.xml"/>
                <source-path path-element="${FLEX_HOME}/frameworks"/>
            </mxmlc>
    in flex-config-sea.xml I put this in for incremental compile and swc build
          <include-libraries>
             <library>/opt/cruisecontrol-bin-2.8.4/projects/sea_client/trunk/main/libs/Mate_08_9.swc</library>
             <library>/opt/cruisecontrol-bin-2.8.4/projects/sea_client/trunk/main/libs/xprogress.swc</library>
             <library>/opt/cruisecontrol-bin-2.8.4/projects/sea_client/trunk/main/libs/component.swc</library>
          </include-libraries>
          <incremental>true</incremental>
    the first time build is ok, but the second time after I changed one single file, the output is
    [mxmlc] Loading configuration file /opt/cruisecontrol-bin-2.8.4/projects/cc/flex-config-sea.xml
        [mxmlc] Recompile: /opt/cruisecontrol-bin-2.8.4/projects/sea_client/trunk/main/src/C.as
        [mxmlc] Reason: The source file or one of the included files has been updated.
        [mxmlc] Files changed: 1 Files affected: 0
        [mxmlc] Required RSLs:
        [mxmlc]     textLayout_2.0.0.232.swz with 1 failover.
        [mxmlc]     framework_4.6.0.23201.swz with 1 failover.
        [mxmlc]     rpc_4.6.0.23201.swz with 1 failover.
        [mxmlc]     mx_4.6.0.23201.swz with 1 failover.
        [mxmlc]     spark_4.6.0.23201.swz with 1 failover.
        [mxmlc]     sparkskins_4.6.0.23201.swz with 1 failover.
        [mxmlc] /tmp/sea_local/app/bin/main.swf (426617 bytes)
    but the output swf is complaining lack of some swc when running, which didn't show up in the first time
    ReferenceError: Error #1065: Variable _shared_maps_GlobalMapWatcherSetupUtil is not defined.
              at global/flash.utils::getDefinitionByName()
              at shared.maps::GlobalMap()
              at main/_main_GlobalMap1_i()
              at main()
              at _main_mx_managers_SystemManager/create()
              at mx.managers.systemClasses::ChildManager/initializeTopLevelWindow()
              at mx.managers::SystemManager/initializeTopLevelWindow()
              at mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::kickOff()
              at mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::preloader_completeHandler()
              at flash.events::EventDispatcher/dispatchEventFunction()
              at flash.events::EventDispatcher/dispatchEvent()
              at mx.preloaders::Preloader/timerHandler()
              at flash.utils::Timer/_timerDispatch()
              at flash.utils::Timer/tick()
    this message normally shows up when there's no Mate_08_9.swc found at runtime. but this shouldn't happen.
    is there anyway to work around this? thanks a lot
    here is the full flex-config-sea.xml:
    <flex-config>
       <!-- benchmark: output performance benchmark-->
       <!-- benchmark usage:
       <benchmark>boolean</benchmark>
       -->
       <compiler>
          <!-- compiler.accessible: generate an accessible SWF-->
          <accessible>true</accessible>
          <!-- compiler.actionscript-file-encoding: specifies actionscript file encoding. If there is no BOM in the AS3 source files, the compiler will use this file encoding.-->
          <!-- compiler.actionscript-file-encoding usage:
          <actionscript-file-encoding>string</actionscript-file-encoding>
          -->
          <!-- compiler.allow-source-path-overlap: checks if a source-path entry is a subdirectory of another source-path entry. It helps make the package names of MXML components unambiguous.-->
          <allow-source-path-overlap>false</allow-source-path-overlap>
          <!-- compiler.as3: use the ActionScript 3 class based object model for greater performance and better error reporting. In the class based object model most built-in functions are implemented as fixed methods of classes.-->
          <as3>true</as3>
          <!-- compiler.compress usage:
          <compress>boolean</compress>
          -->
          <!-- compiler.context-root: path to replace {context.root} tokens for service channel endpoints-->
          <!-- compiler.context-root usage:
          <context-root>context-path</context-root>
          -->
          <!-- compiler.debug: generates a movie that is suitable for debugging-->
          <debug>false</debug>
          <!-- compiler.defaults-css-files usage:
          <defaults-css-files>
             <filename>string</filename>
             <filename>string</filename>
          </defaults-css-files>
          -->
          <!-- compiler.defaults-css-url: defines the location of the default style sheet. Setting this option overrides the implicit use of the defaults.css style sheet in the framework.swc file.-->
          <!-- compiler.defaults-css-url usage:
          <defaults-css-url>string</defaults-css-url>
          -->
          <!-- compiler.define: define a global AS3 conditional compilation definition, e.g. -define=CONFIG::debugging,true or -define+=CONFIG::debugging,true (to append to existing definitions in flex-config.xml) -->
          <!-- compiler.define usage:
          <define>
             <name>string</name>
             <value>string</value>
             <value>string</value>
          </define>
          -->
          <!-- compiler.enable-runtime-design-layers usage:
          <enable-runtime-design-layers>boolean</enable-runtime-design-layers>
          -->
          <!-- compiler.es: use the ECMAScript edition 3 prototype based object model to allow dynamic overriding of prototype properties. In the prototype based object model built-in functions are implemented as dynamic properties of prototype objects.-->
          <es>false</es>
          <extensions>
             <!-- compiler.extensions.extension usage:
             <extension>
                <extension>string</extension>
                <parameters>string</parameters>
             </extension>
             -->
          </extensions>
          <!-- compiler.external-library-path: list of SWC files or directories to compile against but to omit from linking-->
          <external-library-path>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/player/11.1/playerglobal.swc</path-element>
          </external-library-path>
          <fonts>
             <!-- compiler.fonts.advanced-anti-aliasing: enables advanced anti-aliasing for embedded fonts, which provides greater clarity for small fonts.-->
             <advanced-anti-aliasing>true</advanced-anti-aliasing>
             <!-- compiler.fonts.flash-type: enables FlashType for embedded fonts, which provides greater clarity for small fonts.-->
             <!-- compiler.fonts.flash-type usage:
             <flash-type>boolean</flash-type>
             -->
             <languages>
                <!-- compiler.fonts.languages.language-range: a range to restrict the number of font glyphs embedded into the SWF-->
                <!-- compiler.fonts.languages.language-range usage:
                <language-range>
                   <lang>string</lang>
                   <range>string</range>
                   <range>string</range>
                </language-range>
                -->
             </languages>
             <!-- compiler.fonts.local-font-paths usage:
             <local-font-paths>
                <path-element>string</path-element>
                <path-element>string</path-element>
             </local-font-paths>
             -->
             <!-- compiler.fonts.local-fonts-snapshot: File containing system font data produced by flex2.tools.FontSnapshot.-->
             <!-- compiler.fonts.managers: Compiler font manager classes, in policy resolution order-->
             <managers>
                <manager-class>flash.fonts.JREFontManager</manager-class>
                <manager-class>flash.fonts.BatikFontManager</manager-class>
                <manager-class>flash.fonts.AFEFontManager</manager-class>
                <manager-class>flash.fonts.CFFFontManager</manager-class>
             </managers>
             <!-- compiler.fonts.max-cached-fonts: sets the maximum number of fonts to keep in the server cache.  The default value is 20.-->
             <max-cached-fonts>20</max-cached-fonts>
             <!-- compiler.fonts.max-glyphs-per-face: sets the maximum number of character glyph-outlines to keep in the server cache for each font face. The default value is 1000.-->
             <max-glyphs-per-face>1000</max-glyphs-per-face>
          </fonts>
          <!-- compiler.headless-server: a flag to set when Flex is running on a server without a display-->
          <!-- compiler.headless-server usage:
          <headless-server>boolean</headless-server>
          -->
          <!-- compiler.include-libraries: a list of libraries (SWCs) to completely include in the SWF-->
          <!-- compiler.include-libraries usage:
          <include-libraries>
             <library>string</library>
             <library>string</library>
          </include-libraries>
          -->
          <include-libraries>
             <library>/opt/cruisecontrol-bin-2.8.4/projects/sea_client/trunk/main/libs/Mate_08_9.swc</library>
             <library>/opt/cruisecontrol-bin-2.8.4/projects/sea_client/trunk/main/libs/xprogress.swc</library>
             <library>/opt/cruisecontrol-bin-2.8.4/projects/sea_client/trunk/main/libs/component.swc</library>
          </include-libraries>
          <!-- compiler.incremental: enables incremental compilation-->
          <!-- compiler.incremental usage:
          <incremental>boolean</incremental>
          -->
          <incremental>true</incremental>
          <!-- compiler.isolate-styles: enables the compiled application or module to set styles that only affect itself and its children-->
          <!-- compiler.isolate-styles usage:
          <isolate-styles>boolean</isolate-styles>
          -->
          <!-- compiler.keep-all-type-selectors: disables the pruning of unused CSS type selectors-->
          <!-- compiler.keep-all-type-selectors usage:
          <keep-all-type-selectors>boolean</keep-all-type-selectors>
          -->
          <!-- compiler.keep-as3-metadata: keep the specified metadata in the SWF-->
          <!-- compiler.keep-as3-metadata usage:
          <keep-as3-metadata>
             <name>string</name>
             <name>string</name>
          </keep-as3-metadata>
          -->
          <!-- compiler.keep-generated-actionscript: save temporary source files generated during MXML compilation-->
          <keep-generated-actionscript>false</keep-generated-actionscript>
          <!-- compiler.library-path: list of SWC files or directories that contain SWC files-->
          <library-path>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/flash-integration.swc</path-element>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/authoringsupport.swc</path-element>
             <path-element>/opt/flexsdk/4.6.0/frameworks/locale/{locale}</path-element>
          </library-path>
          <!-- compiler.locale: specifies the locale for internationalization-->
          <locale>
             <locale-element>en_US</locale-element>
          </locale>
          <!-- compiler.minimum-supported-version usage:
          <minimum-supported-version>string</minimum-supported-version>
          -->
          <!-- compiler.mobile: specifies the target runtime is a mobile device-->
          <mobile>false</mobile>
          <mxml>
             <!-- compiler.mxml.compatibility-version: specifies a compatibility version. e.g. -compatibility-version=2.0.1-->
             <!-- compiler.mxml.compatibility-version usage:
             <compatibility-version>version</compatibility-version>
             -->
             <!-- compiler.mxml.minimum-supported-version usage:
             <minimum-supported-version>string</minimum-supported-version>
             -->
             <!-- compiler.mxml.qualified-type-selectors usage:
             <qualified-type-selectors>boolean</qualified-type-selectors>
             -->
          </mxml>
          <namespaces>
             <!-- compiler.namespaces.namespace: Specify a URI to associate with a manifest of components for use as MXML elements-->
             <namespace>
                <uri>http://ns.adobe.com/mxml/2009</uri>
                <manifest>/opt/flexsdk/4.6.0/frameworks/mxml-2009-manifest.xml</manifest>
             </namespace>
             <namespace>
                <uri>library://ns.adobe.com/flex/spark</uri>
                <manifest>/opt/flexsdk/4.6.0/frameworks/spark-manifest.xml</manifest>
             </namespace>
             <namespace>
                <uri>library://ns.adobe.com/flex/mx</uri>
                <manifest>/opt/flexsdk/4.6.0/frameworks/mx-manifest.xml</manifest>
             </namespace>
             <namespace>
                <uri>http://www.adobe.com/2006/mxml</uri>
                <manifest>/opt/flexsdk/4.6.0/frameworks/mxml-manifest.xml</manifest>
             </namespace>
          </namespaces>
          <!-- compiler.omit-trace-statements: toggle whether trace statements are omitted-->
          <omit-trace-statements>true</omit-trace-statements>
          <!-- compiler.optimize: Enable post-link SWF optimization-->
          <optimize>true</optimize>
          <!-- compiler.preloader: Specifies the default value for the Application's preloader attribute. If not specified, the default preloader value is mx.preloaders.SparkDownloadProgressBar when -compatibility-version >= 4.0 and mx.preloaders.DownloadProgressBar when -compatibility-version < 4.0.-->
          <!-- compiler.preloader usage:
          <preloader>string</preloader>
          -->
          <!-- compiler.report-invalid-styles-as-warnings: enables reporting of invalid styles as warnings-->
          <!-- compiler.report-invalid-styles-as-warnings usage:
          <report-invalid-styles-as-warnings>boolean</report-invalid-styles-as-warnings>
          -->
          <!-- compiler.report-missing-required-skin-parts-as-warnings: Use this option to generate a warning instead of an error when a missing required skin part is detected.-->
          <!-- compiler.report-missing-required-skin-parts-as-warnings usage:
          <report-missing-required-skin-parts-as-warnings>boolean</report-missing-required-skin-parts-as-warnings>
          -->
          <!-- compiler.services: path to Flex Data Services configuration file-->
          <!-- compiler.services usage:
          <services>filename</services>
          -->
          <!-- compiler.show-actionscript-warnings: runs the AS3 compiler in a mode that detects legal but potentially incorrect code-->
          <show-actionscript-warnings>true</show-actionscript-warnings>
          <!-- compiler.show-binding-warnings: toggle whether warnings generated from data binding code are displayed-->
          <show-binding-warnings>true</show-binding-warnings>
          <!-- compiler.show-invalid-css-property-warnings: toggle whether invalid css property warnings are reported-->
          <!-- compiler.show-invalid-css-property-warnings usage:
          <show-invalid-css-property-warnings>boolean</show-invalid-css-property-warnings>
          -->
          <!-- compiler.show-shadowed-device-font-warnings: toggles whether warnings are displayed when an embedded font name shadows a device font name-->
          <show-shadowed-device-font-warnings>false</show-shadowed-device-font-warnings>
          <!-- compiler.show-unused-type-selector-warnings: toggle whether warnings generated from unused CSS type selectors are displayed-->
          <show-unused-type-selector-warnings>true</show-unused-type-selector-warnings>
          <!-- compiler.source-path: list of path elements that form the roots of ActionScript class hierarchies-->
          <source-path>
          </source-path>
          <!-- compiler.strict: runs the AS3 compiler in strict error checking mode.-->
          <strict>true</strict>
          <!-- compiler.theme: list of CSS or SWC files to apply as a theme-->
          <!-- compiler.use-resource-bundle-metadata: determines whether resources bundles are included in the application.-->
          <use-resource-bundle-metadata>true</use-resource-bundle-metadata>
          <!-- compiler.verbose-stacktraces: save callstack information to the SWF for debugging-->
          <verbose-stacktraces>false</verbose-stacktraces>
          <!-- compiler.warn-array-tostring-changes: Array.toString() format has changed.-->
          <warn-array-tostring-changes>false</warn-array-tostring-changes>
          <!-- compiler.warn-assignment-within-conditional: Assignment within conditional.-->
          <warn-assignment-within-conditional>true</warn-assignment-within-conditional>
          <!-- compiler.warn-bad-array-cast: Possibly invalid Array cast operation.-->
          <warn-bad-array-cast>true</warn-bad-array-cast>
          <!-- compiler.warn-bad-bool-assignment: Non-Boolean value used where a Boolean value was expected.-->
          <warn-bad-bool-assignment>true</warn-bad-bool-assignment>
          <!-- compiler.warn-bad-date-cast: Invalid Date cast operation.-->
          <warn-bad-date-cast>true</warn-bad-date-cast>
          <!-- compiler.warn-bad-es3-type-method: Unknown method.-->
          <warn-bad-es3-type-method>true</warn-bad-es3-type-method>
          <!-- compiler.warn-bad-es3-type-prop: Unknown property.-->
          <warn-bad-es3-type-prop>true</warn-bad-es3-type-prop>
          <!-- compiler.warn-bad-nan-comparison: Illogical comparison with NaN. Any comparison operation involving NaN will evaluate to false because NaN != NaN.-->
          <warn-bad-nan-comparison>true</warn-bad-nan-comparison>
          <!-- compiler.warn-bad-null-assignment: Impossible assignment to null.-->
          <warn-bad-null-assignment>true</warn-bad-null-assignment>
          <!-- compiler.warn-bad-null-comparison: Illogical comparison with null.-->
          <warn-bad-null-comparison>true</warn-bad-null-comparison>
          <!-- compiler.warn-bad-undefined-comparison: Illogical comparison with undefined.  Only untyped variables (or variables of type *) can be undefined.-->
          <warn-bad-undefined-comparison>true</warn-bad-undefined-comparison>
          <!-- compiler.warn-boolean-constructor-with-no-args: Boolean() with no arguments returns false in ActionScript 3.0.  Boolean() returned undefined in ActionScript 2.0.-->
          <warn-boolean-constructor-with-no-args>false</warn-boolean-constructor-with-no-args>
          <!-- compiler.warn-changes-in-resolve: __resolve is no longer supported.-->
          <warn-changes-in-resolve>false</warn-changes-in-resolve>
          <!-- compiler.warn-class-is-sealed: Class is sealed.  It cannot have members added to it dynamically.-->
          <warn-class-is-sealed>true</warn-class-is-sealed>
          <!-- compiler.warn-const-not-initialized: Constant not initialized.-->
          <warn-const-not-initialized>true</warn-const-not-initialized>
          <!-- compiler.warn-constructor-returns-value: Function used in new expression returns a value.  Result will be what the function returns, rather than a new instance of that function.-->
          <warn-constructor-returns-value>false</warn-constructor-returns-value>
          <!-- compiler.warn-deprecated-event-handler-error: EventHandler was not added as a listener.-->
          <warn-deprecated-event-handler-error>false</warn-deprecated-event-handler-error>
          <!-- compiler.warn-deprecated-function-error: Unsupported ActionScript 2.0 function.-->
          <warn-deprecated-function-error>true</warn-deprecated-function-error>
          <!-- compiler.warn-deprecated-property-error: Unsupported ActionScript 2.0 property.-->
          <warn-deprecated-property-error>true</warn-deprecated-property-error>
          <!-- compiler.warn-duplicate-argument-names: More than one argument by the same name.-->
          <warn-duplicate-argument-names>true</warn-duplicate-argument-names>
          <!-- compiler.warn-duplicate-variable-def: Duplicate variable definition -->
          <warn-duplicate-variable-def>true</warn-duplicate-variable-def>
          <!-- compiler.warn-for-var-in-changes: ActionScript 3.0 iterates over an object's properties within a "for x in target" statement in random order.-->
          <warn-for-var-in-changes>false</warn-for-var-in-changes>
          <!-- compiler.warn-import-hides-class: Importing a package by the same name as the current class will hide that class identifier in this scope.-->
          <warn-import-hides-class>true</warn-import-hides-class>
          <!-- compiler.warn-instance-of-changes: Use of the instanceof operator.-->
          <warn-instance-of-changes>true</warn-instance-of-changes>
          <!-- compiler.warn-internal-error: Internal error in compiler.-->
          <warn-internal-error>true</warn-internal-error>
          <!-- compiler.warn-level-not-supported: _level is no longer supported. For more information, see the flash.display package.-->
          <warn-level-not-supported>true</warn-level-not-supported>
          <!-- compiler.warn-missing-namespace-decl: Missing namespace declaration (e.g. variable is not defined to be public, private, etc.).-->
          <warn-missing-namespace-decl>true</warn-missing-namespace-decl>
          <!-- compiler.warn-negative-uint-literal: Negative value will become a large positive value when assigned to a uint data type.-->
          <warn-negative-uint-literal>true</warn-negative-uint-literal>
          <!-- compiler.warn-no-constructor: Missing constructor.-->
          <warn-no-constructor>false</warn-no-constructor>
          <!-- compiler.warn-no-explicit-super-call-in-constructor: The super() statement was not called within the constructor.-->
          <warn-no-explicit-super-call-in-constructor>false</warn-no-explicit-super-call-in-constructor>
          <!-- compiler.warn-no-type-decl: Missing type declaration.-->
          <warn-no-type-decl>true</warn-no-type-decl>
          <!-- compiler.warn-number-from-string-changes: In ActionScript 3.0, white space is ignored and '' returns 0. Number() returns NaN in ActionScript 2.0 when the parameter is '' or contains white space.-->
          <warn-number-from-string-changes>false</warn-number-from-string-changes>
          <!-- compiler.warn-scoping-change-in-this: Change in scoping for the this keyword.  Class methods extracted from an instance of a class will always resolve this back to that instance.  In ActionScript 2.0 this is looked up dynamically based on where the method is invoked from.-->
          <warn-scoping-change-in-this>false</warn-scoping-change-in-this>
          <!-- compiler.warn-slow-text-field-addition: Inefficient use of += on a TextField.-->
          <warn-slow-text-field-addition>true</warn-slow-text-field-addition>
          <!-- compiler.warn-unlikely-function-value: Possible missing parentheses.-->
          <warn-unlikely-function-value>true</warn-unlikely-function-value>
          <!-- compiler.warn-xml-class-has-changed: Possible usage of the ActionScript 2.0 XML class.-->
          <warn-xml-class-has-changed>false</warn-xml-class-has-changed>
       </compiler>
       <!-- debug-password: the password to include in debuggable SWFs-->
       <!-- debug-password usage:
       <debug-password>string</debug-password>
       -->
       <!-- default-background-color: default background color (may be overridden by the application code)-->
       <default-background-color>0xFFFFFF</default-background-color>
       <!-- default-frame-rate: default frame rate to be used in the SWF.-->
       <default-frame-rate>24</default-frame-rate>
       <!-- default-script-limits: default script execution limits (may be overridden by root attributes)-->
       <default-script-limits>
          <max-recursion-depth>1000</max-recursion-depth>
          <max-execution-time>60</max-execution-time>
       </default-script-limits>
       <!-- default-size: default application size (may be overridden by root attributes in the application)-->
       <default-size>
          <width>500</width>
          <height>375</height>
       </default-size>
       <!-- externs: a list of symbols to omit from linking when building a SWF-->
       <!-- externs usage:
       <externs>
          <symbol>string</symbol>
          <symbol>string</symbol>
       </externs>
       -->
       <frames>
          <!-- frames.frame: A SWF frame label with a sequence of classnames that will be linked onto the frame.-->
          <!-- frames.frame usage:
          <frame>
             <label>string</label>
             <classname>string</classname>
          </frame>
          -->
       </frames>
       <framework>halo</framework>
       <!-- include-inheritance-dependencies-only: only include inheritance dependencies of classes specified with include-classes -->
       <!-- include-inheritance-dependencies-only usage:
       <include-inheritance-dependencies-only>boolean</include-inheritance-dependencies-only>
       -->
       <!-- include-resource-bundles: a list of resource bundles to include in the output SWC-->
       <!-- include-resource-bundles usage:
       <include-resource-bundles>
          <bundle>string</bundle>
          <bundle>string</bundle>
       </include-resource-bundles>
       -->
       <!-- includes: a list of symbols to always link in when building a SWF-->
       <!-- includes usage:
       <includes>
          <symbol>string</symbol>
          <symbol>string</symbol>
       </includes>
       -->
       <!-- link-report: Output a XML-formatted report of all definitions linked into the application.-->
       <!-- link-report usage:
       <link-report>filename</link-report>
       -->
       <!-- load-config: load a file containing configuration options-->
       <!-- load-externs: an XML file containing <def>, <pre>, and <ext> symbols to omit from linking when building a SWF-->
       <!-- load-externs usage:
       <load-externs>filename</load-externs>
       -->
       <metadata>
          <!-- metadata.contributor: A contributor's name to store in the SWF metadata-->
          <!-- metadata.contributor usage:
          <contributor>name</contributor>
          -->
          <!-- metadata.creator: A creator's name to store in the SWF metadata-->
          <creator>darkhutgme</creator>
          <!-- metadata.date: The creation date to store in the SWF metadata-->
          <!-- metadata.date usage:
          <date>text</date>
          -->
          <!-- metadata.description: The default description to store in the SWF metadata-->
          <description></description>
          <!-- metadata.language: The language to store in the SWF metadata (i.e. EN, FR)-->
          <language>EN</language>
          <!-- metadata.localized-description: A localized RDF/XMP description to store in the SWF metadata-->
          <!-- metadata.localized-description usage:
          <localized-description>
             <text>string</text>
             <lang>string</lang>
             <lang>string</lang>
          </localized-description>
          -->
          <!-- metadata.localized-title: A localized RDF/XMP title to store in the SWF metadata-->
          <!-- metadata.localized-title usage:
          <localized-title>
             <title>string</title>
             <lang>string</lang>
             <lang>string</lang>
          </localized-title>
          -->
          <!-- metadata.publisher: A publisher's name to store in the SWF metadata-->
          <publisher>darkhutgame</publisher>
          <!-- metadata.title: The default title to store in the SWF metadata-->
          <title>GAME</title>
       </metadata>
       <!-- raw-metadata: XML text to store in the SWF metadata (overrides metadata.* configuration)-->
       <!-- raw-metadata usage:
       <raw-metadata>text</raw-metadata>
       -->
       <!-- remove-unused-rsls: remove RSLs that are not being used by the application-->
       <remove-unused-rsls>true</remove-unused-rsls>
       <!-- resource-bundle-list: prints a list of resource bundles to a file for input to the compc compiler to create a resource bundle SWC file. -->
       <!-- resource-bundle-list usage:
       <resource-bundle-list>filename</resource-bundle-list>
       -->
       <!-- runtime-shared-libraries: a list of runtime shared library URLs to be loaded before the application starts-->
       <!-- runtime-shared-libraries usage:
       <runtime-shared-libraries>
          <url>string</url>
          <url>string</url>
       </runtime-shared-libraries>
       -->
       <!-- runtime-shared-library-path: specifies a SWC to link against, an RSL URL to load, with an optional policy file URL and optional failover URLs -->
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/textLayout.swc</path-element>
          <rsl-url>textLayout_2.0.0.232.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/tlf/2.0.0.232/textLayout_2.0.0.232.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/osmf.swc</path-element>
          <rsl-url>osmf_1.0.0.16316.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/osmf_1.0.0.16316.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/framework.swc</path-element>
          <rsl-url>framework_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/framework_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/charts.swc</path-element>
          <rsl-url>charts_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/charts_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/rpc.swc</path-element>
          <rsl-url>rpc_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/rpc_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/mx/mx.swc</path-element>
          <rsl-url>mx_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/mx_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/advancedgrids.swc</path-element>
          <rsl-url>advancedgrids_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/advancedgrids_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/spark.swc</path-element>
          <rsl-url>spark_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/spark_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/spark_dmv.swc</path-element>
          <rsl-url>spark_dmv_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/spark_dmv_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/sparkskins.swc</path-element>
          <rsl-url>sparkskins_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/sparkskins_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-settings>
          <!-- runtime-shared-library-settings.application-domain: override the application domain an RSL is loaded into. The supported values are 'current', 'default', 'parent', or 'top-level'.-->
          <application-domain>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/textLayout.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/osmf.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/framework.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/charts.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/rpc.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/mx/mx.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/advancedgrids.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/spark.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/spark_dmv.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/sparkskins.swc</path-element>
             <application-domain-target>default</application-domain-target>
          </application-domain>
          <!-- runtime-shared-library-settings.force-rsls: force an RSL to be loaded, overriding the removal caused by using the remove-unused-rsls option-->
          <!-- runtime-shared-library-settings.force-rsls usage:
          <force-rsls>
             <path-element>string</path-element>
             <path-element>string</path-element>
          </force-rsls>
          -->
       </runtime-shared-library-settings>
       <!-- size-report: Output an XML-formatted report detailing the size of all code and data linked into the application.-->
       <!-- size-report usage:
       <size-report>filename</size-report>
       -->
       <!-- static-link-runtime-shared-libraries: statically link the libraries specified by the -runtime-shared-libraries-path option.-->
       <static-link-runtime-shared-libraries>false</static-link-runtime-shared-libraries>
       <!-- swf-version: specifies the version of the compiled SWF file.-->
       <swf-version>14</swf-version>
       <!-- target-player: specifies the version of the player the application is targeting. Features requiring a later version will not be compiled into the application. The minimum value supported is "9.0.0".-->
       <target-player>11.1.0</target-player>
       <!-- tools-locale: specifies the locale used by the compiler when reporting errors and warnings.-->
       <!-- tools-locale usage:
       <tools-locale>string</tools-locale>
       -->
       <!-- use-direct-blit: Use hardware acceleration to blit graphics to the screen, where such acceleration is available.-->
       <!-- use-direct-blit usage:
       <use-direct-blit>boolean</use-direct-blit>
       -->
       <!-- use-gpu: Use GPU compositing features when drawing graphics, where such acceleration is available.-->
       <!-- use-gpu usage:
       <use-gpu>boolean</use-gpu>
       -->
       <!-- use-network: toggle whether the SWF is flagged for access to network resources-->
       <use-network>true</use-network>
       <!-- verify-digests: verifies the libraries loaded at runtime are the correct ones.-->
       <verify-digests>true</verify-digests>
       <!-- warnings: toggle the display of warnings-->
       <!-- warnings usage:
       <warnings>boolean</warnings>
       -->
    </flex-config>

    Somewhere in your pom.xml where you are configuring your build dependancies there will be a line <scope>caching</scope> this line is configuring the build to use a flex runtime shared library. This line is generating the error because caching is not a valid dependancy scope in maven 3 however mojos uses it anyway. There was a defect opened against flexmojos; I've linked it below. Froeder's response to the issue was that it was not fixable, that the warning is expected and that we'll have to live with it for now.
    https://issues.sonatype.org/browse/FLEXMOJOS-363?page=com.atlassian.jira.plugin.system.iss uetabpanels%3Achangehistory-tabpanel

  • Summary of DBXML 2.3.10 indexes

    We are running performance tests on our DBXML 2.3.10 database. There is still some question as to indexing numbers. Could someone briefly summarize the options? I don't think this is well documented (I could be wrong). For example:
    1. Integers - There is no index type for integer, so what should we use?
    2. Decimal -How does it differ from a float or double
    3. Float/double - I assume this is the same idea as in the C language; single and double precision? Why would I not always use double if I am not concerned about memory? Does one perform better than the other.
    Anthony

    John,
    Thanks for the summary. However, I must tell you that in terms of BDBXML, the decimal index does not function correctly based on our tests. I believe 2.3.8 cited problems, and I wrongly assumed 2.3.10 fixed it. Here are the details using DBXML Shell. I am using a container with 1125750 documents. A sample document is included at the end of the post
    dbxml> listindexes
    Index: node-element-equality-double for node {}:rabbits
    This lookupindex works fine with the double index:
    dbxml> time lookupindex node-element-equality-double {} rabbits
    1125750 objects returned for eager index lookup 'node-element-equality-double'
    Time in seconds for command 'lookupindex': 25.066
    We can also use query to get the same data:
    dbxml> time query 'for $a in collection("SCHEMA_1804635228.dbxml") where $a/sys:Metadata/sys:Published/theRabbit/theData[rabbits=1500] return $a'
    1500 objects returned for eager expression 'for $a in collection("SCHEMA_1804635
    228.dbxml") where $a/sys:Metadata/sys:Published/theRabbit/theData[rabbits=1500]
    return $a'
    Time in seconds for command 'query': 5.157
    Now I delete the index:
    dbxml> delindex {} rabbits node-element-equality-double
    Deleting index type: node-element-equality-double from node: {}:rabbits
    ...And add the index, only this time it is decimal:
    dbxml> addindex {} rabbits node-element-equality-decimal
    Adding index type: node-element-equality-decimal to node: {}:rabbits
    I verify the index:
    dbxml> listindexes
    Index: node-element-equality-decimal for node {}:rabbits
    A Lookupindex yields about the same performance as when it was a double:
    dbxml> time lookupindex node-element-equality-decimal {} rabbits
    1125750 objects returned for eager index lookup 'node-element-equality-decimal'
    Time in seconds for command 'lookupindex': 27.551
    Now if I try to run a query to get the same data, asI did when it was a double index the performance is extremely poor:
    dbxml> time query 'for $a in collection("SCHEMA_1804635228.dbxml") where $a/sys:
    Metadata/sys:Published/theRabbit/theData[rabbits=1500] return $a'
    1500 objects returned for eager expression 'for $a in collection("SCHEMA_1804635
    228.dbxml") where $a/sys:Metadata/sys:Published/theRabbit/theDat[rabbits=1500]
    return $a'
    Time in seconds for command 'query': 629.097
    I also tried to cast with similar results:
    dbxml> time query 'for $a in collection("SCHEMA_1804635228.dbxml") where $a/sys:
    Metadata/sys:Published/theRabbit/theData[rabbits=xs:decimal(1500)] return $a'
    1500 objects returned for eager expression 'for $a in collection("SCHEMA_1804635
    228.dbxml") where $a/sys:Metadata/sys:Published/theRabbit/theData[rabbits=xs:decimal(1500)] return $a'
    Time in seconds for command 'query': 651.19
    Sample document:
    sys:Metadata xmlns:sys="http://jbischemas.rl.af.mil/schemas/sys">
    <sys:Extended>
    <im:BaseObject xmlns:im="http://jbischemas.rl.af.mil/schemas/im">
    <im:InfoObjectType>
    <im:Name>mil.af.rl.oim.benchmark.rabbit</im:Name>
    <im:MajorVersion>1</im:MajorVersion>
    <im:MinorVersion>0</im:MinorVersion>
    </im:InfoObjectType>
    <im:PublicationTime>2007-06-23T01:57:10Z</im:PublicationTime>
    <im:InfoObjectID>4b6s1ot-fbp6si-f3907lwp-1-f39fyzol-o4n7</im:InfoObjectID>
    <im:PublisherID>4b6s1ot-fbp6si-f3907lwp-1-f390cm3c-d</im:PublisherID>
    <im:PlatformID>4b6s1ot-fbp6si-f3907lwp-1-f3908pog-4</im:PlatformID>
    </im:BaseObject>
    </sys:Extended>
    <sys:Published>
    <theRabbit>
    <theData>
    <rabbitUID>4b6s1ot-cpx4r3-f390ckhi-1-f390ckhx-2</rabbitUID>
    <sequence_order_number>1500</sequence_order_number>
    <total>1500</total>
    <time_stamp_in_milliseconds>1182563830805</time_stamp_in_milliseconds>
    <rabbits>1500</rabbits>
    </theData>
    </theRabbit>
    </sys:Published>
    </sys:Metadata>

  • Term Store Error

    Hello,
    when I want creating a Managed Metadata column for your SharePoint 2010 I get this error:
    Default termstore for this site cannot be identified.
    I found a lot of solutions, at this link:
    http://www.sharepointfire.com/MyBlog/2013/01/default-termstore-for-this-site-cannot-be-identified-2/
    At our case, our default MMS Service is on another SharePoint farm (service app farm), which is connected successfully whith the not service app farm.
    At MMS, at our service app farm, there is this setting already done: checked, ‘’This service application is the default storage location for column specific term sets”, and click on OK.
    What can be now the problem with this connected service app?
    I hope somebody can help me,
    Thanks Horst MOSS 2007 Farm; MOSS 2010 Farm; TFS 2010; TFS 2013; IIS 7.5

    Hi wuwu,
    According to your description, I understanding is that you were unable to create a managed metadata column using the shared managed metadata service application.
    Please make sure you have shared the managed metadata service application across farms correctly. You can check your process as the following link:
    http://www.c-sharpcorner.com/uploadfile/anavijai/how-to-publish-managed-metadata-service-across-farms-in-sharepoint-2010/
    Check if the link(Update section) is useful for you:
    http://sharedpointers.blogspot.jp/2011/03/exceptions-when-creating-site-columns.html
    In addition, please check the log file to find more information about this issue.
    Best Regards,
    Wendy
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Wendy Li
    TechNet Community Support

  • [JS] XML transformation

    Hello,
    I want handling a xml file with ESTK but I is not the beginning of a solution.
    I am the
    myXMLFile = File ("~/Desktop/content/content.opf");
    myXMLFile.open ('r');
    myXMLFile.encoding = "UTF-8";
    currentXML var = new XML (myXMLFile.read ());
    myXMLFile.close ();
    $ writeln (currentXML.toXMLString ()).;
    Can anyone give me some stuff?
    thank you
    Bonjour,
    je voudrais manipulé un fichier xml avec ESTK mais je en trouve pas le début d'une solution.
    J'en suis là;
    myXMLFile = File ("~/Desktop/content/content.opf");
    myXMLFile.open ('r');
    myXMLFile.encoding = "UTF-8";
    currentXML var = new XML (myXMLFile.read ());
    myXMLFile.close ();
    $ writeln (currentXML.toXMLString ()).;
    Quelqu'un peut-il me donner un quelque truc?
    Merci

    Thank you, I found what helps me, here is the code, I do not know if this is the best codes.
    But I find it hard to test if a tag exite.
    myXMLFile =  File("~/Desktop/content/content.opf");
      myXMLFile.open('r');
      myXMLFile.encoding = "UTF-8";
      var currentXML = new XML(myXMLFile.read());
      //maLectureContent(myXMLFile);
      $.writeln (maLectureContent(myXMLFile));
    function maLectureContent(XMLFile) {
      default xml namespace = "xmlns\:dc=\"http\://purl.org/dc/elements/1.1/\"";
      var refFile = XMLFile;
      var XMLHeader = '';
      var XMLWorkbookHeader = "<\?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?>";
      var XMLWorkbookHeader2 = "xmlns=\"http\://www.idpf.org/2007/opf\" unique-identifier=\"bookid\" version=\"2.0\"";
      if(refFile != null) {
      refFile.open("r");
      var XMLToParse = refFile.read();
      refFile.close();
      var XMLsettings = XML.settings;
      XMLsettings.prettyPrinting = false;
      XML.setSettings(XMLsettings);
      XMLToParse = XMLToParse.replace(XMLWorkbookHeader,"");
      XMLToParse = XMLToParse.replace(XMLWorkbookHeader2,"");
      $.write (XMLToParse);
      var XMLData = new XML(XMLToParse);
      XMLToParse = null;
      } else {
      alert("Error opening XML file.");
      var test = {title:((XMLData.metadata['dc:title'].length() != 0)? XMLData.metadata['dc:title']:"vide"),
      desscription:((XMLData.metadata['dc:description'].length() != 0)? XMLData.metadata['dc:description']:"vide"),
      rights:((XMLData.metadata['dc:rights'].length() != 0)? XMLData.metadata['dc:rights']:"vide"),
      creator:((XMLData.metadata['dc:creator'].length() != 0)? XMLData.metadata['dc:creator']:"vide"),
      language:((XMLData.metadata['dc:language'].length() != 0)? XMLData.metadata['dc:language']:"vide"),
      date:((XMLData.metadata['dc:date'].length() != 0)? XMLData.metadata['dc:date']:"vide"),
      publisher:((XMLData.metadata['dc:publisher'].length() != 0)? XMLData.metadata['dc:publisher']:"vide"),
      subject:((XMLData.metadata['dc:subject'].length() != 0)? XMLData.metadata['dc:subject']:"vide"),
      language:((XMLData.metadata['dc:language'].length() != 0)? XMLData.metadata['dc:language']:"vide"),
    identifier:((XMLData.metadata['dc:identifier'].length() != 0)? XMLData.metadata['dc:identifier']:"vide")};
    //var test = XMLData.spine.itemref[2].@idref;
    return (test["date"]);

  • Captivate 3 not saving SCORM manifest

    I'm trying to use Captivate 3 to create a quiz to upload to
    Moodle. I've added grading to each question, enabled reporting for
    SCORM 1.2 - and all the other settings appear to be fine. But the
    only manifest I get, (and one Moodle doesn't recognize) is
    breeze-manifest.xml - which doesn't look anything like a SCORM
    manifest. Other than that i just have my 2 swf files and a
    BDMetadata.xml file that isn't SCORM related either.
    I am using Windows Vista - not sure if that matters - but
    something about the LMS reporting is not working with Captivate 3 -
    I've tried different settings - SCORM 2004, AICC - and the
    breeze-manifest.zml is all I ever get.

    Uncheck the 'publish Breeze metadata' (or something like
    that) in the
    Publish options to avoid the useless (if your not using
    Breeze) Breeze
    manifest. Be sure you have 'publish to zip file' (or
    something like
    that) checked. I'm pretty sure a manifest is not generated if
    you don't
    output the results to a zip file...
    If you do both those, is there an imsmanifest.xml file in the
    resulting
    .zip file?
    Erik
    stace20 wrote:
    > and the breeze-manifest.zml is all I ever get.
    >

  • Update Metadada via Batch

    Hello
    Guys,
    Is there any way to update a metadata via Batch?
    The Batch Loader will not work for me, because I don´t want to publish new documents.

    Hi
    There is a massmetadataupdate component that is a custom gig done by consultants to do the sort of the requirement which you are looking for . You should be able to get hold of it from any consultants at Oracle. Apart from that BatchLoader is best option for metadata update and I am not sure " what are you referring to as not to be published" .
    Metadata update does not create a new revision of the content .It's only a checkout and checkin operation that creates a new revision for the existing content and sends it to the indexer for getting published / released.
    Hope this helps
    Thanks
    Srinath

  • Flash CS5.5[Publish Settings]: How to include custom Metadata tags in swf?

    In Flash CS5, the 'Publish Settings' for the fla had an 'Export SWC' checkbox that took care of that.
    The option is missing. Why was it removed and how can  that be done in 5.5?

    Thanks sinious, but, it doesn't work.
    Let me elaborate on what I want to do:
    I'm trying to create a swf in Flash CS5.5, that's using a flex library (swc) that relies on Metadata tags (anotations).
    I need to use the metadata tags in my as3 code (in the fla), and They need to be compiled into the swf (by Flash CS5.5 compiler...).
    Although, when I load that swf, the metadata tags aren't compiled into it (I'm using describeType to check if tags are available in the swf).
    In flex, I would use the '-kepp-as3-metadata+=' compiler setting to do that, in Flash CS4 & CS5 I used the 'Export SWC' in the publish settings, but that's removed (WHY???).
    Checking XMP Metadata didn't change that, the tags are still not included in the compiled swf.
    Anyone?

  • SharePoint 2010 Slide Library Unable To Select Managed Metadata When Publishing.

    Hello,
    I'm running into some problems with Managed Metadata when uploading (publishing) slides in a SharePoint 2010 Slide Library.  If I have Managed Metadata Site Columns that are set to be required in my slide library, and I publish my slide(s) into the
    SharePoint 2010 Slide Library I'm not prompted to enter in my required Metadata before the slide is published.  The slide will upload, but then I would need to edit the slide and then enter in the required Metadata.
    If I create a new column with a type set to Choice for example, and set it to be required and I upload (publish) a slide I'm now prompted to enter in the required Metadata, but all the Managed Metadata choices are grayed out and I'm unable to select anything. 
    I'm able to select a Choice for the new column.
    Is this a bug within SharePoint 2010 that does not allow me to enter in Required Managed Metadata Tags on uploading (publishing) slides?
    Regular document libraries work just fine with required Managed Metadata.
    Thanks for any assistance.
    v/r
    JShidell
    v/r JShidell

    Hi,
    According to your post, my understanding is that the Managed Metadata not prompted to enter value in the required metadata.
    I had tested with this issue, and I found the same issue.
    We will help to submit the issue to proper pipeline for you.
    Again, thank you for your report which will definitely make SharePoint a better products. There might be some time delay. 
    Appreciate your time and patience.
    Thank you for your understanding and support.
    Thanks & Regards,
    Jason
    Jason Guo
    TechNet Community Support

  • How to record first-published date in metadata for use with US Copyright Office?

    Hello,
    I'd like to record the date when an image is first published in the image's metadata. This is useful for when I need to send group submissions of published works to the US Copyright Office. Can anyone advise as to the best place to record this information using Lightroom's metdata fields?
    Many thanks in advance,
    Matt

    I haven't found a field for this in Lightroom itself. It only seems to support Date Created, not the first Publication Date which is essential for copyright registration. For now I'm sticking Publication Date in the Instructions field, but I don't know if that's the best solution.
    A Publication Date field is available as part of the PLUS for Lightroom plug-in, which adds fields that support the PLUS image rights standard. It's a bit pricey, but if you run a business that does this all the time it might be worth it.
    You can see the plug-in's Publication Date field being used toward the end of the Part II demo movie at the PLUS for Lightroom plug-in site.
    What's interesting is that Lightroom 3 contains an "IPTC Extension" metadata panel that says PLUS Version 1.2.0 at the bottom, but this panel doesn't contain a Publication Date field. If you look at the XMP reference for PLUS Version 1.2.1, it lists a First Publication Date field. I don't know if that field got added in PLUS 1.2.1, but it's definitely missing from Lightroom 3.5.
    In the Lightroom feature request forum, the closest request I found was this one, so it might be worth adding a request for a Publication Date field.

  • Adding new metadata in DAM asset editor

    Hi All,
    I have a requirement wherein two projects reside on same instance, apps/ProjectA and apps/ProjectB . Now Project A has DAM customized, ie. a new metadata added and hence files,  /apps/dam/content/asseteditors/formitems and folders with files under  /apps/dam/gui/components have been modified to take care of creation of new metadata. Now my question is, Is it possible to have such DAM changes constrained to projectA alone, and Project B using default DAM?
    Is it possible to overlay DAM inside the apps/ProjectA alone?
    Kindly let me know.
    Regards,
    NZ

    Thank you jorg, so you say by applying ACL and deny read access for project B, and if Dam folder is Overlayed under  apps such as apps/dam, I can restrict modified version of DAM for project B thereby ProjectB using the foundation Dam and have modified version of dam for project A? Please correct me if I am wrong, since I have the jsp's such as child asset and metadata editor jsp modified after being overlayed.
    Regards,
    NZ

Maybe you are looking for