[ckan-dev] Importing ISO19139 from GeoNetwork via CSW

[Bruce Crevensten]

Thanks very much, Adrià, this worked perfectly and I've successfully
ingested the records from GeoNetwork.

I'm quite happy about how the harvester sensibly mapped the fields from the
ISO19115 schema in GeoNetwork to corresponding fields in CKAN (the Abstract
became the description, and it created tags based on the Keywords --
nice!), using custom fields to capture geospatial and other specific
information about the dataset.  This makes the CKAN API very useful, as I
can easily fetch metadata for use in client applications, as well as add
arbitrary additional key/value pairs -- that's not a strength of GeoNetwork.

Next, I'm going to spend a bit of time cross-referencing between CKAN's
harvested representation of the dataset and GeoNetwork in order to improve
how we're populating GeoNetwork -- for example, the ingested description
turns into a mess because we didn't anticipate a Markdown parser, and our
data endpoint URL isn't correctly set up.  That's fine, as this process
improves our metadata.

Once I'm happy with the GeoNetwork <-> CKAN metadata correspondence, I'll
explore some of CKAN's geospatial features.  We have a Mapserver /
Tilecache system for serving tiles for online viewing of our data, and I'm
interested in how CKAN may be able to take advantage of that -- especially
if GeoNetwork can provision CKAN with enough information through the
ISO19115 schema so that the harvester can configure the CKAN integration
with little or no further work.  That'd be interesting.

Thanks again,
- Bruce

On Tue, Oct 2, 2012 at 2:39 AM, Adrià Mercader <amercadero at gmail.com> wrote:

> Hi Bruce,
>
> Sorry for the late reply, I've been away for some days.
> Thanks a lot for you detailed report it is very useful.
>
>
> On 27 September 2012 02:37, Bruce Crevensten <becrevensten at alaska.edu>
> wrote:
> > Am I encountering a known limitation of the harvester (not all
> > namespaces/CSW sources can be harvested), or does this seem like a
> > misconfiguration or other error on my part?
> It seems that we added a change a while back that hardcoded the 'gmi'
> namespace on the getrecordbyid request we are performing. As your CSW
> server is probably using 'gmd' one, the requests were failing.
> I've reverted the change and add a small modification to the model and
> after that the records from your server were harvested fine. Please
> pull the latest changes from the 'harvest-generic-iso' branch of
> ckanext-inspire, restart the consumers and try again.
> Moving one, we should find a way of supporting documents with both
> gmd:MD_Metadata or gmi:MI_Metadata root elements (ISO 19115 and ISO
> 19115-2 if I'm not mistaken).
> As I mentioned, this is an area we are currently working on, so this
> feedback is hugely useful, thanks again!
>
>
> > (And, thank you all for your collective work on CKAN, the various
> > extensions, and your helpful replies to my question on the
> > ckan-discuss list.  This is an impressive project, and I am glad to
> > have encountered it.)
> We are glad it can be useful
>
>
> Cheers,
>
> Adrià
>
>
> >
> > - Bruce
> >
> > --
> >
> > Bruce Crevensten, Web Programmer
> > Scenarios Network for Alaska & Arctic Planning
> > 3352 College Road, 2nd Floor Denali Building
> > Fairbanks, AK 99709
> > Phone: 907-474-7134
> > Fax: 907-474-7151
> > www.snap.uaf.edu
> > becrevensten at alaska.edu
>



-- 
*
*
*Bruce Crevensten, Web Programmer
*
Scenarios Network for Alaska & Arctic Planning
3352 College Road, 2nd Floor Denali Building
Fairbanks, AK 99709
Phone: 907-474-7134
Fax: 907-474-7151
www.snap.uaf.edu
becrevensten at alaska.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20121002/7995fcd8/attachment-0001.html>