[Size is given in number of characters, asterisk (*) indicates conditionally required field]
| |
|
FIELD NAME |
DATABASE ITEM |
DATA TYPE |
SIZE |
REQ-UIRED? |
DESCRIPTION |
| 1.1 |
|
Organization / agency |
AGENCY |
Text |
255 |
Yes |
The full title of the agency or organization that currently owns, maintains, and (or) distributes the dataset. Acronyms must be defined. |
| 1.2 |
|
Division / office / branch |
DIVISION |
Text |
255 |
No |
The full title of the division of the agency specified in 1.1, if applicable. |
| 1.3 |
|
Database title |
DBTITLE |
Text |
255 |
Yes |
The descriptive title of the dataset. This is not merely the name of a digital file. |
| 1.4 |
|
Other owner originator |
ORIG_OTHER |
Text |
255 |
No |
The agency, office, branch, organization, etc. that currently owns, maintains, and distributes the dataset, but is not listed in the item 1.1 AGENCY selection list. |
| 2.1 |
|
Web accessibility |
WEBACCYN |
Text |
255 |
Yes |
A YES/NO value stored in the database as “YES” if some or all of the dataset is available on the Internet or as “NO” if none of the dataset is available over the internet |
| 2.2 |
|
Web address |
WEBURL |
Text |
255 |
Yes* |
The complete URL of the Web site where some or all of the dataset can be accessed. This field is only required if item 2.1 WEBACCYN is stored as “YES”. |
| 2.3 |
|
Fees or charges |
FEES |
Text |
255 |
Yes |
A YES/NO value stored in the database as “YES” if there are any fees or charges associated with obtaining a copy of this dataset, and “NONE” if there are no fees or charges. If “YES” is specified, then the amount of and details pertaining to this fee or charge should be described in Distribution Information Remarks |
| 2.4 |
|
Export format |
XPRTFORMAT |
Text |
255 |
Yes |
The primary or most often used export format that the dataset can be provided. This should be completed regardless of whether the dataset is in digital format. Examples include: MS ACCESS, ASCII TEXT FILE, ESRI SHAPEFILE, PHOTOCOPY, etc. |
| 2.5 |
|
Contact phone |
CONT_PH |
Text |
255 |
Yes |
The phone number (voice) and area code of a contact for the dataset who can offer information about the dataset. |
| 2.6 |
|
Contact Email |
CONT_EMAIL |
Text |
255 |
Yes |
The email address of a contact who can offer information about the dataset, such as how to obtain a copy or subset of the dataset. |
| 2.7 |
|
Distribution information remarks
|
DISTRIBINFO |
Memo |
32K |
Yes |
Information related to how the dataset can be obtained, and who to contact to receive more information about the dataset. Additionally, any information regarding fees or charges should be included. Should not exceed 150 words. |
| 3.1 |
|
Statewide extent |
ST_WIDEYN |
Text |
255 |
Yes |
A YES/NO value stored in the database as “YES” if the dataset is statewide, or as “NO” if parts of the state are omitted. "NO" should be checked even if only 1 or 2 counties are excluded. |
| 3.2 |
|
County extent |
SP_CNTY |
Memo |
32K |
Yes |
A comma delimited list of all counties covered by this metadata entry. If ST_WIDEYN is “YES,” all 88 Ohio counties are automatically listed in this field. |
| 4.1 |
|
Digital format |
DIGFORMYN |
Text |
255 |
Yes |
A YES/NO value stored in the database as “YES” if some or all of the dataset is in digital format, or as “NO” if none of the dataset is in digital format. “NO” should be checked even if efforts are currently under way to digitize the dataset but the dataset has not yet been released. |
| 4.2 |
|
Primary digital format |
DIGFORMPRIM |
Text |
255 |
Yes* |
The primary software format of the dataset. Examples are ORACLE, MS ACCESS, etc. This is required only if DIGFORMYN is set to “YES”. |
| 4.3 |
|
Secondary digital format |
DIGFORMSEC |
Text |
255 |
No |
A secondary software format of the dataset. This might be pertinent in a case where the bulk of a database is in ORACLE, but subsets of the dataset are in MS ACCESS or other applications. |
| 4.4 |
|
Nondigital format |
NONDIGFORM |
Text |
255 |
Yes* |
The hard copy format of some or all of the dataset. Examples include Published Report, Hard Copy Field Forms, etc. This is only required if the dataset only exists in hard copy format. |
| 4.5 |
|
Beginning year |
BEGDATE |
Number |
4 |
Yes |
The 4-digit year that signifies the beginning date of the data in the dataset. This is not necessarily coincident with when the dataset was created. |
| 4.6 |
|
Ending year |
ENDDATE |
Number |
4 |
Yes |
The 4-digit year that signifies the ending date of the data in the dataset. |
| 4.7 |
|
Update frequency |
UPDFREQ |
Text |
255 |
Yes |
How often the dataset is updated. Valid values include: quarterly, annually, as data is received or collected, etc. |
| 5.1 |
|
Physical data |
KEY_PHYS |
Text |
255 |
No |
Comma delimited list of keywords pertaining to physical data that may be contained in the dataset. This refers not merely to the overall purpose of the dataset, but also to any ancillary data that might have been collected and stored in the dataset. |
| 5.2 |
|
Chemical data |
KEY_CHEM |
Text |
255 |
No |
Comma delimited list of keywords pertaining to chemical data that may be contained in the dataset. This refers not merely to the overall purpose of the dataset, but also to any ancillary data that might have been collected and stored in the dataset. |
| 5.3 |
|
Biologic data |
KEY_BIO |
Text |
255 |
No |
Comma delimited list of keywords pertaining to biological data that may be contained in the dataset. This refers not merely to the overall purpose of the dataset, but also to any ancillary data that might have been collected and stored in the dataset. |
| 5.4 |
|
Water use data |
KEY_WU |
Text |
255 |
No |
Comma delimited list of keywords pertaining to water use data that may be contained in the dataset. This refers not merely to the overall purpose of the dataset, but also to any ancillary data that might have been collected and stored in the dataset. |
| 5.5 |
|
Data use |
KEY_DU |
Text |
255 |
No |
Comma delimited list of keywords pertaining to the use of the data that may be contained in the dataset. This refers not merely to the overall purpose of the dataset, but also to any ancillary data that might have been collected and stored in the dataset. |
| 5.6 |
|
Data type |
KEY_TYPE |
Text |
255 |
Yes |
Comma delimited list of keywords pertaining to the type of data that may be contained in the dataset. There are only four options for this field: not specified, ground water, surface water, and meteorological. |
| 5.7 |
|
Other data |
DCKEYOTHER |
Text |
255 |
No |
Use this field to add additional content keywords not listed above or to comment on aspects of the dataset that relate to the listed keywords. |
| 6.1 |
|
Metadata record history |
UPDHIST |
Text |
255 |
Yes |
The history of changes of this record. Initially, this will be the initial metadata entry date. |
| 7.1 |
|
Detailed narrative description |
DESCNARR |
Text |
255 |
Yes |
A detailed abstract describing the dataset including why and when it was created, what the content of the dataset is, the completeness of the dataset, how and when the source data was or is collected, what types of processing of the data occurred and by whom, and other sources of funding that made the creation of the dataset possible. |
| 8.1 |
|
Map image hyperlink |
MAPLINK |
Text |
255 |
No |
A comma-separated list (up to three) of image names that are used to populate the swap image behavior of the network mapping application. |