Using iPhoto with an existing directory structure on HD full of jpgs

I'm using iPhoto 6. I recently moved 7,000+ photos (jpgs) off my PC onto my new Mac harddrive. They are organized into dozens of folders and subfolders. How can I use iPhoto to work with the pics within this directory structure? I tried dragging and importing several different ways, but it never preserves my extensive directory structure (just puts them all together into one big pile). I set it not to make a copy when importing. I just want iPhoto to "point" to my existing directory structure, so I can see my folders and subfolders on the left side (and from there I'll create albums and pages stuff). Thanks, Robin

Hello, Robin,
Welcome to the discussions.
First, you have to consider that iPhoto organizes differently from what you are used to doing. It is designed to allow you to do your organizing from within iPhoto, using film rolls and albums. That way, you do not have to be concerned with how and where iPhoto stores the actual photos.
If you want to keep the same type of organization that you have now, you can import the photos one folder at a time, so that iPhoto puts each folder into a separate film roll. You can change the date on import, since iPhoto will give the roll the date of import, not the date of the photo.
To get the subfolders into folders, use the album creation feature in the Source pane and create the albums and folders to suit your organizational needs and drag the photos into the appropriate locations. One of the great features of iPhoto's album function is that you can have a photo in more than one album.
Please take a look at iPhoto's tutorial here:
http://www.apple.com/ilife/tutorials/iphoto/index.html
and some great explanations of how iPhoto is structured and works in these:
http://discussions.apple.com/thread.jspa?threadID=920223&tstart=0
http://docs.info.apple.com/article.html?path=iPhoto/6.0/en/hlp15.html
http://discussions.apple.com/thread.jspa?threadID=959413&tstart=0

Similar Messages

I would like to use iPhoto to see existing Picture folder without importing

The following is a question for Aperture, as well.
I have a huge Picture file (90G), and I do not want iPhoto to import that Picture folder thereby making a duplicate. I only want one Picture file, the existing system folder called Pictures. And I want iPhoto to "reference" those files. I have seen references to setting up iPhoto (and Aperture) to use photos in outside libraries. I have seen them called "referenced"
But I can't find a specific instruction on how to set up iPhoto to do this. And I think it is crazy to have an iPhoto library of 90G, and an aperture library of 90g (already made that mistake, want to get rid of it), because that would give me three sets pf photos, with Pictures, and iPhoto and Aperture Libraries within Pictures (that's where the Aperture library is now). And the iPhoto library is there too, but is now empty. I do not want it to be filled. The User guide says Aperture (and by inference, iPhoto) can "link" to outside photos and create "referenced" libraries.
That is what I want to do, because I do not want my files within iPhoto and Aperture, because they are too hard to handle for other purposes, like using Preview for a quick look, or using Photoshop for editing. Not to mention the waste of disk space created by 2 libraries and the Pictures folder. And the confusion over time about which Photo is the real one.
Surely there is a better way, a way to have iPhoto (and Aperture) use the existing Picture folder in OSX (Snow Leopard).
Can anyone help me here?
Just tell me there is a way to do this, please.
Hope someone can help.

Your question is based on a false premise. It makes no sense to use iPhoto, Aperture and the Finder to manage the photos. The Finder isn't a photo manager. It's a file manager. If you can't grasp that distinction then you stick with the Finder. Both iPhoto and Aperture (and Lightroom, and Picasa) are Photo Managers. The entire point of these apps is to manage the photos without recourse to the files.
If you use a Photo Manager then you don't use the Finder's Quicklook, you use the application's viewing and sharing features.
Think of it this way: would you write your novel in Word, Pages, TextEdit and Nisus Writer at the same time? And also expect to be able to read it without launching your Word Processor?
So, yes, this is crazy:
And I think it is crazy to have an iPhoto library of 90G, and an aperture library of 90g (already made that mistake, want to get rid of it), because that would give me three sets pf photos, with Pictures, and iPhoto and Aperture Libraries within Pictures (that's where the Aperture library is now).
Because you would not use all three options. iPhoto and Aperture do essentially the same job. If you've purchased Aperture then that's the one to use. It's the more powerful application.
But regardless of which you choose, when you do you give up looking at the files in the Finder, you use the Photo Manager.
, because I do not want my files within iPhoto and Aperture, because they are too hard to handle for other purposes, like using Preview for a quick look, or using Photoshop for editing.
Both apps provide integration with Photoshop. Using Photoshop via the Finder and not via the app will cause you problems.
None of these apps are like Photoshop. Photoshop is a layer based pixel editor. These other apps are Digital Asset Managers. It's not the same thing. Photoshop has no management capability at all.
And the confusion over time about which Photo is the real one.
Now you need to do some reading on Photo Managers. All of them use a Non-Destructive workflow. All of them preserve your original photos, The concept of the "real one" makes no sense when you have many possible versions based on a single master file.
You've not grasped the key distinctions in managing digital photos. You're confusing photos with files, confusing the file manager with a photo manager and have given no consideration to Digital Asset Management. I would consider these issues before going any further.
FWIW: using a referenced Library with iPhoto:
*How to do it:*
Simply go to iPhoto Menu -> Preferences -> Advanced and uncheck 'Copy Files to the iPhoto Library on Import'.
*What Happens:*
Now iPhoto will not copy the files, but rather simply reference them on your HD. To do this it will create an alias in the Originals Folder that points to your file. It will still create a thumbnail and, if you modify the pics, a Modified version within the iPhoto Library Folder.
*Some things to consider:*
1. Importing and deleting pics are more complex procedures. You have to to put the files where they will be stored before importing them. When you delete them you'll need to remove the files from the HD yourself.
2. You cannot move or rename the files on your system or iPhoto will lose track of them on systems prior to 10.5 and iPhoto 08. Even with the later versions issues can still arise if you move the referenced files to new volumes or between volumes.
3. Most importantly, migrating to a new disk or computer can be much more complex.
4. Because iPhoto has no tools for managing Referenced Files, if, for some reason, the path to the photos changes then you could find yourself resolving aliases for +each photo in the Library+ one by one.
My own opinion:
I've yet to see a good reason to run iPhoto in referenced mode unless you're using two photo organiser
If disk space is an issue, you can run an entire iPhoto Library from an external disk:
1. Quit iPhoto
2. Copy the iPhoto Library as an entity from your Pictures Folder to the External Disk.
3. Hold down the option (or alt) key while launching iPhoto. From the resulting menu select 'Choose Library' and navigate to the new location. From that point on this will be the default location of your library.
4. Test the library and when you're sure all is well, trash the one on your internal HD to free up space.
If you're concerned about accessing the files, There are many, many ways to access your files in iPhoto:
*For Users of 10.5 and later*
You can use any Open / Attach / Browse dialogue. On the left there's a Media heading, your pics can be accessed there. Command-Click for selecting multiple pics.
Uploaded with plasq's Skitch!
You can access the Library from the New Message Window in Mail:
Uploaded with plasq's Skitch!
*For users of 10.4 and later* ...
Many internet sites such as Flickr and SmugMug have plug-ins for accessing the iPhoto Library. If the site you want to use doesn’t then some, one or any of these will also work:
To upload to a site that does not have an iPhoto Export Plug-in the recommended way is to Select the Pic in the iPhoto Window and go File -> Export and export the pic to the desktop, then upload from there. After the upload you can trash the pic on the desktop. It's only a copy and your original is safe in iPhoto.
This is also true for emailing with Web-based services. However, if you're using Gmail you can use iPhoto2GMail
If you use Apple's Mail, Entourage, AOL or Eudora you can email from within iPhoto.
If you use a Cocoa-based Browser such as Safari, you can drag the pics from the iPhoto Window to the Attach window in the browser.
*If you want to access the files with iPhoto not running*:
For users of 10.6 and later:
You can download a free Services component from MacOSXAutomation which will give you access to the iPhoto Library from your Services Menu. Using the Services Preference Pane you can even create a keyboard shortcut for it.
For Users of 10.4 and later:
Create a Media Browser using Automator (takes about 10 seconds) or use this free utility Karelia iMedia Browser
Other options include:
1. *Drag and Drop*: Drag a photo from the iPhoto Window to the desktop, there iPhoto will make a full-sized copy of the pic.
2. *File -> Export*: Select the files in the iPhoto Window and go File -> Export. The dialogue will give you various options, including altering the format, naming the files and changing the size. Again, producing a copy.
3. *Show File*: Right- (or Control-) Click on a pic and in the resulting dialogue choose 'Show File'. A Finder window will pop open with the file already selected.
Using iPhoto with Photoshop:
You can set Photoshop (or any image editor) as an external editor in iPhoto. (Preferences -> General -> Edit Photo: Choose from the Drop Down Menu.) This way, when you double click a pic to edit in iPhoto it will open automatically in Photoshop or your Image Editor, and when you save it it's sent back to iPhoto automatically. This is the only way that edits made in another application will be displayed in iPhoto.
Note that iPhoto sends a copy+ of the file to Photoshop, so when you save be sure to use the Save command, not Save As... If you use Save As then you're creating a new file and iPhoto has no way of knowing about this new file. iPhoto is preserving your original anyway.
Regards
TD

Creating a Standby Database with the Same Directory Structure

Hello gurus,
I am self-learning the feature Oracle Data Guard, so I am testing it on Oracle 10g R2.
At Oracle documentation there is a section F.4.: Creating a Standby Database with the Same Directory Structure*, that explains how to create a standby database with RMAN but there is something that I don´t understand:
In the standby server, I created a database with the SID equal to production database* with the objetive to have the same directory structure, but when I try to startup nomount the standby database with pfile appear this expected error:
ORA-16187: LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes
So my question is: Is possible have the Same Directory Structure on both: Production and StandBy server?
Thanks in advanced.

Uwe and mseberg: thanks for your quick answers
I have a doubt: How can you have the same directory structure if you have differents SIDs?, for example if you follow the OFA suggestions you would must have:
On Production server: */u01/app/oracle/oradata/PRIMARY/system.dbf*
On StandBy server: */u01/app/oracle/oradata/STANDBY/system.dbf*
Or you created the directory structure manually on StandBy server? For example replacing the string STANDBY* to PRIMARY* before create the database using dbca.
Do you understand my doubt? Excuse me for my english.
Thanks.

Import already existing directory structure into DFS namespace?

Hi all,
I'm planning to migrate three file servers to a single DFS namespace and after reading the official docs and numerous blog posts I'm still unsure about the right way to do it.
The "main" server already has a share with a complex directory structure, called \\server1\team, and that share shall become the root of the new DFS namespace, lets call it \\domain.local\team.
Part of that already existing directory structure is this folder: \\server1\team\admin\communication\archive. The folder "archive" contains thousands of files in numerous folders and shall become a dfs link to another share \\server2\archive. But
before I can create the folder "archive" as a dfs link I have to create the folder "admin" in the dfs hierarchy of course, then below that the folder "communication"
Question: When I try to create a folder "admin" in the dfs namespace, I get the error message "the folder cannot be created in the namespace. The file exists."
Ok, the folder "admin" indeed exists, but how can I "import" this branch of the existing directory hierarchy into the dfs namespace?
Do I have to rename the existing folder "admin" to e.g. "admin2", then create the dfs folder "admin" and move the complete directory structure below "admin2" to "admin"? Or can I simply make the existing folder
"admin" a dfs folder?
Thanks in advance!
Regards
Christoph

Mandy, thanks for your feedback!
I have to describe my problem more precisely: creating the root of the new DFS namespace is *not* the problem. This worked for me exactly as you expained it. The problem appears when I try to create a folder below that root in the DFS namespace. If that
folder already exists in the share you cannot choose how to handle security settings but you get an error message, and that's it.
This may be helpfull to explain what I want to achieve:
Old structure:
\\server1\team - folder admin - subfolder "archive" - lots of subfolders and files
Now I want to move all files and folders from "archive" to \\server2\archive and link this share into the new DFS namespace, so that our users don't notice any change when they access that archive folder.
new structure:
1. Create DFS namespace root: \\domain.local\team -> \\server1\team   (works!)
            |
2. Create folder admin (problem!)
            |
3. Create subfolder "archive" -> \\server2\archive (not possible becaues "admin" couldn't be created)
I could perhaps create a DFS namespace with the root \\server1\team\admin\archive and link that to \\server2\archive, but I would like to avoid creating a new namespace for each share which from \\server2 which I mount into some subfolder of \\server1\team...
Thanks for reading.
Regards
Christoph

Can I use Muse with an existing website?*

I have several existing websites. A couple have more than 40,000 files already. Can I use Muse with an existing website?

Printing_Services wrote:
Why exactly does Muse not support HTML import?
Muse and HTML generators like it only deal with HTML at the very end of production... at export. These generators have their own system (not based on HTML) of arranging text & graphics and structuring page relationships. These kinds of apps have never been able to import HTML. As the world moves to more dynamic web sites (database driven and server-side scripted), it becomes even more unlikely that an HTML generator will ever import HTML.

Can i use iPhoto with my ipad2?

Is it possible to use iPhoto with an ipad2

The iPhoto app for iPad is now available. You must have iOS 5.1 installed and iPhoto will run on an iPad 2 and the new iPad. If a search in the app store does not find iPhoto yet go to the Apple Store website here:
http://www.apple.com/ipad/from-the-app-store/apps-by-apple/iphoto.html
Scroll down to near the bottom to find a link for the iPhoto app for iPad.

I can't get a full screen picture using iPhoto with yosemite. how can i do that?

i can't get a full screen picture using iPhoto with yosemite. how can i do that?

Click the green button in the top left corner.
Matt

Using already existing directory structure to create rolls

I'm converting from iView into iPhoto. I have hundreds of directories titled things like 011606.SamuelWasBorn/ with subdirectories in there called /Images /FinishedImages /WebMedium /EmailSmall etc... and then plenty of .tif and .jpegs inside of those.
I've been doing this one Cmd-Shift-I at a time, followed by a Cmd-A t select all, then a Cmd-Shift-N for a new album, followed by retyping in the name and dropping the date.
Sigh. I'm 6 weeks into this now and still only 1/4 of the way through.
Has anyone tried to drag and drop an entire directory structure into iPhoto's directory structure, fire up iPhoto, and have it recognize all that stuff as a whole bunch of new rolls that lack thumbnails? Would that work? Would iPhot then offer to update its thumbnails? And then would I be happy and fully integrated into my new iPhoto life?
I'm just a bit too chicken to give it a try. If nobody's tried this before, I'll create a test library and give it a go, but if someone has experience with doing this, I'd appreciate any pointers.
Thanks.
Oren

Oren:
Welcome to the Apple Discussions. iPhoto creates a roll with the same name for any folder of image files that are imported into it. All you have to do is select your folders of source files and drag them into iPhoto's open window.
If you want to use iPhoto's alias feature you can keep your current source folders and drag them into a library that's setup to not copy the files into it but use alias files. The library works as a conventional library with the exception that if you delete a photo from the library it does not delete the source file. That must be done manually via the Finder. I've created some Tutorials to assist users to convert over to an alias based system or go to an iView based one.
I use iView as my primary image management and iPhoto's alias feature to create a library of the same source files. That way I have the best of both applications. Also, when using the alias method, the importing process is much faster. Good luck.

An intelligent way to import already existing directory structure to Aperture

Hello,
is there an intelligent way to import already existing big directory structure of photographs (over 2TB) archive into Aperture?
I have my catalogue on a disk created in a way:
date - short shot description (i.e. “2011-02-14 Name Surname (portrait)”)
          Originals
          Converted
          PSD
          Final
I would like, when importing “date - short description”, it to become an Aperture Project with the same name and subfolders Originals, Converted, PSD and Final to become Aperture Albums or Folders in that Project.
The only way I found is to create a Project and Albums in that project manually and then import all the pictures from the corresponding folders, one-by-one, to Aperture’s Albums. I use references only to preserve the current archive structure on a disk as well.
thank you for your time.

You can try and experiment with the various options in File->Import Folders as Projects, specifically the option Import Folders as to see if you get what you are looking for but I doubt you will get exactly what you are looking for.
One way to achieve your goal would be to import the projects and then once that is done create the other entities (either folders or Albums) once and then paste them into each project.
The only way to truly automate this would be to write an Applescript and unless this is an ongoing requirement by the time you developed the script you could have just created the structure and pasted into the projects.

Problem with package and directory structure

Please... I need help with a directory/package structure that I don't understand
why it is not working...
I want to create a custom login SWF which several other SWF movies will use in case they need some kind of login logic (in this case it is a login logic... but the problem doesn't have anything to do with that logic...)
I have created a FLA movie (LOGIN.FLA) and two helper classes (MAINLOGIN.AS and MAINLOGINEVENT.AS)... they are all under the same directory, for example:
c:\
     abc\
          def\
               ghi\
                    login
In LOGIN.FLA, I have included the source path, c:\abc (for example).
MAINLOGIN.AS and MAINLOGINEVENT.AS, have both a package like:
     package def.ghi.login
MainLogin class uses MainLoginEvent (it dispatches events of that type)... but I don't have to import anything as all 3files are in the same directory...
LOGIN.FLA has its class defined as def.ghi.login.MainLogin
And that's all... now comes the problem:
1. If I leave everything as described and try to publis LOGIN.FLA, it throws error 5001 ("The name of the package def.ghi.login.MainLoginEvent doesn't reflect....) for class MainLoginEvent... don't understand why... it is placed exactly as MainLogin and has the same package definition!
2. I have tried several other options, but when I get the SWF to get published, then, the problem comes when trying to use this SWF from another movie:
The way to publish LOGIN.FLA with no errors is: MAINLOGIN.AS and MAINLOGINEVENT.AS with empty package definition ("package" alone...) and LOGIN.FLA with class MainLogin (not def.ghi.login.MainLogin)... LOGIN.FLA doesn't have to include source path to c;\abc in this case. This way, I can publish LOGIN and get LOGIN.SWF.
The problem now is how to use this information from another Movieclip... I want to be able to use and receive events of type MainLoginEvent but can't (it gives error 5001 again, on MainLoginEvent, saying that the name of the package '' doesnt' reflect....)... If I include the path to c:\abc\def\ghi\login on the FLA, then it gives errors in MainLogin when trying to use a class of its library...
Basically, the problem here is that, the movie which wants to use the LOGIN.SWF, is in c:\abc\def, and it is including the source path c:\abc, so if I import def.ghi.login.*
it is when it throws error 5001 (I understand why, but I dont know how to fix it...), but if I dont import def.ghi.login.* then I can't use MainLogin nor MainLoginEvent...
What is the good way of doing this kind of structure... mainly it is creating a SWF, which can be used from other SWF's and which can dispatch events, which the container SWF will capture...
If anyone can please give me a hint... THANK YOU!

Hi kglad , I don't understand the first point... "don't use absolute paths"... I'm not using them (or I don't understand what you mean).
For the second one... the structure is like:
c:\
     abc\
          def\
               LOGINCONTAINER.FLA
               ghi\
                    login\
                         LOGIN.FLA
                         MAINLOGIN.AS
                         MAINLOGINEVENT.AS
In LOGIN.FLA, I include the source path c:\abc, so MAINLOGIN.AS and MAINLOGINEVENT.AS have a package of "def.ghi.login", and the class for LOGIN.FLA is "def.ghi.login.MainLogin"... when trying to publish LOGIN.FLA, Flash throws error 5001 for MAINLOGINEVENT...¿?
What I want to get is a SWF (LOGIN.SWF), which can be loaded from any other SWF (in this example, LOGINCONTAINER.SWF). LOGINCONTAINER.FLA, has a class path "c:\abc" (the same as the other LOGIN.FLA, because of the directory structure), and it has to be able to receive events of type MAINLOGINEVENT... that is why it has to do an import of "import def.ghi.login.*" (for example)
Any idea of why it is not working (or how to organize it correctly)?
Thank you

How to use iPhoto with 1 photo library and 2 user accounts on 1 iMac ?

Title says it all.
I don't want to have a double picture library, it takes enough space from my harddisk already.
My wife and I share the same camera too. We want to see the same pictures when using iPhoto.
Possible solution: Do I have to make a softlink from 1 user account to the photo lib that belongs to the other account ? [in Terminal: ln /Users/.... etc.)
(Yes, I'm an ex-Linux user)
Thnx
Fred4711

If you want to have the same data, do you need separate accounts? A surprising number of people think that must have separate ccounts and they really don't need to.
Anyway:
For iPhoto 09 (version 8.0.2) and later:
What you mean by 'share'.
If you want the other user to be able to see the pics, but not add to, change or alter your library, then enable Sharing in your iPhoto (Preferences -> Sharing), leave iPhoto running and use Fast User Switching to open the other account. In that account, enable 'Look For Shared Libraries'. Your Library will appear in the other source pane.
Any user can drag a pic from the Shared Library to their own in the iPhoto Window.
Remember iPhoto must be running in both accounts for this to work.
If you want the other user to have the same access to the library as you: to be able to add, edit, organise, keyword etc.
Quit iPhoto in both accounts. Move the Library to the Users / Shared Folder
(You can also use an external HD set to ignore permissions, a Disk Image or even partition your Hard Disk.)
In each account in turn: Double click on the Library to open it. (You may be asked to repair the Library Permissions.) From that point on, this will be the default library location. Both accounts will have full access to the library, in fact, both accounts will 'own' it.
However, there is a catch with this system and it is a significant one. iPhoto is not a multi-user app., it does not have the code to negotiate two users simultaneously writing to the database, and trying will cause db corruption. So only one user at a time, and back up, back up back up.

Using iphoto with iphoto library on external hard drive

My Imac is running snow leopard with ilife '11. I have imported way too many photos into Iphoto which is really slowing it down. I'd like to put all of my photos on an external hard drive and use that as my iphoto library--which should be possible, as I gather from reading various other related posts. Another reason to put it on an external drive is so that I can use my new macbook air to edit/organize while on the go.
1. How do I set up my Iphoto library on an external hard drive?
2. How do I make sure that all future photos go to the library on that external hard drive?
3. How do I run Iphoto with the library on an external hard drive?
THANK YOU for your help!

Hello. I just transferred my iPhoto library to a Western Digital My Book for Mac external hard drive. Do you know if I needed to format this drive even though it says it's for Mac. I did not format it and there were not any instructions with the drive that said I needed to do it. The transfer seems to have worked ok but my backups from Time Machine onto Time Capsule are inconsistent. I already posed a question regarding this problem but I noticed this message regarding formating the external disk and I wonder if that is causing the problem. Thanks.

Using iPhoto with batch Photoshop Plug In?

I have a noise reduction plugin which I can batch process with PS elements, but using iPhoto, can I do that with the folder of pictures within the iPhoto library (after they've been imported)? Or, is that super dangerous to monkey with the files outside of iPhoto, so I should have done it before I imported them. If I'm applying to all the photos, it's too time consuming to click through everyone and do edit, apply the plug in, save.
Thanks for your help -
Alexa

Just a suggestion on the workflow. Doing what you suggest will give you the opportunity of rotating any portrait oriented photos you take so that when imported iPhoto doesn't have to create a rotated modified version of it. This happens with photos that come from cameras with the auto rotate feature. Turn it off and rotate them while on the desktop.
As far as uploading to the desktop I prefer using a card reader. It gives you more control and less wear and tear on the cameras ports and battery. *And it's a much faster transfer coming from a card reader.*
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.

How can I use iPhoto with Drobo? Library not copying...

I know from searching this forum that Drobo wasn't suitable for use as a host of the iPhoto Library in the past - but now that Drobo can be formatted as a Mac OS Extended (Journaled) drive, I thought the problem was solved.
However, I can't get my Library to copy over successfully from the external drive I've been using up to now, I get the following error:
The Finder can’t complete the operation because some data in “iPhoto Library” can’t be read or written. (Error code -36)
This is confirmed by the fact that the copied library is much smaller than the original: The original is 94.88gb, and the copied file is 55.57gb.
When I open the new library, no thumbnails are visible, and no photos can be opened.
What's the recommended workaround for storing and using iPhoto on a Drobo?
All help much appreciated!

The Finder can’t complete the operation because some data in “iPhoto Library” can’t be read or written. (Error code -36)
That means there is some file(s) or folder(s) within the library that cannot be copied because the permissions on them are wrong or they are damaged in some way.
The Drobo has nothing to do with it.
Workaround: use a back up app like Chronosync to copy the Library to to disk. Any back up app that makes a straight copy of the Library (rather than increments) will do the job.
Regards
TD

Using iphoto with iview

I am trying to set up a simple system for archiving and backing up photos using the best combination of iview and iphoto. As far as i understand, iphoto makes copies of the original photos to store in its own folder, and iview simply mnakes pointers to the original photos (in my case, they are all on an external harddrive).
So what i believe i have right now is an external HD with all my originals, a copy of each of these photos on my computer (created by iphoto and put into the iphoto folder), and a bunch of pointers to the originals on the HD through the iview catalog.
I was thinking it would be best to make the annotations in iview, then sync them to the originals. Will this affect iphoto as well? Will i have to re-annotate in iphoto, or is there a clever way around this?
Furthermore, what would be the best back-up strategy, in your opinion?
Does anyone use a happy combination of both programs, and if so, what does a sample workflow look like?
Thanks so much

When you sync annotation from iView back to the files, iPhoto will not read them. The only info iPhoto reads is some of the EXIF data, capture date, modify date, exposure, etc. an only during importing. If you use iView on the iPhoto library folder you should be very careful how you use it. If you create a versions folder outside the iPhoto Library folder you may be able to edit photos with iView and save the edit in the versions folder and not mess up the iPhoto library, i.e. tampering with files in the iPhoto Library folder from the Finder.
FWIW here's how I use both iView and iPhoto together.
1 - upload a shoot from the camera to my external HD and put it in my folder system, Year, shoot. (2005 folder and in that folder shoot folders titled like 05/08/05-Mother's Day/Balboa Park)
2 - add that folder to my primary image iView catalog.
3 - sequentially batch rename the files in that folder with the international date format, 2005-8-05-01.jpg, -02.jpg using iViews batch rename capability.
4 - drag that Mother's day folder into my 2005 iPhoto Library window, importing them and creating a rolls with the same title and the folder. The iPhoto library is located on my boot drive.
If I want to create a book I'll use iView to assemble the photographs I want to use in a Category. I then create a new iPhoto library just for that book and drag the photos from iView's window into the open library window. That keeps the library small and less chance for problems.
With two drives I can have two separate copies of my photos. I use iView as my primary image management application and iPhoto as a backup and books.
You can edit photos in the iPhoto Library folder with iView and save to the versions folder that you set up with iView. When viewed in iPhoto the thumbnail image will not be changed but the full size view, in the Edit window, will reflect the changes. I would be very careful in trying to operate on the photos in the library with both applications. Too much chance of something going wrong and corrupting the iPhoto library. It's best to keep separate photo collections as I've described.
Hope this has been of some help. Good luck.
OT

Using iPhoto with an existing directory structure on HD full of jpgs

Similar Messages

Maybe you are looking for