Grouper Users - Open Discussion List

[Chris Hyzer <>]

Can you send me the full stack trace?

> 
> - Partial copy from one instance of Grouper to another.  For example,
>    after a set of stems and groups have been perfected on the test
>    instance, copy these to the production instance with or without
>    person members.  This is because recreating the stems and groups
>    manually in the Grouper UI is tedious and error prone.

Yeah, maybe we need another way to do this, maybe something generates GSH for 
some stems/groups/memberships/privileges...

> - Reporting: extract various informations from the exported file for
>    the purpose of checking (e.g. diff), documenting or doing statistics.

Are there things that can be done with XML that cannot easily be done with 
SQL?

> > Maybe there is a better way than the export/import tool which should work 
> > well for full registries, but obviously has issues with partial 
> > exports/imports...
> 
> What tools and methods would you suggest?

I was thinking some sort of SQL query which generates GSH, though 
concatenating isn’t a SQL standard... hmmm

> >>>   Note: uuid's will only be used on new objects...
> >>
> >> - What defines a new object when importing? the path? the uuid? The
> >>    pair path+uuid?

The name and UUID have to not match.  If either match, its not a new record...

> >> - Any risk of uuid collisions between different instances of Grouper?

Yes

> Just to be sure, with gsh -xmlimport,
> - is it OK to import an object that has a new name (e.g. it has been
>    edited by hand in the exported xml file) but has the same UUID as an
>    existing object?
> 

No, it will rename the existing record I think... if you rename in XML, you 
should change the UUID, which and search and replace it, which isn’t 
convenient

> 
> Just that it can take ages to export and then to import even a small
> stem if the subject list is large.  In the example case, export is
> done in a few seconds with the old style xmlexport and takes half an
> hour with the new style xmlexport.
> 

Yeah, we should not export all members/audits in a partial export of the non 
legacy xmlimport/export...

Thanks,
Chris