Skip to content
David Blodgett edited this page Apr 28, 2020 · 7 revisions

Get involved in geoconnex.us

The geoconnex.us PID server is just getting started and we need as many people involved as possible to get things off the ground. Here are ways to get involved:

  1. Mint PIDs for your organizations web resources. The README of this repository has details.
  2. Add some structured data to your landing pages. See ELFIE and science-on-schema.org for details.
  3. Engage in the discussion in the issues. We want to hear from you! Open an issue with your ideas and questions.
  4. Join a geoconnex.us activity. We're hoping to hold one or more geoconnex.us cross-organization development activites. See here for more.

Types of PIDs made available through geoconnex.us are: (DRAFT -- to be vetted through implementation examples)

  • Organizational monitoring or other information resources.
    • Provides stable identifiers for any organizations' resources.
    • Examples include: organizationally-published web resources about stream gages, wells, dam information, etc.
    • Redirect from geoconnex.us/{org-namespace}/{org-path} to {org-url}
    • Organizations own and maintain the PID list in this repo.
    • More info and examples here.
  • Community reference locations.
    • Provides referenceable identifiers for shared surface water and groundwater locations.
    • Examples: NHD events, catchment indexes, groundwater wells.
    • Redirect from geoconnex.us/{theme-namespace}/{id} to {community-system-url}
    • A community actor or group would be required to curate these locations through some process managed outside this repository.
    • More info and examples here.
  • Environmental feature of interest.
    • Provides referenceable identifiers for shared environmental features.
    • Examples: Reachcodes, comids, local aquifer ids.
    • Redirect from geoconnex.us/{authority-namespace}/{authority-path} to {community-canonical-url}
    • An authoritative community-oriented group would be expected to maintain these identifiers for the community.
    • More info and examples here.
  • Established cataloging feature.
    • Provides referenceable identifiers for areal / place cataloging features.
    • Examples: hydrologic units, principle aquifers, counties, states.
    • Redirect from geoconnex.us/{authority-namespace}/{authority-path} to {community-canonical-url}
    • An authoritative community oriented group would be expected to maintain these for the community.
    • More info and examples here.