Alaska Region Metadata Guide
  • Alaska Region Interim Metadata Guide
    • Other Training Resources
  • Goals of Data Management
  • Project & Data Management Integration
  • Alaska Region Tools
    • Alaska Regional Data Repository
    • Metadata Standard Checklist
    • Contact Master List
    • mdEditor basics
      • Record Types
      • mdJSON vs. mdEditor files
      • Settings
      • Profiles and Schemas
      • Import Records
      • Copy Records
      • Export Records
      • I Need HELP! and Bug Reporting
    • Digital Object Identifiers (DOIs)
    • Data.gov
  • Creating Metadata
    • A Workflow At A Glance
  • Contact Entry Guidance
    • Organization Contacts
    • Individual Contacts
  • Project Metadata Guidance
    • Project Main Tab
      • Guide to Good Titles
    • Project Metadata Tab
    • Project Keywords Tab
    • Project Extent Tab
    • Project Taxonomy Tab
    • Project Distribution Tab
    • Project Funding Tab
    • Project Associated Tab
  • Product Metadata Guidance
    • Product Main Tab
      • Resource Types Defined
    • Product Metadata Tab
    • Product Keywords Tab
    • Product Extent Tab
    • Product Lineage Tab
    • Product Taxonomy Tab
    • Product Distribution Tab
    • Product Constraints Tab
    • Product Associated Tab
  • Product Dictionary Entry Guidance
    • Dictionary Main Tab
    • Dictionary Entities Tab
    • Dictionary Domain Tab
  • Glossary
Powered by GitBook
On this page

Was this helpful?

  1. Product Metadata Guidance

Product Lineage Tab

PreviousProduct Extent TabNextProduct Taxonomy Tab

Last updated 3 years ago

Was this helpful?

Lineage is used to track the process of building products. It's a space that can be used to describe the steps and sources used to create the product, and document the roles and contacts for the product contributors. For example, this is the location where QA/QC procedures could be recorded. Completing the lineage tab is recommended, but not required.

  • Statement (Required): Notes actions taken to verify, transform, repair, and integrate the resource.

  • Process Step (Optional): Consult the Process Step section below to learn how to add information about the creation of your project.

  • Sources (Optional): Use the Sources field to indicate what you used to create the product and then write a statement. This can be done instead of completing all other fields in this tab.

  • Citation (Optional): If you have a citation for a manual, enter it here. This can be done instead of completing all other fields in this tab.

  • Scope (Optional): Select type from the picklist.

Process Step

Process Step allows for documentation of the steps taken to build spatial data.

The following are available and required:

  • Step ID: (Auto filled depending on the number of Process Steps added).

  • Description: Add a description of the process step.

The following fields are available but optional:

  • Step Sources: Information about the source data used in the process step.

  • Step Products: Information about an intermediate data set.

  • Processors: Processors of the process step.

    • Select or enter a role from the Role drop-down and select a contact from the Contacts drop down.

  • Step Reference: Add a citation noting your step process references.

  • Time Period: Add a time period noting the Start Date, End Date, and Fiscal Year.

    • ID: Add a unique identifier for the time period.

    • Description: Add a description of the time period.

    • Time Period Name: Add a name for your time period.

    • Interval: Enter an Interval Amount and Time Unit of the time period.

    • Duration: Describe the time period in terms of Years, Months, Days, Hours, Minutes, and Seconds.

  • Scope: Select the type of resource from the drop-down menu.

Consult the section of this manual to learn about adding contacts.

Contacts