General Terms

The following list contains definitions of some of the terms used within the InPort metadata catalog system.

Catalog Batch Loading
InPort can load some entity and attribute information from the data dictionary of an Oracle database. This information includes table and column names, data types and field lengths, and comments.
Catalog Hierarchy
Catalog items may be organized in a hierarchy that defines the parent-child relationships between catalog items. Each catalog item may belong to one-and-only-one parent catalog item. Each catalog item may be the parent of one or more catalog items. Each catalog item may not be the parent of itself. There are specific rules about which catalog item types may be children of other catalog item types (see InPort User Guide for details).
Catalog Item
A searchable record that describes fisheries dependent or independent information of significance to NOAA Fisheries. There are nine types of catalog items: Projects, Data Sets, Data Entities, Documents, Domains, Procedures, Models, & Data Collection Items
Catalog Item Identification
Basic information about the identification, purpose, and location of the catalog item
Catalog Workflow Control
Each Catalog Item (e.g., a data table or data entity) will be in one of six publication control states. The publication control state determines which operations may be performed on the catalog item and which InPort User Roles may perform those operations.
Data Standard
Information that defines a standard method of storing, managing, and using a specified type of data in a database
Detail Module
Detail Modules may be used to describe individual Catalog Items in greater detail. For example, a database table (Data Entity) may be described by listing its columns (Data Attributes); a Data Collection Item can be further described using a Time Frame to define when is was collected and a Procedure for how it was collected.
Event History
List of events relating to the catalog item, including dates, event descriptions and persons involved
General Terms
Definitions of general terms
InPort Administrators
InPort Administrators have sole authority to define and maintain catalog workflow (control states, InPort user roles), and manage reference codes. It is the InPort Administrator who can create Master (root-level) Organizations and their InPort Metadata Libraries, and create and manage their Librarian and Data Steward accounts.
InPort Author
InPort User Role that allows the person to create and edit metadata in their assigned InPort Library while the metadata is in Draft state
InPort Catalog
The collection of InPort Libraries that contain the metadata for catalogued information items.
InPort Data Steward
InPort Data Stewards have the same catalog privileges as an InPort Reader but have the ultimate responsibility of authorizing or rejecting InPort Catalog Access Roles for their InPort Library
InPort Librarian
An InPort Librarian can create and manage catalog Persons and InPort user accounts for their Metadata Library. Librarians can create and manage catalog project access requests, authorizations and rejections. Librarians create new organizations under their Organization and can create and manage catalog project folders under their Metadata Library.
InPort Library
An organization's Metadata Project. The Inport Catalog contains many InPort Libraries.
InPort Organization
Organization unit or business or professional entity (e.g., division, department, etc.) that is registered in the InPort Catalog
InPort Person
A person that is registered in the InPort Catalog. People that serve in data support roles for catalog items and/or InPort User Roles are required to be registered in InPort
InPort Publisher
InPort Publishers manage the review of metadata and ensure that quality assurance processes are completed. Publishers should give feedback and advice to InPort Authors on metadata quality and sufficiency. Publishers are responsible for web publication, either internally or externally, and for withdrawing metadata for correction or further review. Publishers will monitor metadata issues activity and ensure that issues resolution occurs in a timely fashion.
InPort Reader
InPort Readers review catalog items through the Catalog Editor or log onto the InPort web site to search and view internally published catalog items. Readers do not have any edit abilities. Readers are responsible for reporting any metadata issues.
InPort User Role
The privileges and responsibilities of an InPort user within the InPort Catalog and/or InPort Libraries and Projects. Current roles include InPort Administrator, InPort Librarian, InPort Author, InPort Publisher, InPort Data Steward, and InPort Reader
Organization Assignment
Controls the InPort Libraries in which an InPort Person may be granted InPort User Roles
Published-External
Catalog items published to the general public and are available in InPort web search
Published-Internal
Catalog items published in a restricted mode and available in InPort web search to InPort Users that are currently logged into the InPort web site
Record Details
Auditing details (date of change, changed by) for a given record

Catalog Item Types

The following is a list of the major types of records for which metadata is collected in InPort. The acronym (in brackets) is used in the search results to denote the type of the catalog item.

Catalog Item Types
A list of the various types of items that we catalog in InPort
Data Entity
[ENT] - A catalog item of type Data Entity can describe a data table, a data file, a data report, a spreadsheet, a data entry form with data, an XML file, or other user-defined information item that itself contains data attributes (columns or fields). Data Entities are most frequently thought of as Tables. Data Entities normally are child items of a catalog Data Set.
Data Set
[DS] - A catalog item of type Data Set can describe a Database, a collection of related Data Files, or a user-defined collection, as described in its Abstract
Document
[DOC] - Any existing document that relates to the parent catalog item. If a document contains data, and thus needs to be described with procedures or attributes, then it should probably be catalogued as catalog type Data Entity.
Procedure
[PRC] - a procedure, protocol, or process that is relevant to the parent catalog item
Project
[PRJ] - Project type catalog items can be thought of as metadata folders. A Project folder might, indeed, describe a real-life data project, it might also be used as a convenient way to describe a set of related items under which each of the collected items may be catalogued.

Detail Modules

The following is a list of some of the important "detail modules" collected for items recorded in the InPort catalog.

Acronyms
An abbreviation used in the context of a catalog item
Data Access
Details on the restrictions and legal prerequisites for accessing the data. Includes any access constraints applied to assure privacy or intellectual property and any special restrictions on the use of the data
Data Attribute
A piece of data collected and stored in a table, field, cell, or form, or a calculated value. Data attribute records always reside under a Data Entity parent item.
Data Quality
Details on usage constraints, completeness, and accuracy of the catalog item
Detail Modules
A list of Current "Detail Modules"
Downloads
List of available files, images, and documents for the catalog item with details and links for obtaining them
FAQs
List of questions and answers that have proven helpful to the understanding and use of the catalog item
Geographic Area
Spatial bounds and geographic description of the catalog item
Glossary Terms
List of terms and definitions specific to the catalog item
Issues
List of problems, risks, or questions about a catalog item
Related Items
List of catalog items that have a user defined relationship to another catalog item
Support Roles
List of people and organizations with jobs or responsibilities for the catalog item
Technical Environment
<p>Description of the data in the producer's processing environment, including details such as the name of the software (including version), the computer operating system, file name (including host, path, and filenames), and the data size. <p>Not Required for PARR
Time Frames
List of temporal limits of the catalog item which can be based on either time/date or an event, (e.g., trip)
URLs
List of internet addresses that are relevant to the catalog item