Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Geology discipline to guided setup #6279

Open
grantfitzsimmons opened this issue Feb 25, 2025 · 0 comments
Open

Add Geology discipline to guided setup #6279

grantfitzsimmons opened this issue Feb 25, 2025 · 0 comments
Milestone

Comments

@grantfitzsimmons
Copy link
Member

grantfitzsimmons commented Feb 25, 2025

This issue is a summary that outlines the high-level requirements for adding the Geology discipline to a Specify database. It focuses on the components unique to this discipline.

1. Geology Defaults

1.1 Default Schema

  • Create the default schema for the Geology discipline based on the straw man agreed upon by the GeoSpecify Advisory Committee.
    GeoSpecify Advisory Committee Document

  • Default pick lists are defined in this document, but these are only added once a collection is added under a discipline:
    Default Pick Lists Spreadsheet
    (Age Event | Absolute Dating Method | Relative Dating Method)

1.2 Geologic Time Period Records

  • Use the ICC as the basis for the initial GeologicTimePeriod records.
    Requirements for this are captured here: Issue #5182
    This needs to resolve: Issue #5412

1.3 Sourcing Defaults

  • Source the defaults for the Geology discipline from the Geology Config Directory.
    This component is already verified when databases have a discipline manually updated to geology via the type field in the discipline table. Verification is necessary to ensure it appears appropriately.

1.4 Default Trees

  • Several default trees should be available, preferably within the app, but at least via Specify Taxon Files.

1.4.1 Minerals

1.4.2 Meteorites

1.4.3 Rocks

  • No standard hierarchy is available, but we have data from the BGS we can use upon request. This could be an empty tree by default.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant