Jason,
Since the permissions of the parent are directly inherited by the
children, I can't remove it from the Local System Administrator account and
still have it on the Staff account. I tried it and when I added it back to
the Staff account it automatically added it back to the Local System
Here is the first output:
evergreen=# select id, parent_ou, ou_type, shortname from actor.org_unit;
id | parent_ou | ou_type | shortname
+---+-+---
1 | | 1 | CONS
2 | 1 | 2 | SYS1
8 | 4 | 3 | BKM
10 | 2 |
Since the permissions of the parent are directly inherited by the
children, I can't remove it from the Local System Administrator account and
still have it on the Staff account. I tried it and when I added it back to
the Staff account it automatically added it back to the Local System
On Wed, May 28, 2008 at 8:21 AM, Robert [EMAIL PROTECTED] wrote:
[snip]
and here is the second:
evergreen=# select * from actor.org_unit_type;
id | name |opac_label | depth | parent |
can_have_vols | can_have_users
On Wed, May 28, 2008 at 10:51 AM, Robert [EMAIL PROTECTED] wrote:
Yeah Mike, I see what you're saying. I did mean to take these out as they
were put in before I really knew about the structure of the whole system. I
do have the branches in as the org_unit instead of the org_unit_type. I only
Now that I have my permission problems out of the way, thanks to Dan, Jason
and Mike, I can finally start on something that has been hindering the
progression of our testing. I have some records that we exported from Sirsi
and looking at the documentation about importing, I was able to run all of
