START Conference Manager    

GDI-DE Registry and Drupal’s ISORegistry module: Making registers within a registry available the easy way

Christian Seip, Tim Balschmiter, Nicolas Hagemann and Peter Kochmann

(Submission #153)


Abstract

A fully operating spatial data infrastructure includes a number of elements that have to be clearly described and are referenced by unique IDs. Registries offer the possibility to assign elements and their names, definitions and descriptions IDs, making them distinctly referenceable. The German GDI-DE registry acts as central access point for a number of centrally managed registers, including inter alia organisations, namespaces, codelists and schemes. GDI-DE is currently focusing on the registers for codelists and namespaces. They are necessary to fulfill the INSPIRE regulations, and there is an existing need for accessible codelists for harmonised INSPIRE data and to organise individual namespaces, including the resolving to service operations. To be able to support registers when needed almost on-the-fly without much programming effort, the content-management-framework Drupal is used as a base for a national implementation. A module is used (ISORegistry, https://www.drupal.org/project/isoregistry) to create new registers. This module allows users to register items, i. e. pieces of data or knowledge of general interest within a data infrastructure. In this context it acts like a thesaurus, which stores the common understanding of vocabulary inside a certain domain/data infrastructure. In more technical terms, the ISORegistry module is used to manage item classes according to processes defined by ISO 19135 (Geographic information – Procedures for item registration). The individual item classes are defined in separate submodules with corresponding content types because they have different tasks and functions. Thus far, the ISO 19135 registry workflow is not implemented. However, the item classes codelists and namespaces are currently implemented without the ISO processes. It is possible for codelists to either import INSPIRE codelist schema compliant XML or to build (hierarchical) codelists using forms in the Drupal GUI manually. The response, i. e. output, is displayed via GUI or can be returned as INSPIRE XML (REST). Other formats can be easily implemented and integrated. Besides managing namespaces in principle and apart from providing plain, unique namespaces, the core of this module is the ID-Resolver. It acts as a kind of proxy to use short URLs with an additional ID to point to services and get a response from them, e. g. get a specific feature from a Web Feature Service (WFS). The ID-Resolver can be used with both GET (as a redirect) and POST (as a proxy) requests. Using Drupal’s ISORegistry is the attempt to build the registers easy, user-friendly and even so effective.

Categories

Topic Area:  [3.2] Tools and technologies
Abstract Type:  Oral Presentation

Additional Fields

 
Academic:   Yes
 
Data Provider:   Yes
 
Data User:   No
 
INSPIRE Implementer (IT):   Yes
 
INSPIRE newbies:   No
 
Policy Officers:   No
 
Public Administration (MS/Regional/Local):   Yes
 
Thematic specialists:   No
 
Comments:   Registry, ISO 19135, codelists, namespaces, Drupal, GDI-DE


START Conference Manager (V2.61.0 - Rev. 5269)