Sharing PSE7 Organizer keywords with Bridge?

Question

I want to share my existing PSE7 Organizer keywords with Bridge. I searched the forums and found an some answers to use PSE7's "File/Write Keyword Tag and Properties Info to Photo" menu option. I did some tests with that option, and it appears to only do what I'll refer to as "additive writes," meaning it will add keywords in PSE7 Organizer for a particular photo, but it will not remove any keywords which are presently in the photo file but not in Organizer's informaton for the same photo file.
I'm guessing this is the case because PSE7 Organizer cannot assume the keyboard already in the file originally came from Organizer itself, or that the user (regardless of where an existing keyword came from) wants to remove a keyword if it's not in Organizer for the same file. It would be nice if there were a preferences option which one could select such as "Replace all keywords when writing to file" so that a user like myself could make Organizer's keywords the main keywords.
Does anyone happen to know if I understand this correctly, or is there a way to remove a PSE7 Organizer-written keyword from a file (based on its non-existence in PSE7 Organizer for the same file)?
If there is no way around this, I'm wondering if it may be better to do things the Bridge-way (which seems more like the general standard) since it seems to always keep the current info in the file, so the state is always with the file itself. Even if some features are missing, it may be better than dealing with this sort of PSE7-only feature. Any comments on this would be great to hear.
Thanks for any insight on this,
Tom

Answer 1

Okay, that makes sense on the Albums. I wasn't aware that Albums were ordered.
I was using Bridge some more after my post yesterday, and I was seeing that with PSE7, both Albums and Keyword items seem more readily accessible regardless of location of the items (photo files) because there isn't an extensive file system search required since the DB provides a quick search (assuming first-searches and no pre-existing caching in Bridge).
I started testing Collections with Bridge, and realized that it was sort-of doing that. This is another aspect of Bridge which is sort of a "db" aspect of Bridge in that it requires the browser to persist data seperate from the photo file. .
What can be a little frustrating about any browser-persisted informaton (such as that for Collections) is to not find anything in the docs about how to ensure one gets a good backup of that info. PSE7 does a great job of providing a feature to do just that. Recall this is one thing I really liked about PSE7 when I was unaware of the benefits of Bridge's "minimalist db" approach (where a "db" in Bridge is anything persisted by itself such as Collections).
The "how to" backup app-persisted information (aside from docs a user saves, where the user knows the location) is a must for any pro-am or pro person, if not an end user. People don't want information that is key to something they're building over time to be persisted in some mysterious unknown location. I couldn't find what I wanted in Bridge docs, so I did my own hunting, and found Bridge Collection information hiding in "%APPDATA%\Adobe\Bridge CS4\Collections" (i.e., c:\Users\<user_name>\Roaming\Adobe\Bridge CS4\Collections" on my laptop) in files named "<collection_name>.filelist". But even with that info, I, as a user, would still have to test to ensure I could get a backup good enough for disaster recovery / restoration. I'm a relatively technical user so I cannot imagine what "Dad" or "Mom" would do. This sort of thing is bothersome only because it's remedied with at least a small paragraph in the docs. What would it take to say "Backing Up Bridge Information: If you have a backup program which backs up the "%APPDATA%\Adobe\Bridge CS4" you will have all necessary data to restore the information that Bridge maintains. You must ensure you backup your photo files..." etc. etc. Without that, I have to do a bunch of hunting and testing. 
All that said, I see how Collections, maintained by Bridge, offer some of that PSE7 power where you don't have to search for files in various locations to find what is already noted in a central Bridge file or "db" such as a Collection for which Bridge has a list of files in the Collection itself. (If Collections could contain other Collections, that would be a nice touch. I didn't see that ability.)
What I still like about Bridge's approach is that while Albums don't exist, and while Collections are hierarchical, there's a feeling that Bridge is not taking things over where you are forced to use that app. It persists some items relating to its organizational features, but keeps the rest of the info right in the photo file. Still a nice balance. Another nice thing about this minimalist approach is that there's no importing per se. Everything is browseable/maintainable since the file system is the photo db.
All that said, I can see where PSE7 does things for the non-power user such that they can just use, say, an Album, which has a familiar name, and behaves like an Album with ordering and whatnot. A user like me doesn't need that since I can use tools to create an Album like effect, so the Bridge approach wins since I can fend for myself in areas were I don't see PSE7 to hand hold.