Creating Metadata

I want to import an Express Database in the AWM (10.2.0.3). He shows me Objects in the Object View and not in the Model View. I want to create the new metadata that he shows me the Objects in the Model View.
I have tried it with the create db Standard Form and he brings me many errors. Oracle told me that this function is not implement in the Version 10.2.0.3.
Know somebody a way to program this Metadata?

The migration process might not be the best route for you as the requirements for compliance with Standard Form may not map to the structures within your original Express database. For example, in Express it was quite command to have separate dimensions to manage years, quarters and months. This allowed for extremely flexible reporting as years and quarters could appear on different axis within a report.
I would think the easiest and quickest way to resolve this issue would be to create a new analytic workspace using AWM and rebuild the dimensions and cubes you require using the GUI. This will allow you to make use of some of the new features such as cube compression and cube partitioning.
You will also need to determine the loading process for your cubes. You could continue to load data using Express DML programs, however, I would suggest you try to convert your application to load from relational tables/views as this will make maintenance going forward much easier. If you are currently using flat files to load your Express database these can be exposed to AWM via external tables and can then be used within the mapping editor.
Hope this helps
Keith Laker
Oracle EMEA Consulting
BI Blog: http://oraclebi.blogspot.com/
DM Blog: http://oracledmt.blogspot.com/
BI on Oracle: http://www.oracle.com/bi/
BI on OTN: http://www.oracle.com/technology/products/bi/
BI Samples: http://www.oracle.com/technology/products/bi/samples/

Similar Messages

  • Problems with the "Date Created" Metadata in Adobe Bridge

    Hi everyone.
    I am currently working on an electronic photo library for our organization.  Part of my mandate is to add a Date Created metadata on all the photos since it is very important to know when the photo was taken.  Some photos were dated since 1980s.  Since we do not have the digital version of the old photos, we end up scanning these and, in effect the date specified on the "Date Created" was the date it was scanned.
    I have the date of some of the old photos when it was taken, but for some, I only have the month and the year (sometimes, just the year).  Inventing a day and a month is not an option.
    Is it possible to enter a month-year or just the year on the Date Created field under Metadata?
    I appreciate your help.
    Thanks,
    .m.u.r.d.o.c.h.

    The problem is that dates are recorded in the file in different schemas. Bridge is displaying the XMP Date Created field which was likely derived from the original Exif date (probably DateTimeOriginal, but may be DateTimeDigitized). This will be the date recorded in the file by the scanner software at the time it was scanned.
    The IPTC Date Created field is handled differently. It seems counterintuitive, but if you work in the news business you will know that news photographers often use the IPTC Date Created field more like a "date submitted" or "date scheduled" property, so that photos for a particular shoot which may have been captured over multiple days will sort together.  Because of this, most image browsers will not update the XMP Date Created (or Date Taken) fields when the IPTC Core date is changed.
    You can edit the original capture date in various programs, which should cause both the Exif and the XMP Date Created fields to be updated. Two that come to mind are Lightroom and BreezeBrowser Pro (for Windows).  I've found that with certain images it is necessary to use both programs to get all the dates to line up.

  • Problem while creating metadata files

    I created metadata files to add styles to Photoshop Elements 8 (in Windows 7) and included them in the C:\Program Data\Adobe\Photoshop Elements\8.0\Photo Creations\layer styles folder.  The first several worked great and successfully showed up in the Styles Palette.  Later, when I was trying to add more styles I received a message in PSE 'Could not load styles because the file could not be found'.  I closed PSE.  Now every time I open Editor I receive this message and it locks up the program.  The only way I can close PSE is through Task Manager.
    Any suggestions on how to correct this?

    I put a copy of the third party styles in the Photoshop Elements Preset/styles folder and in the Photoshop Elements 8.0/Photo Creations/layer styles folder.  From the Photo Creations/layer styles folder I selected an existing metadata file and copied it to my desktop.  I changed the first part of the file name to the name of the new style (example: glitter 001.metadata).  I then right clicked and opened with Notepad.  When I found the name of the existing file I was using, I changed the name before the equation sign to the name of my new layer style with no spaces between words.  Then I changed the name after the equation sign to the name of the new style with spaces between words (glitter001=glitter 001).  I then deleted the lines below this except for the line /PSEContent leaving one space between the lines.  I saved and closed the document.  I then put the saved file in the Photo Creations/layer style folder.  When I started PSE I held down the sift key when I selected Editor.  As I said, the first two I did showed up fine.  The next ones is where I had the problem.
    I did all of this in the Admin account.  When I go into my user account, PSE works but now I am afraid to try to add the layer styles.

  • Unable to create Metadata connection for Dictionary Provider

    Hi,
    I am getting the following error while I try to run a Web Dynpro Application;
    The initial exception that caused the request to fail, was:
       com.sap.dictionary.runtime.DdException: 'WD_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
        at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:191)
        at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
        at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
        at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
        at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
        ... 37 more
    The JCo Connections are tested and pinged, they work fine.
    Can anyone please tell what the error could be?

    The details exception list is as below:
    com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.dow.dc.model.types.Syuname could not be loaded: com.sap.dictionary.runtime.DdException: 'WD_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
         at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
         at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sap.dictionary.runtime.DdException: 'WD_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
         at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:191)
         at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
         at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
         at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
         ... 34 more

  • Creating metadata templates

    I've completely ignored metadata templates over the 5 years I have been using Bridge. After reading an article on protecting IP, I decided that I should take an interest, and at least apply personal metadata on image import.
    So, the first thing I did was look at Create Metadata Template. When I activate this dialog box, I get this:
    I was stumped as to how to proceed, until I saw a website screenshot, and realised this is wrong. I searched the forums but came up empty.
    Can anyone suggest how I might solve this, please?

    {smacks forehead}
    Try this a little longer because it took you 4 years to start using this very useful option... :-) :-)
    Here is an example of my template that I have selected to be added on import using Photodownloader. When the 'keepers' are ready I only need to add additional info in the Description field, the city and keywords. Sometimes I need to change the province or even country but these filled template settings are most common for my work area so I decided it is easier to fill them in already and when needed change them.
    Mind also the copyright fields. Just an example, there are more ways of doing it :-)

  • RFC Error: Unable to create Metadata connection for Dictionary Provider

    I configured two RFC ('WD_XXX__MODELDATA_DEST and WD_XXX_RFC_METADATA_DEST). I tested it and it shown green light.
    When I run my application that coonnect to CRM using RFC, I got the following errors:
    <i>com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.xxx.types.Syuname could not be loaded: com.sap.dictionary.runtime.DdException: 'WD_ICEBERG_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_XXX_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
         at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:670)
         at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:233)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:654)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:443)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:381)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:410)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:79)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:121)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:117)
         at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.doInit(MappedNodeInfo.java:207)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:654)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:690)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:560)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:311)
         at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:204)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:347)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:668)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:268)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:40)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.dictionary.runtime.DdException: 'WD_XXX_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_XXX_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
         at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:225)
         at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)
         at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:87)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:73)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
         at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
         ... 49 more</i>
    I understand that I need to configured the Metadata Dictionary type for the RFC. For this, I need to configure the Message Server properties (for load balancing).
    But my Basis guy told me that CRM is an application server, so we only can configured with application server properties. Is this true? (I really doubt it) That is no Message Server connection to CRM system now.
    If it is true, how can I create a RFC connection to CRM system?
    Thanks for help.
    Kent

    Hi KC,
    Try the following links, they may help you.
    http://help.sap.com/saphelp_nw04s/helpdata/en/3a/3b1b40fcdd8f5ce10000000a155106/content.htm
    JCO connection
    Using the SAP Enterprise Connector for generating BAPI Proxy Classes
    points if useful
    Thanks
    Suresh

  • Creating MetaData using workbench

    Hi all,
    I'm trying to create metadata for some of my files, using the workbench,
    without success. When I followed the instructions for the sample classes,
    I can load the classes and manipulate them.
    However, when I try to do the same with my classes, I can see one of two
    things:
    1. When choosing to create a class level metadata file, I can choose the
    class file from the explorer like window, but the class name does not
    get placed on the 'class name to add' edit box in the 'Choose classes'
    dialog.
    2. When trying to mount a jdo file, I get an exception (SAXException)
    and a message that states that a class (the first listed in the file)
    cannot be instantiated.
    the workbench is configured with class paths that include the correct path,
    i.e. my classes are in <classes>\company\product\model\beans and this path
    is listed in the classpath config dialog. The workbench was started in
    <classes>. The classes are of course compiled. the jdk is on the path
    (JDK 5)
    When using ant to perform the mapping (that I want to use workbench for)
    it all works well.
    What gives? What am I doing wrong and how can I get this to work?
    Bonny
    What am I missing

    Hi all,
    I'm trying to create metadata for some of my files,
    using the workbench,
    without success. When I followed the instructions for
    the sample classes,
    I can load the classes and manipulate them.
    However, when I try to do the same with my classes, I
    can see one of two
    things:
    1. When choosing to create a class level metadata
    file, I can choose the
    class file from the explorer like window, but the
    the class name does not
    get placed on the 'class name to add' edit box in
    in the 'Choose classes'
    dialog.
    2. When trying to mount a jdo file, I get an
    exception (SAXException)
    and a message that states that a class (the first
    rst listed in the file)
    cannot be instantiated.
    the workbench is configured with class paths that
    include the correct path,
    i.e. my classes are in
    <classes>\company\product\model\beans and this path
    is listed in the classpath config dialog. The
    workbench was started in
    <classes>. The classes are of course compiled. the
    jdk is on the path
    (JDK 5)
    When using ant to perform the mapping (that I want to
    use workbench for)
    it all works well.
    What gives? What am I doing wrong and how can I get
    this to work?
    Bonny
    What am I missing
    Ok, so I've found in another post that you need to explicitly specify the path to the compiled classes in the classpath arg when starting the kodo workbench. Previously however, I had only specified the path to the root of my project (the directory with bin & src as children) as the value of the "directory" argument. I'm assuming that the previous src & bin directories that were showing up (they still show now ...) are because of this setting. Although I can successfully choose a class to create metadata for, this still doesn't seem like things are configured correctly. More insight would be helpful!
    Thanks,
    P$

  • P2 ingested footage with wrong date created metadata

    Hello, we're trying to standarize all of the media for our systems. Part of this includes ingesting P2 footage using Prelude and encoding it as DVCHDPro quicktime files. I know that the recommended method that adobe gives for ingesting P2 footage is to keep the file structure in tact and use the media browser function of Premiere; this, however, doesn't suit our company's needs of maintaining a relativaly NLE-agnostic media library and having quicktime compatiable discrete video clips of all our media. We're using Mac OSX operating systems, by the way. 
    The problem is that, when using Prelude to ingest, it seems that Prelude obliterates the "date created" metadata and file data (e.g. when selecting the "get info" on the clip itself; that file data). After ingesting a clip, if I open it in Premiere, there is no date-based metadata that matches the original record time on the .mxf file itself. Nor when I view the clip in OSX's "get info" does the "date created" panel reflect the date that the original file was created. It seems that it should be possible to write the original "date created" data to the ingested file (in the ingest panel in Prelude I can see the correct "date created" time); FCPX is able to do this when ingesting P2 media using their systems. Is there an option that I'm missing or is this simply not possible with this version of Prelude?
    To illustrate: here's a screencap of the ingest panel in prelude, notice the "date created" column reads 2013-06-28T11:43:05; which is the correct record date of that clip:
    However, after I ingest the clip, both within Premiere and the "get info" panel in OSX, the "date created" now refers only to my import time:

    Thanks both for your responses. I checked the .mxf file "date created" and it is indeed empty (see picture).
    The "date modified time" however, is correct. I do understand that when dragging media directly from the media browser in premiere that the metadata displays correctly; what I think should also happen is that when the footage is ingested and transcoded via Prelude, it should also display correct metadata. As shown in my pictures above, prelude does indeed see the correct "date created" (wherever it gets that information); it just obliterates it after it transcodes the clip; it's not available either in the "get info data" (which, somehow, FCPX does do when importing P2 media through their system) nor (most strangely) in premiere. Any settings or changes that could be made to address this would be appreciated.

  • Missing Create Metadata Menu Option

    Hi Everyone,
    I just bought and installed Photoshop CS2. and I'm trying to use Bridge (1.04.6)to create a Metadata template, but when I go to to "Tools" there is no "Create Metadata.." option.
    I am using a Vista Premium machine with SP1. Can anyone help?
    Thanks,
    Joe

    When I play the animation it just shows the same image throughout the entire sequence eventhough there is a different image on each layer. 

  • Metadata panel create metadata template I get an old template

    I did click on create metadata template so I should get a new, empy template and not an old one, already filled.

    I can get a clean template (with an old title) only if I start Bridge and
    press the option key, together, otherwise I won't get a clean template, so I
    sort of have to do that all the time, which is not normal.
    I agree that this is not normal, meanwhile try to use clear all values and
    save as an other name for a safe workaround in stead of refreshing prefs
    every time.
    Also, the appearance of the metadata content has changed, probably due to
    resetting default preferences.  All of those
    items of course do not reflect the items in the metadata preferences, where
    everything, really everything stayed checked, and it's tons, really tons of
    them, right?
    Resetting Preferences does set the IPTC to show all in Bridge prefs. The
    fastest way to correct this is to again to Bridge preferences metadata
    section and deselect the checkmark (minus) in front of the name in bold,
    this deselects all fields in one time. Now you have only choose the fields
    you want to show again in the Metadata panel.
    When you also choose to hide empty fields you will have a clean oversight in
    the Metadata panel. Also remember, changing checkmarks in Bridge prefs only
    affects the view ability of the fields and info in the metadata panel, all
    info and metadata is still present in the file (which you can also check in
    the menu File/File info or cmd+i)
    Is there a way to return to the workspace with larger thumbnails?
    Yes, reset workspace or use the slider bottom right to adjust size of
    thumbs.
    However useless, like you rightly said, I used to use it to type in individual
    descriptions for each tumbnails,from the metadata panel, and the description,
    together with the copyright notice and maybe the author, from the template, 
    did show in the metadata workspace with the larger thumbnails.
    As I already stated never to use the Metadata workspace I would advice you
    to play around with a workspace for your own workflow. Drag the panels to
    left or right (grab the tab with the name of the panel) and move it until
    you see a blue line. A single blue line means it fits between the other
    panels, a surrounding blue line means it nests as a tab to the same panel.
    You have 3 columns to work with and you can also resize the columns and
    panels until you are satisfied. After this go to the triangle top right next
    to workspace names and choose new workspace. Save it with a proper name and
    you can always use this workspace again.
    If you have to add info in metadata use the metadata panel for it. Having
    same info for multiple files just select all those files and type in this
    info only once to apply it to all those files. You can fine tune description
    afterwards if you need so for one or more other files by selecting them
    again.
    Also Batch rename is a very useful feature (shiftcmdR or tools/batch
    rename). You can rename all the selected files in one go with different
    sequence number or other options, explore the fields and add or delete a
    field with the plus and minus sign.
    Is there an attach button in the post so I can send you a screenshot
    Use the camera button icon that shows in the reply field of the forum to add
    a file

  • Should i use pipeline in order to get data from file path to create metadata?

    Hi,
    we use sharepoint 2013 to index file share and the folders structure represents data as project name / subject etc.
    Do you reccomend use pipeline capabilities in order to create metadata from those folders name? (so we will be able to use it as refiners later).
    In case so - how to do it?
    thanks
    keren tsur

    Hi  Keren,
    According to your description, my understanding is that you want to convert folder structure to SharePoint metadata.
    For achieving your demand, you can use the tool in codeplex:
    Folders To SharePoint Metadata Migrator (Folders2SP)
    Also you can have a look at the blog:
    http://en.community.dell.com/techcenter/sharepoint-for-all/w/wiki/5443.converting-folder-structure-to-sharepoint-metadata.aspx
    http://stackoverflow.com/questions/22411014/sharepoint-script-to-automatically-import-documents-from-a-network-share-on-a-r
    http://en.share-gate.com/blog/map-folder-names-to-sharepoint-metadata
    Best Regards,
    Eric
    Eric Tao
    TechNet Community Support

  • Why does the Date Created metadata change when images are exported?How do I stop it from changing?

    why does the Date Created metadata change when images are exported?  How do I stop it from changing? I must have a prefernce set up wrong.

    I don't know what OS you are using, or what application you are using to view the data about your exported files, but on Windows and using Windows Explorer the "Date Created" field relates only to the date that the exported file was created, i.e. if viewed immediately after export it will show the date created as being the same date. In order to view "Capture Date" in something like Explorer, you first have to ensure you have included the Metadata as Conrad outlined above, then you have to adjust the display properties of Explorer to show the "Date Taken" field. Here is an example, part of a folder I exported back on March 3rd, note the difference between that last two dates:

  • Please make "Copyright Status" an editable option in creating metadata templates

    I'm new to the Adobe eLearning suite, including Bridge CS4.  I've found a workaround in the forums for this issue already, but I really think this is something that Adobe should fix in the Bridge software itself.  Apologies if someone else has already posted this as a feature request in this forum, but as it seems I'm unable to search within just this forum, I gave up looking.
    In a nutshell: "Copyright Status" should be a field available when choosing what IPTC Core metadata to include in a new metadata template.  And it's also not an editable field when looking at the metadata for an image!  The whole point of metadata templates is to make it unnecessary to edit a single field (like "Copyright Status") one image at a time.  Yet even with the new Bridge CS4, the Copyright Status field is not an option you can include in a new metadata template.  Surely it wouldn't be that big a deal to make the 3-item pick list of "Unknown," "Copyrighted" and "Public Domain" available on the Create Metadata Template checklist.  Or if having a pick list is too tricky to code on that form and it must be just a checkbox item, do that, and let us populate the text in the field ourselves.
    Currently, it's necessary to tweak the metadata on a single image to include the "Copyrighted" status, then Export it and save it as a new metadata template, just to have that one field populated by default.  Supplying copyright status as part of a template is a fundamental need for anyone creating or dealing with large numbers of images, and it shouldn't require a workaround to create a properly inclusive metadata template.
    Thanks!

    In Bridge CS4, highlight your thumbnail, go to the File Menu and select File and then File Info.  There you will be able to choose your Copyright Status under the Description tab.  What a pain in the butt!  Mine kept coming up "Public Domain!"

  • Creating metadata in Flash CS3 and reading it in AS3

    Is there a way to store metadata in a library symbol in Flash
    CS3, and then read it in AS3? For example, I want to have the
    following code run:
    m_Metadata = 'You're cool!'
    I need this data before I can play the movie clip. Is there a
    way to store this? I've been trying to find a solution, but it
    looks like I'm just going to have to load in a separate XML file
    with the data.
    Thanks!

    Unfortunately there's no simple way to add instance level
    code in Flash CS3 or CS4 with AS3. This is a significant authoring
    tool deficiency in my opinion.
    Making a component... depending on what you want to do, there
    can be a lot of overhead. There may also be some very flaky/buggy
    behavior in Flash CS3 with custom components if your experience is
    anything like mine. However, for basic metadata, try this:
    1. Select the Symbol in the Library
    2. Right click, choose Component Definition...
    3. In the Parameters data grid you can add
    parameters/properties. Make sure you set the "Variable" field as a
    unique identifier for each parameter. These are the properties
    you'll use in AS at runtime to retrieve the values.
    4. Now on each instance on the canvas you can go to the
    Parameters tab and enter custom values for each parameter.
    5. At runtime, you should be able to access the values via
    instance_name.variable_name
    I believe that will work without actually creating a
    component class and making it functional.

  • Creating metadata for AWs created programatically (11.2)

    Hi guys
    The aim is to create Analytic Workspace within certain tablespace and with certain number of physical partitions.
    I tried following ways to create the AW:
    1st way:
    begin
    dbms_aw.aw_create(name => 'MIS_LT', tbspace => 'AW_MIS_LT_DI', partnum => 15);
    end;
    2nd way:
    begin
    dbms_aw.execute('AW CREATE MIS_LT PARTITIONS 15 TABLESPACE AW_MIS_LT_DI');
    end;
    After executing code from either 1st way or 2nd way - I got the result that I could see that new AW (MIS_LT) when executing query:
    select * from all_aws;
    Unfortunaltely I could not see the newly created AW in AWM. I suppose it's somehow related to missing metadata (standard form metadata ?).
    When executing following code:
    begin
    dbms_cube.import_xml( to_clob(
    '<Metadata
    Version="1.3"
    MinimumDatabaseVersion="11.2.0.2">
    <AW
    Name="MIS_LT"
    Version="11.2">
    </AW>
    </Metadata>'));
    end;
    PL/SQL block were executed successfully, but still MIS_LT was not visible in AWM (even after relogging):
    When trying to execute following code (like above -but one simple dimension was added):
    begin
    dbms_cube.import_xml( to_clob(
    '<Metadata
    Version="1.3"
    MinimumDatabaseVersion="11.2.0.2">
    <StandardDimension
    Name="CURRENCY_DIM_LT"
    ETViewName="V_CURRENCY_DIM_LT"
    ETKeyColumnName="DIM_KEY"
    ETLevelColumnName="LEVEL_NAME"
    ETMemberTypeColumnName="MEMBER_TYPE"
    ETDimensionOrderColumnName="DIM_ORDER"
    ETHierarchyOrderColumnName="HIER_ORDER"
    DefaultHierarchy="MAIN_HIERARCHY"
    ValueDescriptionAttribute="LONG_DESCRIPTION">
    <Hierarchy>
    <LevelHierarchy
    IsSkipLevel="False"
    IsRagged="False"
    Name="MAIN_HIERARCHY"
    ETParentColumnName="PARENT"
    ETDepthColumnName="DEPTH"
    ETViewName="V_CURRENCY_DIM_MAIN_HIERARC_LT">
    <Description
    Type="LongDescription"
    Language="ENGLISH"
    Value="MAIN HIERARCHY">
    </Description>
    <Description
    Type="ShortDescription"
    Language="ENGLISH"
    Value="MAIN HIERARCHY">
    </Description>
    <Description
    Type="Description"
    Language="ENGLISH"
    Value="MAIN HIERARCHY">
    </Description>
    <HierarchyLevel
    DimensionLevel="CURRENCY">
    <HierarchyLevelMap
    KeyExpression="MIS.MIS_CURRENCY_DIM.MCD_ID_CHAR"
    Query="MIS.MIS_CURRENCY_DIM"
    WhereClause="MIS.MIS_CURRENCY_DIM.MCD_CUNIT_ID = 2">
    <AttributeMap
    Name="LONG_DESCRIPTION"
    Attribute="LONG_DESCRIPTION"
    Expression="MIS.MIS_CURRENCY_DIM.MCD_CURRENCY_LEV_DESC">
    </AttributeMap>
    <AttributeMap
    Name="CURRENCY_LONG_DESCRIPTION"
    Attribute="CURRENCY_LONG_DESCRIPTION"
    Expression="MIS.MIS_CURRENCY_DIM.MCD_CURRENCY_LEV_DESC">
    </AttributeMap>
    </HierarchyLevelMap>
    </HierarchyLevel>
    </LevelHierarchy>
    </Hierarchy>
    <DimensionLevel
    Name="CURRENCY"
    ETKeyColumnName="CURRENCY">
    <Description
    Type="LongDescription"
    Language="ENGLISH"
    Value="CURRENCY">
    </Description>
    <Description
    Type="ShortDescription"
    Language="ENGLISH"
    Value="CURRENCY">
    </Description>
    <Description
    Type="Description"
    Language="ENGLISH"
    Value="CURRENCY">
    </Description>
    <VisibleAttribute
    Name="CURRENCY_LONG_DESCRIPTION"/>
    </DimensionLevel>
    <Attribute>
    <BaseAttribute
    SQLDataType="VARCHAR2(100)"
    AllowAutoDataTypeChange="False"
    ETAttributeColumnName="LONG_DESCRIPTION"
    IsMultiLingual="False"
    PopulateLineage="False"
    IsVisibleForAll="True"
    IsLevelUnique="False"
    Name="LONG_DESCRIPTION">
    <Classification
    Value="STAR"/>
    <Description
    Type="ShortDescription"
    Language="ENGLISH"
    Value="Long Description">
    </Description>
    <Description
    Type="LongDescription"
    Language="ENGLISH"
    Value="Long Description">
    </Description>
    <Description
    Type="Description"
    Language="ENGLISH"
    Value="Long Description">
    </Description>
    </BaseAttribute>
    </Attribute>
    <Attribute>
    <BaseAttribute
    SQLDataType="VARCHAR2(100)"
    AllowAutoDataTypeChange="False"
    ETAttributeColumnName="CURRENCY_LONG_DESCRIPTIO"
    IsMultiLingual="False"
    PopulateLineage="True"
    AttributeGroupName="LONG_DESCRIPTION"
    IsVisibleForAll="False"
    IsLevelUnique="False"
    Name="CURRENCY_LONG_DESCRIPTION">
    <Description
    Type="LongDescription"
    Language="ENGLISH"
    Value="CURRENCY Long Description">
    </Description>
    <Description
    Type="ShortDescription"
    Language="ENGLISH"
    Value="CURRENCY Long Description">
    </Description>
    <Description
    Type="Description"
    Language="ENGLISH"
    Value="CURRENCY Long Description">
    </Description>
    </BaseAttribute>
    </Attribute>
    <Organization>
    <AWPrimaryDimensionOrganization
    MVOption="NONE"
    HierarchyConsistencyRule="CONSISTENT"
    AddUniqueKeyPrefix="False"
    AW="MIS_LT">
    <MVCreationOptions
    RefreshOn="DEMAND"
    RefreshType="COMPLETE"
    UsingConstraintsClause="TRUSTED">
    </MVCreationOptions>
    <AttributeOrganization
    CreateIndex="False"
    Attribute="LONG_DESCRIPTION">
    </AttributeOrganization>
    <AttributeOrganization
    CreateIndex="False"
    Attribute="CURRENCY_LONG_DESCRIPTION">
    </AttributeOrganization>
    <DefaultBuild>
    <![CDATA[BUILD SPEC SYS_DEFAULT
      LOAD,
      COMPILE
    )]]>
    </DefaultBuild>
    </AWPrimaryDimensionOrganization>
    </Organization>
    <Description
    Type="LongDescription"
    Language="ENGLISH"
    Value="CURRENCY DIM">
    </Description>
    <Description
    Type="ShortDescription"
    Language="ENGLISH"
    Value="CURRENCY DIM">
    </Description>
    <Description
    Type="Description"
    Language="ENGLISH"
    Value="CURRENCY DIM">
    </Description>
    </StandardDimension>
    <AW
    Name="MIS_LT"
    Version="11.2">
    </AW>
    </Metadata>'));
    end;
    I got following errors:
    ORA-34492 Analytic Workspace object MIS_REPORTS.MIS_LT!___AW_ALL_OBJECTS doesn't exists.
    XOQ-01600 OLAP DML error when executing DML"SYS.AWXML!R11_MANANGE_DIMENSION"
    All in all it's got to be related to some missing metadata. Is there any way to create that metadata from PL/SQL wihout using AWM?
    Thanks in advance for any help.
    Best Regards
    Piotr

    You are correct in suspecting missing "standard form" metadata.
    The first two of you methods, "dbms_aw.aw_create" and "dbms_aw.execute" will both create an empty AW with no standard form metadata. Such an AW is fully supported and can be accessed through OLAP DML, but it is not visible in AWM and does not show up in the various USER_CUBE_* dictionary views.
    The third method, dbms_cube.import_xml, should have created a valid "standard form" AW that was visible in AWM.
    The error you got from your final method is easier to explain.
    >
    ORA-34492 Analytic Workspace object MIS_REPORTS.MIS_LT!___AW_ALL_OBJECTS doesn't exists.
    XOQ-01600 OLAP DML error when executing DML"SYS.AWXML!R11_MANANGE_DIMENSION"
    >
    The problem is that the import_xml procedure can create a new "standard form" AW or modify an existing "standard form" AW. But it will not convert an existing non-"standard form" AW into a "standard form" AW. I suspect the same thing happened in your third method, but no error was reported.
    The solution is to delete the empty AW by hand and then run your third method again.
    begin
    dbms_aw.execute('AW DELETE MIS_LT PARTITIONS');
    dbms_cube.import_xml( to_clob(
    '<Metadata
        Version="1.3"
        MinimumDatabaseVersion="11.2.0.2">
        <AW
          Name="MIS_LT"
          Version="11.2">
        </AW>
    </Metadata>'));
    end;
    /

Maybe you are looking for