About metadata and XMP

This question was posted in response to the following article: http://help.adobe.com/en_US/lightroom/using/WS638E3AC9-A04C-4445-A0D3-F7D8BA5CDE37.html

I would draw a very clear distinction between the concepts of "backup" and "archive".
Backup is a continuing and regular process, referring always to your most-current live and changing data, and is designed to protect the continuity of that data. This allows you to recover from a problem or accident, whether externally caused or the fault / inattention / reconsidered action / whatever of the user - and get back to where you were beforehand. That might relate to all your data together, as in a disaster of some kind, or selectively.
Archive is a planned process that defines certain data (or a copy of that) as non-current - often, as a matter of unchanging record. This gets put in a place where it can be separately accessed as needed, but often that is accessed by a different means than you access your live data (for example, you have to open a different Catalog).
LR's standard backing-up of the Catalog, also externally copying that to other physical media when LR is not running, as well as making an external copy of all your Raw files etc to other media, all deliver a backup facility - which is only useful if done regularly.
Exporting as Catalog - with negatives - (say) all your images from the year 2007 into a specially labelled and distinct disk drive that then sits on a shelf, is an example of "archiving" as I would use the term. That might be done for its own reasons, even if you also retain some or all of this inside your working data set too. For unchanging data, it doesn't particularly matter when you do this.
[edit: I should have made clearer, the images contained in an exported separate Catalog can be imported into - merged with - another Catalog if that becomes necessary.
If you have kept a backup (older) duplicate of your full working Catalog, you can go into that and get at information which may have been lost in the working version. You can save that out as a new temporary Catalog and use that to transfer things betrween Catalogs - which is effective if sometimes laborious - or for specific images, you may be able to get what you want more rapidly, by writing metadata to the files on disk, and then in the other Catalog, syncing or otherwise re-reading the metadata (or as a last resort, if the images / folders are now not present there at all, fully importing them).
But if it is just a question of "rolling back" the editing of particular images, the History option lets you do that right now, using the Catalog you already have.]

Similar Messages

  • [svn:osmf:] 14140: Change ManifestParser to pick up stream metadata and xmp metadata.

    Revision: 14140
    Revision: 14140
    Author:   [email protected]
    Date:     2010-02-11 17:07:31 -0800 (Thu, 11 Feb 2010)
    Log Message:
    Change ManifestParser to pick up stream metadata and xmp metadata.
    Modified Paths:
        osmf/trunk/framework/OSMF/.flexLibProperties
        osmf/trunk/framework/OSMF/org/osmf/elements/f4mClasses/ManifestParser.as
        osmf/trunk/framework/OSMF/org/osmf/elements/f4mClasses/Media.as
        osmf/trunk/framework/OSMF/org/osmf/metadata/MetadataNamespaces.as
        osmf/trunk/framework/OSMF/org/osmf/net/httpstreaming/HTTPStreamingUtils.as
        osmf/trunk/framework/OSMF/org/osmf/net/httpstreaming/f4f/HTTPStreamingF4FStreamInfo.as
        osmf/trunk/framework/OSMFTest/org/osmf/elements/f4mClasses/TestManifestParser.as

    Revision: 14140
    Revision: 14140
    Author:   [email protected]
    Date:     2010-02-11 17:07:31 -0800 (Thu, 11 Feb 2010)
    Log Message:
    Change ManifestParser to pick up stream metadata and xmp metadata.
    Modified Paths:
        osmf/trunk/framework/OSMF/.flexLibProperties
        osmf/trunk/framework/OSMF/org/osmf/elements/f4mClasses/ManifestParser.as
        osmf/trunk/framework/OSMF/org/osmf/elements/f4mClasses/Media.as
        osmf/trunk/framework/OSMF/org/osmf/metadata/MetadataNamespaces.as
        osmf/trunk/framework/OSMF/org/osmf/net/httpstreaming/HTTPStreamingUtils.as
        osmf/trunk/framework/OSMF/org/osmf/net/httpstreaming/f4f/HTTPStreamingF4FStreamInfo.as
        osmf/trunk/framework/OSMFTest/org/osmf/elements/f4mClasses/TestManifestParser.as

  • I have a tricky question about metadata and iTunes Match!

    Hi,
    Here's my question:
    I have purchased some content from the iTunes Store, most of it classical music (although that's not so relevant for my question). The Store metadata is generally poor, so for every purchased item I changed the metadata to suit my tastes (for example, all albums by J.S. Bach have "Bach" as artist, instead of the performer, which is the default in the iTunes Store).
    I have read some nightmare stories about metadata reverting to the original iTunes Store metadata, when subscribing to iTunes Match.
    I have also understood that iTunes Match does not change the metadata stored locally on my HD.
    So here is my question, which is twofold:
    1) Say I bought a song by the artist "John" on the iTunes Store. On my library, I changed the artist field metadata to "Jeff". Now, I subscribe to iTunes Match. Naturally, it will match my song to the one on the Store. On my iPhone, will my song appear under "John", or "Jeff"?
    2) In the same setting, after subscribing, will I still find this song under "Jeff" on my local library? In other words, what will change in my Desktop experience with iTunes?
    If having bad metadata when browsing my music on my iPhone is the price to pay for having all my music at my disposal anytime, I won't mind. But if iTunes Match messes up all my hard work getting my library just right on my Desktop, then I have to pass.
    Can you guys help me make a decision?
    Thanks,
    Paulo

    Thanks,
    Here is what another user got on https://discussions.apple.com/message/23028717#23028717 :
    "I can say that when my spouse gifted me with iTunes Match it was a disaster for my music library. It's all classical, and I also standardized names of composers, performers especially when there were multiple ones, and a ton of other stuff. Whatever matched, iTunes just upped and erased that, and used the title, artist, and whatever else from the store."
    This is *exactly* what I don't want to see happening! However, I could not find any other reports of what he describes. What do you think?
    Paulo

  • Ideas about viewing/displaying XMP metadata from Reader ?

    Hi,
    We are using Acrobat 9 to add XMP metadata to PDF documents.
    These documents are viewed by the others employees with Acrobat Reader.
    Since "File->Properties->Advanced Metadata" and "Custom Info Panels" are not available in Reader, how can we display XMP metadata ?
    Do you know some ways or plug-ins to do this ?
    Our custom XMP metadata schema have more than 20 fields, so I don't want to put all these informations in the "Keywords" field of the document properties.
    Any idea would be greatly appreciated !
    Thank you !

    Michael... what you are describing above is not accurate.  The iPod Classic does NOT have the capability of using the "Album Artist" field from iTunes to sort music.  This particular metadata field is not even available to the iPod Classic.  Only the "Artist" field is available.  (It is the other way around with the iPod Touch, iPhone, and Ipad -- for these iOS devices, the "Album Artist" field is the one that is available, and not the "Artist" field.)  There are numerous posts here in the discussion forums from other folks who are frustrated by the same issue.  The iPod Classic can only sort and group songs together by "Artist" -- that is, the track artist.  And the track artist is often quite different from the album artist.  For example...  I have 29 different Barbra Streisand albums in iTunes.  For all of them, the album artist is "Barbra Streisand."  There are several different track artists however.  Most of them are just Barbra Streisand.  But she also does a duet or two on several albums.  So there are track artists like...  "Barbra Streisand with Kim Carnes," and "Barbra Streisand with Barry Gibb," and many more like that.  After syncing to my iPod Classic, when I sort on the iPod's "Artist" field, I get about 25 different iterations of "Barbra Streisand and .... " as the artist.  Yes, "Barbra Streisand" does appear among them.  But the only songs that are listed under "Barbra Streisand" are those that she sang by herself, and where she is the only track artist.  Given the setup of the iPod Classic as it is now, using firmware version 2.0.4, it is NOT possible to use the Album Artist field to sort and group songs together. 

  • Synchronizing IPTC/IIM and XMP metadata in JPEG images

    Excerpt of "IPTC Core Implementation Guidelines", section 2.2.1 available on http://www.iptc.org/IPTC4XMP/:
    The basic functionality of this synchronising mechanism [between IPTC/IIM metadata in IRB and XMP metadata] is:
    - To move metadata from the IRB to a new XMP packet in case an image file is opened with such an IRB but without an XMP packet. If the file is saved both the IRB and the XMP packet will be stored to the header section of this file.
    - To move metadata from the XMP packet to a new IRB in case an image file is opened with an XMP packet but without an IRB. If the file is saved both the IRB and the XMP packet will be stored to the header section of this file.
    - To update the metadata values of the IRB respectively the XMP packet from the newer source to the older destination. Which set is newer or older is detected by a hash value over each block of metadata. (More detailed information is available from Adobes XMP web pages at www.adobe.com/xmp and in the software development kits.)
    I have checked for Adobe XMP web site and searched in "XMP Specification, January 2004" and I have not found explanations about this "hash value over each block of metadata" mechanism.
    Moreover, it seems that it does not work regarding to the following simple experiment:
    - 1. add metadata to a JPEG image using Photoshop CS (which adds both IPTC/IIM data in IRB and data in XMP)
    - 2. edit these metadata using an "IPTC/IIM-only and non-XMP-aware" editor like IrfanView, XNView or any other one
    - 3. go back to Photoshop CS which displays the "old" XMP metadata ignoring changes done previously using the IPTC-only editor.
    Of course this experiment works using an "XMP-aware" editor like iView Media Pro or PixVue in step 2.
    So it seems very easy to get images with IPTC/IIM and XMP metadata not synchronized when the image workflow uses different programs to edit metadata.
    Am I missing or misunderstanding something ?
    I have found a radical method stripping XMP metadata (in a step 2 bis...) using David Crowell's JStrip, see
    http://davidcrowell.com/jStrip.aspx
    Do you know any other best method to keep IPTC/IIM and XPM data synchronized when an image workflow uses different metadata editors and some of them are not XMP-aware ?
    Patrick Peccatte
    www.softexperience.com

    Excerpt of "IPTC Core Implementation Guidelines", section 2.2.1 available on http://www.iptc.org/IPTC4XMP/:
    The basic functionality of this synchronising mechanism [between IPTC/IIM metadata in IRB and XMP metadata] is:
    - To move metadata from the IRB to a new XMP packet in case an image file is opened with such an IRB but without an XMP packet. If the file is saved both the IRB and the XMP packet will be stored to the header section of this file.
    - To move metadata from the XMP packet to a new IRB in case an image file is opened with an XMP packet but without an IRB. If the file is saved both the IRB and the XMP packet will be stored to the header section of this file.
    - To update the metadata values of the IRB respectively the XMP packet from the newer source to the older destination. Which set is newer or older is detected by a hash value over each block of metadata. (More detailed information is available from Adobes XMP web pages at www.adobe.com/xmp and in the software development kits.)
    I have checked for Adobe XMP web site and searched in "XMP Specification, January 2004" and I have not found explanations about this "hash value over each block of metadata" mechanism.
    Moreover, it seems that it does not work regarding to the following simple experiment:
    - 1. add metadata to a JPEG image using Photoshop CS (which adds both IPTC/IIM data in IRB and data in XMP)
    - 2. edit these metadata using an "IPTC/IIM-only and non-XMP-aware" editor like IrfanView, XNView or any other one
    - 3. go back to Photoshop CS which displays the "old" XMP metadata ignoring changes done previously using the IPTC-only editor.
    Of course this experiment works using an "XMP-aware" editor like iView Media Pro or PixVue in step 2.
    So it seems very easy to get images with IPTC/IIM and XMP metadata not synchronized when the image workflow uses different programs to edit metadata.
    Am I missing or misunderstanding something ?
    I have found a radical method stripping XMP metadata (in a step 2 bis...) using David Crowell's JStrip, see
    http://davidcrowell.com/jStrip.aspx
    Do you know any other best method to keep IPTC/IIM and XPM data synchronized when an image workflow uses different metadata editors and some of them are not XMP-aware ?
    Patrick Peccatte
    www.softexperience.com

  • Metadata and ePub export and custom XMP fields...

    Hi,
    Does anyone know of a way to add metadata apart from the fields that
    already are available in the ePub export dialog and XMP panels? The
    iBookstore requires a bunch of stuff that I can't find any place to add.
    This trial script that I've put together does add an entry to the DC
    metadata (as you'll be able to see in the XMP panel), but it is not
    retained when the InDesign document is exported. (I believe that it was
    from Tomaxxi's website that I got quite a lot of help for the script.)
    If I don't get any answers here I'll take this over to the scripting forum.
    Thanks,
    Ariel
    PS I hope the following script comes through ok. I've got to post this
    via email, which often mangles things. Apologies in advance if that is
    the case.
    myDocXMP = app.activeDocument.metadataPreferences;
    destNamespace = "http://purl.org/dc/elements/1.1/";
    destContName = "ArielsContainer";
    destNodeName = "ArielsSpecialMetdataField";
    nodeValue = "Great ePub!" ;
    myDocXMP.createContainerItem(destNamespace, destContName, undefined,
    ContainerType.ALT);
    myDocXMP.setProperty(destNamespace, destContName+"[1]", nodeValue);

    Hi David,
    Right. I also suspect that ID is "hardwired" to export only specific
    categories of metadata. And even if I can add to the DC metadata, it
    still won't come through on export -- that's my guess. But maybe,
    hopefully, I'm wrong.
    The script that I posted does add metadata to the DC category (as can
    been seen under the Advanced tab of the XMP Panel). But it adds it in a
    slightly funny way (as an alt container, and not an alt-text container;
    there's no scripting option that I can see for creating alt-text
    containers, but, on the other hand, I don't know what the difference
    between the two types is). Also, it creates some sort of weird array
    (hence the ).
    In short, the script doesn't prove that ID won't export additional
    metadata if it's added in the right way.
    I wonder what you mean by "adding custom metadata" in a non-printing
    story? Also, if that ends up in a .xhtml file that's not so useful,
    because we need it to land up in the content.opf file to be of any use,
    I think?
    Again, I'm not sure what PRISM categories are. But I did actually
    download the XMP SDK at one point, though I never really explored it. If
    your extra metadata exported to PDF, would it export to ePub as well?
    Did you try exporting with CS4, even if not with CS5.5?
    Thanks,
    Ariel

  • [ANN] GeoIPTC 1.0 : geocode your images using metadata standards (IPTC and XMP)

    Hello,
    GeoIPTC is an innovative tool to add geographical identification to your images (geocoding) according to IPTC and XMP metadata embedded in images.
    GeoIPTC reads all IPTC and IPTC Core metadata embedded in an image, isolates localisation data (City, Location, Province/State, Country Code and Country Name), then sends a request to a Geocoding Web Service and finally gets latitude/longitude coordinates.
    To say it briefly: GeoIPTC gets geographical information from the postman address embedded in image.
    Main features
    * Gets full sets of image standard metadata
    * Automatically gets longitude/latitude from widely used Geocoding Web Services like Google Maps, Yahoo! Maps or GeoNames.
    * Locate automatically images on Maps Services like Google Maps, Yahoo! Maps and MapQuest
    * Generate automatically KML or KMZ placemarks and locate single (one image) or multiple (many images) placemarks on Google Earth with full IPTC/IPTC Core metadata
    * Set automatically single or multiple images with appropriate Exif GPS coordinates
    More information and download:
    http://www.geoiptc.com/EN/Index.html
    With best regards
    Patrick Peccatte
    www.softexperience.com

    Note the last paragraph in the original post which explains how Flickr handles resolution changes without breaking the rectangles. Perhaps a more straightforward approach would be to store both the rectangle coordinates for each rectangle AND the image's width and height at the time the rectangles were created. Then if the image is scaled, the rectangles can be scaled accordingly. For example, if a rectangle is at x=100,y=200,w=50,h=70, the "original dimensions" are 1000x2000, and the image's current dimensions are 500x1000, then an application could assume the image has been scaled down by (500/1000=) 0.50, and so the x,y,w,h of each rectangle could also be multiplied by 0.50 (x=50,y=100,w=25,h=35). I'd recommend storing floating-point values so that multiple scalings don't make the rectangles "creep".
    Of course, it is possible that really the image was cropped rather than scaled, but fairly unlikely you would happen to crop it the same percent in both directions. Even if an image is cropped, someone could manually repair the rectangles by sliding and scaling them until the fit back on the faces (unless most of the faces were cropped off).
    A rectangle-aware application could scale and translate the rectangles during a crop or scaling operation, but other applications could still survive scaling if they at least preserve the XMP tags as-is.

  • PdfA1b -  Subject Mismatch between Document Info and XMP metadata

    As far as I can tell, when generating PdfA-1b files I am completely compliant with the spec. Yet when I try to preflight verify my output I get the following error: "Subject mismatch between Document Info and XMP metadata".
    Here is my Document Info:
       /Title (Title)
       /Author (Author)
       /Subject (Subject)
       /Keywords (Key Words)
       /Creator (Creator)
       /Producer (Producer)
       /CreationDate (D:00010101000000)
       /ModDate (D:00010101000000)
    Here is my XMP Stream:
        Key Words
        Producer
        Title
        Subject
            Author
        Creator
        0001-01-01T00:00:00.0011111
        0001-01-01T00:00:00.0022222
        1
        B
    Am I missing something?
        Subject
    vs
       /Subject (Subject)
    It seems like it should be fine.
    -Rick

    You have a disconnect with regard to how Document Info fields are to be mapped to XMP Dublin Core (dc) data fields:
    - Document Info Subject -> dc:description
    [nobody claims this is intuitive, but it is indeed specified reasonably well]]
    The following is not required in your case, but for your info I include it anyway:
    - Document Info Keywords -> dc:subject
    Your best source for this is the actual PDF/A-1 standard (ISO 19005-1, can be purchased form www.iso.org).
    A very good companion for such type of topics are the TechNotes from the PDF/A Competence Center (see www.pdfa.org), downloadable free of charge.
    HTH.
    Olaf Drümmer

  • Iptc and xmp, data important for organizing photos?

    HI, I keep encountering these two acronyms (IPTC and XMP) while working with my photos in Aperture.  Are these data important, should I be doing anything with it?  Essentially what I am doing is, after importing photos from iPhoto, I am filing to Folders, Projects, and Albums (some Smart). Thanks

    Astechman,
    EXIF (which you didn't ask about) is Exchangable Interchange Format, and those fields are generally physical attributes about your photos, as recorded by your camera.  Things like date/time, aperture, shutter speed, etc.  Some people like to think they should be able to change those, but that doesn't make any sense (except if your camera's clock is wrong.)
    IPTC (International Press Telecommunications Council) data is used in digital media as metadata for the author to put things.  These include things like keywords, location narratives, copyright notice, photographer name.  I.e., things that don't have anything to do with the camera or the physical attributes of the photo, but about the subject/content of the photo or the photographer.
    XMP adds onto IPTC, and is often associated with a "sidecar" file, in which a digital asset manager system (DAMS) saves extra metadata to such a file.  (Aperture is a DAMS, but it does not use sidecar files; it keeps data like that within the library.)
    As for what you should be doing with it -- that's up to you.  How much metadata do you want associated with your photos?  Fill in those fields and just ignore the rest.  I tend to fill in keywords and copyright, and that's about it, but there are many other fields that may be of interest to you.
    nathan

  • Simple Bridge script will not read metadata and triggers Adobe Stock Photos

    I have been trying to learn to write scripts for bridge but can't get past the most basic tasks. When I run the script on an open window in bridge it throws an "Uncaught exception metadata" error. The most bizarre thing is it sometimes causes an Adobe Stock Photo script to launch in the extendscript toolkit and throw and the "Uncaught exception metadata" error in that script. My script is as follows:
    #target "bridge"
    if (BridgeTalk.appName == "bridge")
    var items = app.document.visibleThumbnails
    for (i=0; i< items.length; i++)
    item = items[i]
    md=item.metadata
    md.namespace = "http://ns.adobe.com/photoshop/1.0/";
    Window.alert(md.Title)
    Window.alert(i + " "+ " Files Finished")
    Basically I was asking to extract the title of each thumbnail from the metadata and show it in a window. I figured if I could do something as basic as that then I could move on and tackle the more complicated tasks that I need to do.
    Any ideas of what is going on? Has anyone else accidentally triggered Adobe Stock Photos?

    Another bit of info....   As I looked at this further, it seems to be occuring only on those photos where I previously ran camera raw from CS3. I've upgraded to CS5 but have not rerun camera raw since. I understand the camera raw engine in CS3 was different. Could this be involved? Could Lightroom be changing the metadata because the engine is updating the information and I have to save TO file to get this to synch?
    update about this camera raw engine possibilty..... it would not appear to be the answer. I have some files that synch even tho lightroom develop says they are using the 2003 process version. I have some files that are on the new version that won't synch.

  • 5 stars not showing up on other computers when importing images that have been worked on. Catalogues settings include write metadata to xmp keywords do show up though

    our working group usually one team member imports and completes job in lightroom 5 . All settings on team computers include write metadata to xmp.  Key words show up if another team member adds the images to their catalogue but the 5 stars don't show up.
    We use the 5 stars to show images that were worked on and complete.
    Would love to sort this issue out as we rely on being able to see the star rating not just keywords.

    [Sorry for the delay in getting back.] Of the three files you included in the Dropbox .zip, 2 had no rating, and 1 had a 5-star rating (*research*.dng).  So indeed, the rating didn't get written to those two files and wouldn't show up when they were imported into another catalog.
    A couple of suggestions:
    1. Triple-check that the option Automatically Write Changes Into XMP is set in Catalog Settings > File Handling in everyone's Lightroom.
    2.  After someone sets the rating, check the thumbnail in Library grid mode -- does it have a badge in the upper-right corner indicating the metadata needs to be updated?  If it does, then that means the metadata isn't getting written immediately back to the file:

  • I want a stamp to write to the file metadata and be able to display the result in windows explorer.

    I want a stamp to write to the file metadata and be able to display the result in windows explorer. I have read PDF Stamp Secrets and can write to Custom Metadata but don't know how to display that custom field in explorer. Can I have the stamp write to a standard (non-custom) metadata field? Or, how do it get the custom field to display in explorer? Windows is pretty stingy with the file details it displays for PDF files, in fact there are no editable fields provided (like are available for Office files).   I want this to work for multiple users hopefully without having to get the IT group involved to make (or allow) system modifications to make this work. Any ideas? Thank you.

    Metadata for Windows Explorer is tagged with different names than the metadata for PDFs. Acrobat cannot copy the metadata to the tagged items of the file header.
    There are tools like EXIFTool that can manipulate the data as necessary. Phil Harvey also provides the details about the file types and their metadata tags and values so you should be able to map the tags that need to be updated.

  • How should we be going about creating and saving and/ or exporting our ODC files using Excel 2013 for use in Project Server 2013 Online?

    Hi I need your guidance on how I should go about setting up my Excel 2013 reports so that others in our Project Online 2013 environment can access and updates these reports of mine.
    My questions are as follows:
    I presume I need to create and save my ODC files in a PWA > Data Connections folder.  I have English and French users in our environment.  Do I need save them twice?  Once in the French and again in the English Data Connections folder?
     Likewise for the Excel file? 
    How should I go about creating my ODC files within Excel?  By default, the ODC files are being created on my PC's > My Documents > My Data Sources folder.  I presume I need to get them saved or exported to the PWA > Data Connections
    folder. So, How should I be going about creating and saving and/ or exporting the ODC files???
    FYI...My oData Feeds that I wish to use and join in this particular Excel file are as follows:
    https://cascades.sharepoint.com/sites/pwa/_api/projectdata/AssignmentTimephasedData01T00:00:00'
    https://cascades.sharepoint.com/sites/pwa/_api/projectdata/Projects()?$select=ProjectId,ProjectName,CAS_Classification,CAS_PCO,CAS_IT_Department,CAS_Program,CAS_SubProgram
    https://cascades.sharepoint.com/sites/pwa/_api/projectdata/TimeSet()?select=TimeByDay,TimeDayOfTheWeek$filter=TimeByDay ge datetime'2014-10-19T00:00:00'
    https://cascades.sharepoint.com/sites/pwa/_api/projectdata/Resources()?$select=ResourceId,ResourceName,Programs,Supplier,Source,Role,CostType
    Thanks in advance,
    \Spiro Theopoulos PMP, MCITP. Montreal, QC (Canada)

    Thank you Guilaume.  May I ask you to help clarify a bit more for me?  If I have to do it for both languages (the reports and ODC files), do I simply copy the same ODC files from e.g., the English to French folder in PWA (Odc files)?  Or does
    that defeat the purpose?  Or, do I need to create a new set of oData Feed Connection files with a French version of Excel 2013 and save them to the French Data Connections folder in PWA?  Do I need to have a French version of Excel 2013 to create
    French ODC files and ultimately French based reports and/ or vice versa?
    I did notice that the following oData metadata command from within a browser produces different results (ie., English versus French metadata returned) depending on who runs it (i.e., French or English user, etc).  As you can see I am a bit confused.
     Any help you can provide would be greatly appreciated.
    https://XXXXX.sharepoint.com/sites/pwa/_api/projectdata/$metadata
    \Spiro Theopoulos PMP, MCITP. Montreal, QC (Canada)

  • [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

  • Lightroom metadata and Bridge compatibility

    Dear members:
    I have some questions I would like to have answered prior to deciding whether I should invest on Ligthroom and thought I would post them here to get some input. They are:
    1. Is metadata assigned to a DNG file by Lightroom interchangeable with Bridge ? Are both applications equivalent in the way they assign metadata and process image files ?
    2. Is the processing of RAW files by Lightroom the same as that done by Bridge ? In other words, are the same Camera Raw algorithms used by both Bridge and Lighroom ?
    3. Can I process images in Lightroom while keeping these images in their own folders without having to import these images into Lightroom's own database ?
    Thank you in advance for your help and answers,
    Joseph Chamberlain

    1. Yes
    2. For equivalent releases.
    Bridge 4 and LR 1.0, LATER 4.1 and LR 1.1
    3.You keep images where you want. Still have to import images for the dB functions that LR is all about. It is a Metadata editor, so >import.
    Read the LR FAQ and recent forum threads and you will gain a better insight int LR. Also just download the Trial and try it for yourself for 30 days. The Best way to learn what it is all about.
    Don
    Don Ricklin, MacBook 1.83Ghz Duo 2 Core running 10.4.9 & Win XP, Pentax *ist D
    http://donricklin.blogspot.com/

Maybe you are looking for

  • Two rows as one display the data in one row

    Hello All, I would like to have data of two rows put in one as: Lets say the data is like this: SELECT * FROM TEST;       COL1       COL2       COL3 C        1.5          3          1 M                     2          1 C        2.5                   

  • Howto set ImageBase when one cannot deply to  /webapp

    I am using the BC4J html generating classes and WebBeans. I see absolute references to /webapp/imaages in the generated HTML. I cannot deploy to a top-level context on that server, so I am wondering if there is a setImageBase() method or some paramet

  • Oracle SQL Developer does not browse Sybase's objects

    I had installed and configured jtds-1.2.5.jar in Oracle SQL Developer for Sysbase connection. Oracle SQL Developer does not browse any objects. Why? Can you please provide a solution?

  • Convert PDF Chrome extension does not appear/install (Acrobat X)

    Cannot figure out how to add the Convert PDF Google Chrome Extension in Chrome Version 33.  Please help.

  • Hi guys, I hope someone can help me with a technical question

    a couple of days I recharge the battery of my iphone with the original usb adapter to the electrical plug and then in the right moment when I plugged the phone it came a little spark from the electrical plug and my iphone  was shut down by itself the