From: <Mic...@ga...> - 2007-04-02 03:46:59
|
Hi list, =20 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. =20 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 install. =20 Any help would be appreciated. =20 Cheers, Michael Gannon. |
From: Andrea C. <aca...@cr...> - 2007-04-02 11:05:13
|
Hi Michael, 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). Cheers, Andrea > 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 > install. > > Any help would be appreciated. > > Cheers, > Michael Gannon. |
From: Walter B. <wal...@gt...> - 2007-05-04 12:33:42
|
Hello, I am not sure if the following is a bug or just my problem... I have = created metadata using the template iso19115 and then I=B4ve queried the = catalogue using the local search and works ok.. the problem comes up when I try searching remotely (my local geonetwork) which returns nothing. Does = anyone know why? Walter. |
From: Walter B. <wal...@gt...> - 2007-05-07 09:27:15
|
I've fixed it. I just had to set up some privileges.=20 =20 Walter BARBERA I+D Project Engineer =20 GTD SISTEMAS DE INFORMACI=D3N Pg. Garcia F=E0ria, 17 E-08005 Barcelona Tel.: +34 934 939 300 Fax: +34 934 939 334 www.gtd.es - wal...@gt... -----Mensaje original----- De: geo...@li... [mailto:geo...@li...] En nombre de = Walter Barbera Enviado el: viernes, 04 de mayo de 2007 14:33 Para: geo...@li... Asunto: [GeoNetwork-devel] Remote search problem or bug? Hello, I am not sure if the following is a bug or just my problem... I have = created metadata using the template iso19115 and then I=B4ve queried the = catalogue using the local search and works ok.. the problem comes up when I try searching remotely (my local geonetwork) which returns nothing. Does = anyone know why? Walter. -------------------------------------------------------------------------= This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ GeoNetwork-devel mailing list Geo...@li... https://lists.sourceforge.net/lists/listinfo/geonetwork-devel GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork |