Revisiting a question I've seen raised a couple of times but need a 'new' answer as it relates to 2.8.
I want to change regions (eventually making a much shorter, applicable-to-our-users, dropdown for searching and editing metadata). Here is what I've attempted in order to test by adding one new location >
1) I tried editing from the admin module (manage thesauri) but when I select regions.rdf my add/delete options on the right side of the page are grayed out. However, if I add a new blank thesauri I do get the add/delete ability.
2) I then tried editing the actual regions.rdf file from my PC. My new location is showing in the admin module but still does not show on the end-user side of things. And of course as noted above, I cannot edit it from admin either.
3) I was thinking I could just create a new thesaurus and rename it regions.rdf but am not finding my test.rdf location on the PC to even move into the appropriate directory.
4) I also tried editing the countries.xml with the new location but that made no difference either.
I did stop and re-start the server.
What am I missing?
(Also, is there any progress/a fix for why the regions do not show up in the Localization? -- you have to blindly click through until you find the country you are looking for.)
Kathy
_____________________________________
Kathy Koch
Data Curator
501 Avis Drive, Ann Arbor, MI 48108
Office: 734-332-1200 email:kkoch@anonymised.com
LimnoTech www.limno.com
Thanks Ian. Yes the non-appearing regions does appear to be related to that
ticket (albeit I don't get any error messages). However the developers
comments don't seem to tell me if there is anything I can do, so am assuming
this is just a bug someone is working on?
What about not being able to edit a thesaurus? I've tried now from two
different installs and the only edits I can do are directly to the .rdf but
then those changes aren't showing in the region dropdowns so I can only
assume that there is some other place that change needs to occur. So if
anyone has successfully modified regions in 2.8, let me know what steps I
can take and/or what I am missing.
you can change it by directly editing the contents of tables Regions and
RegionsDes.
To do this I would recommend to change GeoNetwork's default database from H2
to Postgres, so you can use some decent tools like pgAdmin to easily run SQL
statements to the DB.
Well, i have been updated the regions and regionsdes in a postgresql
databases as i used to do in previous versions, but it has not impact onthe
dropdown menu (list) the same regions as shown in the regions.dbf files are
displayed .. Should i change the regions.dbf as well ?
the thing with changing the tables regions and regionsdes does not work for
the stable release GeoNetwork 2.10, either.
I have switched off the regions.rdf with the administration panel (set to
"n" in thesaurus management), but GeoNetwork still does not use the tables
regions and regionsdes like it did in the old days.
On the start gui for "Search" there is an empty list for the regions. When
you try to add metadata there is an empty list next to the map where you can
choose the boundingbox for the metadata.
To me it looks as if GeoNetwork always tries to read regions.rdf. I think
the coordinates you can choose are coming from regions.rdf. No matter if
regions.rdf is activated or whether it is not.
Is there any workaround? Or: How could I get rid of the useless / empty
boxes for choosing the area?
There is something I forgot: To me it looks as if the projection in the
mapviewer does not match the WGS84 coordinates from the whatever-list.
Anja wrote
Hello everyone,
the thing with changing the tables regions and regionsdes does not work
for the stable release GeoNetwork 2.10, either.
I have switched off the regions.rdf with the administration panel (set to
"n" in thesaurus management), but GeoNetwork still does not use the tables
regions and regionsdes like it did in the old days.
On the start gui for "Search" there is an empty list for the regions. When
you try to add metadata there is an empty list next to the map where you
can choose the boundingbox for the metadata.
To me it looks as if GeoNetwork always tries to read regions.rdf. I think
the coordinates you can choose are coming from regions.rdf. No matter if
regions.rdf is activated or whether it is not.
Is there any workaround? Or: How could I get rid of the useless / empty
boxes for choosing the area?
1. admin creates a new rdf using the gui (that takes quite some time!!)
2. download the rdf from the gui
3. rename the downloades rdf "regions.rdf"
3. put it in the directory where the original wrong region.rdf is
(directory:
...webapps/geonetwork/WEB-INF/data/config/codelist/external/thesauri/place)
4. restart tomcat
5. login as admin and turn "acivation" of thesaurus to "n" (!)
==> On the search-page there is the new regions-list of your own
==> On the metadata gui´s map you will also find the new regions-list
I only wonder, why you have to set the acivation to "n"... and I must admit:
I still find it easer to use the tables regions and regionsdes like it was
in GN 2.6.4.