Updating/sharing keywords and metadata in Lightroom 4

I will be using an intern to help add keywords & metadata to an extremely large group of photos in Lightroom 4.
The intern will have their own workstation so we'll be passing files back and forth.
I need to add their work to mine, keeping all of the keyword/metadata work tied to the virtual photos which already have some work done to them (some keywords, metatdata and photo enhancements already in place on some photos).
step-by-step appreciated
What is the best way to do this?
I'm still learning LR myself.
suggestions welcomed!
thank you

Lightroom is not a multi-user application, and so you can, via tedious manipulation of files, achieve the result you want, but I should also note that make one mistake, and you potentially have a real mess on your hands.
The best solution (in my opinion) is to put the catalog file and all photos on a server that you can both access. The drawback to doing this is that only one person can be working with a specific Lightroom catalog at a time. And given my usual advice to use only one catalog, this may not meet your needs.
If that's not a good solution, then the intern can create her own temporary catalog of the portion of the photos to be worked on today, add keywords and other metadata, and then pass the catalog file to you to merge with your main catalog using the command File->Import from another catalog.
As another alternative, if the only task the intern will carry out is adding keywords and other metadata, there are many freeware solutions that your intern can use for this, and then when she is done in a particular folder, you can in Lightroom select all the photos in that folder, and then read the metadata from the photo files. For Windows, two such freeware programs are GeoSetter and ExifToolGUI.

Similar Messages

  • How do I import Bridge keywords and metadata to CS6 from CS4 so that I don't lose them if CS4 is not

    I have hundreds of keywords and metadata including Ratings and Labels using CS4 and Bridge CS4.
    It is time to replace my PPC Mac with a new Intel Mac.
    I am going to install CS6 on the new Intel Mac without installing CS4.
    By default.... this eliminates ALL keywords and ratings and labels from my Bridge browser. The keywords will still be present on the files but Not present in Bridge keywords list and all ratings and labels will be lost.
    Making a copy of Bridge CS4 metadata to another computer is quite simple.
    Simply copy All of the Bridge CS4 application support folder to the other computer.
    The question then becomes.... can I aslo do this with CS6 without introducing an incompatibility?
    1. incompatible due to CS6 application support.
    2. incompatible due to transfer from a PPC (APM) to Intel (GUID).
    This concern results from an Bridge CS4 export problem I experienced.
    Bridge CS4 will export all of your keywords and you can import them from a text file but it has some odd troubles. (try it and you will see)
    This does Not mean that CS6 has the same troubles.
    What do I require to preserve existing metedata and keywords that exist on a PPC using CS4 and import them into CS6 using Intel?
    Sound simple?
    I doubt it.
    The points are.
    1. CS4 not installed.
    2. CS4 source is PPC not Intel.
    3. Ratings and Labels are metadata that Are Not part of the file metadata and unique to Bridge only.
    4. Keyword Search and keyword Use requires that Bridge have keyword list, otherwise Finder is the far more useful browser and the new version of Bridge will require hours of keyword listing.
    I don't want to spends hours retyping keywords lists in Bridge.

    Ratings are NOT placed into the file under CS4 Bridge and neither are
    Labels.
    That depends on your file type and settings voor Camera Raw.
    Like Curt stated usually metadata is written in to the file itself. Only Raw files can't be written to and by default they create a XMP file, also called Sidecar XMP files (and do have the same filename, only a different extension called .xmp). These files are also by default hidden in Bridge but If you use Bridge to move files they travel along with the original.
    If you move or copy them using finder you have to be sure these XMP files are also copied with the originals to the new location.
    Using the menu View / show hidden files should reveal the XMP files.
    An other option for the Camera Raw prefs is to set metadata to the Camera Raw database instead of written to sidecar XMP files ( to my knowledge using sidecar files has been the default since about CS3).
    Now here it becomes a bit tricky and I only can tell you my findings, not to be confused with true facts. (and mind you, it is at least 5 years ago I was on a PPC and not even remember which OSX 10 was able to work on it, I just present the acting of CS6 on an intel Mac Pro with OSX 10.7, but I don't believe the difference in location is that much)
    Having written the Metadata to the Camera Raw Database your image settings get written to a file in the user library preferences folder called logically "Adobe Camera Raw Database". But also some info gets added to the Camera Raw Cache folder (User library / Caches/ Adobe Camera Raw) in a file called index.dat.
    Also not having set metadata to xmp sidecars stores the ACR settings in a new .dat file with a unique number (not to be traced as a corresponding filename. And also the default maximum is set to 1 GB of space and when full the oldest files are overwritten with the new ones.
    Personally I use converted DNG files that are capable of writing metadata to so all info and settings are in the file itself and I don't need to bother about central storage that can get lost. The downside is that changes to a DNG need to save the whole file instead of a small xmp file and probably reading cache takes more time then getting info from central storage but I like to be on the safe side and speed is not really needed to be nailed down to split seconds in my workflow.
    Keywords are stored as a file in the Bridge preferences but Like Curt already stated exporting the old list first and then via the same route import again to CS6 should solve your problem and they will be back as persistent, otherwise the files in the content window show as italic and sadly enough have to be made persistent one by one with right click mouse menu, so that is not really an option for you.
    Exporting the list does create a text file that can also be altered manually with a simple text app and as said, again be imported in newer versions as Curt described earlier.
    Making a copy of Bridge CS4 metadata to another computer is quite simple.
    Simply copy All of the Bridge CS4 application support folder to the other computer.
    Well, in fact it is true to call copying this folders a simple task but replacing the existing new CS6 would not be my method. The biggest change for Bridge CS6 was the transition to 64 bit and I lack the knowledge for this but also cache format for thumbs and previews has been different for every version.
    But if you have located the CS4 folder for Bridge in your PPC user library / application support / Adobe / Bridge CS4 you should find a file called 'Adobe Bridge Keywords.xml' and it is fairly safe to replace this CS4 version with the new CS6 version.
    Also custom settings for the output module can be copied (however to my memory the option for custom settings in Output where introduced in CS5) and collections can be copied.
    So for your keywords the copy option might work, rating and labeling for Raw files they will be read in CS6 if they are stored as XMP. ACR settings idem but CS6 ACR has a new (2012) conversion mode that has different settings that do not work with previous settings (unless you first choose to use the 2010 conversion as default Raw setting.
    If it is in the Central Data Base I would start trying to replace the CS4 with the CS6 edition (after back up of existing CS6 version) and see what happens. If it works your out of trouble.
    You can also open the Camera raw Database as a text file but there is a lot of data in. Maybe scripting would be able to reveal those data and transfer to XMP but you have to visit the dedicated Scripting forum for this.
    And while you state to have not installed CS4 anymore it might be wise to reinstall it (but first make a proper back up of the previous mentioned folders and files to be on the save side.
    This gives you the opportunity to export keywords properly and if needed you can use Show Items from subfolders option with filter and set preferences to XMP sidecar to refresh the rating and labels to those XMP files. Just an escape route that might not be as painstakingly as it looks at first sight, just use the options for Bridge to filter.

  • What's the difference and purpose of Keywording and metadata such as title and caption etc?

    What's the difference and purpose of Keywording and metadata such as title and caption, crator, sublocation , label etc?  Where & how is the information used?  Where does it appear?

    Keywording is primarily for your own use for finding photos fast.
    Title, Caption, etc are also for your own use but can be used by your clients or your stock company if you do not <Minimize Embedded Metadata> on export. Keywords are also included on export but are hardly of any use to others - unless you follow a standard for keywording.
    You have the option of selecting title, caption, etc to appear in a Slide Show, on Print, or on a webpage created with LR.
    If you go to the LR Help menu and type "title", or "caption" in the search box you will find plenty of advice for this.
    WW

  • [svn:cairngorm3:] 21115: updating the md5 and metadata and swc release ( just in case, we missed anything in our last commit)

    Revision: 21115
    Revision: 21115
    Author:   [email protected]
    Date:     2011-04-21 09:13:29 -0700 (Thu, 21 Apr 2011)
    Log Message:
    updating the md5 and metadata and swc release (just in case, we missed anything in our last commit)
    Modified Paths:
        cairngorm3/maven-repository/com/adobe/cairngorm/cairngorm3/3.0.18/cairngorm3-3.0.18.pom
        cairngorm3/maven-repository/com/adobe/cairngorm/cairngorm3/3.0.18/cairngorm3-3.0.18.pom.m d5
        cairngorm3/maven-repository/com/adobe/cairngorm/cairngorm3/3.0.18/cairngorm3-3.0.18.pom.s ha1
        cairngorm3/maven-repository/com/adobe/cairngorm/cairngorm3/maven-metadata.xml
        cairngorm3/maven-repository/com/adobe/cairngorm/cairngorm3/maven-metadata.xml.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/cairngorm3/maven-metadata.xml.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/contract/1.4/contract-1.4.swc
        cairngorm3/maven-repository/com/adobe/cairngorm/contract/1.4/contract-1.4.swc.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/contract/1.4/contract-1.4.swc.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/contract/maven-metadata.xml
        cairngorm3/maven-repository/com/adobe/cairngorm/contract/maven-metadata.xml.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/contract/maven-metadata.xml.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/integration/0.16/integration-0.16.swc
        cairngorm3/maven-repository/com/adobe/cairngorm/integration/0.16/integration-0.16.swc.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/integration/0.16/integration-0.16.swc.sha 1
        cairngorm3/maven-repository/com/adobe/cairngorm/integration/maven-metadata.xml
        cairngorm3/maven-repository/com/adobe/cairngorm/integration/maven-metadata.xml.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/integration/maven-metadata.xml.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/integrationParsley/0.16/integrationParsle y-0.16.swc
        cairngorm3/maven-repository/com/adobe/cairngorm/integrationParsley/0.16/integrationParsle y-0.16.swc.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/integrationParsley/0.16/integrationParsle y-0.16.swc.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/integrationParsley/maven-metadata.xml
        cairngorm3/maven-repository/com/adobe/cairngorm/integrationParsley/maven-metadata.xml.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/integrationParsley/maven-metadata.xml.sha 1
        cairngorm3/maven-repository/com/adobe/cairngorm/libraries/maven-metadata.xml
        cairngorm3/maven-repository/com/adobe/cairngorm/libraries/maven-metadata.xml.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/libraries/maven-metadata.xml.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/module/0.15/module-0.15.swc
        cairngorm3/maven-repository/com/adobe/cairngorm/module/0.15/module-0.15.swc.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/module/0.15/module-0.15.swc.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/module/maven-metadata.xml
        cairngorm3/maven-repository/com/adobe/cairngorm/module/maven-metadata.xml.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/module/maven-metadata.xml.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/navigation/1.4/navigation-1.4.swc
        cairngorm3/maven-repository/com/adobe/cairngorm/navigation/1.4/navigation-1.4.swc.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/navigation/1.4/navigation-1.4.swc.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/navigation/maven-metadata.xml
        cairngorm3/maven-repository/com/adobe/cairngorm/navigation/maven-metadata.xml.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/navigation/maven-metadata.xml.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/navigationParsley/1.4/navigationParsley-1 .4.swc
        cairngorm3/maven-repository/com/adobe/cairngorm/navigationParsley/1.4/navigationParsley-1 .4.swc.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/navigationParsley/1.4/navigationParsley-1 .4.swc.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/navigationParsley/maven-metadata.xml
        cairngorm3/maven-repository/com/adobe/cairngorm/navigationParsley/maven-metadata.xml.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/navigationParsley/maven-metadata.xml.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/navigationSpringAS/1.4/navigationSpringAS -1.4.swc
        cairngorm3/maven-repository/com/adobe/cairngorm/navigationSpringAS/1.4/navigationSpringAS -1.4.swc.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/navigationSpringAS/1.4/navigationSpringAS -1.4.swc.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/navigationSpringAS/maven-metadata.xml
        cairngorm3/maven-repository/com/adobe/cairngorm/navigationSpringAS/maven-metadata.xml.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/navigationSpringAS/maven-metadata.xml.sha 1
        cairngorm3/maven-repository/com/adobe/cairngorm/navigationSwiz/1.4/navigationSwiz-1.4.swc
        cairngorm3/maven-repository/com/adobe/cairngorm/navigationSwiz/1.4/navigationSwiz-1.4.swc .md5
        cairngorm3/maven-repository/com/adobe/cairngorm/navigationSwiz/1.4/navigationSwiz-1.4.swc .sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/navigationSwiz/maven-metadata.xml
        cairngorm3/maven-repository/com/adobe/cairngorm/navigationSwiz/maven-metadata.xml.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/navigationSwiz/maven-metadata.xml.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/observer/1.14/observer-1.14.swc
        cairngorm3/maven-repository/com/adobe/cairngorm/observer/1.14/observer-1.14.swc.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/observer/1.14/observer-1.14.swc.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/observer/maven-metadata.xml
        cairngorm3/maven-repository/com/adobe/cairngorm/observer/maven-metadata.xml.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/observer/maven-metadata.xml.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/observerParsley/1.14/observerParsley-1.14 .swc
        cairngorm3/maven-repository/com/adobe/cairngorm/observerParsley/1.14/observerParsley-1.14 .swc.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/observerParsley/1.14/observerParsley-1.14 .swc.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/observerParsley/maven-metadata.xml
        cairngorm3/maven-repository/com/adobe/cairngorm/observerParsley/maven-metadata.xml.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/observerParsley/maven-metadata.xml.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/popup/1.13/popup-1.13.swc
        cairngorm3/maven-repository/com/adobe/cairngorm/popup/1.13/popup-1.13.swc.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/popup/1.13/popup-1.13.swc.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/popup/maven-metadata.xml
        cairngorm3/maven-repository/com/adobe/cairngorm/popup/maven-metadata.xml.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/popup/maven-metadata.xml.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/popupParsley/1.13/popupParsley-1.13.swc
        cairngorm3/maven-repository/com/adobe/cairngorm/popupParsley/1.13/popupParsley-1.13.swc.m d5
        cairngorm3/maven-repository/com/adobe/cairngorm/popupParsley/1.13/popupParsley-1.13.swc.s ha1
        cairngorm3/maven-repository/com/adobe/cairngorm/popupParsley/maven-metadata.xml
        cairngorm3/maven-repository/com/adobe/cairngorm/popupParsley/maven-metadata.xml.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/popupParsley/maven-metadata.xml.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/task/1.10/task-1.10.swc
        cairngorm3/maven-repository/com/adobe/cairngorm/task/1.10/task-1.10.swc.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/task/1.10/task-1.10.swc.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/task/maven-metadata.xml
        cairngorm3/maven-repository/com/adobe/cairngorm/task/maven-metadata.xml.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/task/maven-metadata.xml.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/validation/1.13/validation-1.13.swc
        cairngorm3/maven-repository/com/adobe/cairngorm/validation/1.13/validation-1.13.swc.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/validation/1.13/validation-1.13.swc.sha1
        cairngorm3/maven-repository/com/adobe/cairngorm/validation/maven-metadata.xml
        cairngorm3/maven-repository/com/adobe/cairngorm/validation/maven-metadata.xml.md5
        cairngorm3/maven-repository/com/adobe/cairngorm/validation/maven-metadata.xml.sha1

    word!
    second that.
    This is really hard to follow, even for us who keep an eye on every update and read every single post and have an imagination of update problems out there.
    You tried to make digitalpublishing.acrobat.com (the "dashboard") the one-stop place for downloading and updating all necessary tools. good idea to make this the central point, because adobe.com download sections is a pain in the arse when trying to find updates for secondary tools like the DPS.
    also, make it super-duper clear what version is the current and what versio are currently available. I already wrote about lining up version numbers months ago and you seem to get this working — but it is still a mess. 1.7 vs 1.1.7 vs. 2.0 vs. drop17 vs. 11.4.2.201111104_m_670635 7.5.5.16 (you can imagine where I took the latter from)
    Peter: The bold line in the sticky forum message was added later, as I recall.
    —Johannes

  • Keyword and metadata for non-image files.

    Hi, everyone.
    As I have started to use Bridge to browse files in my system including those that are not image files I tried to find information on how Bridge handles the assignment of keywords and metadata to these files but couldn't find anything on Adobe's site.
    Considering non-image files such as PDF's, MS Office (Word, Excel), Text, HTML, and others, how does Bridge handles the assignment of metadata and keywords ? Where are they stored ? Embedded in the files themselves or in a sidecar file similar to what happens to RAW image files ?
    I've read some posts from other users about problems with this. Some report that they are able to assign keywords but these aren't maintained once the file is re-saved.
    Is there a manual on Adobe's site that covers the handling of keywords and metadata in Bridge ?
    TIA,
    Joe

    Joe,
    Being a digital archivist dealing primarily with pages digitized from the turn of the 20th Century for a religious sect I am highly involved in the usage of keywords.  Each page of a work, be it either a volume of a newspaper or a book, contains keywords.  I do not use side-car files but instead incorporate my keywords directly into the resultant TIF file.
    So I used your posting to see what the answer was.  To that end I am presently working on a 1922 title, Thirty-One Years of Organized Work in Oklahoma, Texas, New Mexico and Louisiana by Church of the Brethren from 1891 to 1922, that will consist of slightly over 500 pages.  To test your question I placed the title of the work as a keyword.  I then used Bridge's find ability.  It did not work.
    I forgot that Bridge converts all commas into semi-colons.  And changing the colons into semi-colons still returned no results.  An examination of the keywords tab showed the string broken down in to sections.  Searching for the longest string showed the problem.  Returning to my keyowrd string I removed all instances of the semi-colons and re-searched.  This resulted in a properyl found file.
    So.  The longest string I have tested to date is 120 characters, the title of the work minus the commas.  I suspect that Curt is correct in his assumption that it is limited by the operation system.  I tested this theory by incorporating a double string (without the commas) of my book's title.  This was 241 characters including the space between the duplicated title.  The search was successful.  A triple set of the title returned no hits.
    Wayne Webb

  • Can you apply keywords and metadata for only some subfolders at import?

    I thought I should make a separate thread for my second LR file import question.
    It seems that LR authors assumed that most users would download single events or projects but that isn't the case with me.  I'm just an amateur with a Canon 30D and a 4 gb CF card.  I can get hundreds of raw files on that card and many times I won't download the contents of the card to my computer until I have taken pictures at several different events.  So I may have a birthday and a campout and some landscapes in the download and the same keywords or metadata may not apply to all of them.  LR allows me to group these different events by date in different subfolders but it looks like the metadata/keywords that you can add at download apply not to individual subfolders but to the entire download, is that right?  If I've misunderstood or overlooked something how do you apply different keywords or metadata to different subfolders at download?

    As you have discovered, Lightroom applies the same keywords, metadata and any develop settings to every photo during import. The workaround to break the import down into individual events by only selecting one shoot at a time in Import dialog thumbnail window. Deselect ALL of the thumbnails then use the keyboard modifiers such as Opton/Alt, Cmd/Ctrl or Shift to select the particular shoot that you want to import.

  • Script to Export and Import Keywords and Metadata

    I have a requirement to mass upload and download keywords and various metadata fields (i.e. File Name, Date Created, City, Country, Document, Title, etc.) into an external database from the Adobe Bridge. Ideally it would be compatible to .txt, .csv, etc type of database format. Currently I have to accomplish this task one at a time. I have an immediate need to upload 1000 plus pictures and various text fields into my website to share with others and be able to sell my pictures online.
    My immediate is for exporting the metadata and keywords.
    Does anyone know of a script that is aavailable?
    Arnold

    John,
    Thanks for your quick response. Below is the script I just modified this morning. When looking in the keyword field, it returns the word "undefined" for all records.
    I tried that yesterday and it didn't work. When looking at the Advance file info on Adobe Bridge I see the below format which had 2 levels. All the others I used only had one. Since I am not a programmer, I need help on that part of the script.
    ==========================
    EXIF Properties (exif,http://ns.adobe.com/exif/1.0/)
    - exif:Flash
    - exif:Fired: True
    ====================================
    Any luck on determining how to obtain file size.
    Again thank you so much for supporting me on my project,
    Arnold
    =====================
    #target bridge
    if (BridgeTalk.appName == "bridge")
    // Let's create our menu
    var menu = MenuElement.create( "command", "Export CSV File", "at the end of Tools");
    menu.onSelect = function(m) {
    try
    // Let's ask what the name of the output file
    var f = File.saveDialog("Export file list to:", "Comma delimited file:*.CSV");
    // Write the column headings
    f.open("w");
    f.writeln("Seq Number,New File Name,New File Name Path,Original File Name,Org Dt & Tm,ISO,Exposure Time,F Stop,EV,Exposure Program,Meter Mode,Focal Length,Flash,Lens,Author, Author's Position,City,Country,Description,Title,Orientation,Width,Height,Rating,Label");
    // Let's get a list of all the visible thumbnails
    var items = app.document.visibleThumbnails;
    for (var i = 0; i < items.length; ++i) { var item = items[i]; f.writeln(i + 1, ",\"", item.name, "\",\"", item.path.replace(/\"/g, "\"\""), "\",\"", ListMetadata(item), "\",\"", "\"" ); } f.close(); } catch(e) { } } menu.onDisplay = function(m) { m.enabled = app.document.contentPaneMode == "filesystem" && app.document.visibleThumbnails.length > 0;
    function ListMetadata(tn)
    md = tn.metadata;
    md.namespace = "http://ns.adobe.com/photoshop/1.0/";
    varAuthor = md.Author + "\",\"" + md.AuthorsPosition + "\",\"" + md.City + "\",\"" + md.Country + "\",\"";
    md.namespace = "http://ns.adobe.com/exif/1.0/aux/";
    varLens = md.Lens + "\",\"" ;
    md.namespace = "http://purl.org/dc/elements/1.1/";
    vartitle = md.title + "\",\"" + md.description + "\",\"" ;
    md.namespace = "http://ns.adobe.com/xap/1.0/mm/"
    VarPreservedFileName = md.PreservedFileName + "\",\"" ;
    md.namespace = "http://ns.adobe.com/exif/1.0/"
    VarDateTimeOriginal = md.DateTimeOriginal + "\",\"" + md.ISOSpeedRatings + "\",\"" + md.ExposureTime + "\",\"" + md.FNumber + "\",\"" + md.ExposureBiasValue + "\",\"" + md.ExposureProgram + "\",\"" + md.MeteringMode + "\",\"" + md.FocalLengthIn35mmFilm + "\",\"" + md.Flash + "\",\"" ;
    md.namespace = "http://ns.adobe.com/tiff/1.0/"
    varOrientation = md.Orientation + "\",\"" + md.ImageWidth + "\",\"" + md.ImageLength + "\",\"" ;
    md.namespace = "http://ns.adobe.com/xap/1.0/"
    varRating = md.Rating + "\",\"" + md.Label ;
    md.namespace = "http://ns.adobe.com/photoshop/1.0/";
    varKeywords = ListKeywords(md) + "\",\"" ;
    function ListKeywords(md)
    var varKeywords = "" ;
    for (var i = 0; i < md.Keywords.length; ++i) { varKeywords = varKeywords + md.Keywords[i] + ", "; } //strip off final comma and space varKeywords = varKeywords.substring( 0, varKeywords.length-2);
    return VarPreservedFileName + VarDateTimeOriginal + varLens + varAuthor + vartitle + varOrientation + varRating + varKeywords;
    ==============================

  • Can Aperture import keywords and ratings from Lightroom?

    Decided to download the Aperture trial, and imported 17,000 images without a problem until I realised that my keywords and star ratings are missing (and even some vertical shots are horizontal).
    Is there a way to get Aperture to look at the sidecar files generated by Lightroom? Without that I'm unlikely to use Aperture for anything other than books that iPhoto can't do.
    Thanks,
    Nigel

    Unfortunately, no.
    It might be possible by use of AppleScript (the script would need to parse the XML files and put this data into Aperture), but this would not be trivial to write and to the best of my knowledge nobody has done it.
    It's a shame, as Aperture can export XMP sidecar files so LR will pick up Aperture ratings and keywords (but not adjustments) just fine.

  • Photoshop CC 2014 crashes when cropping - since today's update via CC and installation of Lightroom CC

    Running Windows 8.1
    No issues up until the latest update of PS CC 2014, Bridge and Lightroom (from LR 5 to LR CC / 6) - installed this morning.
    Now when cropping an image PS crashes.
    Faulting application name: Photoshop.exe, version: 15.2.2.310, time stamp: 0x5480338c
    Faulting module name: MSVCR110.dll, version: 11.0.51106.1, time stamp: 0x5098826e
    Exception code: 0xc0000005
    Fault offset: 0x000000000003c5f0
    Faulting process ID: 0x360c
    Faulting application start time: 0x01d07cdb67ff87b2
    Faulting application path: C:\Program Files\Adobe\Adobe Photoshop CC 2014\Photoshop.exe
    Faulting module path: C:\Windows\SYSTEM32\MSVCR110.dll
    Report ID: e8dffa73-e8cf-11e4-8286-14dae929bf86
    Faulting package full name:
    Faulting package-relative application ID:

    Photoshop itself hasn't had an update since December.
    But crashes in MSVCR usually come from bugs in third party plugins or drivers.

  • Metadata, keywords and collections

    This may be a dumb question but I would like to be sure.
    Is everything that I type in the metadata trough bridge and all the keywords that I assign to a file staying with that file/photo/video/photoshop etc.
    So if I give that file to someone else, he opens it in bridge, he can also find it using that keyword...
    Can these keywords and metadata be used by other management software?
    Is it possible to share collections over LAN or internet? If we have a a lot of organized assets in one computer, everyone is using that and if one user make a collection on his computer, others can see that collection in their bridge.
    Thanks for help

    Boy a lot of questions!
    Is everything that I type in the metadata trough bridge and all the keywords that I assign to a file staying with that file/photo/video/photoshop etc.
    Keyword file is in user/app data/roaming/adobe/keywords
    Can these keywords and metadata be used by other management software?
    Keywords, and some metatdata, but not all, are imbedded on the file.  So other software,such as Windows Explorer, can read them, even if you send the photo to someone else.
    Is it possible to share collections over LAN or internet? If we have a a lot of organized assets in one computer, everyone is using that and if one user make a collection on his computer, others can see that collection in their bridge.
    Collections are like a spreadsheet with the addresses of the photos on your computer.  So they can not be shared by sending a collection to another.  When you get into a networked situation you have lost me as I don't use them.  If the other person can access the others' computer and look through thier files I guess they could.
    Hope this helps.

  • LR2 Question syncing keywords and/or Metadata.

    I am shooting RAW and import the files into my catalog as DNG.
    After adding keywords and changing metadata to all the DNG files I would like to apply those changes back to my original RAW files.
    Can I do that easily? Maybe adding XMP files to the same directories as the original RAW files?
    Once I have the RAW files tagged with the same keywords and metadata I plan to archive them and delete from my disk.
    Thank you,

    For your first question - You can select the folder containing the files then use the Save Metadata command from Folder panel context menu (see attached screen shot). Alternatively, you can select the actual files then use Save Metadata to file command (Ctrl/Cmd+S). This latter method is much slower.
    For you second question - not using your current workflow. That said, if you changed your workflow slightly it's possible. To do it you ned to import your raw files without converting to DNG. Next, you apply keywords, metadata, etc. then use method described above for saving back to file (this creates the XMP sidecars). Now select all of the images in Grid view and convert the raw files to DNG (Convert to DNG from Library menu).
    The final step would be to archive the raws plus XMP sidecars, this will need to be done outside of Lightroom.

  • Bridge CS6- Thumbnails gone and metadata too!

    Hi everyone.
    I am in panic mode.
    I am running Bridge CS6 (5.0.2.4) And PS CS6. I recently updated something Can't remember if it was DNG and/or Camera Raw.
    My problem started today when i went to view a folder of DNG images in Bridge. Initially the thumbnails of the images showed up, but then one by one, the thumbnails turned into the Adobe DNG icon. This is happening with tiff files too.
    I went to Tools>Cache>Purge Cahe for Folder... That did not help. I simply can not re-generate the thumbnails.
    I've also noticed that when I click on almost any image, my metadata does not show up in the Meta Data Panel in Bridge.
    Another odd thing is all my images are keyworded. I used to be able to click on an image, and see in the Keyword Panel the keywords I chose for that image. That is no longer the case, however when I open that image in Photoshop CS6 and get file info, I see that my keywords and Metadata is there!
    And the very last weird thing: If I go to the Bridge menu>Camera raw preferences, nothing happens. I used to be able to set my TIFF and JPEG handling options there.
    This happened as I was finishing archiving about 20,000 images so you'll understand that I am a little bit more than upset....
    Your help would be most appreciated.
    Jonathan

    After reading a few things online I decided to try re-installing the DNG/CR Update 8.4.0. That did not help.
    I then decided to delete the ACR cache files, the Adobe Bridge 256, 1024, and Full cache folders, since there were tens of thousands of them.
    I realize that Bridge might have to rebuild and it would take a while, but was wondering if something got corrupted there.
    (I hope this wasn't a mistake).
    I relaunched bridge, and as expected, none of my images have thumbnails, but I also see no way to re-generate those!
    BTW- All this has happened with my back-up of this archive on a seperate HD.
    I am unable to get the CR preference window to show in Bridge but I am able to acces the prefs from within PS CS6!
    Going crazy!

  • CS3 - Keywords and Description Error

    I have tried to update our Keywords, and get the following error:
    If I click OK twice, it goes away, and I am able to type new keywords in.  However after entering new keywords and clicking OK on that screen, I get another error: "You cannot perform this action in this region of the page" and any new words I entered are cleared.
    Can anyone help me? What I am doing wrong?

    I just had this happen for the first time too, wondering the same thing you are Aust.

  • Exporting photos and metadat from iPhoto '09 to Lightroom 3

    After several years managing 110K+ photos and movies in iPhoto, I am reluctantly considering moving to Adobe Lightroom. I paid $200 for Aperture, but the most recent releases of both Aperture and iPhoto are so buggy that I'm not upgrading. I was very sad to reach this conclusion.
    I am seriously considering moving to Adobe Lightroom for its power, stability, and availability on much cheaper PC hardware. Does anyone know of a way to export everything I've done in iPhoto (including hundreds of hours of tagging and photo editing) to Lightroom? I've spent a couple of hours reading forums and haven't seen anything (instructions or app) that will do the job.
    I really wish Apple had nailed Aperture since I'm now needing it's photo editing power together with iPhoto's excellent organization capabilities. This was the promise of Aperture 3. Now I just feel dumb for spending the $200 (since the app is both buggy and available for $80 in the app store).
    I would deeply appreciate any advice on the transition to Lightroom 3 from iPhoto '09... and I will always be an Apple fan.

    Terence,
    You rock for posting such a quick reply so late at night. Thank you!
    I forgot about those checkboxes. Excellent point. Thanks for the description heads up. I'm fine losing the faces info (esp. since LR3 doesn't offer it as you said). It's the keywords and titles that I've spent 100's of hours on
    Have you tried importing to LR with exported metadata? Did it work end to end for you? I'll check out iPhoto to Disk in depth.
    I would like to keep my originals and the modified versions. Do you know of any way to avoid doubling the item count in my library to nearly a quarter of a million? I am hoping to avoid having an original and modified version of each file. I actually suffered that once through an iPhoto issue a couple of years ago and hope not to repeat.
    To add more context to my Aperture and iPhoto '11 comments, the iPhoto '11 comments are purely a reflection of what I've read in hours of forum reading and not my direct experience. On Aperture, my experiences are actually limited -- focusing solely on importing a huge iPhoto library to Aperture. I spent tens of hours over several weeks trying to migrate and simply failed. The memory leaks got me time and again, no matter how I reconfigured the import (for example by splitting 110K photos into approx 50 individual imports). I should've called out that once (partially) imported, everything seemed to be faster and smoother in Aperture than in iPhoto. Thanks for the call out.
    Guy

  • Sharing keywords between LR and PSE 9 Organiser? :-(

    OK, I've owned 3 photo products from Adobe (Photoshop Album, Lightroom and Photoshop Essentials) and have 3 keyword file formats! I use LR as my main photo organiser and have started using PSE and its Organiser but am frustrated by the lack of coherent design of keyword files. I have hundreds of keywords in LR. I had to write some Python code to convert my "Album" keywords to the LR format and it seems I have to do the same to get keywords from LR into PSE's organiser. But there's now a new problem...
    Unfortunately when I import keywords into PSE's Organiser any duplication of existing keywords results in duplication in the keyword list - i.e. when I add "From file.." PSE adds to the list rather than merging! PSE is clearly not designed to re-load keywords from file any extend the keywords. If I export all my keywords and re-import them I don't expect the number of keywords to double! Oh - I can;t delete keywords before importing because I'm told everything it's 'learned' (people etc. will be lost).  Keywords appear to be exportable but not importable.
    I clearly cannot import keywords into PSE's organiser as I can with LR.
    Is anyone sharing keywords between LR and PSE's Organiser?

    Thanks, I can see how that can work and the problems. It looks like the keywords themselves cannot be easily shared and I agree that having two organising programs is problematic but I wanted to 'export' the keywords I have created including their structure from Lightroom and import them into PSE organiser. You'd think you could do this with two similar products from the same company. The organisers in question are used for two purposes and the photos in each are different - i.e. I use lightroom for my pro stuff and PSE for family/casual stuff and no photo would be present in both. It looks like PSE really isn't designed to import keywords. I have Python code to create a PSE keyword file from a lightroom file so that will have to do as it's clear there's no interoperability.
    Thanks for your suggestions.

Maybe you are looking for