Update to exemption for lithostrata and code table description change

[Jegelewicz]

Code tables affected

ctlithostratigraphic_bed ctlithostratigraphic_formation ctlithostratigraphic_group ctlithostratigraphic_member

Change request

British Geological Survey has a lexicon, we can use to verify lithostratigraphic requests. I would like to add this to the code table descriptions so that everyone can find it.

https://www.bgs.ac.uk/technologies/the-bgs-lexicon-of-named-rock-units/

Edit text in the code table descriptions:

from

The unit is registered in a national geologic database, with a link included in the documentation (for example: https://ngmdb.usgs.gov/Geolex/search). If the unit is not listed in a national database, the documentation should include a link to a publication that describes the unit.

to

The unit is registered in a national geologic database, with a link included in the documentation (for example: https://ngmdb.usgs.gov/Geolex/search, https://www.bgs.ac.uk/technologies/the-bgs-lexicon-of-named-rock-units/). If the unit is not listed in a national database, the documentation should include a link to a publication that describes the unit.

Also, can we make it so that this text isn't all bold?

This would be easier on the eyes

Locality Attribute: Lithostratigraphic Formations

Controlled vocabulary for lithostratigraphic formations available as locality attributes. Terms may be added to this table without DBA approval and with the approval of one active Code Table Committee member, as long as that Code Table member did not also request the term if the following criteria are met:

• The unit is registered in a national geologic database, with a link included in the documentation.
  • https://ngmdb.usgs.gov/Geolex/search
  • https://www.bgs.ac.uk/technologies/the-bgs-lexicon-of-named-rock-units/
  If the unit is not listed in a national database, the documentation should include a link to a publication that describes the unit.
• The term is properly formatted as "Name Type". Lithology descriptors should only be included when the unit is not referred to both with and without the descriptor. When a lithology descriptor is included, the format is "Name Lithology Type". Acceptable examples: Cierbo Formation, Clare Shale Formation
• In addition to the required links, it is strongly preferred that the documentation include a short description of the unit. Information suggested to be in the description includes: the geographic region(s) in which the unit outcrops, geologic age, and dominant lithology.

Table ctlithostratigraphic_formation -

[dustymc]

Big-picture: yes.

Minor request: <li> the examples, they all sorta run together in the parens.

[Jegelewicz]

Controlled vocabulary for lithostratigraphic beds available as locality attributes. Terms may be added to this table without DBA approval and with the approval of one active Code Table Committee member, as long as that Code Table member did not also request the term if the following criteria are met:

• The unit is registered in a national geologic database, with a link included in the documentation.
  • https://ngmdb.usgs.gov/Geolex/search
  • https://www.bgs.ac.uk/technologies/the-bgs-lexicon-of-named-rock-units/
  If the unit is not listed in a national database, the documentation should include a link to a publication that describes the unit.
• The term is properly formatted as "Name Type". Lithology descriptors should only be included when the unit is not referred to both with and without the descriptor. When a lithology descriptor is included, the format is "Name Lithology Type". Acceptable examples: Westfield Fish Bed, Down Cliff Sand Member Starfish Bed
• In addition to the required links, it is strongly preferred that the documentation include a short description of the unit. Information suggested to be in the description includes: the geographic region(s) in which the unit outcrops, geologic age, and dominant lithology.

https://github.com/ArctosDB/arctos/issues/7844

[Jegelewicz]

Controlled vocabulary for lithostratigraphic formations available as locality attributes. Terms may be added to this table without DBA approval and with the approval of one active Code Table Committee member, as long as that Code Table member did not also request the term if the following criteria are met:

• The unit is registered in a national geologic database, with a link included in the documentation.
  • https://ngmdb.usgs.gov/Geolex/search
  • https://www.bgs.ac.uk/technologies/the-bgs-lexicon-of-named-rock-units/
  If the unit is not listed in a national database, the documentation should include a link to a publication that describes the unit.
• The term is properly formatted as "Name Type". Lithology descriptors should only be included when the unit is not referred to both with and without the descriptor. When a lithology descriptor is included, the format is "Name Lithology Type". Acceptable examples: Cierbo Formation, Clare Shale Formation
• In addition to the required links, it is strongly preferred that the documentation include a short description of the unit. Information suggested to be in the description includes: the geographic region(s) in which the unit outcrops, geologic age, and dominant lithology.

https://github.com/ArctosDB/arctos/issues/7844

[Jegelewicz]

Controlled vocabulary for lithostratigraphic groups available as locality attributes. Terms may be added to this table without DBA approval and with the approval of one active Code Table Committee member, as long as that Code Table member did not also request the term if the following criteria are met:

• The unit is registered in a national geologic database, with a link included in the documentation.
  • https://ngmdb.usgs.gov/Geolex/search
  • https://www.bgs.ac.uk/technologies/the-bgs-lexicon-of-named-rock-units/
  If the unit is not listed in a national database, the documentation should include a link to a publication that describes the unit.
• The term is properly formatted as "Name Type". Lithology descriptors should only be included when the unit is not referred to both with and without the descriptor. When a lithology descriptor is included, the format is "Name Lithology Type". Acceptable examples: Dunquin Group, Old Red Sandstone Supergroup
• In addition to the required links, it is strongly preferred that the documentation include a short description of the unit. Information suggested to be in the description includes: the geographic region(s) in which the unit outcrops, geologic age, and dominant lithology.

https://github.com/ArctosDB/arctos/issues/7844

[Jegelewicz]

Controlled vocabulary for lithostratigraphic members available as locality attributes. Terms may be added to this table without DBA approval and with the approval of one active Code Table Committee member, as long as that Code Table member did not also request the term if the following criteria are met:

• The unit is registered in a national geologic database, with a link included in the documentation.
  • https://ngmdb.usgs.gov/Geolex/search
  • https://www.bgs.ac.uk/technologies/the-bgs-lexicon-of-named-rock-units/
  If the unit is not listed in a national database, the documentation should include a link to a publication that describes the unit.
• The term is properly formatted as "Name Type". Lithology descriptors should only be included when the unit is not referred to both with and without the descriptor. When a lithology descriptor is included, the format is "Name Lithology Type". Acceptable examples: Cameron Creek Member, Down Cliff Sand Member
• In addition to the required links, it is strongly preferred that the documentation include a short description of the unit. Information suggested to be in the description includes: the geographic region(s) in which the unit outcrops, geologic age, and dominant lithology.

https://github.com/ArctosDB/arctos/issues/7844

[Jegelewicz]

updates made to code table descriptions