Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#1277 closed enhancement (fixed)

Harvesters belonging to a group, and can be managed by UserAdmin

Reported by: heikki Owned by: heikki
Priority: minor Milestone: v2.10.0 RC1
Component: General Version: v2.8.0
Keywords: harvesters, harvesting, owner, group, UserAdmin Cc:

Description

In ticket #1198 the concept of harvester having an owner was introduced.

This ticket takes it a step further by also allowing harvesters to belong to a group.

Users with profile UserAdmin are also authorized to create and run harvesters (not only Administrators). This is useful because many GN installation make use of the group feature to represent organizations, who with this change can manage their own harvesters.

UserAdmins can only see and edit the harvesters belonging to one of their own groups.

Harvesters can only belong to 'real' user groups, not to the system groups ('all', 'intranet', etc.).

Harvesters created from before this change may not have an owner and certainly are not associated to a group. The harvester owner may also have been deleted after creating a harvester. In the case that there is no owner or he was deleted, just any Administrator is picked to 'own' the harvester when it is running. If there is no group, the behaviour is as before this ticket, there simply is no group (then the harvester is only visible to Administrator users).

Change History (8)

comment:1 by heikki, 12 years ago

Resolution: fixed
Status: newclosed

pushed to master 4341d2cecab2a7ceedfe1929b2a2ffc985bffe22

comment:2 by heikki, 12 years ago

pushed to 2.10.x 482a9980caf48d06c4808b2356f9866f6bddc4f6

comment:3 by heikki, 12 years ago

Milestone: v2.10.0v2.10.0 RC1

comment:4 by fxp, 12 years ago

I would move the group configuration field to the bottom of the harvester config ? near privileges and configuration. It's not really the first field to populate I think.

comment:5 by fxp, 12 years ago

Maybe not in fact, but the label is in some harvesters hardcoded to "group" which is not explicit (metadata group ? harvester group ?) and in some other places set /root/gui/harvesting/selectownergroup (eg. csw). Maybe we should set the same label in all harvesters ?

comment:6 by heikki, 12 years ago

fix 'sample' is not a system group :

2.10.x: df330187ec6719eaa5e34a9223195e2ba5a42069 master: 962a9e678115516b0902f0afd6af06383b9c160d

comment:7 by heikki, 12 years ago

Maybe we should set the same label in all harvesters ?

Of course, absolutely. I'll check it.

About position on top or bottom, I don't really care so much. If you or others do, go ahead and put it wherever..

comment:8 by heikki, 12 years ago

fixed missing i18n:

2.10.x: 0bc0c3f37b1ee625fbd6022de1cbc9adcb9f1345 master: a82fb1a64db98941e717198a82fa652552457ac3

Note: See TracTickets for help on using tickets.