I'm trying to use Geonetwork to manage a different Metadata Schema. I searched the list historic and I found Paul Grzeszczak that has made an adaptation to work with EML.
I want to know what are the steps that I should follow to customize my own dataset. The problem is that I already have a system that manage this Metadata and it's based on FGDC, but has some other fields. I'm wanting to migrate all this data to Geonetwork but I can't loose this data.
Thanks in advance and sorry about my english,
"Se o Senhor não constrói a casa, em vão trabalham os construtores (Sl 127,1)
Yahoo! Acesso Grátis - Internet rápida e grátis. Instale o discador agora!
dear Felipe, all,
On Thu, Sep 28, 2006 at 07:47:26PM +0000, Felipe Costa wrote:
> I'm trying to use Geonetwork to manage a different Metadata Schema.
> I searched the list historic and I found Paul Grzeszczak that has
> made an adaptation to work with EML.
> I want to know what are the steps that I should follow to customize
> my own dataset. The problem is that I already have a system that
> manage this Metadata and it's based on FGDC, but has some other
> fields. I'm wanting to migrate all this data to Geonetwork but I
> can't loose this data.
I would like to +1 on this very much. At OSGeo we've also been working
with a custom metadata schema derived from FGDC with additional
properties describing file formats and OGC web services.
http://wiki.osgeo.org/index.php/Geodata_Metadata_Model <- overview
I am really keen to make use of the catalog publishing capacities of
GeoNetwork - bleeding edge CSW support, etc - but to be able to keep
using this metadata model (which maps to a PostGIS database)
underneath. Rather than wanting to "migrate" in one shot, it would be
wonderful if it were possible to "migrate" in real time by
establishing a map of what GeoNetwork thinks of as ISO properties to
what a different user base thinks of as FGDC properties.
The GeoTools toolkit contains some nice metadata model abstraction
interfaces - cf Jody Garnett's recent explication at
from the client-side, metadata-reuse perpective this is good stuff.
If there are GeoNetwork user needs to migrate from one (reasonably)
well-known metadata model to another - it would be wonderful to be
able to put the effort into developing a common abstraction which
would enable people either to port data over to the GeoNetwork schema
or to be able to use their own data stores with a GeoNetwork frontend
- at least for the CSW/OAI-PMH/etc publishing parts if not for the
forms-based metadata-entry parts...
I hope this makes sense, and hope that others have more pragmatic
answers for you :)