Meteorite taxonomy plan

[Jegelewicz]

I was going to place the meteorite taxon names in with the mineral name types. Meteorite taxonomy often uses codes instead of words for names. For instance

CI1 - A carbonaceous chondrite of the CI group that is petrologic type 1. https://www.lpi.usra.edu/meteor/metbullclass.php?sea=CI1

I cannot create the name CI1 (and by the way that is capital c capital i 1) because I am not allowed two capital letters in a mineral taxon name. Can we relax that trigger for minerals or create a new name type "meteorite" with the relaxed triggers?

I am trying to get some data in for the UNM meteoritic collection.

[dustymc]

It's now allowing 2 uppercase characters followed by an integer for mineral taxonomy.

or create a new name type

I think that's worthy of discussion. Losing the distinction between taxonomy (formal stuff) and identifications (how that formal stuff gets applied to individuals) would be a loss of functionality, and I'm not sure that distinction really exists in "non-Linnean" codes, "assigned by the database editor" is pretty explicitly stuff someone made up outside of any formal process, and I have no idea how we should be treating that.

[Jegelewicz]

@Nicole-Ridgwell-NMMNHS @beth3ha now that I have the list of meteorite taxa, I am wondering if we should create a new name type = meteorite. This would make it easy to get all of the meteorite names whereas if I add them as type = mineral, they will be mixed in with the mineral names and we would need something else to tease them out. What do you guys think?

[beth3ha]

It sounds like creating a new type would be most beneficial. I second the motion.

Best Regards

======

Beth Ha Program Coordinator COMPRES/Institute of Meteoritics 1 University of New Mexico MSC03 2050 Albuquerque, NM 87131 @.**@.> 505-503-0416

I do not expect you to read, act or respond outside your normal work hours.

On Jan 27, 2022, at 12:37 PM, Teresa Mayfield-Meyer @.**@.>> wrote:

[EXTERNAL]

@Nicole-Ridgwell-NMMNHShttps://github.com/Nicole-Ridgwell-NMMNHS @beth3hahttps://github.com/beth3ha now that I have the list of meteorite taxa, I am wondering if we should create a new name type = meteorite. This would make it easy to get all of the meteorite names whereas if I add them as type = mineral, they will be mixed in with the mineral names and we would need something else to tease them out. What do you guys think?

— Reply to this email directly, view it on GitHubhttps://github.com/ArctosDB/arctos/issues/4277#issuecomment-1023573305, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVIGRWA6D7YW4E4TQWBBZ4DUYGNIVANCNFSM5MNRFE2Q. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.Message ID: @.***>

[Nicole-Ridgwell-NMMNHS]

I'd definitely willing to be persuaded, but just looking at the taxon types now, they are very, very broad categories: https://arctos.database.museum/info/ctDocumentation.cfm?table=cttaxon_name_type, and it seems to me there ought to be some other way meteorite names could be extracted.

Mineral type taxa are currently very diverse encompassing rocks as well and includes multiple different types of classification systems.

[Jegelewicz]

I think a brief meetup would be good - let's talk about this at the next code table meeting. - I'll send an invite to @beth3ha

[beth3ha]

Yesterday was a snow day for UNM. I am available today or next week starting in Tuesday.

Best Regards

======

Beth Ha Program Coordinator COMPRES/Institute of Meteoritics 1 University of New Mexico MSC03 2050 Albuquerque, NM 87131 @.**@.> 505-503-0416

I do not expect you to read, act or respond outside your normal work hours.

On Feb 3, 2022, at 9:16 AM, Teresa Mayfield-Meyer @.**@.>> wrote:

[EXTERNAL]

I think a brief meetup would be good - let's talk about this at the next code table meeting. - I'll send an invite to @beth3hahttps://github.com/beth3ha

— Reply to this email directly, view it on GitHubhttps://github.com/ArctosDB/arctos/issues/4277#issuecomment-1029154856, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVIGRWEW2WPNEIPLNNAJSX3UZKS5BANCNFSM5MNRFE2Q. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.Message ID: @.***>

[beth3ha]

Oh! I just realized you invited me to a meeting on a Thursday in two weeks. My apologies. I am not following my "no email before coffee" policy.

[Jegelewicz]

@beth3ha Lol - can you make that one?

[beth3ha]

Yeah! I've accepted the invitation.

[Jegelewicz]

Beth and Nicole are good with using mineral names and make sure meteorite is in all of the classifications.