Extracting "File Properties" metadata from Photoshop CS3

After processing scanned images in Photoshop CS3, I am up loading them to a DAM solution that has the capability to extract embedded metadata using custom defined keys. I would like to know the syntax/structure of embedded metadata labels that display in the "File Properties" template of Bridge CS3 (e.g. File Size, Dimensions, Color Space) so that I can extract that metadata.
Thank you!

I have this printer and use Leopard, but I don't have this problem I am useing the 6.2 driver. There are two drivers on their website, I am using only the driver that came with the machine. I would re-install the driver. Secondly and this caught me up a bit at first. You open the CS print manager, press print and then the Epson driver emerges, there i s no direct access from CS3 to the driver. Secondly in the Epson driver there are two or three set of drop down menus, the one that permits setting the paper profile is not exactly where you expect it, just have a look through all the menus(I am not sitting in fronto of my mac right now so I am of limited help). Good luck.

Similar Messages

  • Extracting "File Properties" metadata

    After processing scanned images in Photoshop CS3, I am uploading them to a DAM solution that has the capability to extract embedded metadata using custom defined keys. I would like to know the syntax/structure of embedded metadata labels that display in the "File Properties" template of Bridge CS3 (e.g. File Size, Dimensions, Color Space) so that I can extract that metadata.
    Thank you!

    In Preferences>Metadata there are two choices for dimensions - inches and cm, check the box for your poison.

  • Extract 'File Properties' Metadata

    I am looking for a way to extract all the information in the File Properties to a .csv. I have downloaded the Export Metadata script and it, works except I cannot include the File Properties in the Schema field. I hope there is a way to modify this script to include the File Properties.
    Eric

    Thanks
    Good Luck.
    My
    Si
    tes

  • Upgrading from Photoshop CS3 to CS6

    I am upgrading photoshop CS3 to CS6 on Windows 7.
    I have downloaded two files: Photoshop 13_LS16.exe and Photoshop_LS167z.
    However, it has not installed properly.
    I can only open CS6 if I click on the LS167z file with (open with PS).
    And although it opens I get the message: Could not complete your request because it is not the right kind of document.
    CS3 is still as it was.

    Many thanks
    That makes everything clear.
    Also thanks for the deletes!
    Von: PECourtejoie [email protected]
    Gesendet: Montag, 3. September 2012 16:13
    An: planni
    Betreff: Upgrading from Photoshop CS3 to CS6
    Re: Upgrading from Photoshop CS3 to CS6
    created by PECourtejoie <http://forums.adobe.com/people/PECourtejoie>  in Downloading, Installing, Setting Up - View the full discussion <http://forums.adobe.com/message/4669378#4669378

  • From Photoshop CS3 to Suite Production Premium CS4 - order failed

    Hello,
    I have a little problem with buying a product from Adobe. I have Photoshop CS3 and I want to buy CS4 Suite Production Premium. When I search for this product and check the upgrade options it says that I can upgrade from my Photoshop CS3 version. However, when I order this product I get an order cancelation after some minutes without any reason - and no, it is not a CreditCard problem - I checked everything. All data is correct. Where there would be a real problem, why I don't get a call from them?
    Then I called the sales hotline and the guy on the line told me that I need the Upsell version and that he can't check why the online order was canceled. Ok - I ordered this upsell version for a higher price than the online upgrade version. Some hours later I got a weird email from Adobe saying again that my order has been canceled. ??? I wonder whats going on there. I can't reach the sales guy on the weekend so I have to wait and I know that he can't give any information about why the order has been canceld again (why that?). That way it seems I am not able to order any product from Adobe and honestly I don't want to order it from Adobe directly anymore.
    May it be possible that I can't upgrade or upsell from Photoshop CS3 alone to the Production Premium Suite CS4 - even it saying like this on their website.
    Also, why is there only the upgrade version available on the online store and not the upsell version and why do I see an upgrade option even it must be called upsell version?
    Why is the upgrade manager: http://www.adobe.com/products/creativesuite/upgrade saying the same that I CAN UPGRADE from Photoshop CS3 to this Suite.
    I am speechless about that much trouble with a company like Adobe. And yes, this is my first try to order a Suite from Adobe directly. Now I am very unsure what to buy, where to buy and how I get this to work.
    Btw. Customer Support didn't answer my emails about this.
    Thanks for any hint!
    Andreas

    I did that twice and called them. They are always saying that they can't see what the problem is but they can setup a new order and try again - hello? - try and error ordering. I will not order on the Adobe Store anymore. This was the first and my last time I tried to order on their site or via a sales agent from their sales team. Also, when I see their emails that came back about the cancelation: No Subject line, weird emailaddress and with some really confusing product description and with a standard answer. I first thought it was some spam. I am really disapointed about their service.
    I also found out that the sales guy put in a wrong phone number and I can remember we checked the number three times. I mean, I don't order a pair of socks here - I want a pro sales service for a pro product where I pay a lot of money for.

  • Should i upgrade from photoshop cs3 extended to photoshop cs6 non extended

    hi im just wondering should i upgrade from photoshop cs3 extended to photoshop cs6 NON extended...... would i loose options from my extended version?
    also i dont use photoshop cs3 that much, does anyone think its worth me upgrading?
    thanks
    lee

    Good day!
    I think I read that with 2013 the upgrade path would be shortened, so you are probably not eligible for upgrading anymore.
    Apart from that the benefit of purchasing the current version of Photoshop naturally depends on what you are doing with Photoshop (both in terms of which features you use and how much you use the application overall).
    Smart Objects have been improved quite a bit, Puppet Warp is an interesting feature, Configurator allows for the easy creation of custom Panels that can combine Tools, Commands, Actions etc.,  …
    But to judge the programm yourself you could just install the trial – mind you, the trial is Photoshop Extended, so you may want to consult the Reference on which features you would not get with Potoshop Standard.
    You might also want to look into Cloud Licensing – or at least »Adobe« wants you to …
    Regards,
    Pfaffenbichler

  • Post script error printing from Photoshop CS3

    Getting PS error when trying to print to new Lexmark c543dn from Photoshop (CS3).  Prints endless pages with multiple symbols/characters.  Otherwise prints fine from any other programs.  Worked fine with 9 year old Epson inkjet.  Any solutions? Lexmark doesn't have any updated drivers that address this. 

    Amy, your question would get a better response from the Photoshop general Forum. Post there if you have NOT already done so…
    oppps beaten to it…

  • Can I upgrade from Photoshop CS3 to CS6?

    Can I upgrade from Photoshop CS3 to CS6?

    I think so, but only via the Creative Cloud, and with a one year commitment. And that upgrade may be only for suites, not individual apps. I didn't look that closely. See the page here:
    https://creative.adobe.com/#plans

  • Office File Properties - Metadata

    Hi all,
    How can I populate the actual contents of a file (word, excel,...) with metadata values? And the reverse... extract custom metadata field value from a Microsoft Office document and then use these value to populate metadata fields on the content server.
    Thanks,

    Hi,
    I think that you can populate metadata automatically with the "Content Categorizer" component.
    You can : - populate the metadata with the Word file properties
    - populate the metadata with some references that are included in the Word document.
    For the reverse side, I think you have to develop your own component...
    I hope it will help!!
    Romain.

  • How to make my old file info panel from photoshop work in xmp

    Help. Not a photoshop guy but rather a genealogist. Many years ago downloaded a custom file info panel for photoshop which I used to enter meta text about the family photos I scanned. Currently using adobe creative cloud but cant figure out how to use panel or see most of my metatext last few version. Below is information about the panel. All I really want to do is install my panel and get back to genealogy. I apologize but not sure I need to understand the basics of photoshop..
    john weis
    [email protected]
    This is the authors description of the panel:
    Genealogy Photo (Private Collection) Custom File Info Panel 1.0 for Photoshop. 11 FEB 2007
    Developed by Ron Reiger [email protected]
    Please contact me to suggest improvements.
    1. BASIS FOR THIS CUSTOM FILE INFO PANEL
    2. DESCRIPTION OF EACH PROPERTY NAME
    3. WHERE EACH PROPERTY NAME MAPS & OTHER NOTES
    4. WHERE TO INSTALL THE CUSTOM FILE INFO PANEL
    1. BASIS FOR THIS CUSTOM FILE INFO PANEL
    The Custom File Info Panel is used to capture metadata about a genealogy/family history photo that is privately held (that is, the photo is not in the possession of a library). The metadata property names on the File Info Panel are based on my interpretation of the recommended primary citation for a photograph (private possession) (annotated, with provenance) as described on page 95 of Elizabeth Shown Mill's "Evidence! Citation & Analysis for the Family Historian" and on my interpretation of recommended primary citation for an Electronic File (Image from Private Files - Annotated), Mills, "Citation!", page 81. I added a few more property names for location and date the photo was taken and keywords (to ID people by number rather than by name), the name of the person who provided the description, a surety for their description, and an informal description. Each field is discussed below.
    2. DESCRIPTION OF EACH PROPERTY NAME
    Date Scanned: This is the date the photo was scanned. Date is populated by Photoshop and is not editable.
    Provider: The owner of the photo as of the date it was scanned. A researcher in a future generations will know who had the photo at a particular point in time.
    Provenance: Describe as best you can how the photo got from the person in the photo to the Provider.
    Description Provided By: List the person who identified the people and location in the image.
    Description Surety: (This is an open text field. You can use any surety rating system you want.) Describe or rate the quality of the Description of the image's people and location. Note any uncertainties regarding any particular people in the photo.
    Complete Subject Description: List the full name of each individual in the image, in order. You may want to list the location and date of the image even though there are separate property names for that data.
    Informal Subject Description: An optional non-genealogical description of the image, perhaps for using the photo outside of genealogy. Example Informal Subject Description: "Grandpa as a young man."
    Media Description: Describe the paper photo you scanned. Dimensions, border, frame, damage, etc. Your ancestors will have an easier time finding the paper photo later if you describe it well!
    Annotations: Copy any annotations on the front or back of the photo and frame. Transcribe any photographer embossing/imprint; this is a clue for dating/locating photos.
    Special Editing/Alterations: Describe any restoration you performed on the digital image. Did you correct for the lateral reverse of a tintype or daguerreotype?
    City/County: List the City/County where the image was taken.
    State: List the State where the image was taken.
    Country: List the County where the image was taken.
    Photo Date: List the date the image was taken.
    Keywords: This is the standard keyword entry. Commas or semicolons can be used to separate keywords. I type the TMG ID number of each person in the photo here so I can search for all photos of the person without typing their name.
    3. WHERE EACH PROPERTY NAME MAPS & OTHER NOTES
    I have not created a working namespace URI or rdf ala http://purl.org/dc/elements/1.1/ for this panel. I have not created localization dictionary files for this panel. Data entered into the panel will appear in Adobe Bridge. As you can see below I re-used lots of pre-existing property names and dumped all my new property names into the photoshop namespace. I don't know if this approach has drawbacks.
    Date Scanned:                xmp_path: 'CreateDate'   Pre-existing property name
    Provider:    xmp_namespace: photoshop, xmp_path: 'Credit'    Pre-existing property name
    Provenance:    xmp_namespace: photoshop, xmp_path: 'Provenance'
    Description Provided By:  xmp_namespace: photoshop, xmp_path: 'DescriptionProvidedBy'  Pre-existing property name
    Description Surety:   xmp_namespace: photoshop, xmp_path: 'DescriptionSurety'
    Complete Subject Description:   xmp_namespace: photoshop, xmp_path: 'Description'   Pre-existing property name
    Informal Subject Description:  xmp_namespace: photoshop, xmp_path: 'Caption'   Pre-existing property name
    Media Description:   xmp_namespace: photoshop, xmp_path: 'MediaDescription'
    Annotations:     xmp_namespace: photoshop, xmp_path: 'Annotations'
    Special Editing/Alterations:  xmp_namespace: photoshop, xmp_path: 'SpecialEditing'
    City/County:    xmp_namespace: photoshop, xmp_path: 'City'    Pre-existing property name
    State:     xmp_namespace: photoshop, xmp_path: 'State'    Pre-existing property name
    Country:     xmp_namespace: photoshop, xmp_path: 'Country'   Pre-existing property name
    Photo Date:    xmp_namespace: photoshop, xmp_path: 'DateCreated'   Pre-existing property name
    Keywords:               xmp_path: 'Keywords'   Pre-existing property name
    4. WHERE TO INSTALL THE CUSTOM FILE INFO PANEL
    I have tested this panel with Photoshop CS2 and Adobe Bridge CS2 only.  It may not work on earlier versions.  FWIW a malformed Custom File Info Panel will fail to load in File Info; it won't crash Photoshop.
    The following was taken from "XMP Custom Panels," Adobe, Oct 2003.
    Each time an Adobe application opens the File Info dialog, it scans all the files in these directories and appends them to the file list. If more than one of the description files has
    the same panel name, the one found in the last file to be loaded is added, and others are ignored.
    Changes to the contents of the directories do not require you to reload an application; changes are automatically reflected in the dialog the next time it is opened.
    The panel description and localization dictionary files must reside in the following locations for use with Adobe Creative Suite applications:
    Mac OS X
    {Root Volume}/Library/Application Support/Adobe/XMP/Custom File Info Panels
    {Home Directory}/Library/Application/Adobe/XMP/Custom File Info Panels
    Windows
    \Program Files\Common Files\Adobe\XMP\Custom File Info Panels
    \Documents and Settings\<user>\Application Data\Adobe\XMP\Custom File Info Panels
    The panel description and localization dictionary files must reside in the following locations for use with Adobe Acrobat 7.0 or 6.0:
    Mac OS X
    {Root Volume}/Library/Application Support/Adobe/Custom File Info Panels
    {Home Directory}/Library/Preferences/Adobe/Custom File Info Panels
    Windows
    \Program Files\Common Files\Adobe\\Custom File Info Panels
    \Documents and Settings\<user>\Application Data\Adobe\Custom File Info Panels
    I actually do not understand how to write a panel but here is the actual panel:
    <?xml version="1.0">
    <!DOCTYPE panel SYSTEM "http://ns.adobe.com/custompanels/1.0">
    <panel title="$$$/CustomPanels/Acro/PanelName=Gen Photo (Private Collection)" version="1" type="custom_panel">
    group(placement: place_column, spacing: gLargeSpace, horizontal: align_fill, vertical: align_top)
    group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
      static_text(name: '$$$/AWS/FileInfoLib/Panels/Description/DateCreated=Date Scanned:', font: font_small_bold_right, vertical: align_top);
      date_static_text(fbname: '$$$/AWS/FileInfoLib/Panels/Description/DateCreated=Date Scanned', name: '$$$/AWS/FileInfoLib/Panels/DateCreated=Created', xmp_path: 'CreateDate', horizontal: align_fill, vertical: align_top, truncate: true, locked: true);   
    group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
      static_text(name: '$$$/CustomPanels/Genealogy/Provider=Provider:', font: font_small_bold_right, vertical: align_top);
      edit_text(fbname: '$$$/CustomPanels/Genealogy/Provider=Provider', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'Credit', vertical: align_top);
      mru_popup(xmp_namespace: photoshop, xmp_path: 'Credit', container_type: alt_struct, no_check: true, vertical: align_top);
    group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
      static_text(name: '$$$/CustomPanels/Genealogy/Provenance=Provenance:', font: font_small_bold_right, vertical: align_top);
      edit_text(fbname: '$$$/CustomPanels/Genealogy/Provenance=Provenance', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'Provenance', container_type: alt_struct, v_scroller: true);
      mru_popup(xmp_namespace: photoshop, xmp_path: 'Provenance', container_type: alt_struct, no_check: true, vertical: align_top);
    group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
      static_text( name: '$$$/CustomPanels/Genealogy/DescriptionProvidedBy=Description Provided By:', font: font_small_bold_right, vertical: align_top);
      edit_text(fbname: '$$$/CustomPanels/Genealogy/DescriptionProvidedBy=Description Provided By', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'DescriptionProvidedBy', vertical: align_top);
      mru_popup(xmp_namespace: photoshop, xmp_path: 'DescriptionProvidedBy', container_type: alt_struct, no_check: true, vertical: align_top);
    group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
      static_text( name: '$$$/CustomPanels/Genealogy/DescriptionSurety=Description Surety:', font: font_small_bold_right, vertical: align_top);
      edit_text(fbname: '$$$/CustomPanels/Genealogy/DescriptionSurety=Description Surety', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'DescriptionSurety', v_scroller: true);
      mru_popup(xmp_namespace: photoshop, xmp_path: 'DescriptionSurety', container_type: alt_struct, no_check: true, vertical: align_top);
    group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
      static_text(name: '$$$/CustomPanels/Genealogy/Description=Complete Subject Description:', font: font_small_bold_right, vertical: align_top);
      edit_text(fbname: '$$$/CustomPanels/Genealogy/Description=Complete Subject Description', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'Description', container_type: alt_struct, v_scroller: true);
      mru_popup(xmp_namespace: photoshop, xmp_path: 'Description', container_type: alt_struct, no_check: true, vertical: align_top);
    group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
      static_text( name: '$$$/CustomPanels/Genealogy/Caption=Informal Subject Description:', font: font_small_bold_right, vertical: align_top);
      edit_text(fbname: '$$$/CustomPanels/Genealogy/Caption=Informal Subject Description', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'Caption', v_scroller: true);
      mru_popup(xmp_namespace: photoshop, xmp_path: 'Caption', container_type: alt_struct, no_check: true, vertical: align_top);
    group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
      static_text( name: '$$$/CustomPanels/Genealogy/MediaDescription=Media Description:', font: font_small_bold_right, vertical: align_top);
      edit_text(fbname: '$$$/CustomPanels/Genealogy/MediaDescription=Media Description', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'MediaDescription', v_scroller: true);
      mru_popup(xmp_namespace: photoshop, xmp_path: 'MediaDescription', container_type: alt_struct, no_check: true, vertical: align_top);
    group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
      static_text( name: '$$$/CustomPanels/Genealogy/Annotations=Annotations:', font: font_small_bold_right, vertical: align_top);
      edit_text(fbname: '$$$/CustomPanels/Genealogy/Annotations=Annotations', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'Annotations', v_scroller: true);
      mru_popup(xmp_namespace: photoshop, xmp_path: 'Annotations', container_type: alt_struct, no_check: true, vertical: align_top);
    group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
      static_text( name: '$$$/CustomPanels/Genealogy/SpecialEditing=Special Editing/Alterations:', font: font_small_bold_right, vertical: align_top);
      edit_text(fbname: '$$$/CustomPanels/Genealogy/SpecialEditing=Special Editing/Alterations', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'SpecialEditing', v_scroller: true);
      mru_popup(xmp_namespace: photoshop, xmp_path: 'SpecialEditing', container_type: alt_struct, no_check: true, vertical: align_top);
    group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
      static_text( name: '$$$/CustomPanels/Genealogy/City=City/County:', font: font_small_bold_right, vertical: align_top);
      edit_text(fbname: '$$$/CustomPanels/Genealogy/City=City/County', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'City', vertical: align_top);
      mru_popup(xmp_namespace: photoshop, xmp_path: 'City', container_type: alt_struct, no_check: true, vertical: align_top);
    group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
      static_text( name: '$$$/CustomPanels/Genealogy/State=State:', font: font_small_bold_right, vertical: align_top);
      edit_text(fbname: '$$$/CustomPanels/Genealogy/State=State', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'State', vertical: align_top);
      mru_popup(xmp_namespace: photoshop, xmp_path: 'State', container_type: alt_struct, no_check: true, vertical: align_top);
    group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
      static_text( name: '$$$/CustomPanels/Genealogy/Country=Country:', font: font_small_bold_right, vertical: align_top);
      edit_text(fbname: '$$$/CustomPanels/Genealogy/Country=Country', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'Country', vertical: align_top);
      mru_popup(xmp_namespace: photoshop, xmp_path: 'Country', container_type: alt_struct, no_check: true, vertical: align_top);
    group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
      static_text( name: '$$$/CustomPanels/Genealogy/PhotoDate=Photo Date:', font: font_small_bold_right, vertical: align_top);
      edit_text(fbname: '$$$/CustomPanels/Genealogy/PhotoDate=Photo Date', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'DateCreated', vertical: align_top);
      mru_popup(xmp_namespace: photoshop, xmp_path: 'DateCreated', container_type: alt_struct, no_check: true, vertical: align_top);
    group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
      static_text( name: '$$$/AWS/FileInfoLib/Panels/Description/Keywords=Keywords:',font: font_small_bold_right, vertical: align_top);
      cat_container_edit_text(fbname: '$$$/AWS/FileInfoLib/Panels/Description/Keywords=Keywords',horizontal: align_fill, height: gTextViewHeight, xmp_path: 'Keywords', container_type: bag_struct, v_scroller: true);
      mru_popup(xmp_path: 'Keywords', container_type: alt_struct, no_check: true, vertical: align_top);
    </panel>

    You are not going to be able to run your old system from the backup on this old computer as the hardware is incompatible.
    You need to get a new computer or a refurbished one.

  • Importing into iPhoto, edited RAW photos from Photoshop CS3

    I edit all my photos in Photoshop CS3. Sometimes I just batch edit many of them. But when I import these edited images, iPhoto only shows them in unedited form. How do I import these edited images into iPhoto, and yet maintain the edits.
    I am a professional photographer, and the only reason I need to import these images into iPhoto, is that I use the web galleries as the viewing tool for my clients.
    Thanks.

    coxpix:
    When iPhoto imports a RAW file it creates a jpg version of it for display and editing with by iPhoto. Therefore, when you edit a RAW with CS3 you must import the new edited version, of whatever format you chose to save as, and use that one. It's the nature of the beast. All edits to RAW files when saved must be saved as a new file.
    For what it's worth, the following may be of some help in using CS3 with iPhoto:
    Using iPhoto Library Manager to Rebuild Your iPhoto Library
    1 -Download iPhoto Library Manager and launch.
    2 -Click on the Add Library button, navigate to your User/Pictures folder and select your iPhoto Library folder.
    3 - Now that the library is listed in the left hand pane of iPLM, click on your library and go to the File->Rebuild Library menu option
    4 - In the next window name the new library and select the location you want it to be placed.
    5 - Click on the Create button.
    Note: This creates a new library based on the LIbraryData.xml file in the library and will recover Events, Albums, keywords, titles and comments but not books, calendars or slideshows. The original library will be untouched for further attempts at fixing or in case the rebuilt library is not satisfactory .
    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto (iPhoto.Library for iPhoto 5 and earlier) database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
    I've created an Automator workflow application (requires Tiger or later), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 6 and 7 libraries and Tiger and Leopard. Just put the application in the Dock and click on it whenever you want to backup the dB file. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.
    Note: There's now an Automator backup application for iPhoto 5 that will work with Tiger or Leopard.

  • Canon 5D RAW files not opening in Photoshop CS3

    Windows Vista Home Premium SP1.
    Hey Ho!
    I did a photoshoot at a friend's studio last week, using his Canon 5D as it was all set up with the lights etc etc.
    He saved the files for me as RAW - *.CR2 - as I am used to using with my 450D. The only difference I can see is that his files are numbered like this:
    _MG_1791.CR2
    whereas mine would have an "I" at the front - like it would be:
    IMG_1791.CR2
    I cannot open his files in my Photoshop CS3 - I get the error "Cannot complete your request as it is not the right type of file" or similar. I have no problems opening my own CR2 files from my 450D.
    I have searched this issue on the Adobe forums, as well as other photography forums, and they say to download the plugin update remove the old one and replace it with the new. I have tried following step-by-step, but I still can't get it to work.
    If anyone has come across a similar problem, I would be greatful to hear what you did.
    Thanks in advance.

    I am trying the DNG converter again, and it seems to be converting this time - maybe I didn't do it right last time... I hope that CS3 will be able to read the DNG files - will let you know how it goes shortly!

  • IPhoto cannot import certain JPEGs created from Photoshop CS3

    recently I found out, that if I save a JPEG from a zip compressed TIFF file via Photoshop CS3 it will not import into iPhoto '08.
    Only if I save the JPEG from an uncompressed TIFF file it will import.
    I think iPhoto is much to picky ...

    You did get it imported OK though, didn't you? You can report that to Apple via http://www.apple.com/feedback/iphoto.html.
    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto (iPhoto.Library for iPhoto 5 and earlier) database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
    I've created an Automator workflow application (requires Tiger or later), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 6 and 7 libraries and Tiger and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.≤br>
    Note: There now an Automator backup application for iPhoto 5 that will work with Tiger or Leopard.

  • Powershell: How do I upload files with metadata from a manifest file?

    I am using the script from this blog to try to upload files into SharePoint, using a manifest file to specify the metadata associated with each file. Right now, the script works, but is not populating
    the metadata from the manifest (xml) file. When I write the $metadataManifest variable out to the console, I get the contents of my xml file, so the code is reading the file when it should. However when it gets to the line in bold ($metadataManifest.Columns.Column),
    it does not go into that block...it just skips on to checkin the file. Again the $metadataManifest variable shows all the content in my xml manifest file. Here is what the script looks like...
    #Get web and document library objects
    $web = Get-SPWeb "http://companySite"
    $Library = "My Library"
    $docLibrary = $web.Lists[$Library]
    $ManifestFilePath = "C:\PowerShellScripts\Manifest.xml"
    $LocalPath = "C:\Upload\Test Upload\My Upload Directory\"
    if ($ManifestFilePath)
    $metadataManifest = (Get-Content ($ManifestFilePath))
    write-host "Manifest file: " $metadataManifest
    else
    write-host "Manifest file not specified for categorising uploaded documents"
    #Check for the LibraryStartFolder parameter to specify a root folder
    if ($PSBoundParameters.ContainsKey('LibraryStartFolder')) {
    $folder = $web.GetFolder($docLibrary.Title + $LibraryStartFolder)
    else
    $folder = $docLibrary.RootFolder
    #Attach to local folder and enumerate through all files
    if($IncludeSubFolders) {
    $files = Get-ChildItem $LocalPath -Recurse
    else
    $files = Get-ChildItem $LocalPath
    $files | ForEach-Object {
    #Check if the object is a folder - if so, create it in doc library
    if ($_.PSIsContainer) {
    if (($IncludeSubFolders) -and (!$FlattenStructure)) {
    #Generate folder path for creation in SharePoint
    #by looking at the parent folder on the local path
    $spFolderPath = ($_.Parent.FullName.Replace($LocalPath,"")).Replace("\","/")
    #Get the folder into which the new folder will be created
    #by adding the folder path generated above, if one existed
    if ($spFolderPath -eq "") {
    $currentFolder = $web.GetFolder($folder.Url)
    else
    $currentFolder = $web.GetFolder($folder.Url + $spFolderPath)
    #Check to see if subfolder already exists
    #and create it if not
    $testFolder = $currentFolder.SubFolders[$_.Name]
    if ($testFolder -eq $null) {
    write-host "`nAdding folder" $_.Name "to" $docLibrary.Title "in" $web.Title "..." -foregroundcolor Green
    $newFolder = $currentFolder.SubFolders.Add($_.Name)
    else
    write-host "`nFolder" $_.Name "already exists in" $docLibrary.Title "and shall not be created" -foregroundcolor Red
    else
    #Generate file path for upload into SharePoint
    if ($FlattenStructure) {
    $spFilePath = ("/" + $_.Name)
    else
    $spFilePath = ($_.FullName.Replace($LocalPath,"")).Replace("\","/")
    $spFullPath = $folder.Url + "/" + $spFilePath
    #Check if the file exists and the overwrite option is selected before adding the file
    if ((!$web.GetFile($spFullPath).Exists) -or ($Overwrite)) {
    #Add file
    write-host "`nCopying" $_.Name "to" $spFullPath.Replace("/" + $_.Name,"") "in" $web.Title "..." -foregroundcolor Green
    $spFile = $folder.Files.Add($spFullPath, $_.OpenRead(), $true)
    #$spFile = $folder.Files.Add($folder.Url + "/" + $file.Name, [System.IO.Stream]$fileStream, $true)
    $spItem = $spFile.Item
    #Walk through manifest XML file and configure column values on the file
    $metadataManifest.Columns.Column | ForEach-Object {
    #Single value text columns
    try
    if (($_.Type -eq "Text") -or
    ($_.Type -eq "Choice") -or
    ($_.Type -eq "Boolean") -or
    ($_.Type -eq "Number") -or
    ($_.Type -eq "Currency")) {
    $columnName = $_.Name
    write-host "Setting value on column"$columnName "..." -foregroundcolor Blue
    $_.Values.Value | ForEach-Object {
    $spItem[$columnName] = $_
    write-host "Value set to"$_
    catch {}
    #Multiple line text column
    try
    catch {}
    #Multiple choice columns
    try
    catch {}
    #Hyperlink columns
    try
    catch {}
    #Single User column
    try
    catch {}
    #Multiple User column
    try
    catch {}
    #Single value Managed Metadata column
    try
    catch {}
    #Multi value Managed Metadata column
    try
    catch {}
    #Update document with new column values
    $spItem.SystemUpdate($false)
    #Check in file to document library (if required)
    #MinorCheckIn=0, MajorCheckIn=1, OverwriteCheckIn=2
    if ($CheckIn) {
    if ($spFile.CheckOutStatus -ne "None") {
    $spFile.CheckIn("File copied from " + $filePath, 1)
    write-host $spfile.Name"checked in"
    #Approve file (if required)
    if ($Approve) {
    if ($spItem.ListItems.List.EnableModeration -eq $true) {
    $spFile.Approve("File automatically approved after copying from " + $filePath)
    if ($spItem["Approval Status"] -eq 0) { write-host $spfile.Name"approved" }
    else
    write-host "`nFile"$_.Name "already exists in" $spFullPath.Replace("/" + $_.Name,"") "and shall not be uploaded" -foregroundcolor Red
    $web.Dispose()
    And here is what the manifest file looks like...
    <?xml version="1.0" encoding="utf-8"?>
    <Columns>
    <Column Name="Column1" Type="Text">
    <Values>
    <Value>First File</Value>
    </Values>
    </Column>
    <Column Name="Column2" Type="Text">
    <Values>
    <Value>12585</Value>
    </Values>
    </Column>
    <Column name="Column3" type="Text">
    <Values>
    <Value>Some Data</Value>
    </Values>
    </Column>
    <Column name="Column4" type="Text">
    <Values>
    <Value>More Data</Value>
    </Values>
    </Column>
    </Columns>
    <Columns>
    <Column Name="Column1" Type="Text">
    <Values>
    <Value>Second File</Value>
    </Values>
    </Column>
    <Column Name="Column2" Type="Text">
    <Values>
    <Value>9876</Value>
    </Values>
    </Column>
    <Column name="Column3" type="Text">
    <Values>
    <Value>Some Data2</Value>
    </Values>
    </Column>
    <Column name="Column4" type="Text">
    <Values>
    <Value>More more Data</Value>
    </Values>
    </Column>
    </Columns>
    I can't figure out what am doing wrong...why my script is not iterating through the manifest file to upload the document along with the metadata. I would really appreciate any help. Thanks

    Hi Spawn,
    Name should not be a problem.. I will probably post you the entire code (I modified it to meet your goals for having multiple column xml nodes as well)
    For the code snippet below:
    a. In powershell all my changes will have ## prefixed comments
    b. in XML I have changed one column name to "Name" to replicate your case and also added a parent node for making the xml well formed.
    and the SharePoint output
    Please see the code below
    $web = Get-SPWeb "http://intranet/sites/test"
    $Library = "My Library"
    $docLibrary = $web.Lists[$Library]
    $ManifestFilePath = "D:\Manifest.xml"
    $LocalPath = "D:\UploadPath\"
    if ($ManifestFilePath)
    ##read the xml file as an xml object
    [xml]$metadataManifest = (Get-Content ($ManifestFilePath))
    write-host "Manifest file: " $metadataManifest
    else
    write-host "Manifest file not specified for categorising uploaded documents"
    #Check for the LibraryStartFolder parameter to specify a root folder
    if ($PSBoundParameters.ContainsKey('LibraryStartFolder')) {
    $folder = $web.GetFolder($docLibrary.Title + $LibraryStartFolder)
    else
    $folder = $docLibrary.RootFolder
    #Attach to local folder and enumerate through all files
    if($IncludeSubFolders) {
    $files = Get-ChildItem $LocalPath -Recurse
    else
    $files = Get-ChildItem $LocalPath
    $counter=0
    $files | ForEach-Object {
    #Check if the object is a folder - if so, create it in doc library
    if ($_.PSIsContainer) {
    if (($IncludeSubFolders) -and (!$FlattenStructure)) {
    #Generate folder path for creation in SharePoint
    #by looking at the parent folder on the local path
    $spFolderPath = ($_.Parent.FullName.Replace($LocalPath,"")).Replace("\","/")
    #Get the folder into which the new folder will be created
    #by adding the folder path generated above, if one existed
    if ($spFolderPath -eq "") {
    $currentFolder = $web.GetFolder($folder.Url)
    else
    $currentFolder = $web.GetFolder($folder.Url + $spFolderPath)
    #Check to see if subfolder already exists
    #and create it if not
    $testFolder = $currentFolder.SubFolders[$_.Name]
    if ($testFolder -eq $null) {
    write-host "`nAdding folder" $_.Name "to" $docLibrary.Title "in" $web.Title "..." -foregroundcolor Green
    $newFolder = $currentFolder.SubFolders.Add($_.Name)
    else
    write-host "`nFolder" $_.Name "already exists in" $docLibrary.Title "and shall not be created" -foregroundcolor Red
    else
    #Generate file path for upload into SharePoint
    if ($FlattenStructure) {
    $spFilePath = ("/" + $_.Name)
    else
    $spFilePath = ($_.FullName.Replace($LocalPath,"")).Replace("\","/")
    $spFullPath = $folder.Url + "/" + $spFilePath
    #Check if the file exists and the overwrite option is selected before adding the file
    if ((!$web.GetFile($spFullPath).Exists) -or ($Overwrite)) {
    #Add file
    write-host "`nCopying" $_.Name "to" $spFullPath.Replace("/" + $_.Name,"") "in" $web.Title "..." -foregroundcolor Green
    $spFile = $folder.Files.Add($spFullPath, $_.OpenRead(), $true)
    #$spFile = $folder.Files.Add($folder.Url + "/" + $file.Name, [System.IO.Stream]$fileStream, $true)
    $spItem = $spFile.Item
    ## ensure we pick the corresponding node in the columns xml (first file, first xml node, second file - second node likewise)
    #Walk through manifest XML file and configure column values on the file
    $metadataManifest.FileData.Columns[$counter].Column | ForEach-Object {
    #Single value text columns
    try
    if (($_.Type -eq "Text") -or
    ($_.Type -eq "Choice") -or
    ($_.Type -eq "Boolean") -or
    ($_.Type -eq "Number") -or
    ($_.Type -eq "Currency")) {
    $columnName = $_.Name
    write-host "Setting value on column"$columnName "..." -foregroundcolor Blue
    $_.Values.Value | ForEach-Object {
    $spItem[$columnName] = $_
    write-host "Value set to"$_
    catch {}
    #Multiple line text column
    try
    catch {}
    #Multiple choice columns
    try
    catch {}
    #Hyperlink columns
    try
    catch {}
    #Single User column
    try
    catch {}
    #Multiple User column
    try
    catch {}
    #Single value Managed Metadata column
    try
    catch {}
    #Multi value Managed Metadata column
    try
    catch {}
    #Update document with new column values
    $spItem.SystemUpdate($false)
    ##increment the counter to read the next xml node
    $counter++
    #Check in file to document library (if required)
    #MinorCheckIn=0, MajorCheckIn=1, OverwriteCheckIn=2
    if ($CheckIn) {
    if ($spFile.CheckOutStatus -ne "None") {
    $spFile.CheckIn("File copied from " + $filePath, 1)
    write-host $spfile.Name"checked in"
    #Approve file (if required)
    if ($Approve) {
    if ($spItem.ListItems.List.EnableModeration -eq $true) {
    $spFile.Approve("File automatically approved after copying from " + $filePath)
    if ($spItem["Approval Status"] -eq 0) { write-host $spfile.Name"approved" }
    else
    write-host "`nFile"$_.Name "already exists in" $spFullPath.Replace("/" + $_.Name,"") "and shall not be uploaded" -foregroundcolor Red
    $web.Dispose()
    and the xml file
    <?xml version="1.0" encoding="utf-8"?>
    <FileData>
    <Columns>
    <Column Name="Name" Type="Text">
    <Values>
    <Value>First File</Value>
    </Values>
    </Column>
    <Column Name="Column2" Type="Text">
    <Values>
    <Value>12585</Value>
    </Values>
    </Column>
    <Column name="Column3" type="Text">
    <Values>
    <Value>Some Data</Value>
    </Values>
    </Column>
    <Column name="Column4" type="Text">
    <Values>
    <Value>More Data</Value>
    </Values>
    </Column>
    </Columns>
    <Columns>
    <Column Name="Name" Type="Text">
    <Values>
    <Value>Second File</Value>
    </Values>
    </Column>
    <Column Name="Column2" Type="Text">
    <Values>
    <Value>12585</Value>
    </Values>
    </Column>
    <Column name="Column3" type="Text">
    <Values>
    <Value>Some Data</Value>
    </Values>
    </Column>
    <Column name="Column4" type="Text">
    <Values>
    <Value>More Data</Value>
    </Values>
    </Column>
    </Columns>
    <Columns>
    <Column Name="Name" Type="Text">
    <Values>
    <Value>Third File</Value>
    </Values>
    </Column>
    <Column Name="Column2" Type="Text">
    <Values>
    <Value>12585</Value>
    </Values>
    </Column>
    <Column name="Column3" type="Text">
    <Values>
    <Value>Some Data</Value>
    </Values>
    </Column>
    <Column name="Column4" type="Text">
    <Values>
    <Value>More Data</Value>
    </Values>
    </Column>
    </Columns>
    <Columns>
    <Column Name="Name" Type="Text">
    <Values>
    <Value>Fourth File</Value>
    </Values>
    </Column>
    <Column Name="Column2" Type="Text">
    <Values>
    <Value>12585</Value>
    </Values>
    </Column>
    <Column name="Column3" type="Text">
    <Values>
    <Value>Some Data</Value>
    </Values>
    </Column>
    <Column name="Column4" type="Text">
    <Values>
    <Value>More Data</Value>
    </Values>
    </Column>
    </Columns>
    <Columns>
    <Column Name="Name" Type="Text">
    <Values>
    <Value>Fifth File</Value>
    </Values>
    </Column>
    <Column Name="Column2" Type="Text">
    <Values>
    <Value>12585</Value>
    </Values>
    </Column>
    <Column name="Column3" type="Text">
    <Values>
    <Value>Some Data</Value>
    </Values>
    </Column>
    <Column name="Column4" type="Text">
    <Values>
    <Value>More Data</Value>
    </Values>
    </Column>
    </Columns>
    </FileData>
    Thanks and Regards,
    Partha
    AvePoint

  • Preview has taken over RAW file type binding from Photoshop

    Preview v 3.0.4 has taken over as the default program with which to open RAW files. Double-clicking a RAW file in OS 10.3.9 or earlier (?) used to automatically open RAW files into the latest Photoshop version installed (be it 7, CS, CS2).
    After purchasing a new Dual 2.7 G5 with Tiger 10.4 or 10.4.4, ALLL RAW ICNS have changed to a PREVIEW.app's icon for RAW images, and RAW files now default to Preview when double-clicked, instead of the Photographer's choice of Photoshop, as it has been for years.
    These and other file type bindings (PDF) have been captured by Preview in the new OS.
    What is going on? What to do? How do I regain the original file binding of RAW files to an intelligent and professional program (PHTOSHOP CSx), instead of this NEWBIE nearly unusable PREVIEW application?
    Simply remove all PREVIEW resources? Then it's usefulness for browsing large numbers of images will be lost.
    I simply want PREVIEW to leave my professional digital world alone and let me continue working efficiently.
    Any help? Ideas?
    Thanks a bunch,
    jes360

    Simply select one of your crw files, do GetInfo (command-i) on the file and in the Open With section choose Photoshop. Click the Apply to All button. From now on all crw files will open in Photoshop. I suspect the default changed because Preview can now open many many raw files, and not everyone has Photoshop.
    Francine
    Schwieder

Maybe you are looking for