I was given a project that was never completed. It involves a large number of referenced images. I am also working on a server from across the country, so things are sluggish to begin with.
When I attempt to open this file, all the images have been moved from their referenced location (to many different locations). What I would like to do is, when I find the image, copy it in rather than change the referenced location. I don't want to reference the images, as I have no control over people moving images from one location to another. It also makes the program super sluggish when I reference the file.
So I guess what I'm asking is if there is an easy way, once I find the image while openinging the file, to copy it in rather than change the referenced location.
You can't swap from a referenced file to a copied one within FM without re-importing the graphic, which means you may also need to re-size, re-position and crop depending upon what was done to the original. You will also make the FM source file size blow up incredibly, as FM doesn't use any sophisticated compression techniques for internal graphic storage. A single JPG could add 20, 50, 100Mb or more to the file size depending upon the original image.
You really need to set up a procedures with your co-workers for handling the graphics (though it sounds like you're stuck between a rock and a hardspot in this case). The graphics never should be moved from their locations once a publication has been started. If they need them for their own documents, they should copy. But it would be even better if all you have an established repository/library set of folders that everyone can reference.
FM is known to spontaneously and randomly lose embedded graphics leaving you with an empty grey box where graphic once was. It may work fine for weeks or months, but at some point Murphy's Law comes into play and when that deadline is fast approaching - poof! [Been there...] So, if at all possible, try to keep your graphics as referenced files and find some way to get a supervisor/manager to intervene when others shuffle the files around.
I would copy all the images to ./images/
Make a log of the original filepaths.
Then, when ready to release, write a shell script that replaces all the files in ./images/ to hard links, symbolic links, shortcuts (or whatever the OS supports) pointing to the actual source images. Be sure to re-gen the document, both to ensure the links are working, and to capture any image updates.
What is your opinion on embedding graphics that serve as background on Master Pages? I've read some posts that suggest that approach.
Also, somewhat on topic... I have a file that asks to relink a missing graphic every time I open it. I've scoured the body, master, and reference pages and cannot find this graphic or it's tell-tale gray box (missing file).
I import even backgrounds on master pages by reference. In my particular case, the background is part of a cover page. Recently, the design of the cover pages was changed. All I had to do was update the ONE image file. Then when an author opened a book, the change was automatic. If the image is embedded, then you have to re-embed each document that uses it.
As Van says, I'd recommend using Referenced files. In a properly managed environment, I really see no benefit in copying a graphic file directly into FM.
The easiest way to track down the missing graphic would be in a MIF file. Look for the <ImportObFileDI pathname> entries. This specifies every imported graphics objects location.