Re: [cobalt-users] CMU enhancement?

[Jeff Bilicki <jeff@xxxxxxxxxxx>]

<> wrote:
>> > I've just found an 'issue' with CMU 2.43 - is it being maintained still?
>>> The problem was, I was importing a site and hit a same username - ie, the site I was importing had a username the same as a site I had already imported from another machine - no problem, the CMU offered to quit, change or delete the user.
>>> Well... me thinking I'm smarter than this, I go and change the already existing user to another name by dropping the user, and setting up a replacement user with a different name, but the original name as an alias (it was only a user to collect online form information and forward it on, and it out from one of our own domains).
>>> The CMU continues to tell me there is a conflict - I tried to change and enter the same value, but it still says there is a conflict - ie, it doesn't check when I enter the conflicting name whether the conflict has been resolved - ie simply assumes that because the name is the same, that the conflict still exists.
>>> I know I can quit the import and run it again, but it is in the middle of a large number of imports - it's a bit of a pain to do it that way...
>>> If anyone is maintaining or enhancing the CMU, this would be a nice thing to fix.
>>
>>The conflict resolution on cmu should have handled this for you, try selecting
>>the change for the user name and add the alias after the user has been
>>importing.   My guess is that when you tried to change the user in the cmu.xml
>>file you didn't change the key that conflict checks for which I believe is the
>>username or userName field. 


> No - I removed the conflicting account attached to the domain already on the server - then tried to use change and the same name to attempt to get the NEW IMPORTED user to create properly (as I had just removed the conflicting account using a browser and the GUI) - it failed because at the point of entering the change, it doesn't check for conflicts again if the name is entered the same.

> My chosen method was to resolve the conflict myself by removing the account already known and created in a pre-existing site on the server, NOT change the one I was importing - that doesn't appear to work as it's not possible to put the same account name in, and have a conflict resolution run again, once conflict is found in the CMU, it's only possible to change the details, quit the import, or delete that user.

> In the end, I simply had to use the method you suggested, of changing the account name and using an alias - which is exactly what I was trying to avoid, as the site I was importing was a client site, the other site on the server was one of our internal domains, which I could not have cared less about.

Yup, you do have quit and re-run the conflict resolution if you make a change
to the system while cmu is running.  Scaning out the system each time a
conflict was detected was resolved proved to be too much overhead if a lot of
conflicts where found.   The thing about conflict resolution is that no real
work of import has been done when conflict resolution runs.  The import runs
only after successful completion of the conflict resolution.    

I can see how running CMU - quiting - resolving conflict - running CMU could
get very tedious.  I would suggest running cmuImport with the -C option, this
will run it in conflict-only mode.  It will not run the import (scanin) phase
of CMU.

Jeff-