Quote:
Originally Posted by chaley
What would you do about multiplicity? Could you require that the source and destination be the same? If they are not, then you can have all sorts of bizarre behavior, such as authors being munged together because the separating ',' was deleted.
|
I'm not too worried about bizarre behavior - this is going to wipe your Library if you do it wrong. You're truly brave to make it accessible to all, although I like it.
Quote:
In any event, I think you are suggesting something like:
0. verify that source and dest have the same multiplicity.
1. get value from source
2. process it with regexp, taking into account multiplicity
3. store result in dest.
|
Essentially, yes. I envisaged step 0 as testing for a compatible field transfer. I could send a comma separated text string of tags into a comments field, even if not the other way around. I could send a single valued text into tags, etc.
I don't see any critical need to process with regexp in a single shot. Your existing regexp should do it. And, step 3 would be an append so I can append fields.