ECP-2007-GEO OneGeology-Europe. Annex 1: Cookbook

Transcription

1 ECP-2007-GEO OneGeology-Europe Annex 1: Cookbook for creating multilingual metadata records using the OneGeology-Europe Metadata system (MIcKA) Authors: Lucie Kondrová, Robert Tomas, Štěpán Kafka Version and date: version 2, reviewed May 2013

2 MIcKA multilingual metadata catalogue uses the EN ISO terminology, therefore WP4 team provides this Cookbook and the Explanatory notes with a detailed comparison of the ISO elements with the 1G-E metadata profile elements. Element reference numbers in this document refer to reference numbers in the Explanatory notes. The following steps will help you to create metadata records of your national datasets, dataset series and services according to the developed 1G-E metadata profile. 1. STEP: MIcKA multilingual metadata editor for OneGeology-Europe project is available from this website: and the start page looks like this:

3 2. STEP: If you are logged as a user with editing rights, you may create a new record by clicking New record in the left menu. For login, please use the login information that you received by . You have to choose the option ISO standard (default) and set the metadata languages (left column is for the selection of the primary language = English, right for setting all other languages that will be represented in the multilingual elements, i.e. all consortium languages as shown on the above image). During the implementation phase of the OneGeology-Europe Plus initiative, this list will be updated to also include languages of the new data providers. The set of languages can be also edited during the editing process under Record administration. However, it is strongly recommended to define all the consortium languages right at the beginning because only then all the automatically filled multilingual fields as keywords or code lists will be really filled with the multilingual content (see STEP 6). Then click Create. You may also import metadata from an XML (ISO 19139) metadata file or by harvesting your catalogue service or other types of web services (WMS, WFS). In this case, please refer to the end of this document STEP 10.

4 3. STEP: A new blank record is created. Displayed language (element reference #18) is the one you selected as your primary language of your metadata. For the Resource type element (#3), valid values for the OneGeology-Europe project are dataset, series, or service (values from the EN ISO B.5.25 code list). On the next image and in the following paragraph, the general features of the MIcKA application are demonstrated. GENERAL FEATURES of the MIcKA application On this example, please note some features that are useful during the whole process of record editing: - on the right side there is an interesting feature verification of the record against INSPIRE rules missing mandatory elements are marked in red, conditionally mandatory in green. - in the left menu you can see, which metadata profile (which metadata elements) is displayed in the main window for filling metadata you will use the profile onegeology, for translating records of other data providers you will use the profile 1GE-translate - in the left menu, there is an option to Save the record with the possibility to continue editing, or Stop editing (= Save + stop editing) - small markers in the form of triangles mark that there is a hidden subset of elements - + or signs give you the option to multiply (or delete) the related elements - the option From list marks that there is a predefined list of values to use - in the case of the contact list (for example for filling the metadata contact point - #16), you can edit the list once and then use the values in more metadata records see the following image. Name of organization and country name should be entered in national language and in English in the metadata record.

5

6 4. STEP: In the spatial representation menu, the most used option will be probably the vector representation if you select it, a submenu appears, where you can define the Topology level (#27 - EN ISO B.5.28 code list) and a list of geometric objects from the EN ISO B.5.15 code list (using the + you can add more geometric layers): 5. STEP: For the reference system (#25.1, 25.2, 25.3), you can either choose it From list, or enter the code manually:

7 6. STEP: The main part, Identification of the data, has several parts. The first part is citation. For the Code (Resource identifier - #5), a unified template has been defined as [COUNTRY].[ORGANIZATION].[DATASET_IDENTIFIER], for the codespace use the first two parts of the code [COUNTRY].[ORGANIZATION]. The number of language versions depends on the number of languages you selected during creation of the record but may be changed under the Record administration. However, it is strongly recommended to define all the consortium languages right at the beginning because only then all the automatically filled multilingual fields as keywords or code lists will be really filled with the multilingual content:

8 Title of the dataset (#1) and Abstract (#2) will be translated in all consortium languages. Each country should provide an abstract in their national language and then a version in English for translations (English version can be shorter). Date (#11) and its type have to be filled. Point of contact (#15,15.1) - the list of contacts may be used again for filling these elements, or you can edit them manually. For the role element EN ISO B.5.5 code list is available. Resource maintenance (#20,21) there are two elements nested under this name maintenance frequency (mandatory EN ISO B.5.18 code list) and maintenance note (optional, any other note about the maintenance of the data in national language and in English). Descriptive keywords (#8) You have to select at least one keyword from the 1G-E Thesaurus and one from the GEMET Thesaurus (you select the thesaurus in the left drop-down menu in the pop-up

9 window), then search for your keyword in the searching window. When you find your keyword, press Use: In the corresponding fields you will see the translations of your keyword in all available languages:

10 In the same way you will choose a keyword from the GEMET thesaurus. Currently the GEMET contains also all the INSPIRE Spatial Data Themes. In order to select at least the term geology to reflect the relevance to the INSPIRE Data theme Geology, you should select INSPIRE (subcategory of GEMET) from the list of thesauri. The citation should then be (GEMET - INSPIRE themes, version 1.0).

11 Resource constraints (#13,14) Descriptions of terms and conditions applying to access and use of the dataset shall be provided through the element Constraints > uselimitation. This is a place for describing what the dataset is or is not good for. If no conditions apply, or are unknown then you can select from the list this values. To describe the conditions more precisely, the 1G-E template is provided, which defines the desired structure of this element (suitability of use, charges, other conditions, more information). If a data provider has more information on webpages, then the URL can be provided through the href element. In the case of National geological map datasets that are used for 1:1mil 1G-E Geological map layer of Europe (WP3 specification) the common text defining the conditions for use should be placed here. Concerning the Limitations on public access here there are 3 ISO elements that can be used. Two of them are list of values (MD_LegalConstraints > accessconstraints and MD_SecurityConstraints > classification). If the value otherrestrictions (under MD_LegalConstraints) is selected, then the third ISO element can be used (otherconstraints), which is a free text element and is somehow reserved for the INSPIRE possible limitations listed in the directive Article 13. For adding the MD_LegalConstraints and MD_SecurityConstraints use the + sign again.

12 Spatial resolution (#12) can be described by equivalent scale or a distance: Language element (#6) this one is used to describe the language of the dataset. Optionally, also the character set can be stated. Topic category (#7) for geological and applied geological data should be set to Geoscientific information: In the Environment description (#19) field you should enter the name of the GIS software, which has been used for the data creation and maintenance (name in English + in national language, if it is different from the English name): Extent information Geographic element (#9) you can get this information from your GIS software, or you can use the From map button to define the area of your dataset and then add the coordinates to the corresponding fields, or you can use a list of bounding polygons by pushing the From list button. For the temporal element (#10), you can specify either a range of dates relevant for the dataset, or a single date. The highest number that you can input is 2099.

13 7. STEP: Distribution (#22.1,22.2) Format name and its version should be specified under the Distribution element. In linkage field (#4 Resource locator) a link to the data should be provided (link to web pages with information about the distribution of data or link to ftp or http server that can be used for downloading the data).

14 8. STEP: Data quality part: Report Under the Report part, you have to check the Domain Consistency option to be able to provide information about the conformity (#23.1,23.2) of your data to a specification. You should provide the title, date and specification of a document you are referring to. For the 1G-E 1:1M datasets, the result should be set to pass = yes and the document name should say 1G-E data specification and data model, Lineage statement (#24,28,29) For the lineage element, a predefined structured template in English has been prepared by WP4. The template is added by pushing the From list button. The number of map sheets option is available only for data set series, not for datasets (here it is shown just as an example of the template content). The percentcoverage option should give the user information about the percentage of state area covered by digital data (in case of an on-going process of digitization, this number doesn t have to be 100%). It is expected from the data provider to provide a brief description of the level of geometric and thematic harmonization of his data. There are three options to choose from (YES / PARTLY / NO) and a possibility to add a more detailed free-text description. In this example, geological map has been geometrically adjusted so that it forms a seamless map, not a map with errors on the map sheet boundaries. Also, the geological legend has been unified across the whole map. For the 1G-E datasets (used for WP3 1:1M geological map of Europe), the thematic harmonization has been done by mapping the national legends to GeoSciML terminology. The content of the lineage statement element has to be available in national language and in English. Lineage process step description (#26) For this element, a predefined structured template in English has been prepared by WP4 to describe the digitizing method (i.e. how the digital dataset was created). The template is added by pushing the From list button.

15 Lineage source description (#30,35) In this element, information about the mapping project (of the source) and the source number of map sheets can be specified as a free-text description. Source description should be available in national language and in English. Scale denominator (#34) Here, a scale denominator of the source geological map should be given. Source reference system (#36) Reference system of the source geological map should be described here by its code and codespace. Source citation (#31,33) Title of the source geological map should be put here in national language and in English. Geological source Date and its type should be filled. Optionally, also a range of dates can be specified under the Source Extent element to better describe the process of the geological mapping.

16 Source step description (#32) For this element, a predefined structured template in English has been prepared by WP4 to describe the mapping method (i.e. how the source geological map was created). The template is added by pushing the From list button. Source description should be available in national language and in English. If the data providers wish to provide information also about the topographic background of the source geological map (topographic background, which has been used for the field survey), they can specify it in the next element (if a data provider wants to describe also the topographic source, which has been used for publication of the source geological map, this has to be EXPLICITELY specified in the free text description of the topographic source - element #37). Source s topographic source description (#37) Source description should be available in national language and in English. Scale denominator (#40) Here, a scale denominator of the topographic map should be given.

17 Source reference system (#41) Reference system of the topographic map should be described here by its code and codespace. Source citation (#38,39) Title of the topographic map should be put here in national language and in English. Topographic source Reference Date and its type should be filled. Optionally, also a range of dates can be specified under the Source Extent element to better describe the process of the mapping. 9. STEP: After filling the metadata record, please check that it is made public for everyone to be able to search and view it by checking the appropriate checkbox in the Record administration:

18 10. STEP: If you already have an XML file (ISO 19139) with your metadata, or you want to harvest metadata from a catalogue service, please choose the Import from file/url option on the New record page and then either select your file from disc, or enter a URL of your service. Depending on the amount of information you are providing in your service, more or less of the metadata elements will be automatically filled. You have to check this after creating the record and edit manually the missing ones according to the rules described in this cookbook. 11. STEP: After finishing your editing session, please always create an XML file of your record as a backup copy, just to make sure you don t loose any of your metadata in any case: