Aperture as a general photo managment tool

Hi
has any one used aperture as a general photo management tool, i mean has any body used to manage 40 gb of RAW photos on their hard drive. does any body has any tip on how to manage large volume of photos using aperture.
using the vult would only back the libarary photos and i am not sure how i can export photos to clear some harddisk space at the same time be able to access them using aperture.
is there any web site or books about "how to manage you photo library "
thanks

Jeff - I have a PB and have no issues using the external Lacie FW800 with this. What's really neat is once I have it mapped right in preferences on both the G5 and PB, I can go anywhere and still have the most updated records go with me, eg ratings etc. The problem with running dual systems is when you for example add a keyword on one system - it is written within the local system, not in the Aperture library, so it is not in the menu when used on the other system.
Also, what's totally awesome (although somewhat slower) is when I can't be bothered disconnecting the Lacie from the G5, I simple turn on the G5, grab the PB and go sit in the lounge or wherever. I can then map (through wifi) the Lacie as one of my drives and HEY PRESTO it still works as if it was hooked up (minus the faster speed, as stated above). It maybe slower but less clutter for sure.

Similar Messages

Is there a photo management tool/plug-in?

I'm still test-driving LR. It's development functionality is really superb. Far better than any PP tool I've used in the past.
One shortcoming that I find with LR, though, is its photo management tool. I used ACDSee Phto Manager, among others, in the past, the photo management function in ACDSee was really good and intuitive. The following functions were really convenient in ACDSee that I find missing in LR.
Grouping (in addition to sorting) by almost any criteria - original date, day taken, month taken, camera, focal length, etc.
Displaying any number of attirbutes - camera, resolution, size, etc.
convenient batch renaming
Easy copy and move
As you can see, these are all file management functions. Does LR have these functions as well?
If not, maybe I'll have to use two tools after all - LR for development, and ACDSee Photo Manager for file management.

Certainly, Lightroom is a photo management tool that compares well with ACDSee. There are probably advantages and disadvantages to each, but everything on your list is present in LR except the display of resolution (if by that you mean pixels per inch of the photo).
Grouping like this can be done via the filter bar or smart collections
The metadata panel displays attributes
F2 renames in batches
Moving photos is done via the folder panel. LR does not make copies, as the Lightroom paradigm does not include making actual copies; it does include virtual copies. You of course can create copies via a different tool, File->Export. You can make copies in your operating system.
But if you want LR to have the same workflow/features/ease of use/etc, as ACDSee (or Bridge, or Photoshop Elements, or any other program), let's be honest, it does not. Programs work differently. You will have to learn the methods and mechanics of each program. Each has its pros and cons, and LR has many "pros" to its photo management tools.

Re-locating metadata after migration to Aperture 3 from ACDSee photo manager

Hi all,
Do you have experience from migrating a photo library from ACDSee Photo Manager 2009 (PC-software) to Aperture 3 with relevant metadata following each jpeg picture? Specifically, how to re-locate the metadata entered to ACDSee in Aperture 3 after importing the pictures to Aperture library?
ACDSee uses XMP to embed database information in each file (MGIF, JPG, DNG, PNG, and TIF file formats). Thus the database information (e.g. categories, keywords, descripitons etc) can be embedded inside the file ... and they should be usable when using other photo libraries... but apparently not. ACDSee Photomanager apparently does not copy the database information to IPTC fields but uses some other place in the files to store it. As a result I cannot re-locate the metadata once I've imported the pictures to Aperture.
Any advises on how to use Aperture to find the "lost" metadata is appreciated.
regards

I've faced the same problem too, and am making a little progress. The most important metadata for me is the rating (I'm still working on keywords etc) and I've managed to port that to Aperture by embedding it in an unused IPTC field in ACDSee and then searching for that field in Aperture, setting the rating as I go.
Would love to hear some suggestions for setting the keywords, especially ones that don't cause Aperture to crash.

Aperture vs. iView as a photo manager

So, I've been reading a lot of the pro's and con's of aperture as a raw conversion tool, but I haven't been able to really find anybody talking about the pros/cons of Aperture as simply a photo management tool against programs such as iView. Opinions? Basically I'm wondering if it's going to be beneficial to buy the program now, learn the interface and use it as I would use iView so that once they get all the bugs worked out I can start doing my raw conversions with it as well.

They really are difficult to compare, as each does things the other doesn't. And you are asking about Aperture's strongest features.
I have not yet used iView 3, so my comments are about 2.6, 3 has some new features that compare favorably to Aperture
So my take:
iView:
Pro -
Handles very large libraries (I currently have about 85000 images in my iview catalog)
Handles images regardless of where they are stored (online, offline, across many drives, dvds, tapes, whatever)
Extraordinarily fast
Very robust file-format support
Fantastic slideshow and web export, adequate contact sheets
Extremely deep (and correctly implemented) metadata support
Seamlessly integrates with all third-party "helper apps" - whatever, and however many you choose
Con -
No side-by-side compare
No raw editing
Limited file conversion options
Can be a little sluggish when importing (not when viewing) raw files
Raw support depends on third-party drivers
Slightly clunky interface
Aperture -
Pro -
Beautiful, realtime interface
Stacks
Raw editing (though low-quality)
Versions
Side-by-side viewing/comparing
Con -
Files locked up in local library
Only handles online, local files
No archiving support
Very limited file-format support
Poorly implemented metadata support (ignores metadata from other apps, does not export metadata to other apps)
Poorly implemented "external editor" support (very difficult to access raw files)
Limited slideshow/web export. Adequate contact sheets
Very poor quality exported files
Basically - if Aperture could handle files from multiple locations (especially offline files) it would completely clobberize iView. But it doesn't, and although the side-by-side compare and stacks and versions are wonderful, Aperture's library and "doesn't play well with others" attitude makes it a mediocre (if not outright poor) digital asset management tool at this point in time.

I just put snow leopard 10.6.8 on my macbook pro and I was told that I could purchase Apature for photo management- now its says I need a different version.... is there an older version I could get? so frustrating.

I just put snow leopard 10.6.8 on my macbook pro and I was told that I could purchase Apature for photo management- now its says I need a different version.... is there an older version I could get? so frustrating.

The current version of Aperture requires 10.7.5 or later.
Upgrade Paths to Snow Leopard, Lion, and/or Mountain Lion
You can upgrade to Mountain Lion from Lion or directly from Snow Leopard. Mountain Lion can be downloaded from the Mac App Store for $19.99. To access the App Store you must have Snow Leopard 10.6.6 or later installed.
Upgrading to Snow Leopard
You can purchase Snow Leopard through the Apple Store: Mac OS X 10.6 Snow Leopard — Apple Store (U.S.). The price is $19.99 plus tax. You will be sent physical media by mail after placing your order.
After you install Snow Leopard you will have to download and install the Mac OS X 10.6.8 Update Combo v1.1 to update Snow Leopard to 10.6.8 and give you access to the App Store. Access to the App Store enables you to download Mountain Lion if your computer meets the requirements.
     Snow Leopard General Requirements
       1. Mac computer with an Intel processor
       2. 1GB of memory
       3. 5GB of available disk space
       4. DVD drive for installation
       5. Some features require a compatible Internet service provider;
           fees may apply.
       6. Some features require Apple’s iCloud services; fees and
           terms apply.
Upgrading to Lion
If your computer does not meet the requirements to install Mountain Lion, it may still meet the requirements to install Lion.
You can purchase Lion by contacting Customer Service: Contacting Apple for support and service — this includes international calling numbers. The cost is $19.99 (as it was before) plus tax. It's a download. You will get an email containing a redemption code that you then use at the Mac App Store to download Lion. Save a copy of that installer to your Downloads folder because the installer deletes itself at the end of the installation.
     Lion System Requirements
       1. Mac computer with an Intel Core 2 Duo, Core i3, Core i5, Core i7,
           or Xeon processor
       2. 2GB of memory
       3. OS X v10.6.6 or later (v10.6.8 recommended)
       4. 7GB of available space
       5. Some features require an Apple ID; terms apply.
Upgrading to Mountain Lion
To upgrade to Mountain Lion you must have Snow Leopard 10.6.8 or Lion installed. Purchase and download Mountain Lion from the App Store. Sign in using your Apple ID. Mountain Lion is $19.99 plus tax. The file is quite large, over 4 GBs, so allow some time to download. It would be preferable to use Ethernet because it is nearly four times faster than wireless.
     OS X Mountain Lion — System Requirements
       Macs that can be upgraded to OS X Mountain Lion
         1. iMac (Mid 2007 or newer) — Model Identifier 7,1 or later
         2. MacBook (Late 2008 Aluminum, or Early 2009 or newer) —
             Model Identifier 5,1 or later
         3. MacBook Pro (Mid/Late 2007 or newer) — Model Identifier 3,1 or later
         4. MacBook Air (Late 2008 or newer) — Model Identifier 2,1 or later
         5. Mac mini (Early 2009 or newer) — Model Identifier 3,1 or later
         6. Mac Pro (Early 2008 or newer) — Model Identifier 3,1 or later
         7. Xserve (Early 2009) — Model Identifier 3,1 or later
To find the model identifier open System Profiler in the Utilities folder. It's displayed in the panel on the right.
Are my applications compatible?
         See App Compatibility Table — RoaringApps.
     For a complete How-To introduction from Apple see Upgrade to OS X Mountain Lion.

Is Aperture for me? (Photo organisation for a non-professional)

I'm not a professional photographer, I'm just looking for a way to better organise my personal photos. However I am a graphic designer and know my way around editing photos and I have some of RAW files too.
So, currently, my iPhoto library is a wasteland- mostly duplicates that I imported at some point for some reason or another.
The rest of my photos are simply in named folders. I have about 200 gigs of the stuff, going back to 2006 (plus older ones on other drives)
Currently, I simply use cover flow and quick view to browse photos. It works surprisingly well, but it's no match for a proper solution (geotagging, face recognition, creating books, flagging, rating, etc.)
So, if you use Aperture, I'd love to ask you:
• Is Aperture your primary photo organisation tool, or do you also continue to use the finder or other solutions at the same time?
• How is storing photos on an external drive handled in Aperture? Is it easy, or does it involve a lot of dragging stuff around and messing up your existing events/albums?
• Once photos are stored on an external.. how do you back them up in case that drive fails?
• On the Apple "iPhoto to Aperture" page, they say iPhoto and Aperture share their libraries. So what happens to photos Aperture has moved to an external drive, do they disappear from iPhoto?
• How's the speed? I always found iPhoto to be slow and unresponsive. I do have the 13" MBP from 2010 (2.4 Ghz, Intel Core 2 Duo) but it does everything else smoothly so I fail to see what is so intense about iPhoto to justify the poor performance.
I plan to upgrade to a new MBP, so maybe this is a moot point.
• Is importing all my old photos gonna be pretty straightforward? I'd assume Aperture will take the dates on the files, rather than the date I import them.
• Since I never used iPhoto much, I don't get the difference between an Event and an Album- though I assume that events are for separating photo dumps (say, your visit to italy and your skiing trip) and albums are for combining an arbitrary set of photos (for instance your best travel photos featuring images from italy and the skiing trip among others), so when you delete one from an album, the image is still in the event, but if you delete from an event, it goes to the trash?... is this correct?
• any other advice you may have
Thanks!

I will comment on some of the items and exclude the external drive questions as I use a 'Managed' library on the internal drive.
• Is Aperture your primary photo organisation tool, or do you also continue to use the finder or other solutions at the same time?
I use Aperture specifically for organizing, viewing and enhancing images from my camera (with one proviso noted at end of this section). Since I use Photoshop and Illustrator to create composites and other graphic images, I keep that type of work outside of Aperture and use Bridge to view those in the finder disk structure. Basic line of thought here is just like iTunes is for music files, Aperture is for camera image files.
Although I could hold composite PSD files from Photoshop inside the Aperture library, I don't simply because I don't know if Apple may decide not to support those fully in the future. I used to keep PSD files in the library, but moved away from that practice.
Note - the proviso mentioned above is that I do have one Project that contains imported composites and rasterized Illustrator files that I wish to sync with iDevices. This is the only place I keep anything other than JPEG or RAW original camera files in the library.
• How's the speed? I always found iPhoto to be slow and unresponsive. I do have the 13" MBP from 2010 (2.4 Ghz, Intel Core 2 Duo) but it does everything else smoothly so I fail to see what is so intense about iPhoto to justify the poor performance.
I plan to upgrade to a new MBP, so maybe this is a moot point.
Aperture's speed depends on what you are doing in the program. Importing many images can take a little time, but no more so than other programs (e.g., Lightroom or even Bridge - which has to build it's cache). Face detection can take some time if you have a lot of faces in the images, but once it completes it is done.
Making adjustments to images can be quick in most of the adjustment bricks and HUD's, although; the retouch and skin softening brushes can become slower when you are adding a lot of local adjustments. This is no different than in Lightroom or Adobe Camera RAW when using brushes. Photoshop actually edges out these programs if you use layers and masks when brushing as far as processing speed goes, but that takes time to create a layer > fill > brush adjustment. Since Aperture does the masking for you on the fly, the speed is pretty much a wash.
Note - if iPhoto is slow and unresponsive on your machine, it may be due to something in the library database being the issue. However, it seems that most software creators (Apple, Microsoft, Adobe, etc.) always want to take advantage of the leading edge hardware when possible, which can lead to depleted performance in underpowered machines. With your machine, I would probably look at the library first aid items to improve performance though as iPhoto should be able to run decently.
• Is importing all my old photos gonna be pretty straightforward? I'd assume Aperture will take the dates on the files, rather than the date I import them.
Importing is easy and you have a number of options. Aperture will read the metadata of the image files and if the date and time are there, you can use that as the naming scheme if you wish. I would suggest reading the bit about file naming presets here:
http://documentation.apple.com/en/aperture/usermanual/index.html#chapter=4%26sec tion=6%26tasks=true
I will leave the external drive ideas to others who run a reference library as they will have much better information than I can provide.
• Since I never used iPhoto much, I don't get the difference between an Event and an Album- though I assume that events are for separating photo dumps (say, your visit to italy and your skiing trip) and albums are for combining an arbitrary set of photos (for instance your best travel photos featuring images from italy and the skiing trip among others), so when you delete one from an album, the image is still in the event, but if you delete from an event, it goes to the trash?... is this correct?
In either iPhoto or Aperture, you have to import image before the programs know about them and therefore before you can work with them in the program. iPhoto uses 'Events' to hold imports and Aperture uses 'Projects'. They are really the same thing - a container for the imported images.
In both programs, Albums are manually created collections of 'aliases' to the imported images that reside inside the Events / Projects. If you delete an image alias in an Album, it only removes the link to the image in the Event / Project. If on the other hand you delete the imported image from the Event / Project, then it will remove the image as well as any aliases to that image that you have created in Albums.
In both programs, if you delete an image from the Event / Project where it resides, it will go to the program's internal Trash first. If you then emtpy that internal Trash via command, it will go to the Finder trash. Note - you can put an image back from the program's internal Trash without re-importing. If you send to the Finder trash, you will need to re-import the image if you want to replace it.
Both programs also incorporate 'Smart Albums' which are created using filtering criteria and remain dynamic. Meaning any current image that meets the filter criteria will be shown as well as any future image that meets said criteria (either via import, ranking, keyword, adjustment, etc.).
Note - the library structures in both programs don't really mirror the file structure on disk. While you can try to set it up that way (and many users may well do that) - I just felt it was too time consuming for me. So I just use Aperture like I do iTunes. Camera image in > organize > enhance as needed > enjoy.
One thing in Aperture that is really nice is a feature called 'Quick Preview Mode'. With the click of a button or a keyboard press, you can tell Aperture not to worry about rendering an adjustable version and just show you the image as it currently is. Really great for cruising the images. Just remember to switch off the Quick Preview Mode when you want to make adjustments.
http://documentation.apple.com/en/aperture/usermanual/index.html#chapter=5%26sec tion=7%26tasks=true
Hope that helps.

As an asset management tool it should manage all images but only adjust raw

Is Aperture an image management tool, raw converter/workflow tool, or both?
Let it be both! Restrict what is is ALLOWED to ADJUST, but manage it all.
When I do a shoot, I start out with 300-1000 RAW images.
By the time I am finished with the client I will have narrowed the pile of image assets down to 20% of the original RAW files, JPGs of all of those, AND 10% of the selected originals will also end up as layered PSD/TIFF files. But when I go back in and want to open a PSD file then why not allow just that Then save it back as the same or a version..
OR when I tell it to open a PSD file in CS2 it will as "make a version(full or flat), or edit original?" and of course a "don't ask me again for this format" check box!
So why not leave the layered PSD/TIFF files alone and NOT allow them to be adjusted, only managed?
Think about it, IF I want to adjust my multilayered PSD file I will most definitely only trust that to CS2 where I retain full creative control over the layers, and I can output a version if I want!
IF I am crazy enough to feel the need to use the shallow tools of Aperture to tweak the brightness/level/curves/saturation/WB/etc/etc of a flattened COPY of my layered PSD file then I will make a copy and drag it into Aperture. By shallow I mean that CS2 and layers has much more control than the single layer tools of Aperture.
As an option leave it open as a configuration choice in the prefs... "Adjustable image formats: RAW, JPG" and even on a per image basis, right-click--> image status-->Adjustable or Unadjustable.
Yes, I sent this idea off to Apple!

Moki,
Right there with you. Here's my rough scenario:
1. I shoot 500 RAWs.
2. Cull down to 100 keepers.
3. Client culls down to their 50 selects.
4. Anywhere from 25-50 become layered PSD files, depending on the presentation the client wants (sizes, packages, borders, special effects, etc.).
5. In addition to those 25, there may be *completely new* composites (PSD's) created from combinations of the 25 -- this isn't a version of one of the original masters -- it is a *completely new* image that Aperture needs to manage in the project (so import of PSD without flattening and/or allowing Photoshop to Save-As into the Aperture library is a must).
I'd even add to your request about allowing adjustments. It would be totally cool if the adjustment tools were context-sensitive, enabled when working with an image (like RAW or JPG) where Aperture can adjust, and disabled when working with an image (like layered PSD or TIFF) that it won't adjust.
Anyway, I have complete confidence that eventually, the RAW conversion will be fixed, so even though that's an immediate glaring issue, it doesn't seem to me to be the long-term workflow killer. Being able to traverse this editing stage of the workflow with Photoshop is crucial. Without this, its basically
a complete project export after the initial organization stage, and the rest of the workflow is either managed entirely in another tool, or a complete pain to bring back into Aperture for output, which leaves files strewn everywhere for backup and archiving.
Brad

Disk Management Tool error in Disk Utility

Update: (first, reviewing problem that I and others have been having, including on 10.4.x systems):
When I attempt to repair permissions on my HD with Disk Utility, I get this specific error message: "Disk Utility internal error -- Disk Utility has lost its connection with the Disk Management Tool and cannot continue. Please quit and relaunch Disk Utility" and the repair-permissions will not proceed. It fails to get the proper "correct" permissions info for that drive to allow the repair. The error log points to a file in the Library called "DiskManagementToll" The path is ~/System/Library/PrivateFrameworks/DiskManagement.framework/Resources/DiskManag ementTool)
This problem is appearing in many forums here and elsewhere, including 10.4.x systems (like mine) and persists in a few after deleting suggested files. Is there a sophisticated solution that addresses the problem through the DiskManagementTool file by replacing some values or replacing the file from a backup vis SUDO or Root?
Previous posts have focused on Macs running 10.3.x and with iTunes 6.0x installed. Not here, so the problem is more general. None of the "delete iTunes / plists / Chess.app" suggested fixes have worked for me. Also tried running DU from my Tiger install disk; no luck! -- still fails when it tries to determine the correct permissions.
The "DiskManagementTool" file apparently either stores the correct file permissions or handles reading them from the receipts in the Library. If I understand things right, Disk Utility is actually a (user)-permissioned graphic front end, while DiskManagementTool is a Root-user-level tool that actually does the heavy lifting. Can I replace -- and any benefit to that -- or rewrite it with proper access?
There is a complete crash log report in Crash Reporter, by the way. Anyone want the text, and would it help figure out what's happening?
I've tried the suggested deletion of iTunes 6.0.2 or Chess.app and their plists (these and other steps were suggested on MacFixIt at http://www.macfixit.com/article.php?story=20060111090035797 the advice is, basically, to delete iTunes 6.0.2 and/or Chess.app and related plist files.) As I said, no luck!
Everyone that I talk to says it MUST be the fault of some other 3rd-party disk utility software.
For what it's worth, I HAVE run Disk Warrior -- and, the drive that's having the problem is a recent reinstall from a backup using Carbon Copy Cloner. The original disk is NOT having such a problem, only the hard drive on my iBook after the reinstall. Don't know if that gives any clues (or to how the link gets somehow disengaged between Disk Utility and the Disk Management Tool file / software).
Any thoughts on that? What about replacing the Disk Management Tool file in the Library or forcing some kind of re-link to it? some Unix guru MUST know a fix!
Obviously, the big worry for me is that I can't update my System to 10.4.5 or anything else without repairing permissions first. This IS a big deal. And others are having the same problem. Help?!?
New 2 GHz dual g5 , Dual g4, & iBook G4 (recent) Mac OS X (10.4.4)

A system problem was involved that became, briefly, a "known issue" that was solved in the next minor update. Solved, anyway, by the advice given by the last poster. Thanks! SJ

Photo Management for old (import) & new pictures

Below is a proposal for organising my photo management system.
I'm a hobbiest photographer with over 30 years of pictures to file. I have read extensively, including this forum and sort best practice to developed a plan to do achieve an organised scalable system.
I would appreciate sharing of experience by providing comments on my suggested plan of action and questions I raise below.
My Objective:
Organise and manage existing legacy photos and provide a system for future photos that is not tied into specific system or vendor. For example where possible Metadata free from vendor specific format or database.
Background:
My collection consists of many photos in over 50 folders, these are:
a) Scanned picture that are now JPGs,
b) Shot JPG,
c) Raw (new and existing).
I files my pictures on my PC & external back up copy.
I file: /my pictures/<YYYY>_<MM>_<Location_Event> for example: /my pictures/2013_04_Yorkshire_Family_Weekend.
On some of my digital pictures I have included the Metadata using Google Picasa v3. Most of my scanned pictures have no Metadata as yet.
I own and aim to use Lightroom 4 to do Post Production and photo filing and management whilst also continuing to use Google Picasa for viewing & Face Recognition (at least until I feel fully confident in Lr).
Suggested plan of attack:
Stage 1)
Add "My Picture" folder, including sub folders to Lightroom Library, Standard View.
Stage 2)
Continue with /my pictures/<YYYY>_<MM>_<Location_Event>
For example: /my pictures/2013_04_Yorkshire_Family_Weekend.
Stage 3)
Use Lr to apply to both existing and new photos file name format as follows: <My Initials>_<YYYYMMDD>_<Key_Words Inc_Location_Event_Description>_<sequence xxxx>
For example:RB_20130420_Peru_Cusco_Holiday_Shots_0001
NB: Regarding Version Control for RAW I will use Lr inc use of "Virtual Copies", for Jpeg I will use additional field for Developed JPEGs of <vX>
For example:RB_20130420_Peru_Cusco_Holiday_Shots_0001_v01.jpg
Stage 4)
Manually use Lr to add Metadata & Ratings to all pictures to date.
Metatdata: Include "My Name" to all pictures, "Date" by Windows folder, "Keyword" by folder, "Additional Keyword" to 3* and above.
Rating: 1&2* no action required, 3*+ maybe further editing if time permits.
Stage 5)
Run "Save Metadata to file" in Lr. This will run Metadata to file for JPG and to XMP side car for RAW files.
Stage 6)
Import new shots to new folder using "/my pictures/<year><month number><event>" structure. As they are in sub folder they will be included automatically to Lr library.
Stage 7)
Create JPG in same folders as RAWs for Developed Photos.
Stage 8)
Back up "My Photos" and Lr dbase on regular basis as per Lr best practice.
Questions:
1) Is Lr more powerful than Google Picasa for Renaming File & Adding Metadata?
2) Once I "Save Meta Data to Photo" in Lr will I be able to access it in Google Picasa?
3) Can I automate the Importing of new shots to Lr and have it maintain / build upon my existing file structure?
4) Any recommendations for Keyword Schema to include in Metadata?
5) Does my approach above seem sensible?

Honestly, if your goal is to have metadata that is not tied into a specific system or vendor, then here's what I would do:
I would not put any effort at all into organizing your folders (or improving the organization of the folders), or renaming files, as I think your time is better spent on keywords. In my opinion, the benefits of keyword organizing are many; in addition, without you putting any effort into reorganizing your folders, you can also search for you photos by date inside Lightroom using Lightroom tools regardless of the folder structure (and you can search this way inside of any other photographic management software I have used as well, regardless of the folder structure).
In Lightroom assign whatever keywords and metadata are appropriate, and then instruct Lightroom to write the metadata to the files. There are two ways to do this, one is Ctrl-S, and the second is to turn on the option in Preferences that does this automatically (Edit->Catalog Settings->Metadata) Once the metadata has been written by Lightroom, you now have metadata that can be read by any photographic software (and even all major operating systems) that I know of. Having keywords in the file name is redundant, it doesn't help you find photos and faster but it does require extra work; and there is a limit to the number of characters you can have in a path\filename.
Another point ... don't use Lightroom collections or pick flags as part of this "metadata that is system and vendor independent", as Lightroom does not write this information to the files.
You ask for Keyword schema, but without knowing what your photo's subject matter is, there's no way I could give any advice.

Aperture doesn't display some managed masters

My Aperture 3.5.1 library has 11,000 referenced masters plus 1000 managed masters (mostly images saved from shared photo streams). Recently, Aperture has started listing some of the managed masters as missing. I replace them from backups but then other managed masters go missing (usually just after I import some new managed images). Referenced masters never go missing. I have tried all three library repair options including rebuilding the database, but the problem keeps recurring. I've checked the drive with Disk Utility and found no problems.
Today, I tried using "Relocate Masters" to move all 1000 managed masters to a folder on the same drive and then discovered that the Masters folder in the library package still contained over 3000 photos that had not been moved and are not displayed by Aperture when I search for managed masters. Presumably, these are the files that went missing. Rebuilding the library located 16,0000 versons in the progress bar but the final rebuilt library displays only 12,000 versions even with all stacks open and "Showing All".
I'm tempted to manually drag the 3000 "forgotton" masters from the Masters folder using the Finder and then try a rebuild. Everything else is working and I have Time Machine and other backups available in case this causes major problems. Alternatively, I could just leave the 1.6 GB of orphaned files alone and stop using managed masters entirely.
Any ideas on why these managed files are not recognized by Aperture?

I think I have figured out where the “orphaned" photos in the managed masters folder came from.
To recapitulate: I emptied the Masters folder inside the library package by using finder to drag all images to the system trash and then emptied the trash.
I then rebuilt the Aperture library. When I turned on iCloud in Aperture preferences it spent 30 minutes downloading the shared photo streams from my children.
Each photo stream was copied to the Aperture Masters folder in its own folder. Example:
Only the single image in the top folder (which corresponds to “My Photo Stream”) shows up when I search for managed masters in Aperture. The others are hidden from the user. Thus, the images from the shared photo streams ARE NOT MANAGED FILES despite being in the Masters folder. This appears to be by design.
When I unsubscribe from a shared photo stream, the corresponding folder is deleted from the managed masters folder. Thus, Aperture in OS X appears to use the managed-masters folder for temporary storage of shared streams. I suspect that the database that keeps track of these files may have become corrupted in my library. We’ll see if deleting these files and rebuilding the library fixes the problem.
These same photo stream images were also downloaded to the user Library at ~/Users/dickweis/Library/Application\ Support/iLifeAssetManagement/assets/sub/. However, there are many older images in this location that have not been modified in years and were not deleted when I deleted the contents of my photo stream and turned off iCloud sharing in Aperture.
Léonie, you previously advised using Aperture to delete these files (see https://discussions.apple.com/message/19375439#19375439). However, most of these files are no longer accessible to Aperture or iPhoto and appear to be orphans. If I continue to have problems, I will be tempted to drag these to the system trash to see if it helps (I have saved the images I want to keep). Any advice here would be welcome.

Updating photo management strategy with add'l laptop?

Hello -
I have added a new MacBook Air to a set of computers - old MacBook, older iMac. The iMac hard drive bit the dust earlier this year so it has a brand new 750 GB hard drive with Mavericks installed. That's the background to wanting to updating my photo management / storage strategy now that I have an additional computer.
I keep my iPhoto library on an external drive connected to my desktop (the iMac) and have since the beginning - that baby is about 350 GB and isn't updated b/c now I've had photos on the Macbook and don't want to get into the same habit with the new MB Air. I take a lot of photos, decent amount of video but it's all personal, not my profession. My camera shoots with 10 - 15 MB size per photo though, so it adds up. I use SmugMug to share my photos (and online backup strategy) - the process on a good day is to pull the photos off my camera, do any editing, upload the ones I want to share to Smugmug, then save/store the originals.
I'd like to consolidate now that I've got a new computer in the mix - and storage drives keep keep getting bigger and less expensive. ;-)
My current thinking is to get a NEW big external storage drive and set it up to be ONLY a repository for photos and video. I'd likely use that storage drive with a main iPhoto library (or whatever software I use) on the desktop, especially since it's now on an updated OS.
What I'm debating is whether I should go with the larger storage of a desktop storage drive - or go with the portable with the largest storage capability just in case I *ever* want to take it and use it with the laptop (now or in the future)?
Does that seem like a sound strategy? Thoughts? Thanks!
P.S. A good thing to add is that the iMac has only Firewire 800 available, unfortunately (and USB obviously). The MacBook Air has thunderbolt. If I use a Thunderbolt storage drive on the iMac it would need a converter (which I think will slow it down - but is that slower than the usual Firewire 800 speeds?) If I use a Firewire 800 storage drive with the iMac, I'd need a converter if I went to use it with the Macbook Air - not ideal, but not going to happen very often.

1. You need two drives: one to hold the Photos and one to be a back up for that.
2.
What I'm debating is whether I should go with the larger storage of a desktop storage drive - or go with the portable with the largest storage capability just in case I *ever* want to take it and use it with the laptop (now or in the future)?
Well, as you need both, I'd get one of each, and keep the portable outside the house - even in your car.
SmugMug is excellent as off-site storage (as is Flickr) for your photos. But if whatever you choose to manage your apps has a library of any form, then you need to also back that up. And everything pretty much uses a Library - Picas, iPhoto, Aperture, Lightroom etc - of some form or other.
The thunderbolt to Firewire adaptor will not make an appreciable difference in performance. But frankly, I'd go for USB, I'm not sure of the long term prospects for Firewire.

Photo Management through Dropbox and without iPhoto

Good evening,
I have finally made the jump back from iPhone to BB and i'm loving it. Go Blackberry!!!
The ability to port some apps from android has bridged most of the gaps from the store.
My biggest show stopper right now is getting dropbox to sync my photos and for blackberry link not to use iPhoto to sync photos with my computer. I would like to select a folder of pictures that i want synced and select a folder where i want the new camera to be synced.
Does anyone have any tricks that i could use to facilitate my photo management through dropbox and BBLink? If these are features being worked on I'd appreciate to get an idea how long it will take to get it.
Thank you very much and happy holidays.
Mathieu

1. As a consultant I have to suggest my client whether they should go for interface between sap and eternal recording system or not... What you guys suggest which one is better.
If your client wish to go for postive time management it is must for you create interface either you willing to say or not.
Without that interface you can't do time positive time management
2. I came to know that there is a standard interface(HR PDC) in sap to interact with ecternal recording system. I want to know how this Sap interact with external recording system i.e. online or offline using this interface.
I belive this needs some third party tool to intract with PDC. then you have use time evaluation status TMSTA 1 according to PDC
I belive it bit differnt from what you are looking for.
please tell me what kind of time terminal your client is using at the moment?
Best Regards

Photo Management App

I am interested in an app to handle some relatively basic activities for organizing photos on my iPad: moving copying, folder management, etc. I prefer simplicity and elegance to a bunch of features.
Thank you for your thoughts on this.
-Bruce

Yes indeed, one of the stranger shortcomings for the iPad.
SortShots is a powerful photo organizing tool for iPad: it retains the photo's EXIF data, including the original filename, and you can create tags and apply them to the photos. You organize your photos into "sorts" based on these tags. Searches can be done on filenames and tags. You can send photos to other apps and save them to the Photo Library if you want. However, you cannot send them to an editor, edit them, and then save them back to SortShots automatically. Your photos in SortShots do not appear in the iPad Photo Library or any of its "albums." They are synched as data in the SortShots App.
The only way that I can see to edit photos from SortShots is to save a photo to the Photo Library on the iPad, open it in an iPad photo editing App, save the edited the image back to the Library (yes, it's a new file and does NOT retain the EXIF data from the original), and then import that edited version back into SortShots. THEN you can delete the original version and rename the edited image with the filename of the original and enter the original tag and other metadata. Yikes.
However, I don't think that there is any other photo organizer App as powerful as SortShots right now. The iPad was built as a photo viewer of photos that primarily exist back on your computer where they are organized and edited and then synched back onto the iPad.

Web content management tools for enterpise portal

I'm currently trying to research web content management tools for enterprise portal.
My general requirements are:
- Tool should sit on top of the portal/km and not require another landscape infrastructure, in other words we don't need another document management repository, but rather a way an easier interface to KM.
- Should be geared towards end-user management of actual content. In other words IT provides the site framework and the business user handles the rest, with approvals with business unit
- Compatible with EP 7.0
My research so far has turned up two possible solutions:
- Webpage composer delivered by SAP
- EasyWCM by btexx
Are there any other solutions that people are using which might meet these needs or alternative web content management tools that could live with the portal on the same physical hardware environment? I have searched this forum and ecohub and have not found much besides this thread which is now almost 4 years old:
https://forums.sdn.sap.com/click.jspa?searchID=24164203&messageID=448870
Thank you,
Stephen

Hi Stephen
I'm not aware of too many other options than the ones already mentioned here. Also Iu2019m probably not the right person to ask as I have been part of the development team for the KMD product. So Iu2019m a bit biased on that part.
You could try to have a look at this presentation where other WCM solutions are mentioned (page 5):
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d07b5354-c058-2a10-a98d-a23f775808a6
However if you are looking for a WCM solution with no extra landscape infrastructure and low initial setup effort you are (in my opinion) down to 3 options (Web Page Composer, Btexxu2019s or KMDu2019s product). I think all of them can be used for external content. Try to have a look at this web site u2013 made entirely with the web page composer:
http://www.kmd.dk
It was no easy task but it can be done.
Martin

RE: [REQ] Assisted management tools/methods for planshierarchies(imp/ex

Hi William, and all forté subscribers.
Thanks for your answers.
To discuss on honest basis, let's say we don't plan to buy any product yet.
But the 'small' forté code management is source of many problems.
We're interfacing the 'workspaces handling' with text-based source control
tools, and this (can) allows proper 'control'. Shame we can't build forté
applications from proper text files :)
Our issues are more about understanding the hierarchy between projects when
it's not documented. Therefore, quite a reverse-engineering point of view,
despite we stay in a " forte TOOL code " level.
For your information, we have Select, used as " reference " model, and as
interface to Express.
For the Issues I've expressed, here's my (current) status.
I learned 'b-tree' repositories have become standard for 3.0 (despite 2.0 had many),
and therefore we're extremely waiting for 'R.4.0' code management.
We've got a way to " visualize " plans depandancies from an exported workspace,
but this doesn't allow 'update' (lacks forté workspace cross-verification facility).
We've got another way to export a 'workspace' in both 'wex' and set of 'pex's,
and building the import script from the wex file using an intelligent grep/sed script.
Thanks for all your suggestions,
J-Paul GABRIELLI
Integration Engineer
De: William Poon[SMTP:[email protected]]
Date d'envoi: vendredi 10 juillet 1998 16:58
A: 'Jean-Paul GABRIELLI'
Cc: John Apps; Forte -- Development
Objet: RE: [REQ] Assisted management tools/methods for plans hierarchies(imp/exports, supplier plans management & external APIs control)
Hi Jean-Paul,
One of our consultants has forwarded your message to me. I am
extremely interested in learning more about your requirement. I am the
lead engineer in the Compaq-Digital enterprise organization building
component based development tools. Following are some of my thoughts as
well as questions.
William Poon, Compaq-Digital
-----Original Message-----
From: John Apps
Sent: Friday, July 03, 1998 6:40 AM
To: Forte -- Development
Subject: FW: [REQ] Assisted management
tools/methods for plans hierarchies (imp/exports, supplier plans
management & external APIs control)
From the Forte-Users newslist: I think this person is
looking for CBD tools?! Perhaps William has an answer out of his
research?
Cheers,
From: Jean-Paul
GABRIELLI[SMTP:[email protected]]
Reply To: Jean-Paul GABRIELLI
Sent: Friday, July 03, 1998 11:28
To: '00 Forte Mailinglist'
Subject: [REQ] Assisted management tools/methods
for plans hierarchies (imp/exports, supplier plans management & external
APIs control)
Hi,
I'm looking for cross-projects investigation tools, to
provide graphical understanding and management of
forté source code. Viewing/updating plans dependencies,
as well as managing external APIs calls are my
requirements.
I am not clear about this question. But I will give my best shot. Are
you looking for some form of "source profiling" or "reverse engineering"
tool where by it reads the Forte TOOL code and turn that into UML which
then can be displayed in graphical form. My understanding is that
SELECT's Enterprise has this capability for C/C++ code. They also work
closely with Forte so they might have something that will work with TOOL
code.
In order to manage international developments between
sites, applications have been split into 'components'.
Therefore, and to keep it simple, each component comes
out of a separate dedicated repository.
At integration and build time, those sets of source code
are merged together, supplier plans updated and
forté applications built.
Controlling UUIDs at export time keeps simple the reload
of new delivered versions.
But my issue is in the physical process to actually
(get) deliver(ed) those sets of source code.
Forté fscript allows to export classes, plans, or
workspaces.
Only 'plan exports' (pex) can provide a way to only
deliver plans which have to be delivered.
(i.e. without test projects, stubs or third party
products plans which could be part of the workspace).
Therefore, whereas an export script can easily be
automated (list plans, and then for each plan find it
and then export it with a meaningful name), the import
process can't, because of plans dependancies.
In order to assist that process, I would like to know if
any of you did find ways to :
1) Display in a tree view the plans hierarchy for a given
workspace, or for a given repository baseline
I don't think you can do it in Forte 3.0. But my I understanding is
that they will have this capability in Forte 4.0. But Forte people will
have more information.
2) Export from a given workspace plans as separate
files, as well as related import script (with proper sequence)
3) Get from a set of pex files a plans hierarchy and a
proper import script.
Current workaround has been first to 'batch load' all
the pex files until having them all loaded
(first go loads top providers, then more and more as
dependancies are resolved).
Another one has been spending time grep'ing from pex
files the 'includes' lines and designing on paper
the tree. But that's long and evolving.
Thanks for ideas and suggestions,
J-Paul GABRIELLI
Integration Engineer
France
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Maybe Hamish Speirs can explain it - it was his post in another thread that gave me the idea and commands to try (see http://forums.novell.com/forums/nove...r-10038-a.html).
We had a confluence of changes at the beginning of the semester (Sept) that no doubt helped contribute to the problem and yet also mask the real cause to a certain extent.
1. The Thawte cert expired and was replaced with a new cert - Thawte does not support doing renewals on NetWare. This happened around the start of Sept.
2. School semester begins. Thousands of students return.
3. We use Pcounter for pay-for-print and it uses httpstk to provide a webpage for students to authorize print jobs.
4. Printing activity in general goes way up.
5. All printers are Secure.
6. Apache, iPrint and httpstk all use the same Thawte certificate
7. The print server was also hosting the netstorage service which also uses the Thawte cert (via apache).
8. The print server was recently (August) virtualized (via p2v using the excellent Portlock Storage Manager)
Eventually I built a new NetWare vm to host print services and got a new cert so at least the netstorage and print services were no longer running together. I suspected at that point that the likely source of the abends was NetStorage since Nile and SSL were almost always involved in the abends.
After the separation the issues continued - so it wasn't netstorage's fault. Desparate searching of the 'net lead to H.'s post. The rest is history!
It has now been 9 days up uptime without a single nile/ssl related abend ( I had one abend in pcounter but services survived).
Ron
"Seasoned Greasings and Happy New Rear!"

Aperture as a general photo managment tool

Similar Messages

Maybe you are looking for