Metadata field ordering incorrectly

I'm using profiles with 7.5.2 and in setting up new profiles I am having a hard time getting metadata fields to display in the correct order. They seem to have a mind of their own.
For instance I have a parent/child relationship setup but when I put the fields in the rule (parent then child) and open the check-in page for that profile they display -
Child
Parent
It isn't just DCL's though. It seems very random what fields will display in the correct order and which ones just seem to drop in where they feel like it LOL.
Any ideas?

If I disable the rule all the fields show up and I believe they show up in the order that they were added.
This is the only rule applied to this profile. Other rules do utilize them though in other profiles and they work fine.
It doesn't matter where I move the fields... the child field still shows up above the parent field in the profile.
If I group the rule everything displays fine but I want to be able to seperate or section off the content ID, author, title, account, and security group at the top and have all of these below. I guess I was trying to accomplish this within one rule because that is the way it is setup for our other Profiles.

Similar Messages

  • Field Order/Dominance question

    I've been noticing that spots I've produced that air on my local cable network appear to be having problems with jerky movement of elements created in Motion. I thought that maybe the field order was set wrong on my Motion projects. (I should add that I'm doing "the big no-no" by only monitoring these on my computer and not on a TV monitor. I know, I'll have to remedy that someday.) Anyway, I'm using the "NTSC Broadcast SD" preset and that means field order is lower/even. I'm definitely rendering these out with field rendering on (Apple ProRes, btw) as I can see the interlace combing when viewing the output file.
    I thought I'd try an experiment by creating a Motion project that would expose interlacing problems in the worst way and then render it out of Motion three ways: lower, upper and none. I then encoded these to mpeg-2 using Squeeze and burned them to a DVD (in DVDSP) to view on my consumer DVD player and SD television. (Remember, that's the only way I can view them played back interlaced...) To my surprise both the upper and lower movies looked terrible and the one rendered with no field dominance looked the best.
    What gives? Any ideas? Does this seem right?
    Thanks!
    --Kurt Cowling

    Wow Iain, you know waaaay more about this than I do. In fact, I asked a question in the iDVD area of this board many moons ago regarding whether or not there was some sort of metadata or tag that let iDVD know if the incoming file was interlaced or progressive and the response was basically "I don't know for sure, but I don't think so".
    Anyway, I can confirm what you say regarding the output of ProRes files. The content is interlaced, but when clicking the deinterlace button in the advanced area of QuickTime player nothing happens.
    I tried as you suggested and opened the "Advanced..." area of the output settings in Motion and found that interlace was indeed not checked in the ProRes settings. When I output a file after checking that box I can also confirm that the deinterlace button in QT player did actually deinterlace the display of the file.
    I normally output my Motion projects in several layers and bring them back into FCP (as rendered video, not Motion files) to composite them with the underlying camera footage. (Makes later changes and updates easier to deal with for my workflow.) I then export the composite out of FCP as uncompressed SD and then proceed to encode for FTP delivery from there (usually H.264). I opened a recent uncompressed file that was output from FCP and found that it suffered from the same problem, namely that the file was not tagged as interlaced, even though the content was interlaced.
    I then opened one of the H.264 files that was encoded from the uncompressed master. Same issue again.
    The one thing I haven't tried (yet) is outputting my test project from Motion as described in my first post (but with the files tagged correctly this time!) and see if the DVD that gets burned plays correctly. I will try this in the next day or two.
    I don't know what happens to my files after I FTP them to the cable provider, but I assume they must transcode them from H.264 into their system. If the files aren't tagged as interlaced then their system is probably treating them incorrectly, as well.
    This brings me to the final question(s) that may solve all of this for me:
    Is there a way to change just the metadata/tag in an existing QuickTime file (so that it is tagged correctly as interlaced) without having to re-render from the beginning? Also, It appears that FCP may suffer from the same issue since it obviously uses QT to export, just like Motion. If I correctly tag a file rendered from Motion and then import it into FCP and FCP doesn't then pass the correct tag on output to uncompressed I still have the same problem. Or, if FCP tags the uncompressed file correctly, but QT doesn't pass this along to the H.264, I'm still screwed. Hence, my question at the top of this paragraph! I think I really only need the last file I handle before FTPing to have the correct tag, since the content has been fine all along.
    Thanks so much Iain for looking into this! I would never have found this on my own. I'm not exactly sure if this is a bug or just a bad implementation, but this seems like a bad oversight for sure and not something that could be figured out from reading the manual.
    --Kurt
    p.s. I will try some more experimenting with this and hopefully can come back and marked this thread as "question answered" since a workaround seems doable. Iain, would you be willing to submit this to Apple as a bug report? You seem to have a much better handle on this than I do.

  • Custom metadata fields in ISCSSearchResponse

    Hi all,
    we are search UCM with CIS using the ISCSSearchAPI. The returned ISCSSearchResponse object contains most of our metadata fields as properties, but some are missing. Of course, we need one of the missing ones.
    When I call the GET_SEARCH_RESULTS service from UCM, the missing metadata field is returned.
    Does anybody know how I can configure the search to return my specific field as well?
    thanks,
    Harold

    Hi Ronen,
    you can
    If you have defined the properties working now, you know this path: System Administration - System Configuration - KM - Configuration - CM - Global Services - Property Structures.
    There you have the property structure DefaultPropertiesStructure using the property group all_groups.
    all_groups consists of system, custom ... etc. in the order the tab strips come up when using details for a resource. Within each group, under group items the property or the property group to be rendered appears (in the order they get rendered). This holds recursively for all groups.
    If you have defined your properties within group "custom", just arrange them in Group Items in the order you like.
    Hope it helps
    Detlev

  • How to hide custom metadata field in custom profies ??

    hi,
    how to hide custom metadata dropdown list in a custom profile based on choosing the security group.
    ex: if i choose xxx security group, custom metadata dropdown should not appeared, for remaining security groups it should be visible.
    so, Based on criteria, custom metadata should be hidden in custom profiles..
    how to achieve it ?? where and how to configure ??
    Detail guidance should be required
    Thanks in advance

    You cannot do this through profiles alone if I understand you correctly.
    If I load a check in page, choose a security group and at this moment want a custom metadata field to disappear then you are beyond what profiles offers.
    Rules evaluation can only be based on information that is know at the time the page is requested. That means in order for this to work you would need to make security group an non editable field and have a set of profiles for each security group.
    The alternative is to customize the UI with soem DHTML or AJAX
    Tim

  • Retrieve a list of different values of custom metadata field of an UCM connection

    Hi
    I am planning to create a custom search document functionality for my UCM and Portal integration. Basically, I am planing to create CMIS queries dynamically. In order to create the CMIS query, I need the possible values of custom metadata for the user to select from and through a backing bean construct the cmis query based on this selection.
    I have created a custom metadata field (lets say, 'KindOf'). So I want to show the user a list of all possible 'KindOf' values, so user selects the values he wants and I use those values to build the cmis query and show the results.
    What is the easiest, best practices, how would you do it, way of achieving this?
    I have little experience with UCM.
    Regards

    Hi,
    As rightly pointed out by jiri machotka, you want that option list .
    if you create a option list metadata, you have to publish schema to get the values. You can do it by two ways:
    1) Wait for the event which publish the schema automatically.
    2)Select "Publish schema" in the options menu of the Configuration Manager.
    Some good implementation info about searching can be found at - Students at Oracle: UCM: Creating search and check-in profiles with custom metadata
    and http://www.slideshare.net/heikim/effective-strategies-for-searching-oracle-ucm
    Otherwise if you want faceted search or something near to enterprise searching capabilities, then go for enterprise search engines.
    I have recently worked on Enterprise Search Engines on various CMS products for better,intuitive and relevant search results.
    Hope, above information can help you out.
    Regards,
    Hoque

  • Editing Autofill List for Custom Metadata Fields

    I have 13,000+ photographs cataloged in Aperture 2.1 In an effort to better manage these photographs, I have added custom metadata for my own use. The fields let me know whether I have printed for my portfolio, watermarked, added to my web site, status of release, etc. All of this data is manually entered and at times my fingers don't always hit the correct keys on the keyboard so I end up with autofill data that is incorrect. I have been unable to find a way to edit the autofill data for custom metadata fields. Selecting 'Edit Autofill List' does not give me access to my custom field autofill information. Am I missing something? Is this an oversight on my part or on the part of the application?

    Unfortunately I'm not using presets to do this. I don't think presets will help me with this, but it could be just that I don't understand presets that well. I use presets for entering Metadata from a shoot as I 'import' the raw files into Aperture. Maybe I'm trying to do something that Aperture was never intended to do, yet I need to have as few locations where I track
    As an example, as I print a photograph for my portfolio I mark one of the custom fields labelled 'Printed' as 'Yes'. Later I can locate those 4 or 5 star photographs that haven't been printed and decide if I want to print them. I use the same type of arrangement for my website with an 'Added to web' indicator as 'Yes'. I may also mark that 'Printed' field as 'N/A'. The reason follows. For watermarking photographs before adding them to my site via iWeb, I export and the photographs and then reimport the watermarked photographs into a separate project but since these photographs are at a lower resolution, have a different color profile and are jpegs, I never print them for my portfolio so I mark them 'N/A' in the 'Printed' field. Well my fingers do slip on the keys and before I realize it the nifty autofill now requires that I type not just the 'N' to get an 'N/A', but I must type it all, because one time I typed 'N and a space' or some such and that is what autofills. It even happens with 'Yes'. I suppose the real answer is to be more careful as I type, but that is not my reality.
    So, all I'm looking for is a way to have access to the autofill list that is created for my custom metadata fields so that I can delete the erroneous autofill entry. I've thought about deleting the field entirely and recreating it, but that would remove all those indicators or flags that I have already entered for my photographs.
    Alternatively I could find an IPTC field that I am not using and find a way to use it, (because those fields have autofill lists that can be edited). However my record keeping would be exported with the photograph. Some of the information that I collect is private and should not be included in the metadata while other information should be; that is why I've settled on custom metadata fields.
    I hope there is a simple answer to this that I'm overlooking.
    If someone else has another way of tracking this same information that is better than the custom metadata fields, I would like to hear about it. However, it would mean reworking all my photographs that Aperture currently manages.

  • Field order issues after export to DV Pal from uncompressed

    We are experiencing some difficulty exporting clips from FCP to our Omneon Server for TX.
    We are capturing 8 bit uncompressed (AJA and Blackmagic) from digibeta for our edit and all editing stays in uncompressed until final output. Our transmission system demands DV PAL files so we export finished items as DV PAL in FCP and drop onto the server
    Our problem is that on playback from the server, the field order is incorrect. Although the exported DV clips properties show lower field order, the clip is obviously playing upper field first. If we capture and edit in DV and export the DV file to the server, then we have no problems. I have tried
    exporting uncompressed clips to DV via Compressor and changing the field order in frame controls but no success. It seems that when a clip is captured and edited in upper field it hangs onto that status even after conversion to DV!! Any thoughts greatly appreciated!

    when you drop one of your 8 bit uncompressed source clips into your DV PAL timeline, is FCP correctly adding the Shift Fields filer to those timeline instances?
    do you edit in 8-bit uncompressed and then export direct to DV PAL or do you nest your 8 bit uncompressed sequence into a DV PAL sequence first and then export as Quicktime Movie w/ current settings? if not the latter, try it (and make sure your nest has the Shift Fields filter applied)

  • Batch process to create large number of metadata fields in UCM?

    Is there any kind of scripting available to create a large number of metadata fields in UCM?.
    thanks

    I can give you a code in java, which adds two metadata fields. It's quite hardcoded, but you could use it as a basis for a script:
    String FIELD1_NAME = "xsecretKey";
    String FIELD2_NAME = "xattachmentID";
    if (binder == null)
    binder = new DataBinder(SharedObjects.getSafeEnvironment());
    String maxOrderQuery = "select MAX(dOrder) as dOrder from DocMetaDefinition";
    try
    String val = loader.getDBConfigValue(COMPONENT_NAME, COMPONENT_SUBNAME, null);
    //binder.putLocal("dName", FIELD1_NAME);
    binder.putLocal("dName", FIELD2_NAME);
    ResultSet tempRs = ws.createResultSet("Qmetadef", binder);
    if (val == null || tempRs.isEmpty())
    ResultSet rset = ws.createResultSetSQL(maxOrderQuery);
    String orderStr = ResultSetUtils.getValue(rset, "dOrder");
    int order = NumberUtils.parseInteger(orderStr, 0);
    setNewFieldParams(binder, "BigText", "secretKey", "<$dateCurrent()*1$>");
    addNewMetadataField(FIELD1_NAME, binder, ++order, null, null, ws, cxt);
    setNewFieldParams(binder, "Text", "attachmentID", null);
    addNewMetadataField(FIELD2_NAME, binder, ++order, null, null, ws, cxt);
    rset = ws.createResultSetSQL("select * from DocMeta where dID=0");
    if (!testResultSetFieldExists(rset, FIELD1_NAME))
    FieldInfo fi[] = loader.createFieldInfo(new String[] {
    FIELD1_NAME
    }, 200);
    //fi[0].m_type = 5;
    ws.alterTable("DocMeta", fi, null, new String[] {
    "dName"
    if (!testResultSetFieldExists(rset, FIELD2_NAME))
    FieldInfo fi[] = loader.createFieldInfo(new String[] {
    FIELD2_NAME
    }, 30);
    //fi[0].m_type = 3;
    ws.alterTable("DocMeta", fi, null, new String[] {
    "dName"
    loader.setDBConfigValue(COMPONENT_NAME, COMPONENT_SUBNAME, "7.0", "1");
    catch (Exception e)
    SystemUtils.dumpException(null, e);
    }

  • Creating custom Metadata fields

    When I import images I need to add contact details of property owners and there's sometimes 2 or 3 owners so I've created a custom Metadata preset and used the "other" tab at the bottom of the Metadata inspector to add the fields: "Contact 2", "Contact 3" and "Cell phone", "Email" etc.
    The problem I have, is that I can add a new field in the "New Custom Metadata" box at the top of that tab, but the "+" symbol remains greyed out unless I enter characters into the Metadata value field. However, entering "placeholder" characters into the value field in order to activate the "+" symbol seems crazy because I'm creating a template, and the data will be different every time I import and I don't want to have to delete the placeholder characters when I'm importing. I just want to have custom fields and a blank box for data entry beside ready for me to fill it in when I import. Is this possible?

    A metadata field of type boolean will be a checkbox as long as there is no lookup associated with it.
    If you assign a lookup to it (either when you create the field, or in the group), then you will see it with a lookup.

  • Adobe Bridge CC: Batch Rename using any metadata field

    How can I add certain Metadata fields to the pull down menu in the batch rename function?
    I need to do a batch rename of files, but using metadata fields that are not available as an option on the pull down menu.
    Hoping to use any or all of these:
    Audio : Artist, Album, Genre
    IPTC Core : Description, Keywords, etc..

    I don't think there is any way in which you can add to the built-in functions…
    Unless this is actually provided by one of the Adobe start-up scripts… ( I've not see it when digging about )
    You would probably need a scripted solution that can give you drop down menu of the extra options you want.

  • To plugin developers: can I have access to any metadata field of the catalog in Print Module?

    Dear LR plugin developers,
    Maybe one of you has already implemented such a feature, maybe I can entice you to do so, if several people find this useful?
    Is there a forum for plugin feature requests? If so, forgive me for using this general user-to-user for this. Or would you look on the Adobe feature request forum for such input?
    I would like to have access to any metadata field of the catalog in Print module, ok if for all LR standard catalog fields, preferable if also for custom fields created by other plugins.
    I would want to add such a field underneath each image on a print page, e.g. something like complete exposure info.
    Doing so in export in a "Mogrify-like" way would also be ok, if metadata accessible. Fixed custom text obviously would be cumbersome, as limiting to 1 image to export at a time. Creating jpgs in export is ok,
    Print module would be preferable as I was hoping for more than one image per page=jpg.
    Now if such text could even be placed anywhere on a print template, possibly containing also free text, and formatable - you would have corrected the basic design flaw of the Book module imo...
    Cornelia

    Cornelia
    The problem one faces is that the SDK does not access Print or Book. You'll need to (ab)use the fields that are available, and I'd suggest you look at my Search and Replace plugin which can transfer values between fields. So you could move info from an inaccessible field to one that can be printed. Maybe use virtual copies which you can just discard afterwards?
    John

  • How to add a new metadata field to iPhoto where new field is calculated as age in years and month based on a specific date and the date photo was taken ? I want to calculate and display the age of my two kids on every photo.

    Hi
    How can I add 2 new metadata-fields to every photo in iPhoto ?
    The new fields should state the age of my kids in years and months based on the date that they were born and the date that photo is taken.
    Exampel:
    My son is born 01.01.2010
    My daughter is born 01.01.2012
    Photo taken by data
    Aage of son
    Aage of daughter
    01.07.2011
    1 year 6 month
    not born yet
    01.01.2014
    4 year 0 month
    2 year 0 month
    I would like to be able to search by kids age and get the info displayed when doing slideshows.
    How to do this in iPhoto ?
    Any alternatives to accomplish the same ?
    Kind regards

    It can't be done with iPhoto.  There are some DAM (digital asset management) applications that can write to other IPTC fields that iPhoto can't read. One such app is Media Pro 1.
    However you would have to calculate the age for each date and add it to one of the fields. There are online age calculators that can do that for you: Age Calculators
    If you go thru that much trouble then use iPhoto, make the calculations and add the age to the Description field.  Then you can use Smart Albums to search for 1year 6 month text.
    OT

  • Export QuickTime Movie shifts field order

    In august I finished grading a project and made a QT Prores 422 master file for the client to have delivered on a hard drive.
    The client has kept quiet until now about an issue - the field order seems to be wrong. I couldn't believe my ears when he told me that. The timeline is lower (even) while the QT file he had received is Upper (odd).
    I selected 5 seconds of the timeline and exported using CMD+E, and it says "Setting: current settings". So I thought it would be lower field as the timeline - but no - it comes out as upper, every single time.
    How does this happen? Do I really have to make a conversion through compressorr?!

    The following settings are the same for the prepped timeline and the one that came back from Color
    *Sequence settings*
    720x576 PAL Anamorphic 16:9
    Field Dominance: Lower (even)
    Compressor: Apple ProRes 422
    *Item Properties*
    Frame Size: 720x576
    Anamorphic: Yes
    Compressor: Apple ProRes 422
    Field Dominance: Lower (even)
    However, I think I nailed it. Gonna do some further testing to make sure though... In the Export to QuickTime Movie window, I found that I can select some other setting, using ProRes 422 PAL Anamorphic for instance. And as far as I know - PAL is always lower field, and it seemed to work for the first test I did.

  • How to make metadata fields required when creating folders

    Hello all....
    Related issue with SR 3-6472229431 and SR 3-6471130611.
    We're using DIS 11.1.6 64-bits (2011_11_29 (rev 9756) 11.1.6.97) in a Windows 7 64-bits workstation (with UCM 11.1.1.5 in a Linux machine). The check-in of images to UCM goes fine.
    I'm trying to make some metadata fields required when creating a folder. These fields are required when making a check-in, but not when creating folders.
    Folders_g is enabled. DesktopTag too.
    EDIT: Patch: 14695303 - WCC 11.1.1.5.0 BUNDLE ( MLR 16 ) NOV 6 2012 applied.
    Is it possible?
    Thanks for all.
    Edited by: fgomes on 22/11/2012 03:24

    After reading your response and rereading the original question a bit closer, the metadata prompting feature does not apply to creating new folders, only content.
    Again, though, I think the focus here is in the wrong place. The metadata applied to a folder is intended to be ultimately applied to the content. You can build global rules that fire on submission of content to check if a field has a value, and throw an error if the value is empty.
    If you expect users to create folders (and actually apply any metadata to the actual folder itself), you will be disappointed. Experience shows that users are not interested in that level of detail when creating content, let alone folders. Letting typical users create folders is a bad idea anyway, as they tend to create the same inefficient folder structures they previously created in file shares within Content Server.
    If you need to tightly control folder attributes, you'll be better served by locking down the ability to create new folders. Otherwise you're looking at some type of customization. Keep in mind that you won't be able to customize the right click behavior of DIS. Any changes to DIS would have to be an enhancement request.

  • Field Order is a required field for G/L account ....

    Hi Experts,
    I am getting following error while posting payroll to FI (tcode PC00_M99_CIPE - Create Posting Run).
    ================================================================================================
    Field Order is a required field for G/L account 1000 23107
         Message no. F5808
    Diagnosis
         The value for field "Order" in the interface to Financial Accounting is
         an initial value but you are required to make an entry in the field
         selection for G/L account "23107" in company code "1000" linked to the
         field selection for posting key "50".
    System Response
         Error
    Procedure
        It might be an error in the configuration of the G/L account field
        selection. The initial application, used to call up the interface must
        otherwise define a value for field "Order". If this is the case, contact
        the consultant responsible for the application used to call up the
        interface or get in contact with SAP directly.
    ================================================================================================
    Thanks for the solution in advance.
    Regards,
    Waqas Rashid

    Thanks Dilek for quick reply, but I am unable to find order field for my field status group in OBC4.
    Let me tell you the background of what I did ...
    I have one wage type 4113 which was linked to vendor account. I changed the link from vendor to balance sheet account and specified new GL 23206 for my symbolic account of wage type 4113.
    When I post the payroll result to FI after this change. I got this error.
    Regards,
    Waqas Rashid

Maybe you are looking for