chown functionality status
Posted: Wed Mar 04, 2015 10:41 pm
Hi,
We're trying to work out whether it's possible/feasible for an imaging core to use our OMERO instance in a manner where they upload files for users, then 'hand-off' the files to the users. They'd prefer to be able transfer ownership rather than share via group access since they want the user to be in control of removing files, and disk usage in OMERO to be attributed to the user etc.
I came across a previous thread mentioning chown functionality, and was wondering if this has matured, so an ownership change could be scripted?
http://www.openmicroscopy.org/community ... ilit=chown
That thread also mentions importing as another user, but presumably this is something only admins can do? The core staff cannot have full admin rights over the repository - which will be used various other groups.
Any hints gratefully appreciated !
DT
We're trying to work out whether it's possible/feasible for an imaging core to use our OMERO instance in a manner where they upload files for users, then 'hand-off' the files to the users. They'd prefer to be able transfer ownership rather than share via group access since they want the user to be in control of removing files, and disk usage in OMERO to be attributed to the user etc.
I came across a previous thread mentioning chown functionality, and was wondering if this has matured, so an ownership change could be scripted?
http://www.openmicroscopy.org/community ... ilit=chown
That thread also mentions importing as another user, but presumably this is something only admins can do? The core staff cannot have full admin rights over the repository - which will be used various other groups.
Any hints gratefully appreciated !
DT