> The only one solution I can propose is to export sitegroup record information > into different file and require to import it with admin priviledges > _before_ importing whole sitegroup data itself. > > What do you guys think?
This is what I already expected. It ensures the hard 'DNA' of the new organism to be recognised in the new body :-)) What about the soft relation to the new sitegroup ? Will it be konsistent ? E.g I tried to avoid sitegroup mismatch by creating SG1 by hand on the target midgard before importing from source midgard sitegroup with an existing SG1 Following your advice the sitegroup to be importet should keep both kind of identification: The GUID and the SG level e.g.1 or 2, that all data is related to. What if the SG to be importet already exists on the new midgard ? dieter -- Kind regards Dieter Heine Systemadministration Unix Astrium GmbH Raumfahrt Bremen EMail: [EMAIL PROTECTED] Fax: 49 421 539 5698 Phone: 49 421 539 4989 User Help Desk Astrium Hamburg Phone (office Bremen): on request --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
