Hi,
We have GeoNetwork catalog (version 2.10) and an organisation partners that has CKAN want to harvest the entire metadata content. However, the organisation told us that the DCAT format in GeoNetwork is not following the standard and it should be like this one: https://github.com/ckan/ckanext-dcat/blob/master/examples/catalog_datasets_list.rdf
The organisation told us also that our point of entry should not be a list of url but the entire content of the DCAT in one dump file.
Does anyone has any idea the best way to harvest from GeoNetwork in DCAT to CKAN without having to customize each software (CSW is not also good enough, based on what the organisation told us) or what standard GeoNetwork support compared to CKAN?
Here is our link to harvest our DCAT:
http://www.donnees.gouv.qc.ca/geonetwork/srv/eng/portal.sitemap?format=rdf
There is not a lot of documentation on the web on GeoNetwork and DCAT-RDF.
Thanks.
Nicolas Gignac
Hi Nicolas,
2015-03-26 16:39 GMT+01:00 NICOLAS GIGNAC <NICOLAS.GIGNAC@anonymised.com>:
Hi,
We have GeoNetwork catalog (version 2.10) and an organisation partners
that has CKAN want to harvest the entire metadata content. However, the
organisation told us that the DCAT format in GeoNetwork is not following
the standard and it should be like this one:
https://github.com/ckan/ckanext-dcat/blob/master/examples/catalog_datasets_list.rdf
The organisation told us also that our point of entry should not be a list
of url but the entire content of the DCAT in one dump file.
Does anyone has any idea the best way to harvest from GeoNetwork in DCAT
to CKAN without having to customize each software (CSW is not also good
enough, based on what the organisation told us) or what standard GeoNetwork
support compared to CKAN?
Here is our link to harvest our DCAT:
http://www.donnees.gouv.qc.ca/geonetwork/srv/eng/portal.sitemap?format=rdf
There is not a lot of documentation on the web on GeoNetwork and DCAT-RDF.
DCAT export format was implemented 3 years ago with main goal to be able to
harvest the catalog content into a SPARQL endpoint (in that case, it was
virtuoso). The format implemented was based on the draft W3C standard. See
http://trac.osgeo.org/geonetwork/wiki/proposals/DCATandRDFServices for
more details.
Currently there is some initiatives to create DCAT profiles and we probably
need to update GeoNetwork for better interoperability with what is ongoing
on this side.
BTW if the harvesting system does not support the semantic sitemap
extension, maybe they could use the rdf.search service to get all in one
dump ? Which in your case generate a 132M file ... CSW with paging could be
better to harvest your catalog 
Cheers.
Francois
Thanks.
Nicolas Gignac
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website,
sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for
all
things parallel software development, from weekly thought leadership blogs
to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork
Hi Nicolas, the current dcat implementation in geonetwork is some years old and hasn't have an update since then. We currently have a project in which we are going to work on this, so expect some results soon.
In this project we also became aware that virtuoso (and maybe also ckan) does not understand our linked approach. Some suggestions there:
- we could add the rdf endpoints to the atom/rss endpoint of geonetwork, some clients would be able to extract the rdf from there
- i wrote a script that extracts all metadata and pushes it to 1 big file, i can share the script with you, note that it can run for multiple hours if you have quite some metadata in your catalog.
Good to hear that you're also starting to work on this, keep us updated.
Bye Paul.