Geoportal Database Tables

Release 9.3.1 E-mail This Topic Printable Version Give Us Feedback

Geoportal Database Tables

The Geoportal 9.3.1 database scripts create a set of tables that define database users, permissions, indexes, tables, and initial values for the database. If your organization has installed the optional MetadataServer component, then there will be an additional set of tables.



The tables are described below.

  1. Tables created by the Geoportal SQL database creation scripts

    Seven tables are created by the Geoportal SQL database creation scripts. Read about each table in the chart below. Each Geoportal table has its corresponding columns, the data type of the values within that column, and the meaning of the column's values given. A "*" next to a column name indicates that this column is a primary key for its table.

    Table Name Column Name DataType Meaning
    GPT_ADMIN, Administration Table DOCUUID* varchar Unique string associated with each metadata record, connecting this table to the GPT_METADATA table (or GPT_META table if SDE-Enabled database model was implemented)
    APPROVALSTATUS varchar Indicates if record is approved ("approved"=approved, "NULL"= not approved, record has any other status
    PUBMETHOD varchar How the document was published to the portal (e.g. "upload", "harvest", "batch", "editor")
    SITEUUID varchar Site identifier string of the registered repository that the record came from, if it was harvested
    SOURCEURI varchar Originating location of the record
    FILEIDENTIFIER varchar Value that may be stored in the metadata xml document to identify it among other metadata records. Because not every record may have a FileIdentifier in its XML, the Portal assigns the DOCUUID to uniquely identify each record
    CATSYNC numeric Flag for synchronization (1 = record is synchronized, 0 = record is not synchronized or not a candidate for synchronization, such as not yet approved)
    ACL varchar Indicates the restriction policy (if any) on the record
    GPT_HARVESTING , Harvesting Table ID numeric Number assigned to each registered repository
    UUID* varchar Unique string associated with each repository
    USERID numeric UserID of the user who will own harvested documents. Same USERID that is in the GPT_USER table
    INPUT_DATE datetime Date repository was registered
    UPDATE_DATE datetime Date repository information was last updated
    NAME varchar User-defined name of the repository
    HOST_URL varchar URL of the repository
    PROTOCOL_TYPE varchar Protocol the repository uses (e.g., "arcims", "z3950", "csw", "oai", "waf")
    PROTOCOL text Xml encoding of the repository's parameters, as defined when the user registered the repository (WAF example: <?xml version="1.0" encoding="UTF-8"?><protocol type="WAF"><username/><password/></protocol>)
    USE_THEME_LOOKUP varchar true/false: is theme lookup table used
    THEME_LOOKUP varchar If theme lookup table is used, the text information entered in the "Lookup Table" text box when the repository was registered
    FREQUENCY varchar How often the repository should be harvested (e.g., "Monthly", "BiWeekly", "Weekly", "Dayly", "Hourly", "Once", "Skip")
    SEND_NOTIFICATION varchar True/false: send user an email when repository is harvested
    GPT_HARVESTING_HISTORY, Harvesting History Table UUID* varchar Unique string associated with each harvesting history record
    HARVEST_ID varchar ID of the repository that was harvested
    HARVEST_DATE datetime Date of the harvest
    HARVESTED_COUNT numeric Number of documents harvested (duplicated from harvest_report column for better performance and sorting)
    VALIDATED_COUNT numeric Number of harvested documents that were valid (duplicated from harvest_report column for better performance and sorting)
    PUBLISHED_COUNT numeric Number of harvested documents that were published to the portal (duplicated from harvest_report column for better performance and sorting)
    HARVEST_REPORT text Information that will be displayed for the harvesting report text
    GPT_HARVESTING_JOBS_COMPLETED, Harvesting Jobs Completed Table UUID* varchar Unique string associated with each completed harvesting job
    HARVEST_ID varchar ID of the repository that was harvested in that job
    INPUT_DATE datetime 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 datetime 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 varchar 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 varchar 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 , Harvesting Jobs Queued Table UUID* varchar Unique string associated with each pending harvesting job
    HARVEST_ID varchar ID of the repository that will be harvested in this job
    INPUT_DATE datetime 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 datetime 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 varchar Status of the harvesting job (e.g., "submitted" or "running")
    JOB_TYPE varchar 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
    SERVICE_ID varchar 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_METADATA, metadata indexing table that handles retrieval of full metadata documents and information for details page DOCUUID* varchar Unique string associated with each metadata record, connecting this table to the GPT_ADMIN table
    DATASETNAME varchar Title of the resource described by the metadata record
    OWNER numeric UserID of the user who has ownership of the document. Corresponds to USERID in the GPT_USER table
    FOLDER numeric folder indicator (current implementation, always 0)
    UPDATEDATE datetime timestamp of the last occasion that the metadata document was published or republished to update
    XML text complete xml of the metadata record
    THUMBNAIL varbinary stored image associated with the thumbnail graphic for records containing binary image information in the metadata xml
    GPT_SEARCH , Saved Search Table UUID* varchar Unique string associated with each saved search
    NAME varchar Name of the saved search
    USERID numeric UserID of the user who saved the search
    CRITERIA text XML string that defines the saved search
    GPT_USER , Table for Referenced Geoportal Users USERID* numeric Unique number assigned to each user
    DN varchar Full LDAP distinguished name (e.g., cn=gptadmin,ou=users,ou=system)
    USERNAME varchar Username (e.g., gptadmin)


  2. Tables created by the metadata service (Note: only present with SDE-enabled database model)

    The five tables created when the MetadataServer service is started are listed below. These tables follow the conventions of ArcIMS 9.3 Metadata Server. If your organization has chosen a Geoportal deployment that does not use the MetadataServer, then these tables will not be present.

    • GPT_META
    • GPT_METAD
    • GPT_METADR
    • GPT_METAR
    • GPT_METAU


    After starting the metadata service, you may notice that additional tables exist in your Geoportal database as well. Examples of these tables are shown highlighted in the graphic below. These are tables that sde maintains and references in the database. The functions of these tables and their column values are not outlined in this document, but these tables are necessary for the proper functioning of the Geoportal. Do not delete them.







    Because there are connections to SDE, it is important to use ArcCatalog if the database or tables within it ever need to be deleted. Deleting tables through ArcCatalog ensures that any references to SDE tables are also deleted, whereas dropping the database through sql commands does not always delete these references.