Importing / exporting users and their permissions and settings...

We're setting up a new bric system and migrating our users
over from
an older one.  (We did this once for ETonline.com, now we're
doing it
for theINSIDERonline.com.)  We'd like to simply copy over
our users.
They're all the same and should have the same permissions. 
Is there
an easy way?  For ET we recreated them all manually.  There
aren't
THAT many but I'd rather just quickly copy them over than
manually
recreate them.

JD

I suppose the easiest way to do it is the "make
clone" which will 
duplicate your whole installation.


>We're setting up a new bric system and migrating our
users over from
>an older one.  (We did this once for ETonline.com, now
we're doing it
>for theINSIDERonline.com.)  We'd like to simply copy
over our users.
>They're all the same and should have the same
permissions.  Is there
>an easy way?  For ET we recreated them all manually. 
There aren't
>THAT many but I'd rather just quickly copy them over
than manually
>recreate them.
>
>JD


-- 
Matt Rolf, J.D.
Web Technology Analyst
Computing Services
Denison University
(740) 587-6537

yes but i don't want any of the rest of the installation. 
just the users....

On 3/28/07, Matt Rolf <rolfmdenison.edu> wrote:
> I suppose the easiest way to do it is the "make
clone" which will
> duplicate your whole installation.
>
>
> >We're setting up a new bric system and migrating
our users over from
> >an older one.  (We did this once for ETonline.com,
now we're doing it
> >for theINSIDERonline.com.)  We'd like to simply
copy over our users.
> >They're all the same and should have the same
permissions.  Is there
> >an easy way?  For ET we recreated them all
manually.  There aren't
> >THAT many but I'd rather just quickly copy them
over than manually
> >recreate them.
> >
> >JD
>
>
> --
> Matt Rolf, J.D.
> Web Technology Analyst
> Computing Services
> Denison University
> (740) 587-6537
>

On Mar 28, 2007, at 14:34, John Durkin wrote:

> yes but i don't want any of the rest of the
installation.  just the  
> users....

   bric_soap user list_ids - | bric_soap export >
users.xml
   bric_soap user create users.xml

Best,

David

On Wed, 28 Mar 2007, David E. Wheeler wrote:
> On Mar 28, 2007, at 14:34, John Durkin wrote:
>> yes but i don't want any of the rest of the
installation.  just the 
>> users....
>
> bric_soap user list_ids - | bric_soap export >
users.xml
> bric_soap user create users.xml

NB: that won't do groups/permissions.

I tried to implement groups in bric_soap once,
but it's too nasty for my brain.
(Biggest problem I think was no unique way to identify
groups,
besides the 'id' which would generally vary in different
servers.)

thanks david, for some reason i just assumed you couldn't
list_ids on
"users" with soap, but it does of course make
total sense.  they're
just another element like stories or media, yes?  for the
most part?
k, i dunno why i assumed i couldn't do that.



jd

On 3/29/07, Scott Lanning <lanningswho.int> wrote:
> On Wed, 28 Mar 2007, David E. Wheeler wrote:
> > On Mar 28, 2007, at 14:34, John Durkin wrote:
> >> yes but i don't want any of the rest of the
installation.  just the
> >> users....
> >
> > bric_soap user list_ids - | bric_soap export >
users.xml
> > bric_soap user create users.xml
>
> NB: that won't do groups/permissions.
>
> I tried to implement groups in bric_soap once,
> but it's too nasty for my brain.
> (Biggest problem I think was no unique way to identify
groups,
> besides the 'id' which would generally vary in
different servers.)
>

(From `perldoc bric_soap`

   Commands:

     Asset Commands (story, media, template, element_type,
category,
                     media_type, site, keyword, user, desk,
                     element_type_set, output_channel,
contrib_type,
                     dest, pref):

       list_ids
       export
       create  (not 'pref')
       update
       delete  (not 'pref')

     Workflow Commands:

       publish
       deploy
       checkin
       checkout
       move

On Thu, 29 Mar 2007, John Durkin wrote:
> thanks david, for some reason i just assumed you
couldn't list_ids on
> "users" with soap, but it does of course make
total sense.  they're
> just another element like stories or media, yes?  for
the most part?
> k, i dunno why i assumed i couldn't do that.
>
> 
>
> jd
>
> On 3/29/07, Scott Lanning <lanningswho.int> wrote:
>> On Wed, 28 Mar 2007, David E. Wheeler wrote:
>> > On Mar 28, 2007, at 14:34, John Durkin wrote:
>> >> yes but i don't want any of the rest of
the installation.  just the
>> >> users....
>> >
>> > bric_soap user list_ids - | bric_soap export
> users.xml
>> > bric_soap user create users.xml
>> 
>> NB: that won't do groups/permissions.
>> 
>> I tried to implement groups in bric_soap once,
>> but it's too nasty for my brain.
>> (Biggest problem I think was no unique way to
identify groups,
>> besides the 'id' which would generally vary in
different servers.)

i get an error when trying create on my exported user list
that has to
do with password being 'undef' - but in the db it is NOT
NULL so the
insert fails... but - the password i went through and
actually set to
the same password for everyone in the xml file (created by
the soap
user export) and i tried create again but i get the same
error... as
if there is nothing in my xml file for password. the error
still says
the insert statement is trying to set password =>
'undef'

Use of uninitialized value in exists at
/usr/local/bricolage/lib/Bric/SOAP/User.pm line 359,
<GEN245> line 19.

[Thu Mar 29 22:07:45 2007] [error]
SOAP::Serializer::envelope: Server
Application error Unable to execute SQL statement:
DBD::Pg::st execute
failed: ERROR:  null value in column "password"
violates not-null
constraint for Statement

            INSERT INTO usr (id, login, password, active)
            VALUES (?, ?, ?, ?)

with ParamValues: 4='1', 1='1030', 3=undef, 2='jassimos'

at /usr/local/bricolage/lib/Bric/Util/DBI.pm line 1083,
<GEN245> line 19.

[/usr/local/bricolage/lib/Bric/Util/DBI.pm:1084]
[/usr/local/bricolage/lib/Bric/Biz/Person/User.pm:1410]
[/usr/local/bricolage/lib/Bric/SOAP/User.pm:413]
[/usr/local/bricolage/lib/Bric/SOAP/Asset.pm:243]
[/usr/local/share/perl/5.8.8/SOAP/Lite.pm:2569]
[/usr/local/share/perl/5.8.8/SOAP/Transport/HTTP.pm:327]
[/usr/local/share/perl/5.8.8/SOAP/Transport/HTTP.pm:621]
[/usr/local/bricolage/lib/Bric/SOAP/Handler.pm:169]

On 3/30/07, Scott Lanning <lanningswho.int> wrote:
> (From `perldoc bric_soap`
>
>    Commands:
>
>      Asset Commands (story, media, template,
element_type, category,
>                      media_type, site, keyword, user,
desk,
>                      element_type_set, output_channel,
contrib_type,
>                      dest, pref):
>
>        list_ids
>        export
>        create  (not 'pref')
>        update
>        delete  (not 'pref')
>
>      Workflow Commands:
>
>        publish
>        deploy
>        checkin
>        checkout
>        move
>
> On Thu, 29 Mar 2007, John Durkin wrote:
> > thanks david, for some reason i just assumed you
couldn't list_ids on
> > "users" with soap, but it does of course
make total sense.  they're
> > just another element like stories or media, yes? 
for the most part?
> > k, i dunno why i assumed i couldn't do that.
> >
> > 
> >
> > jd
> >
> > On 3/29/07, Scott Lanning <lanningswho.int> wrote:
> >> On Wed, 28 Mar 2007, David E. Wheeler wrote:
> >> > On Mar 28, 2007, at 14:34, John Durkin
wrote:
> >> >> yes but i don't want any of the rest
of the installation.  just the
> >> >> users....
> >> >
> >> > bric_soap user list_ids - | bric_soap
export > users.xml
> >> > bric_soap user create users.xml
> >>
> >> NB: that won't do groups/permissions.
> >>
> >> I tried to implement groups in bric_soap
once,
> >> but it's too nasty for my brain.
> >> (Biggest problem I think was no unique way to
identify groups,
> >> besides the 'id' which would generally vary in
different servers.)
>