Keywords, Include on Export, Save Metadata to File, and SmugMug???

My workflow and issue (LR 5.7 and SmugMug plugin 2.1.10):
1) I import RAW files as DNGs
2) I do various Lightroom stuff, plus add Keywords. Some of the keywords do not have "Include on Export" checked. Some of my keywords are part of hierarchies that have "Export Containing Keywords" checked. And some of keywords have synonyms.
3) Once I am all done with a file, I select "Save Metadata to File"
4) Then I publish to SmugMug using the SmugMug publish service.
5) The SmugMug website shows keywords which I did not intend to be included on export, it does not show the complete hierarchy for those keywords that should, and none of my synonyms show. I noticed this is the same way the keywords were saved to the DNG when I view the file in Bridge.
6) When I export the file to a file on my desktop and check the metadata with Bridge, the Keywords all export correctly.
All of this behavior makes sense, I guess, but I cannot figure out what to do about it. Should I not bother to "Save Metadata to File", this seems to be what is messing up the SmugMug publish service? Is the SmugMug publish service behaving correctly? I would have expected it to behave like an export which would write synonyms, exclude keywords that should be excluded, etc, which seems to work ok in point 6 above. Are the publish services more effort than they are worth? So I get SmugMug to work, what happens when I try Flickr? I hate to stop "Save(ing) Metadata to File(s)", since that seems like a nice hedge against db corruption and the next time I decide to try a whole different image database.
Any advice on this issue would be greatly appreciated.

Perhaps someone with direct experience with publishing to Smugmug will chime in.  Short of that, some thoughts on your issues:
Should I not bother to "Save Metadata to File", this seems to be what is messing up the SmugMug publish service?
I very much doubt that it is messing up the publishing.  What gets saved to the file from the catalog is independent of what gets exported.  Saving metadata to the file is generally a good practice (in case you screw up your catalog backups).  Many, perhaps most, users set the preference Catalog Settings > Automatically Write Changes Into XMP.
I would have expected it to behave like an export which would write synonyms, exclude keywords that should be excluded, etc, which seems to work ok in point 6 above.
Yes, that's a reasonable expectation.
You may have done this already, but double-check: Right-click the Smugmug publishing service in the left-hand column of the Library, select Edit Settings, and in the Metadata section verify that you have Include: All Metadata set.
Did you download the Smugmug plugin from Smugmug? You might try this Smugmug plugin instead -- the author designed the publishing architecture of LR and has an excellent reputation. 
Are the publish services more effort than they are worth? So I get SmugMug to work, what happens when I try Flickr?
I think many users find the publishing services are generally worthwhile.  I publish regularly to Flickr (using the built-in Flickr plugin, which isn't completely reliable) and the Zenfolio plugin from Friedl. 

Similar Messages

  • Feature Request: save metadata to file, and read metadata from file.

    Please have function to save metadata to file, and read metadata from file.
    This would allow us to write cross-platform plugins that can assure data is up-to-date in the xmp, or modify xmp and have it reinstated in the catalog.
    This would go nicely with the ability to save xmp for virtual copies, dng, and rgb formats.

    Perhaps someone with direct experience with publishing to Smugmug will chime in.  Short of that, some thoughts on your issues:
    Should I not bother to "Save Metadata to File", this seems to be what is messing up the SmugMug publish service?
    I very much doubt that it is messing up the publishing.  What gets saved to the file from the catalog is independent of what gets exported.  Saving metadata to the file is generally a good practice (in case you screw up your catalog backups).  Many, perhaps most, users set the preference Catalog Settings > Automatically Write Changes Into XMP.
    I would have expected it to behave like an export which would write synonyms, exclude keywords that should be excluded, etc, which seems to work ok in point 6 above.
    Yes, that's a reasonable expectation.
    You may have done this already, but double-check: Right-click the Smugmug publishing service in the left-hand column of the Library, select Edit Settings, and in the Metadata section verify that you have Include: All Metadata set.
    Did you download the Smugmug plugin from Smugmug? You might try this Smugmug plugin instead -- the author designed the publishing architecture of LR and has an excellent reputation. 
    Are the publish services more effort than they are worth? So I get SmugMug to work, what happens when I try Flickr?
    I think many users find the publishing services are generally worthwhile.  I publish regularly to Flickr (using the built-in Flickr plugin, which isn't completely reliable) and the Zenfolio plugin from Friedl. 

  • Save metadata to file + Edit in PS = Reset develop adjustments?

    Hello:
    I don't know if this issue has been raised  before, since it's not easy to describe it and, hence, to perform a  search based on it. I would like to know if this is a bug or there is  some reason for it which I haven't think of yet.
    Let me explain... I use LR 3.3 to develop a raw file  as usual. Ok. Then I do "Edit in PS" to perform some pixel edition, then  back to Lr. Next, I apply some LR adjustments to the resulting file  (PSD or TIFF, depending on the preferences) that I just edited in PS. So  far, everything's fine: I can keep going back and forth between PS and  LR without trouble...
    ... but if I save metadata to  file (control+S), and then try to edit the PSD/TIFF as "original" in PS,  guess what: the file opens in PS with the LR adjustments not visible  (this is normal), but simultaneously, the develop settings for the file  are reset in Lightroom! So, to summarize:
    1) I develop a raw file using LR adjustments
    2) I edit in PS and save as PSD (or tiff, depending on the preferences)
    3) Back in LR, i apply some develop adjustments to the new PSD/TIFF file.
    4) I save metadata to file and choose "edit in PS as original"
    5) The file opens in PS, but the settings for the file are reset in LR!
    This  doesn't happen if I uncheck the "Include develop settings in metadata  in jpg, tiff and psd files" in the Metadata tab of the Catalog  preferences.
    I could record a video (screencast) if the explanation is not clear enough. Thanks in advance for your answers!

    I have recorded a screencast. For some reason, now I can't make it happen the first time around - I have had to do it twice this time (save metadata to psd file, edit in Ps, close Ps, save metadata to psd file, edit in Ps).
    I won't go into details since I think the video is pretty self explanatory. I know it's not usual to save metadata to file (including develop settings) just before editing in PS, but... is this normal, expected behavior? Am I doing something wrong without noticing? Same thing happen both in my desktop PC (Win 7 64, LR 3.3, CS5 64) and my laptop (Vista 32, LR 3.3, CS5 32).
    Thanks for your help.
    VIDEO (view fullscreen, hd, if possible): http://www.youtube.com/watch?v=7mRnwnoCtMw

  • Selecting images for "Save metadata to file"

    To improve performance we're being "encouraged" to turn off "Automatically write changes". Which means I now have many images scattered throughout the catalog that have metadata changes of some sort on a regular basis. I agree that with the automatic write turned on, LR's performance is horrendous for any kind of metadata change, but turning it off means having to regularly and frequently manually save changes.
    Is there some mechanism that can be used to select ONLY those images that NEED to have the file updated rather than displaying all 36,000 images and starting the "Save metadata to file" and rendering LR unusable for hours? There HAS to be a better way than this blind, sledgehammer approach.

    >Is there some mechanism that can be used to select ONLY those images that NEED to have the file updated rather than displaying all... There HAS to be a better way than this blind, sledgehammer approach.
    Lightroom will only update those images that need to be updated. In other words, only those images were the metadata change date stored in the catalog is newer than the metadata change date stored in the file. The same criteria applies to the auto write to XMP feature. Furthermore, selecting a folder and choosing
    Save Metadata from the folder context menu is
    much faster than selecting the files and choosing the
    Save Metadata to File command found under the Metadata menu.
    It's also worth noting that any time you select multiple files Lightroom will spend time "accumulating" existing metadata. IMO, this is one of Lr's most painful and unnecessary performance drags. The more files you select the longer Lr will take to accumulate the metadata. So, you really should avoid selecting large numbers of files. If you can't avoid making such a selection then it's best that you deselect them immediately after issuing the Save/Read metadata command. Doing so will save yourself a
    lot of time.

  • Context right-click to export XMP metadata to file

    I'd like to have the right click context menu include the option to "Export XMP Metadata to Files" in the Library grid or filmstrip. Currently an annoying trip to the Menu bar is required to invoke this function.

    It was there for B4.1. The Contextual Menus are getting crowded, so maybe that's why they took it out.
    I like lots of Contexual Menus,too. But they get a little useless if too crowded, so maybe they need ot be user configuarable for what one uses the most.
    Maybe by V1.5?
    Don
    Don Ricklin, MacBook 1.83Ghz Duo 2 Core running 10.4.8 & Win XP, Pentax *ist D
    http://donricklin.blogspot.com/

  • Lightroom 2.0: Save Metadata to File is not working correctly!

    Hi,
    I have this JPG file with no EXIF data whatsoever but I know it's capture time so I went to "Metadata » Edit Capture Time" and changed the capture time. On Lightroom in the Library module, I can see the capture time but then I save the metadata with "Metadata » Save Metadata to File". However, when I check the file on Windows Explorer, the capture time (or date taken as named by Windows) is not specified at all.
    Why isn't the "Save Metadata do File" working correctly?

    > Ok, this problem was working on only a specific file, so I just re-exported the file and it's all good.
    Exporting to a JPEG and writing metadata to the original JPEG is two different things.
    My experience was that when saving xmp metadata, LR does not create an EXIF section in a file where it was initially missing (And that's a common scenario with scanned film). The date and time information is only stored in the embedded xmp, of which Windows Explorer does not know a thing.
    When exporting your original to a JPEG, that's a completely different thing. You create a new file, rather than modifying your original. SO, Lightroom will create a brand new valid jpeg with a valid exif section and everything.

  • Bug: Keywords behave incorrectly after "Read Metadata from File"

    (Happens in LR3.4 RC and probably also in previous versions... but I am not sure if it happened in LR2)
    The problem seems tro be somthing like de-sync of database status and what we see on the screen.
    1) Let's say we have a photo with keyword "abc"
    2) Click in the Keyword List on the arrow around the "abc" keyword to show only photos with this keyword (single one), leave the filter on this settings
    2) Save Metadata to File
    3) Edit XMP in an external application, add new keyword "def"
    4) Read Metadate from File
    5) Now what happens is: The photos disappers from the screen as if it lost the "abc" keyword (weird), but if you look at the Keyword List, the "abc" keyword has still 1 photo attached to it. Also, if you release the filter and find the photo, it clearly has the "abc" and "def" keywords in the Keywording panel. And you can search for this keyword in the text filter (works correctly), but if you click on the arrow around the "abc" keyword, the photo is not shown.
    6) If you restart the Lightroom, it will work correctly again.
    I have an own application that is able to modify the XMP and the modifications may not be perfect, but in my opinion, this shouldn't happen when reading the metadata. If any developer is reading this, I can supply a file with original and changed metadata for debugging.
    It would be great it this could be resolved.
    Thanks!

    Please do report your find with the details you state (well done!) here: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
    Thanks.........

  • Does "save metadata to files" degrade jpeg

    I have a commission to add keywords and other metadata to jpeg files already held by the client. I have done this in my LR2. I want to save the metadata to the files for transfer back to their facilities. I will eventually be re-importing the files into their copy of LR2. If I "Save metadata to files" in my LR2, will this degrade the quality of the jpg image?
    Thanks for your help.

    No. The data is saved back to the file but the JPEG compression algorithm is not reapplied with every metadata save.

  • Does Save Metadata to file save EVERYTHING? and...

    1. Does Save Metadata to file save EVERYTHING? in other words, all Lr settings, ratings, Picks, keywords, etc?
    and
    2. does Lr automatically read the metadata from those XMP files when the images are imported into a different catalog?

    Does Save Metadata to file save EVERYTHING? in other words, all Lr settings, ratings, Picks, keywords, etc?
    Everything, with the exception of flags, color labels, collection membership, and stacking.
    Does Lr automatically read the metadata from those XMP files when the images are imported into a different catalog?
    Yes. Note that XMP files are created for raw files only; for other image formats (JPEG, TIFF, PNG, DNG), the metadata is stored within the file itself. Unfortunately, LR doesn't save metadata for videos (either in XMP sidecars or the video file).

  • Working with folders and save metadata to file compatability.

    when i edit in developer within lightroom, then move from the 'previous import' list to the folders which hold different projects by dragging them into the folders i have imported from the hard disk, it saves only the original files, and not my new edits.
    do i have to batch export everything i edit in lightroom to be able to use it in non adobe applications??
    i tried save metadata to file for these images, and then in finder they are no longer available for quickview (spacebar or command y) and finder quits. futhermore when these files, with the updated metadata, are dropped into an iwork file, they are not recognised as jpeg's anymore. but do work in photoshop, and i assume other adobe applications because the embedded metadata was designed to be compatible with adobe.
    how can i have the 'develop' editing i am doing in lightroom transfer to the folders i want to have these images saved in without laboriously exporting them and having saved each image twice? does lightroom have a way i can do this?

    If you're largely preparing images for the web, you simply export a batch from LR at the appropriate size and quality, in sRGB space, with or without metadata as you choose. Nothing laborious about it.
    Are you starting with JPEGs or RAW images?
    The bug in Leopard is known, but you also cannot expect the Finder to show what edits you have made in LR until the images are rendered out, as they are in an Export.

  • Lightroom 1.4.1 "Save Metadata to File" not working

    If I make changes in a DNG file in the Develop module, if I select "Save Metadata to File", the change does not appear in Adobe Bridge CS3 (2.1.1.9). Likewise, if I make changes in Adobe Bridge, and then go to Lightroom and choose "Read Metadata from File" or "Update DNG Preview & Metadata", the changes are not recognized in Lightroom. Any suggestions?

    > Ok, this problem was working on only a specific file, so I just re-exported the file and it's all good.
    Exporting to a JPEG and writing metadata to the original JPEG is two different things.
    My experience was that when saving xmp metadata, LR does not create an EXIF section in a file where it was initially missing (And that's a common scenario with scanned film). The date and time information is only stored in the embedded xmp, of which Windows Explorer does not know a thing.
    When exporting your original to a JPEG, that's a completely different thing. You create a new file, rather than modifying your original. SO, Lightroom will create a brand new valid jpeg with a valid exif section and everything.

  • Save Metadata to File Problem

    This is really puzzling me .... In Catalogue Settings, I have 'Automatically write changes into XMP' NOT ticked. When I want to save, I Select All and then 'Save Metadata to File' . However, most of the time this only saves the 'Most Selected' image, it does not create/write to XMP for all the selected files? However, I know this is meant to save to all the selected files and I also know that sometimes it does/has saved all the XMP files for me. I cannot figure out why sometimes it saves all the files and sometime only the 'most selected' ? I have tried in both Library and Develop Modules. Is there a reason for this or is it some kind of bug?
    I'm using Lightroom Ver. 3 on a Mac. But I also used to have the same problem on Version 2 as well.
    Many Thanks

    Switch to Grid view - anything you do in Grid view will always apply to all selected images.

  • Command: "save metadati on file".

    Hi, my name is Alberto. I've Photoshop elements 12. Last night i've saved many files with tags from Organizer. I've saved with the command: "save metadati on file". My Catalogue and the files are on disk "F", but at the end of process my disk "C" there are not available more than 18 GB. My question is: Who know where i can find the space used on disk "C" and how i can come back at the begin of process?? I'm sorry for my bad english... Thank you.

    Hi,
    I think that you will find many files in your %temp% folder which have been left around by the save metadata command.
    The easiest way to tidy up your disk is to use the Disk Cleanup utility in windows.
    Let it analyse your C: drive and see how much space is taken up by the Temporary files. You should be able to allow the utility to clear it down.
    Brian

  • Export Table to flat file and upload to FTP server for external vendor

    I have done some extensive searches on the forums and I think I have an idea but really need some help. Basically have a table that needs to be exported to a flat file and uploaded to a FTP server so that our vendor can get the data Monday-Saturday and automated by sysdate. This data is used to produce daily letters that go out to customers.
    After doing some searching I came across the UTL_FILE package and reading more into this right now but I am not sure if it is what I should be using to create the file.
    I am using TOAD right now and can see how to do it manually however really need the file to create itself and send automatically at 6 am Monday - Saturday with the date at the end of the file name making it a unique file for each day.
    Thanks in advance for all of your help.

    As Justin and others have mentioned I wrote [XUTL_FTP|http://www.chrispoole.co.uk/apps/xutlftp.htm] so you wont find it in the Oracle documentation. It's pure PL/SQL and uses UTL_TCP and implements an integrated PL/SQL FTP client / API. One of it's many overloaded procedures FTP's the contents of a refcursor straight to a FTP server of your choice, meaning no intervening file is required. Since it is pure PL/SQL, it is trivial to schedule using DBMS_JOB/DBMS_SCHEDULER.
    Any questions just ask.
    HTH Chris

  • When I save a pdf file and try to open it I get an error message

    When I save a pdf file and try to open it I get an error message, "Adobe Reader could not open 'file name.pdf' because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn't correctly decoded)."
    When I try to open it with Preview I get this message, "file name.pdf” could not be opened because it is empty."
    I am running  Maverick OS X 10.9.1.  What's up with this?

    Good question (I'm not a Mac guy these days).
    But Adobe Reader is only viewing the file as it has been saved. If it happens to all pdf files from all sources, I would begin to investigate your OS (and possible permissions but I'm not sure) maybe in the Apple forums.

Maybe you are looking for