[ome-users] FW: Latest OMERO Binary repository

[Van Meter, Bill]

Josh,

I see a reference to it in OMERO.server-Beta-4.2.0/lib/python/django/contrib/auth/backends.py. The object is in our  OMERO4 version which was created last year as 4.0.2.

Thanks,

Bill

--
Bill Van Meter
Computational Science Center
National Renewable Energy Laboratory
x4082
303-275-4082


On 7/27/10 12:30 PM, "Josh Moore" <josh at glencoesoftware.com> wrote:

Bill,

great to hear. As for the "auth_group_permissions" table, do you know where it comes from? It's not used by the OMERO server. If it's something that other sites may run into, we'll need to add your exception to the patch release.

Thanks for the feedback,
~Josh.

On Jul 27, 2010, at 6:02 PM, Van Meter, Bill wrote:

> Josh,
>
> I work with Kristin and we were able to migrate the users and then run the final upgrade script "OMERO4.1__0.sql". I did receive an initial error using "omero-4.1-move-to-group.sql" relating to the table "auth_group_permissions" not having an "owner_id". I revised the select statement for "omero-4.1-move-to-group.sql " in the for loop to contain an additional protection for tables only containing "owner_id":
>
>    for rec in select table_name as tbl FROM information_schema.columns
>              WHERE column_name ='group_id'
>                    AND table_name IN
>                   (select table_name from information_schema.columns where column_name = 'owner_id')
>    loop
>        sql := 'update ' || rec.tbl || ' set group_id = '|| GRP ||' where group_id <> '|| GRP ||' and owner_id = '|| USR;
>        execute sql;
>        return next rec.tbl || 'updated for user ' || USR || ' in group ' || GRP;
>    end loop;
>
> After that we were able to migrate each user successfully out of the guest and default groups.
>
> We appreciate the help and quick response - Thank you,
>
> Bill
>
> --
> Bill Van Meter
> Computational Science Center
> National Renewable Energy Laboratory
> x4082
> 303-275-4082
>
>
> On 7/27/10 1:06 AM, "Josh Moore" <josh at glencoesoftware.com> wrote:
>
> Hi Kristin,
>
> are you actively using the "default" and "guest" groups at your site? If not, your best bet is probably to move all data for users 4, 5, and 8 (and probably all others) to group 5 ("BSCL") and make that group collaborative or read-only depending on your needs.
>
> To do that, execute a command like:
>
>  psql -vGRP=5 -vUSR=4 -v ON_ERROR_STOP=1 --pset pager=off -h localhost -U omero -f omero-4.1-move-to-group.sql  omero
>
> for each user. Once that's done, re-try the upgrade. If that's successful, get your 4.2 server running and then either from Insight or WebAdmin change the permissions on the group. You can read more about the meaning of the permissions system under http://www.openmicroscopy.org/site/support/omero4/server/permissions and a screencast for administering a group's permissions is available under http://cvs.openmicroscopy.org.uk/snapshots/movies/omero-4-2/mov/Permissions1.mov
>
> If you _are_ using the groups "default" and "guest" actively, you'll need to decide whether or not to add user 8 back to group 3, or move all of 8's data into another group. You'll also need to change the groups for the projects and datasets marked "Different groups", but we could provide an example script for that if necessary.
>
> Let us know how things go.
> ~Josh
> _______________________________________________
> ome-users mailing list
> ome-users at lists.openmicroscopy.org.uk
> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users
>

_______________________________________________
ome-users mailing list
ome-users at lists.openmicroscopy.org.uk
http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users