Orientation to the Create Metadata Page
Pages 202
- Home
- 2009 Esri Federal UC
- 2009 Esri International UC
- 2010 Esri Federal UC
- 2010 Esri International UC
- 2011 Esri Federal UC
- 2012 Esri Federal UC
- 2013 Esri Federal GIS Conference
- 2013 Esri International User Conference
- 2015 SDI Special Interest Group
- Add a Custom Profile
- Add an OpenSearch endpoint for Federated Search
- Add Another Tab to the Geoportal Interface
- Add Custom Link to a Search Result
- Add Custom Search Criteria
- Add the Geoportal Search to a List of Search Providers
- Add v1.1.1 FGDC editor to a previous Geoportal release
- AGP TO AGP Harvesting with the Geoportal
- AGS TO AGP Harvesting with the Geoportal
- All gpt.xml file settings
- An Introduction to vi
- Apache Tomcat geoportal logging
- Being a Good Robot
- Best Practice for Edits to JSP files
- Biological or Remote Sensing FGDC xsds
- Browse Tree
- Cart Processor
- Catalog Service
- Clear the Tomcat Work Folder
- Collections
- Common problems and solutions
- Communities and live examples
- Components
- Configure a Directory Server for the Geoportal
- Configure geoportal User and Schema in the PostgreSQL Database
- Configure Previewable Filetypes
- Configure Searching of YouTube
- Configure the gpt.xml File
- Configure Widgets
- Connecting to a User Directory
- Create a user account
- Create Relationships between Resources
- Customizations
- Customize DCAT output
- Customize Metadata Validation
- Database problems
- Database Tables
- DataDownload Tab
- Deploy and Configure the Geoportal Web Application in Tomcat
- Deploy and Configure the Servlet Web Application
- Deploy the Geoportal Web Application
- Details of Lucene Indexing in the Geoportal
- Development topics
- Discovering Resources
- Eclipse Project from Compiled WAR
- Eclipse Project from Source Code
- Enable Search Using an Ontology Service
- Error Messages in the Geoportal Web Application
- Esri Geoportal Server LiveDVD
- Extending the Web Harvester
- Federated Search in Portal for ArcGIS
- Feedback
- FGDC Biological Profile and Remote Sensing Extension
- FGDC Service Checker Integration
- Geoportal Clients for ArcGIS
- Geoportal CSW Clients
- Geoportal Facets using Apache Solr
- Geoportal genie
- Geoportal Project from Compiled WAR
- Geoportal Publish Client
- Geoportal Server 1.2.5 What's New
- Geoportal Server 1.2.6 What's New
- Geoportal Server 1.2.7 What's New
- Geoportal server as a broker
- Geoportal Server Downloads
- Geoportal Server v 1.0 What's New
- Geoportal Server v 1.1 What's New
- Geoportal Server v 1.1.1 What's New
- Geoportal Server v 1.2 What's New
- Geoportal Server v 1.2.2 What's New
- Geoportal Server v 1.2.4 What's New
- Geoportal SPARQL Sample
- Geoportal User Interface Components
- Geoportal Web Application File Organization
- Geoportal XML Editor
- Get Assistance with an Implementation
- GXE Concepts
- GXE Crash Course
- GXE Structure
- GXE Workflow
- High Availability and Large Number of Records
- How to Browse for Resources
- How to Create and Manage My Profile
- How to find all documents of a particular metadata standard
- How to Leave a Resource Review
- How to Login and Manage my Password
- How to Manage and Edit Resources
- How to Publish Resources
- How to Restrict Access to Resources
- How to Search for Resources
- How to Search with an Ontology Service
- How to Set Up an Esri Geoportal Server on Linux
- How to Use Search Page Results
- How to Use the Data Download Feature
- How to View Resource Relationships
- IDE Topics
- Identity Components LDAP and Single Sign On
- Index All Metadata Content
- Indexing and Searching the Time Period of the Content
- Install Apache Tomcat 6
- Install Desktop Tools
- Install Esri Geoportal Server
- Install PostgreSQL 9.1.2
- Install the JDBC .jar Files
- Installation
- Installation Version 1.0
- Installation Version 1.1
- Installation Version 1.2
- Installation Version 1.2.2
- Installation Version 1.2.4
- Installation Version 1.2.5
- Installation Version 1.2.6
- Installation Version 1.2.7
- Installation Version 1.2.8
- Integrate with a Content Management System
- Integrate with the con terra Security Solution
- Localization
- Log In to the Geoportal
- Logging
- Look and Feel of the User Interface
- Main Page
- Map LDAP Attributes on the Registration Page
- Map Viewer
- Online form editing for all publication methods
- Open source acknowledgements
- Oracle WebLogic geoportal logging
- Orientation to the Create Metadata Page
- Perform Preinstallation Computer Setup
- Portal for ArcGIS Integration
- Post Deployment Actions
- Preinstallation
- Preinstallation 0.9
- Preinstallation 1.0 and 1.1.x
- Preinstallation 1.2
- Preinstallation 1.2.2
- Preinstallation 1.2.4
- Preinstallation 1.2.5
- Preinstallation 1.2.6
- Preinstallation 1.2.7
- Preinstallation 1.2.8
- Preview Function
- Publication Components
- Ratings and Comments for Search Results
- Register ArcGIS for Server with the Geoportal
- Release notes
- REST API Syntax
- Sample FGDC metadata.xml
- Scheduled tasks
- Search Components
- Search Map
- Search Widget for Flex
- Search Widget for HTML
- Search Widget for Silverlight
- Security Concepts
- Set Up Systemwide Environment Variables
- Set up the Geoportal Database
- Share Link
- Single Sign On
- Smoketest the Geoportal
- Standards Support
- Supported CSW Profiles for Synchronization
- Theme Library
- Troubleshooting
- Troubleshooting Tips
- Two geoportals on the same server
- Upgrade 1.x to 1.2 database
- Upgrading file system approach
- Upgrading Read This Overview
- Upgrading SVN approach
- Url filter customization
- Use an XSLT to Render the Details Page
- Use Ant to build Geoportal
- User Functions and Roles
- User Management Interface
- Using a geoportal
- Using Lucene Search Text Queries
- Version 0.9
- Version 1.0
- Version 1.1
- Version 1.1.1
- Version 1.2
- Version 1.2.2
- Version 1.2.4
- Version 1.2.5
- Version 1.2.6
- Version 1.2.7
- Version 1.2.8
- What is a geoportal and the geoportal server
- What is the esri geoportal server
- What's New
- wiki template
- WMC Client
- Show 187 more pages…
Clone this wiki locally
Access the Create Metadata Page
When a publisher clicks the Use dedicated editor to create metadata manually link from the Add page on the Administration tab in the Geoportal interface, an initial page opens that shows the available standards for which metadata can be generated. The publisher selects one of the radial buttons, clicks Proceed and is taken to the Metadata Editor page, where he/she can enter information that will be included in an output metadata document. The publisher enters in all the pertinent information about his/her data resource, clicks Save. An output metadata document is created and stored in the geoportal database.
How the Metadata Editor is defined
The Metadata Editor form is defined by the a configuration file - the definition.xml file. There is a definition.xml file for each standard or profile supported in the geoportal.
This definition.xml file can either define the parameters for the form itself, or can point to the Geoportal XML Editor (GXE) method of defining the form. Older versions of the Geoportal Server used the definition file exclusively to define the Metadata Editor, but now the GXE is the preferred method for defining the Metadata Editor. It is preferred because the GXE allows for unlimited repeating sections and fields in the metadata.
This topic describes what the Metadata Editor form looks like if you use the older definition file method of configuring the form. See Geoportal XML Editor to read about the GXE method.
Create Metadata Page Layout - Definition file method
The following image shows a Metadata Editor page as defined by the definition.xml file alone. There are five types of graphic elements on this page, and each are described in the image below.
images/create_metadata_form.png
About Sections, Parameters, and Fields
It is important to understand the relationship between what is input in the Metadata Editor, and the resulting metadata document. Information submitted in the Metadata Editor's fields will populate the output metadata document. For example, when a string is typed into the File Identifier field, the <fileidentifier></fileidentifier> element will be populated with that string in the output metadata document. Fields left blank in the form result in elements left blank in the output metadata document.
Sections
The sections are shown as large bold type, and introduce a set of related parameters in the form. Sections are not mapped to any specific metadata elements, but do control which ones are visible when the Metadata Editor is opened, and can indicate what input is mandatory. A section will have a box next to it that shows a plus sign ('+'), a minus sign ('-'), or is left empty. The plus indicates that there are additional parameters hidden that can be filled out. If the plus sign is clicked, it becomes a minus sign, and the section expands to show the additional parameters. It can be clicked again to contract and hide them. If the box next to the section is empty - does not contain a '+' or '-' sign - then that section is considered "conditional optional". Conditional optional means that the section is not mandatory unless one of the parameters within it is filled out. For example, if a section has no check in the box next to it, then no information concerning the elements within that section will be included in the output metadata document. If a section is checked, it is then enabled, and the output metadata document will contain the metadata tags associated with elements in that section. Mandatory elements in that section must then be populated for the document to validate and publish successfully.
Parameters
Parameters can be mandatory or optional. A mandatory parameter will appear in bold text on the form. If the field next to a mandatory parameter is left blank or is not entered correctly (for example, in the correct date format), then the document will not publish.
Fields
Fields can be text fields, dropdown boxes, radial or checkboxes for elements, or any other typical form-input mechanism. Fields can also be given default values that show up when the Metadata Editor page is launched. Default values in fields can be designated as uneditable, which is useful when the publisher should be aware of a value in the form even though he/she is not able to change it. Uneditable values are shown by default as light gray-colored text.
Back to Customize Metadata