harvested records reflect remote privileges. If you harvest using an account
you are willing to get confidential data so a metadata visible only to that account
is not visible to a guest user.
If a remote metadata is made public, when harvested it remains public and so it
is visible to a guest user.
Maybe someone has a better idea on how to keep privileges on confidential
metadata during harvesting.
The group assigned to a guest account is 'All' (that is, the internet one).
> Hi list,
> I have another question to do with harvesting. Once a dataset is harvested I
> seem to have to log into be able to view the records, a guest that has no
> username or password cannot view the metadata for these records. Am I able to
> set somewhere that on import records are publicly viewable? Or perhaps an
> addition for the next version.
> For the time being I was just going to make an sql change to the
> operationallowed table but don't know what groupid the guest account is
> associated with, indeed there seems to be no quest account on the default
> Any help would be appreciated.
> Michael Gannon.