Database Tables
mhogeweg edited this page Dec 22, 2014
·
5 revisions
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
The geoportal database scripts create a set of tables that define database users, permissions, indexes, tables, and initial values for the database. Read about each table's columns and the meaning of that column's information in the chart below.
GPT_HARVESTING_HISTORY
| Column Name | Meaning |
|---|---|
| UUID | Unique string associated with each harvesting history record |
| HARVEST_ID | ID of the repository that was harvested |
| HARVEST_DATE | Date of the harvest |
| HARVESTED_COUNT | Number of documents harvested (duplicated from harvest_report column for better performance and sorting) |
| VALIDATED_COUNT | Number of harvested documents that were valid (duplicated from harvest_report column for better performance and sorting) |
| PUBLISHED_COUNT | Number of harvested documents that were published to the portal (duplicated from harvest_report column for better performance and sorting) |
| HARVEST_REPORT | Information that will be displayed for the harvesting report text |
GPT_HARVESTING_JOBS_COMPLETED
| Column Name | Meaning |
|---|---|
| UUID | Unique string associated with each completed harvesting job |
| HARVEST_ID | ID of the repository that was harvested in that job |
| INPUT_DATE | Date and timestamp marking when the harvesting job was created. This is the same INPUT_DATE that is in the GPT_HARVESTING_JOBS_PENDING table |
| HARVEST_DATE | Date and timestamp for when the harvesting job was completed. This is the same HARVEST_DATE that is in the GPT_HARVESTING_JOBS_PENDING table |
| JOB_TYPE | Harvesting job type (e.g., "full"=Full Harvest or "now"= Harvest Records that have been updated since last harvest. Same JOB_TYPE that is in the GPT_HARVESTING_JOBS_PENDING table |
| SERVICE_ID | The Harvesting Service ID of the Harvesting Service that took over the job. Its ID is defined through the Harvesting Service install wizard (e.g., GPT_Harvesting_Service) |
GPT_HARVESTING_JOBS_PENDING
| Column Name | Meaning |
|---|---|
| UUID | Unique string associated with each pending harvesting job |
| HARVEST_ID | ID of the repository that will be harvested in this job |
| INPUT_DATE | Date and timestamp marking when the harvesting job was created. This is the same INPUT_DATE that is in the GPT_HARVESTING_JOBS_COMPLETED table |
| HARVEST_DATE | Date and timestamp for when the harvesting job was completed. This is the same HARVEST_DATE that is in the GPT_HARVESTING_JOBS_COMPLETED table |
| JOB_STATUS | Status of the harvesting job (e.g., "submitted" or "running") |
| JOB_TYPE | Harvesting job type (e.g., "full"=Full Harvest or "now"= Harvest Records that have been updated since last harvest. Same JOB_TYPE that is in the GPT_HARVESTING_JOBS_COMPLETED table |
| CRITERIA | XML string that defines the saved search |
| SERVICE_ID | The Harvesting Service ID of the Harvesting Service that will take over the job. Its ID is defined through the Harvesting Service install wizard (e.g., GPT_Harvesting_Service). |
GPT_RESOURCE
| Column Name | Meaning |
|---|---|
| DOCUUID | Unique string associated with each resource |
| TITLE | Title of the resource |
| OWNER | UserID of the user who has ownership of the document. Corresponds to USERID in the GPT_USER table |
| INPUTDATE | Date resource was registered |
| UPDATEDATE | Date resource was last updated |
| ID | Number assigned to registered resources to provide backward compatibility with the Geoportal 9.3.x harvesting mechanisms Note: DOCUUID vs. ID: DOCUUID is used to uniquely identify resources. ID, being a numerical value, is also used because certain database operations are faster on numerical values. If you are migrating a Geoportal 9.3.x database to Geoportal Server, migration will extract the metadata xml out of the 9.3.x GPT_METADATA table to the Geoportal Server's GPT_RESOURCE_DATA table. Both GPT_RESOURCE and GPT_RESOURCE_DATA are linked together using the ID for performance on UPDATE requests. For searching, and reading/downloading raw metadata, the DOCUUID is better to use. Maintaining both the ID and the DOCUUID for resources is a balance that maintains backward compatibility, usability, and increases performance. |
| APPROVALSTATUS | Indicates if resource is approved ("approved"=approved, "NULL"= not approved, record has any other status) |
| PUBMETHOD | How the resource was published to the portal (e.g. "upload", "registration", "harvester" (synchronization), "batch", "editor") |
| SITEUUID | If the resource is synchronized, this is the site identifier string of the registered resource from which it came. |
| SOURCEURI | User id and originating filename/location of the resource |
| FILEIDENTIFIER | Value that may be stored in the resource's metadata xml to distinguish it from other resources. Because not every record may have a FileIdentifier in its XML, the geoportal assigns the DOCUUID to uniquely identify each record |
| ACL | Indicates the restriction policy (if any) on the record |
| HOST_URL | If the resource is a registered network resource, this is its URL |
| PROTOCOL_TYPE | If the resource is a registered network resource, this is the protocol it uses (e.g., "arcims", "res", "csw", "oai", "waf", "thredds") |
| PROTOCOL |
Xml encoding of the resource's parameters, as defined when the resource is registered. An example with WAF:
<?xml version="1.0" encoding="UTF-8"?><protocol type="WAF"><username/><password/></protocol>
|
| FREQUENCY | How often the resource should be synchronized (e.g., "Monthly", "BiWeekly", "Weekly", "Daily", "Hourly", "Once", "Skip") |
| SEND_NOTIFICATION | True/false: send user an email when resource is synchronized |
| FINDABLE | String associated with each metadata record, indicating whether it can be found when searching for metadata. The value can either be null for metadata that is not describing a searchable endpoint or true or false for metadata records that are describing a searchable endpoint. |
| SEARCHABLE | String associated with each metadata record indicating whether to include the resource in the distributed search list. The value can either be null for metadata that is not describing a searchable endpoint or true or false for metadata records that are describing a searchable endpoint. |
| SYNCHRONIZABLE | String associated with each metadata record indicating whether the content can be synchronized. The value can either be null for metadata that is not describing a searchable endpoint or true or false for metadata records that are describing a searchable endpoint. |
| LASTSYNCDATE | Date resource was last synchronized |
GPT_RESOURCE_DATA
| Column Name | Meaning |
|---|---|
| DOCUUID | Unique string associated with each metadata record, connecting this table to the GPT_RESOURCE table |
| ID | Number assigned to registered resources to provide backward compatibility with the Geoportal 9.3.x harvesting mechanisms |
| XML | complete xml of the metadata record |
| THUMBNAIL | stored image associated with the thumbnail graphic for records containing binary image information in the metadata xml |
GPT_SEARCH
| Column Name | Meaning |
|---|---|
| UUID | Unique string associated with each saved search |
| NAME | Name of the saved search |
| USERID | UserID of the user who saved the search |
| CRITERIA | XML string that defines the saved search |
GPT_USER
| Column Name | Meaning |
|---|---|
| USERID | Unique number assigned to each user |
| DN | Full LDAP distinguished name (e.g., cn=gptadmin,ou=users,ou=system) |
| USERNAME | Username (e.g., gptadmin) |
GPT_COLLECTION - (version 1.2 and up)
| Column Name | Meaning |
|---|---|
| COLUUID | Unique string associated with each collection |
| SHORTNAME | Name of the collection |
GPT_COLLECTION_MEMBER - (version 1.2 and up)
| Column Name | Meaning |
|---|---|
| DOCUUID | Document UUID of the record in the collection |
| COLUUID | Collection ID of the collection containing the document |
∗ The GPT_COLLECTION and GPT_COLLECTION_MEMBER tables are unused unless your organization has collections enabled. See Collections for details.