Metadata specification at work: some examples of INSPIRE use cases with a cataloguing tool
•Download as PPT, PDF•
0 likes•30 views
Metadata specification at work: some examples of INSPIRE use cases with a cataloging tool
Recommended
More Related Content
Similar to Metadata specification at work: some examples of INSPIRE use cases with a cataloguing tool
Similar to Metadata specification at work: some examples of INSPIRE use cases with a cataloguing tool (20)
More from Desconnets Jean-Christophe
More from Desconnets Jean-Christophe (20)
Recently uploaded
Recently uploaded (20)
Metadata specification at work: some examples of INSPIRE use cases with a cataloguing tool
- 1. Metadata Specification at Work: Some examples of INSPIRE use cases with a cataloging tool Jean Christophe Desconnets IRD - ESPACE www.espace.ird.fr
- 2. Objectives Metadata specification at Work From metadata specification for protected sites to Protected Sites Use Case implementation OR How do metadata and associated tools serve the goals of data discovery and usage ?
- 3. Use cases for protected sites
- 4. Use cases for protected sites
- 5. Use cases for protected sites
- 6. Use cases for protected sites
- 7. Use cases for protected sites
- 8. Use cases for protected sites
- 9. What is a community profile? Metadata elements based on requirements of user community ISO Core elements standard profile
- 10. What is a community profile? Case of the natureSDI+ project Specific theme metadata Directive 2007/2/EC metadata Nature SDI+ profile
- 11. Example of implementation with NatureSDI+ French geoportal
- 12. NatureSDI+ French geoportal Dissemination and communication platform for the project’s French aspect Test platform Implementation of INSPIRE specifications in MDweb Interoperability tests with other implementation of the INSPIRE specifications
- 13. NatureSDI+ French geoportal Specification at work GeoToolkit WS manager CSW -T MDServ WS Thes. CSW -T MDServ WS Thes. Search Edition Admin. DBMS FS Repository Nature SDI+ Profile
- 14. Implementation of NatureSDI+ profile with MDweb tool The sub-profiling Nature SDI+ Profile Nature SDI+ Profile - Vector data Nature SDI+ Profile - Grid data Nature SDI+ Profile - service
- 15. Presentation of use cases with MDweb & PuzzleGIS
- 16. Use Case 1: Discovery and display of protected site Scenario : A member of an environmental protection organization has knowledge of a quarrying project in his district. He wants information on protected areas which could be within the district.
- 17. Use Case 2: Search, display and summary of protected areas Scenario: An administrator of the network of protected natural spaces has to create summary maps of protected areas (here NATURA 2000) in the Languedoc Roussillon region
- 18. Use Case 3: Cataloging a dataset on the habitats of species Scenario: a data administrator of the Natural Spaces conservatory enters metadata on the vector layer ‘Cartography of natural habitats of the Gardon Gorges regional natural reserve’.
- 19. Use Case 4: Cataloging a dataset by harvesting a CSW service Scenario: A data administrator of the Natural Spaces conservatory harvests a transnational CSW service to populate (update) the regional catalog
Editor's Notes
- In this presentation, I intend to explain and illustrate the differents steps that allows us to arrive at the definition of a requirement expressed and formalized in the context data specfications of INSPIRE towards its implementation. My illustration will particularly on metadata usage. My proposal will be supported by demonstrations based on use cases derived from the data specifications of protected sites.
- In fact, the process of going from data and metadata modelling to its implementation within infrastructures Can be a little bit unclear. The idea behind this presentation is to show and demonstrate how, within the framework of the NatureSDI project, we can go: from the draft of a specification to its use in a tool for making available via a web portal the expected services for discovery, display and analysis of data on protected sites. Or how metadata and associated tools serve the goals of data discovery and use.
- The base of a specification is built by identifying the requirements of the users concerned. These requirements can be formalized via uses cases which allow the expression, in simple language, of the expected features of, and the actors who will interact with the system. The data specification of protected sites is based on the following broad use cases: We first distinguish the identified actors: The non-expert, the semi-expert, the regional expert, the local expert, the European expert and member state.
- the first use case is the creation of a summary report of the analysis by a European expert of protected sites using transnational data.
- The second use case is the simple search for, and the display of data of, protected sites by a user seeking information about them.
- The third use case is the advance search for and analysis of data for creating maps according to the objectives of the impact study conducted.
- The last one is the download of data and metadata of protected sites. I will not describe in detail all the usage cases but only mention that in cases 2, 3, and 4
- the actors have to use tools and conduct searches on metadata to be able to identify the datasets Their spatial localization, their conditions of access, etc. This is especially true for use cases 2 and 3. So, we can add a dependency to the use case 5 to provide metadata of PS For this, the data specifications for each INSPIRE theme propose metadata specific to the description of the data. For this purpose, the data specification should include metadata specification
- In the same way as for data, the specification of metadata relies on the definition of the profile. The ISO metadata standard introduces the concept of community profile. This concept allows the possibility of using metadata elements which have been proposed based on the requirements of a user community. These metadata elements contained in a profile, have to respect the constraints imposed by the standard: i.e., include obligatory elements or core depending on the scope of the application. Others elements from the standard This profile could be also contain complementary metadata elements required by the community called extended elements The requirements defined in the previous use cases, for example. We can also, depending on the requirements, extend the standard with additional new metadata elements proposed by the community.
- In the context of the NatureSDI+ project and, more broadly, in the context of European nature-conservation data, The metadata profile specified is derived from a complex process. 1) First of all, it is based on the INSPIRE Directive on metadata implementation. For data collections, spatial data and services, it defines the metadata elements which should be made available to describe them and access them. This Directive is associated with a technical implementation guides such as the one for implementing metadata with the ISO standards. These two stages lead to what I will call the minimum INSPIRE profile. It is complemented by an XML encoding model which will allow the validity of all the metadata produced in this context. 2) The third stage of the process is the one that leads to a ‘community’ profile, i.e., a profile useful to the requirements of the community that will use the nature-conservation data Complementary metadata have therefore been defined by the drafting teams of the ‘protected sites’ theme. 3) Finally, the last stage, within the framework of the NatureSDI project, in which we have added or modified the properties of some elements.
- I now intend to show you how we can use this metadata profile to meet: The requirements for discovery and usage of nature-conservation data in the French context. For this, we have implemented a prototype of geoportal on the NatureSDI+ project.
- The implementation of this geoportal has a double objective: Allow, at the French level, to make accessible and visible the work done within the framework of this project, at least on the technical aspects, and Allow the experimentation with specifications originating from this project within the MDweb cataloging and search tool And, finally, to allow interoperability tests with other implementation of the INSPIRE specifications within the NatureSDI+ project.
- Let us now try to see where this metadata profile is located and how it is used within this portal.The first impression that we get of it, is via the services proposed and the components that make them possible. This portal is based on the MDweb tool suite, an open source platform. 1) MDweb is constructed using the Geotoolkit, an OGC compliant geographical library which provides the objects and methods using which have been constructed: 2) The MDweb service manager. It implements 3) web services for : Discovery or cataloging web service Services to edit and manage metadata and users A web service to access the SKOS thesaurus 4) This platform offers web applications that allow these services to be used: A discovery application with which a user can conduct searches An administrative application for the platform which is used to manage metadata profiles, associated thesuari, etc. An editing applicaton which is used to create metadata records. 5) This last application permits metadata management by connecting to data sources to retrieve: The community metadata profile which will be used to guide the metadata input And a data source in which will be stored the metadata created.
- we have introduced an additional level in the use of metadata specifications. We call this the sub-profiling. It concerns the specialization of the community profile to provide metadata-input interfaces which give, depending on the type of data to be described, only those metadata elements which we require. For example, in a first approach for the NatureSDI project, we have broken up the metadata profile into 3 sub-profiles: One sub-profile to allow the input of metadata relating to the vector data type One other to allow the input of metadata relating to the raster data type A third one to allow the input of metadata relating to the spatial service This allows us to present to the user input forms specific to each of these data types.
- I propose now to illustrate the use of metadata specification with the Presentation of 4 use cases, relating to the requirements defined in the framework of the specification of protected sites. They are shown via a video film of a MDweb demonstration and the use of the PuzzleGIS GIS tool.
- The usage case 1 is of a non-expert user who is searching for, and wants to display, protected sites in a particular district.The scenario is as follows... The user will use the French geoportal. We describe and illustrate this scenario with the following video... The user connects to the NatureSDI+ French geoportal, go to search module web client to submit his request: To do that, the user uses the map client to zoom to the area of interest : the district closed of Béziers b) He defines his request by using the rectangle to mark out arround the district of Beziers …. He thus obtains metadata records, which he goes through. He finds a link to a service for displaying protected areas. He go through this link to visualise the protected area arround The district of Beziers
- The usage case 2 is of an expert user who is searching for, and wants to display and make a summary of protected sites in the region of Languedoc Roussillon The scenario is as follows... For this, the member will use the French geoportal and an desktop GIS application. We describe and illustrate this scenario with the following video... The user go to search module of the geoportal : he uses the map client to zoom to the area of interest : Languedoc roussillon region b) He defines his request by using the rectangle to mark out arround the languedoc roussillon …
- The use case 3 is of an expert user who is an administrator of the geoportal and who wants to describe a dataset on habitats. The scenario is as follows... For this, the member will use the metadata editing module of the geoportal. We describe and illustrate this scenario with the following video... To do this, he connects to the NatureSDI+ portal, authenticates himself, then accesses to the editing application to: a) create a new record b) enter metadata. c) Specially, he enters keywords using the thesaurus web service d) and the WMS client to enter bounding box values c) save the newly created record He then publishes the newly created record and reinitializes the search index. The metadata are published and queryable from the web search application.
- The use case 4 is also of an expert user who is an administrator of the geoportal and who wants to import the metadata from a data supplier who has a CSW cataloging service using harvesting. The scenario is as follows... For this the member will use the geoportal’s configuration module. We describe and illustrate this scenario with the following video... To do this, he connects to the administration module, authenticates himself, then accesses the harvesting section: a) enters harvesting parameters (url, …) b) retrieves metadata c) verifies and publishes metadata The metadata is now published and queryable from the web search application.
- I hope I have succeeded in showing and demonstrating the utility of a metadata specification approach. Thank you for your interest.