This conversation has been merged. Please reference the main conversation: Lightroom: LR4 "TIP" - avoiding data loss converting LR1/LR2/LR3 Local flags... (and a BUG report)
Apologies for adding another topic on this issue, but the previous threads seem old, and possibly overlooked; one was even marked as "Implemented" which is counter to noting the resultant data losses created by LR4's mandated global status flags.
The new, all or nothing, global flag behavior is a major step backwards (for those who understand the old, much more powerful local behavior).
Sorry to be late to the party, BUT, this "new" global flag behavior is REALLY damaging to our information (and to our other colleagues and our workshop students).
All the (considerable) collection-based selection criteria we have in LR3 is wiped out when "upgrading" to LR4. Simply put, this is a DATA LOSS, which we'd consider to be a bug.
For instance, we have many individual collections that contain particular Client Proofing selections via the Picked/Rejected flags. Such collections often contain overlapping images. One client might want to order Image123 (so click "Select") in their collection, but the next client may not (so click "Reject") in their own collection. Similarly, their particular "maybe's" are left unflagged. With the new global behavior, the last one to change a status wipes out all other's preferences.
With LR4 we can no longer allow recording this proofing (without a huge hassle of maintaining separate, little catalogs for each client/job/interaction/output type - and then the little catalogs become outdated/out of synch with master changes, etc.). It seems like a big step backwards.
Similarly, we have various collections containing output jobs that use Local status selections (and ordering) for what was/wasn't included in a given job. Examples include various Calendars, Books, and even Gallery Shows. All this information is destroyed by LR4.
Pretty, pretty please can you revert the local vs global flag behavior to a simple Preference? (since it sounds like "local" was confusing too many folks, then "global" could be the default pref).
Please don't go the way Apple seems to be heading, in "dumbing down" your products, and create a Lowest Common Denominator situation.
Either way, the level of manual/power user/pro control seems to be inconsistent. How many folks who can't figure out the difference between local and global selections are going to be able to figure out separate RGB curves?
Lightroom/Photoshop are amazing, crucial tools for any serious photographer. Please consider not crippling parts of the incredible product as you advance others!