Hi all - we're trying to decide whether to persevere with GN or fall
back to a webapp wrangling fgdc xml edited in ArcCatalog. We've been
having trouble editing attribute (table column) descriptions in GN, I
just tried compiling SVN but am only getting "Problem
accessing /geonetwork/. Reason: Not Found" - any pointers on either of
these issues much appreciated.
Thanks, Terry Brown
Hello,
Can you tell me what version of GeoNetwork you are using and what platform
you are trying to compile it on?
Also, in regards to "editing attribute discriptions" I assume you are
referring to feature attributes of you datasets?
Cheers,
Byron
LISAsoft
--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/GN-attribute-table-column-description-editing-tp6769327p6769862.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.
On Wed, 7 Sep 2011 16:30:50 -0700 (PDT)
ByronCinNZ <cochranes4@anonymised.com> wrote:
Can you tell me what version of GeoNetwork you are using and what platform
you are trying to compile it on?
We have 2.6.3 running on Ubuntu 9.10, and I've been trying to compile
SVN on Ubuntu 10.4.
mvn clean install gets as far as "BUILD COMPLETED OK" or similar, but
after that spits out some error about the database being already
closed, which is perhaps irrelevant.
jetty and gast will run, but 127.0.0.1:8080/geonetwork/ just give the
not found error.
Also, in regards to "editing attribute discriptions" I assume you are
referring to feature attributes of you datasets?
Correct, specifically the columns in the .dbf table associated with
a .shp file.
Thanks,
Terry
Terry,
From your first post in the thread I gather you are using FGDC as your
metadata standard?
If so the attribute information can be placed the the "Entity and Attribute
Information" tag. This is not visible in the FGDC template record supplied
with GeoNetwork unless you set the view to "Advanced". Scroll down the page
and you will see this tag with a "+" sign next to this. Expand the entry and
you can find the appropriate paces to hold your attribute info. Saving these
expanded entries will make them available in the "Simple view" interface.
When the template is selected again later for creating new records these
tags will be there. The process for ISO metadata is similar.
I am attempting to build GeoNetwork from trunk on Ubuntu right now. I will
let you know how it goes.
Cheers,
Byron
LISAsoft
--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/GN-attribute-table-column-description-editing-tp6769327p6770461.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.
Hi Terry,
I downloaded the source onto Ubuntu 10.4 and had the following experience:
Like you the mvn clean install command ran fine except for the error
messages when testing the h2 database at the very end.
I did get jetty to start using the command mvn jetty:run in the web module.
This was a terribly slow way to launch GeoNetwork. But once started, the
GeoNetwork page launched okay at http://localhost:8080/geonetwork with the
exception of the map that did not display.
My preference is to build the installer by running ant in the install
directory, and then running the command "java -jar
geonetwork-install-2.7.0-SNAPSHOT.jar in the geonetwork-2.7.0 directory and
installing the program in the default directory (/usr/local/geonetwork). I
did this but could not get jetty to run with the geonetwork-start.sh
command.
I usually bypass this command anyway and run GeoNetwork from Tomcat instead.
You might try that. And if the database gives you any difficult, I would
suggest pointing it at a Postgres database instead.
Cheers,
Byron
LISAsoft
--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/GN-attribute-table-column-description-editing-tp6769327p6774582.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.
On Thu, 8 Sep 2011 19:55:22 -0700 (PDT)
ByronCinNZ <cochranes4@anonymised.com> wrote:
Hi Terry,
I downloaded the source onto Ubuntu 10.4 and had the following experience:
Like you the mvn clean install command ran fine except for the error
messages when testing the h2 database at the very end.I did get jetty to start using the command mvn jetty:run in the web module.
This was a terribly slow way to launch GeoNetwork. But once started, the
GeoNetwork page launched okay at http://localhost:8080/geonetwork with the
exception of the map that did not display.My preference is to build the installer by running ant in the install
directory, and then running the command "java -jar
geonetwork-install-2.7.0-SNAPSHOT.jar in the geonetwork-2.7.0 directory and
installing the program in the default directory (/usr/local/geonetwork). I
did this but could not get jetty to run with the geonetwork-start.sh
command.I usually bypass this command anyway and run GeoNetwork from Tomcat instead.
You might try that. And if the database gives you any difficult, I would
suggest pointing it at a Postgres database instead.
The production system 2.6.3 is using postgres - probably not related to
the editing problems though.
Thanks for those pointers on getting 2.7 to run, will give it a
shot.
Any thoughts on why the attribute doesn't seem to be identified in the
Advanced editor view in the 2.6.3 images in my previous msg.? I'll try
and get 2.7 running and see if it's any different there, but it seems
odd.
Thanks again,
Cheers -Terry
Hi Terry,
The method for capturing attribute information is the same in GN 2.6 as in
2.7, like I described earlier. follow those instructions in 2.6 and you will
be able to add attribute info.
It is really more of a metadata standards issue than a GeoNetwork one IMHO.
Things like data schemas (such as your table column info), data
dictionaries, and portrayal info are all structured in ISO to be held
externally to the main metadata record. In GN 2.7 support for ISO 19110 data
dictionaries was introduced. These can be linked to any number of metadata
records. I hope this proves useful and then is extended to support schemas
and portrayal info.
I come from a GIS Data Management background and so tend to agree that these
are important to capture, but not all agree. And the standards are a
compromise by nature of the number of viewpoints they must support.
Cheers,
Byron
--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/GN-attribute-table-column-description-editing-tp6769327p6774821.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.
On Thu, 8 Sep 2011 21:28:16 -0700 (PDT)
ByronCinNZ <cochranes4@anonymised.com> wrote:
It is really more of a metadata standards issue than a GeoNetwork one IMHO.
Things like data schemas (such as your table column info), data
dictionaries, and portrayal info are all structured in ISO to be held
externally to the main metadata record. In GN 2.7 support for ISO 19110 data
dictionaries was introduced. These can be linked to any number of metadata
records. I hope this proves useful and then is extended to support schemas
and portrayal info.I come from a GIS Data Management background and so tend to agree that these
are important to capture, but not all agree. And the standards are a
compromise by nature of the number of viewpoints they must support.
Very helpful background perspective, thank you.
Cheers -Terry