Skip to main content
Archived

Metadata support for OGC Catalogue services, DCAT-AP and ESRI formats

Related products:FME Form
  • March 4, 2020
  • 1 reply
  • 42 views
T

Metadata is important. You know this as well. Yet I think the reader/writer support for those formats are lacking, to say the least. I am aware that the title asks for more than one format so lets break them down:

  • OGC Catalogue services for the web uses XML (admit, you love xml ;-) ) and have several good standards for content. A reader for searching and displaying posts from a metadata portal is increasingly important as more and more national metadata portals goes live.
  • CKAN and DACAT-AP are both common government and EUtypes of metadata portals. There already exists a CKAN writer plugin (https://github.com/OpenGov-OpenData/CKAN-DataStore-Writer-for-FME-Software) but I think it sholuld be integrated into the main software.
  • scripting ESRI metadata management is lousy at its best. As with ogc catalogue services it is based on xml (more love) and both a reader and writer would greatly improve life those of us working with enterprise databases, file geodatabases and even shapefiles.

I have marked FME Desktop as the space below but I believe one can have great use of this on server as well.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

A
Forum|alt.badge.img+6

Hi @tinkergnome!

We would like to do some initial requirements gathering on CKAN specifically—If you would be willing to share your thoughts, we'd really appreciate any and all input you may have!

 

 

From your perspective and experience, what would be:
  • The minimum set of functionality required to meet your current needs, for a CKAN reader and/or a CKAN writer? Do you require both reading and writing?
  • What would be a delightful set of functionalities required to exceed your expectations: What would make a CKAN reader/writer make you go, "this truly is like a data spa!"
  • If implemented, what would you be wary of in terms of functional gaps or shortcomings? What would a feature look like if we were totally misguided and produced something that is frustrating to use? Perhaps there are already examples of this!

Any and all input regarding scenarios, workflows and expectations for CKAN support in FME would be helpful towards us better understanding the challenges you are facing, and how we might best tackle them!

Community Stats

32,724
Posts
124,149
Replies
41,214
Members
Terms & ConditionsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.