Hi,
I have been performing some harvesting, and all is working well mostly. The setup we want here at AIMS is an internal MEST which is used to draft up metadata records and release them internally. This MEST is not visible to other agencies. A second External MEST is the one that will be visible to other agencies. Our plan is to harvest released/approved records from the internal MEST to the external MEST.
Now this harvest doesn’t use an account, as the records being harvested are freely available on the internal MEST without authentication. i.e they all have privileges set on the All group. So the harvest is created as type 2.2 node, doesn’t specify an account, or any criteria as we want all the release records up on the External MEST, and the All group is retrieved and ‘create and copy’ (tried copy as well) used. The harvest itself works, however the issue is with the resulting privileges. The doco in the manual states that for the all group, special logic is performed with the All group which ends up not setting privileges to the All group on the External MEST, but creates a new internal group named ‘All (Internet)’ and assigns access to this group.
Now what I see then is the following behaviours.
- Even if I create a user account, and assign this group All (Internet) to that account, the records can’t be searched until as admin I view the metadata record.
- I can’t modify the privileges of the harvested records as admin, even though I’m the admin. So now the only way for me to grant access to the real ‘All’ group is to hack the operationallowed table in the DB.
- Even though I perform step 2, the records are still not searchable when not logged in, until I open each record as admin.
I searched through the geonetwork dev forums and can’t find any items on this. Why is it that All privileges don’t go to All privileges on the Harvestor system. If it’s already publicly available on the harvestee, why hide it on the harvestor?
Why do we not let the administrator edit privileges on a harvested record (understand not allowing edit but the others would be handy)? Same for delete, I would have though the admin would be able to delete the harvested records. How else could they be removed from the system? (to get around this I have to run GAST to reset the DB everytime to clean out the records)
Can you shed any light on why I have to open the record before it becomes searchable by others who have privileges? I can’t see anything in the DB that gets updated by opening the record, but probably missed it. If there’s a simple update I can make this part of our AIMS internal to external harvest steps.
Thx
Kevin
--
------------------------------------------------------------------------
The information contained in this communication is for the use of the
individual or entity to whom it is addressed, and may contain
information which is the subject of legal privilege and/or copyright.
If you have received this communication in error, please notify the
sender by return email and delete the transmission, together with any
attachments, from your system. Thank you.
------------------------------------------------------------------------