-
Notifications
You must be signed in to change notification settings - Fork 0
Geonetwork Admin Notes (work in progress)
Peter Parslow edited this page Jul 21, 2021
·
13 revisions
- For general GeoNetwork issues or to-dos, or documentation requests, submit them in this repository. Issue templates have been created for bugs (with varying degrees of severity), feature requests and documentation, with appropriate default labels. P1 Bugs are auto-assigned to @archaeogeek but other issue types are not. Either leave them unassigned, or assign someone as you see fit.
- For issues relating to Gemini 2.3 submit them in https://github.com/AstunTechnology/iso19139.gemini23/issues. These are auto-assigned to @archaeogeek.
- This setting can be configured by administrators in admin -> settings -> Enable self-registration (tick box and save settings)
- Users create an account by clicking the "sign-in" button on the home page and then clicking "Create an account"
- They must fill in the Name, Surname, Email and requested profile at the very least and then click "Register"
- An account is created immediately but as a Registered User only. An email is sent to the catalog administrator who then confirms the registration, sets the correct membership profile and group membership.
See https://geonetwork-opensource.org/manuals/trunk/en/administrator-guide/managing-users-and-groups/index.html for core documentation on users and groups
- The easiest method of doing this is to pick a record that has all the elements filled in, then pick that from the list in Admin console -> Settings -> CSW -> Record to use for GetCapabilities (then click "save")
- The same settings can be configured in Admin console -> Settings -> Catalog Service for the Web (CSW)
- There are three methods:
- Conversion when importing a record (choose "Convert Gemini 2.2 to 2.3 on import" as the XSL transformation, which is at the very bottom of the list at present)
- Bulk conversion as an administrator (admin console -> tools -> batch process, choose "Convert from Gemini 2.2 to 2.3" as the process)
- In-place conversion when editing a record (use the suggestions wizard on a Gemini 2.2 record)
See https://github.com/AstunTechnology/iso19139.gemini23/wiki/Conversion-from-Gemini-2.2-to-2.3 for details
Now that credentials are encrypted in the database, it is necessary to ensure that you keep a copy of data/config/encryptor/encryptor.properties if you are redeploying or upgrading. If you don't, then you won't be able to decrypt existing entries in the database
Set the IP address and mask in Admin settings, but what to?