Add "Softproof" as a searchable Metadata field or attribute

Eventually I expect that I will have a lot of Softproof copies on my hard drive, and will inevitably want to quickly identify those copies. Going through each individual photo in Lightroom and looking at the Copy Name is not very fast.
Ideally as a Metadata searchable field, the system would group and classify all Softproofs by printer color profile. Identifying all Softproofs for a specific paper and/or specific printer would be a snap.
Alternatively a searchable attribute "Softproof" which could quickly identify the Softproofs (or non-proofs if I negate it).
I note that currently the Copy name may be searched as a text field. If I enter the search criteria "Copy name" "Contains" "icc" I can pulll up my softproof copies. It would be far superior if I could use Metadata or Attribute.
Scott

Thank-you for the note ... I didn't realize that Is "Proof" had been added as a filter field in Smart Collections.
This is certainly a good work around, which I will use.
If "Proof" is an attribute of the photo (and/or virtual copy) then I still feel that it would be desirable as a criteria in the Library Filters. Until then I will use the Smart Collection (and "Copy Name" field search)
Scott

Similar Messages

Library filters: can I add to the list of metadata fields that I can search by?

Is it possible to add to the list of metadata fields that lightroom can search for images by?
I know about the 'Any searchable ... ' but that does now allow me to search for specific conditions -
I am using some of the IPTC fields as a way to classify images of mine for various purposes and would like to
do something like search for images where the iptc source field has a certain value while the instructions
fields has some other value. I do not think this is possible using the available tools.
So, I'd like to be able to add these fields to the menu of possible fields in Smart collections
of the library metadata filter.
So, am I missing something obvious? Can this be done?
Cheers,
Bonny

Hi Rob,
Thanks for this plug in - it's really great.
The fields I'm looking for are part of the IPTC fields, and since I'm entering them in LR, they're not part of the image,
and I assume not something that exiftool can find in the image. So unfortunately I do not think I can use this plugin
for the actual purpose I'm intending.
I'll shed some light on what I'm doing and therefore what I'm looking for:
I have a collection of images (of people) that I need to match names to.
I use some IPTC fields (that are otherwise useless for me) to store this data.
These fields are the "Job Identifier", "Instructions", "Creditline" and "Source" in the IPTC tagset.
At some point I then want to look for errors in the data entry, etc and so I need to search for various
values of those fields for validation purposes mainly.
I created a tagset using Jeffrey's plugin and it allows me to view and use only the info I'm after, but no searching.
Your plugin provides more complete functionality (tagset creation as well as the searchability). The only question
is how do I go about using your plugin to use the fields I'm using?
Cheers,
Bonny

Script to add content to IPTC core metadata fields

Is there the possibility that a script could be used to add data to IPTC standard fields?
Thanks.

They've confirmed the same thing i've found, that Save For Web actually preserves a chunk of the IPTC core data, but this isn't really any good for the quality of image I need to save.
It's strange how the XMP preserve option isn't available for a standard PNG save.

UCM Metadata modeling - Complex metadata field

Hi,
We are currently in the process of modeling our UCM for our enterprise webcenter application.
We have a requirement where a metadata field may have non-straigthforward values.
We have a table called worklocation_table with rows of data such as
Columns : | doc id | office | city | province | country
row 1 : | 1 | 12 Ave | NY | NY | USA
row 2 : | 1 | Buffalo | NY | NY | USA
row 3 : | 2 | Stn 2 | Edmonton | AB | Canada
We want a metadata field xWorklocationMetadata which associates a document with a one to many relationship with worklocaton_table.
So if we have a docMeta table in UCM
Columns : | dId | xWorklocationMetadata
row 1 : | 1 | 1
row 2 : | 2 | 2
But the problem will be with searching ? How will the search understand a foreign key relationship between docMeta and xWorkLocationMetadata ?
How should we approach our modeling ? Are they any features in UCM that will allow us to do that. Our main concern is
searching, metadata management and ease of development.
Thanks,
Sunil
Middleware Developer
Edited by: user9138987 on Nov 8, 2012 9:19 AM
Edited by: user9138987 on Nov 8, 2012 9:20 AM
Edited by: user9138987 on Nov 8, 2012 9:24 AM

How about changing your database scheme a bit?
a) one table (documents) with the primary key dId - in fact, dId is for revisions, not documents, but be it
b) the other table (worklocations) with its own primary key - No doc id there!!! (it is not a property of the worklocations, but of a document, or of a binding)
c) the third table (binding) which will contain many:many relationship between docs and locations (your data suggests that the relationship is rather many:many rather than one:many as doc_id 1 is in both 12 Ave and Buffalo; one:many would actually be even easier)
Now, the third table can be replaced by a custom metadata; one:many is a peanut - each doc is in just one location, so you can add the location as a metadata field. With many:many, it could be a bit trickier - OOTB you could go with Multiselect List, but if you have a lot of worklocations, the user experience might be too bad. Therefore, probably some customization (and why not keeping the binding in a separate table, then?) would be needed anyway.
Either way, check what schemes http://docs.oracle.com/cd/E23943_01/doc.1111/e10978/c04_metadata.htm#DAFEDBBA can do for you.

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

How to use ADD_METADEF to add a custom metadata field

Hi All,
I am trying to add a custom metadata field to check in profile, and this I want to do using RIDC library through my java program. I have tried the following code, but some how I could not see its getting added to Information Fields and also to Standard check in profile.
Can you let me know what am I missing?
            myIdcClient = myIdcClientManager.createClient("idc://XXXX:4444"); // just commented out
            IdcContext myIdcContext = new IdcContext("weblogic", "weblogic1");
            ServiceResponse myServiceResponse = null;
              DataBinder myRequestDataBinder = myIdcClient.createBinder();
                myRequestDataBinder.putLocal("IdcService", "UPDATE_OPTION_LIST");
                myRequestDataBinder.putLocal("dKey", "xLocationList123");
              myRequestDataBinder.putLocal("OptionListString", "Madrid\nTokyo\nLondon\nWashington");
                myServiceResponse = myIdcClient.sendRequest(myIdcContext, myRequestDataBinder);
                myRequestDataBinder = myIdcClient.createBinder();
                myRequestDataBinder.putLocal("IdcService", "ADD_METADEF");
                myRequestDataBinder.putLocal("dName", "xLocations123123");
                myRequestDataBinder.putLocal("dIsRequired", "0");
                myRequestDataBinder.putLocal("dOptionListKey", "xLocationList123");
                myRequestDataBinder.putLocal("dOptionListType", "choice");
                myRequestDataBinder.putLocal("dIsOptionList", "1");
                myRequestDataBinder.putLocal("dIsSearchable", "1");
                myRequestDataBinder.putLocal("dIsEnabled", "1");
                myRequestDataBinder.putLocal("dType", "Text");
                myRequestDataBinder.putLocal("FieldName", "xLocations123123");
                myRequestDataBinder.putLocal("dCaption", "Locations");
                myServiceResponse = myIdcClient.sendRequest(myIdcContext, myRequestDataBinder);
                myRequestDataBinder = myIdcClient.createBinder();
                //IdcService=UPDATE_META_TABLE
                myRequestDataBinder = myIdcClient.createBinder();
                myRequestDataBinder.putLocal("IdcService", "UPDATE_META_TABLE");
                myServiceResponse = myIdcClient.sendRequest(myIdcContext, myRequestDataBinder);
                myRequestDataBinder = myIdcClient.createBinder();
                myRequestDataBinder.putLocal("IdcService", "START_SEARCH_INDEX");
                myRequestDataBinder.putLocal("IsRebuild", "1");
                myServiceResponse = myIdcClient.sendRequest(myIdcContext, myRequestDataBinder);
                myRequestDataBinder = myIdcClient.createBinder();
                myRequestDataBinder.putLocal("IdcService", "PUBLISH_SCHEMA");
                myServiceResponse = myIdcClient.sendRequest(myIdcContext, myRequestDataBinder);
Thanks in advance.

Try calling the following code:
import static intradoc.shared.MetaFieldUtils.hasDocMetaDef;
import static intradoc.shared.MetaFieldUtils.updateMetaDataFromProps;
import intradoc.common.ServiceException;
import intradoc.data.DataBinder;
import intradoc.data.DataException;
import intradoc.data.Workspace;
    protected static void addMetadataFields(final Workspace workspace, final DataBinder binder) {
        traceVerbose("Start addMetadataFields");
        // Parameters for metadata field
        final String[] parameters = new String[] { "dsdComponentName", "dComponentName", "dsdVersion", "dType", "dIsRequired", "dIsEnabled", "dIsSearchable", "dIsOptionList", "dOptionListKey", "dOptionListType", "dDefaultValue", "dOrder", "dIsPlaceholderField", "dsdCheckFlag",
                "dsdDisableOnUninstall" };
        // Common values for primary and alternate field values
        final String[] values = new String[] { "ComponentName", ComponentName, "build_1_20131206", "BigText", "0", "1", "1", "0", "", "", "", "2500", "0", "", "" };
        // Primary file checksum field parameters and values
        final Properties field = new Properties();
        for (int i = 0; i < parameters.length; i++) {
            field.put(parameters[i], values[i]);
        // Setup primary file specific parameters
        field.put("dName", "Metadata field name");
        field.put("dCaption", "Metadata field caption");
        try {
            // Name of metadata field
            final String fieldName = field.getProperty("dName");
            trace("dName: " + fieldName);
            if (fieldName != null && fieldName.length() > 0 && !hasDocMetaDef(fieldName)) {
                try {
                    updateMetaDataFromProps(workspace, null, field, fieldName, true);
                    trace("Successfully added metadata field " + fieldName);
                } catch (final ServiceException e) {
                    warn("Metadata field " + fieldName + " was not installed.", e);
                } catch (final DataException e) {
                    warn("Metadata field " + fieldName + " was not installed.", e);
            } else {
                trace("Metadata field already exists; will not modify");
        } finally {
            traceVerbose("End addMetadataFields");
Jonathan
http://jonathanhult.com

Custom metadata fields?

I'm trying to find a way to create custom metadata fields so I can better organize my footage. For example, say I'm filming a bunch of old cars, and I want to sort them by make and model, obviously there's no make and model field by default. I've read articles that say this is possible, but I can't seem to find a way to do it. Thanks!
Edit: And related to that, is there a way to delete any of the metadata fields? Since I'm doing video, I'd rather not have to scroll through things like Album and Artist, etc. Thanks.

In the Metadata panel open the flyout menu in the upper right and choose "Metadata Display..."
Now you can turn off the metadata schemas you're not interested in seeing.
Now click the New Schema button.
Give your new Schema a name.
Now click the Add Property button next to your new custom schema.
Give it a name, like "Make", of type "Text".
Then do the same again for "Model".
Now you can select a set of clips all of the same make then enter what you'd like into the "Make" field and that metadata will be applied to the selected clips.
This is searchable, so in the Project panel you can search for the text you've entered into one of these fields and only clips containing that metadata will appear in the list (next to the search box Prelude reports "(filtered)" to let you know you're not currently seeing all of your clips.
I hope this helps!

Search the IPTC metadata field "Source" in Lightroom 5?

How is it possible to search for photos in Lightroom 5, where the IPTC field "Source" is empty? Is it possible to add additional metadata fields to the Library Filters?

The only way to search the IPTC Source field in LR is to use the "Searchable IPTC" criterion:
This searches all the "searchable" IPTC fields (Adobe doesn't specific exactly which fields those are, but they do include Source).
However, you want to find photos whose Source field is empty. LR doesn't have an "is empty" criterion for most fields, but the normal way you'd work around that, e.g. for Title, is to do:
Title Doesn't Contain a b c ... x y z 0 1 2 3 4 5 6 7 8 9
Unfortunately, that workaround won't work in your case, since
Searchable IPTC Doesn't Contain a b c ... x y z 0 1 2 3 4 5 6 7 8 9
would only return those photos all of whose IPTC fields are empty. If there was a photo with a non-empty IPTC Headline and an empty Source, this criterion wouldn't return the photo.
To search the Source field in particular, you'd need to use a third-party plugin, e.g. ExifMeta, Data Explorer, or Any Filter.

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

Custom metadata fields used in file name?

Hi,
Is it possible to add to the list of meta data fields that are used as tokens for file names?
I've been using Rob Cole's excellent custom meta data in the library module and now I want to use these fields to name the file during export...
While at it, is it possible to add the same custom meta data fields to the info view overlay in develop mode?
Cheers,
Bonny

1. Its possible an export filter (post-process action) could be defined that supports the custom metadata for export filenaming (Lightroom itself does not have any other hooks I'm aware of) - dunno if anyone's done that, yet.
2. I think not (see PM).
Rob

Managed Metadata Fields not showing up in preview mode

0down
votefavorite
In our SharePoint 2013 Publishing page, managed metadata fields doesn't show in preview, they show up only in edit mode or after we publish page.
Is this bug?
Thanks in advance.

Hi,
According to your post, my understanding is that the managed metadata fields not display in preview.
I tried to reproduce the issue, the managed metadata fields worked well in my environment.
I create a publishing page, add a library web part which contained managed metadata columns.
Then click the preview option in the ribbon, the managed metadata columns worked well.
Did the issue occur in other publishing pages? You can create a new publishing page to check whether it works.
Did you use the compatibility mode or add the site into trusted sites?
You can use compatibility mode to check whether it works.
Open IE->Tools->Compatibility View Settings
You can also add the site into Trusted sites.
Open the IE->Internet Options->Security->Sites->add the site into the Websites, then check whether it works.
What's more, you can use other browsers to check whether it works, such as Firefox, Chrome.
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

In adobe camera raw, what metadata field needs to be filled in so that if an image is uploaded to facebook by a customer, your copyright/info shows up?

In adobe camera raw, what metadata field needs to be filled in so that if an image is uploaded to facebook by a customer, your copyright/info shows up?

Facebook used to but now I believe it includes it. I also read that possible facebook adds metadata to images uploaded to albums but not wall posts. Regardless, what metadata field has to be filled in?

Select Button beside custom metadata field on Check In Form

Hi
In Oracle Content Server 10gR3, is there a way to add a "Select" button to User Alias Applet for a new Meta data field on New Check In Form? I tried creating a component but I don't see a select button being shown up. The button does shows up if it's a standard metadata fields but not for the custom one. Here is the component code. Any idea what I am doing wrong and how to fix it.
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>
CustomMetaData htmlIncludeOrString
</title>
</head>
<body>
<@dynamichtml std_meta_fields@>
<textarea name="xClbraAliasList" rows=3 cols=40 wrap=virtual></textarea>
<input type="button" value="Select..."
onClick="popupSelectAlias(document.Checkin);">
<script language="JavaScript">
     var aliasForm;
     function popupSelectAlias(frm)
          var selUser = document.selectAliasApplet;
          aliasForm = frm;
          selUser.createFrame();
     function setAliasString(val)
          if (val.length == 0)
               return;
          var str = aliasForm.xClbraAliasList.value;
          str.trim;
          if (str.length > 0)
               str += ",";
          str += val;
          aliasForm.xClbraAliasList.value=str;
     </script>
     <applet name="selectUserApplet"
    code=com.intranetsol.utilities.SelectUserApplet.class
      codebase="/idc/common/"
     archive=suapplet.zip
    id=selectUser
    width=0
    height=0
     MAYSCRIPT>
          <param name=CGI-URL value="/idc/idcplg">
          <param name=JsDisplaySeparator value=",">
          <param name=IsPaged value="1">
          <param name=IsUserList value="1">
          <param name=JsFunction value="setUserString">
</applet>
<applet name="selectAliasApplet"
    code=com.intranetsol.utilities.SelectUserApplet.class
      codebase="/idc/common/"
     archive=suapplet.zip
    id=selectAlias
    width=0
    height=0
     MAYSCRIPT>
          <param name=CGI-URL value="/idc/idcplg">
          <param name=JsDisplaySeparator value=",">
          <param name=IsPaged value="1">
          <param name=IsAliasList value="1">
          <param name=JsFunction value="setAliasString">
</applet>
<@end@>
</body></html>
Then I tried using the same code as above but instead used the built-in dDocType to show a "Select" button. This works but the button obviously shows besides dDocType but when I try for custom metadata as shown above it doesn't. Here is the sample code for dDocType:<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>
CustomMetaData3 htmlIncludeOrString
</title>
</head>
<body>
<@dynamichtml std_doc_page_definitions@>
<$include super.std_doc_page_definitions$>
<$include custom_modify_comments_definitions$>
<@end@>
<@dynamichtml custom_modify_comments_definitions@>
<$if isCheckin$>
<$xComments:isHidden = 1$>
<$xComments = "some preset and hidden comments"$>
<$elseif isUpdate$>
<$xComments:isInfoOnly = 1$>
<$endif$>
<@end@>
<@dynamichtml compute_std_field_includes@>
<$include super.compute_std_field_includes$>
<$if fieldName like "dDocType"$>
<$if isCheckin or isUpdate$>
<$fieldEntryInclude = "custom_doc_type_popup_field_entry"$>
<$endif$>
<$endif$>
<@end@>
<@dynamichtml custom_doc_type_popup_field_entry@>
<input type="text" name="dDocType" value="<$fieldValue$>">
<input type="button" value="Select..."
onClick="popupSelectAlias(document.Checkin);">
<script language="JavaScript">
     var aliasForm;
     function popupSelectAlias(frm)
          var selUser = document.selectAliasApplet;
          aliasForm = frm;
          selUser.createFrame();
     function setAliasString(val)
          if (val.length == 0)
               return;
          var str = aliasForm.xClbraAliasList.value;
          str.trim;
          if (str.length > 0)
               str += ",";
          str += val;
          aliasForm.xClbraAliasList.value=str;
     </script>
<applet name="selectAliasApplet"
code=com.intranetsol.utilities.SelectUserApplet.class
     codebase="/idc/common/"
     archive=suapplet.zip
id=selectAlias
width=0
height=0
     MAYSCRIPT>
          <param name=CGI-URL value="/idc/idcplg">
          <param name=JsDisplaySeparator value=",">
          <param name=IsPaged value="1">
          <param name=IsAliasList value="1">
          <param name=JsFunction value="setAliasString">
</applet>
<@end@>
</body>
</html>
Can someone please let me know what is in my above code that I am missing that is preventing the button not being shown in-front of the custom metadata field.
Any help would be greatly appreciated.
Thanks
Edited by: guest0012 on Aug 29, 2009 4:24 PM

Interesting!
You'll need a component. You already mentioned you had a custom metadata field. You will also need to add a counter to the counters table for your component. During a check in you will need to fetch the next value from the counters table, increment the counter and store the new number back in the table. The year portion of the id is easy, get the current year and grab the last two characters. Then, put this all togther to get the data for your metadata field.
The big question now is where in the check in process will you do all this? You will need something called filters probably. Maybe addFiles, maybe validateStandard, there are several that this could work with.
Check out the how-to-components:
http://www.oracle.com/technology/products/content-management/ucm/samples/index.html
-Jason
http://www.corecontentonly.com

Allow User to Create Metadata Fields

There should be a way to allow user to define their own metadata fields - Bridge is the most logical place to do this.
For example I'd like to add a field for color profile info:
1 a boolean field which indicates whether or not a CP is embeded,
1 text field for the name of the CP (This info should already be built into metadata - but until it is, I'd sure like a quick way to check)
--Take a look at Portfolio for an example of how this could be done.
thanks, xandr

yes yes.. I want to do this also??

Add "Softproof" as a searchable Metadata field or attribute

Similar Messages

Maybe you are looking for