New locality attribute - Mindat location identifier

[Jegelewicz]

Issue Documentation is http://handbook.arctosdb.org/how_to/How-to-Use-Issues-in-Arctos.html

Goal I am cataloging mineral specimens and many of them come from mines with locality information stored at https://www.mindat.org I would like to have a locality identifier that links to mindat using a base URI of https://www.mindat.org/loc-

Context A locality ID that can DO something!

Table http://test.arctos.database.museum/info/ctDocumentation.cfm?table=ctlocality_attribute_type

Value Mindat location identifier

Definition Enter the identification number only of the Mindat location

Collection type N/A

Attribute data type free text, but can we limit to numbers only?

Attribute value N/A

Attribute units N/A

Part tissue flag N/A

Other ID BaseURL https://www.mindat.org/loc-

Priority Please assign a priority-label.

NOTE: I am creating named localities for a lot of mines using the Mindat information and placing the URL to the Mindat location in either the locality remark (if Mindat provides no coordinates) or the georeference source (if Mindat provides coordinates)

See Valenciana Mine

[dustymc]

This could be implemented as you suggest but it's Major Surgery, would be overly complicated, and the identifiers would be unnecessarily fragile (eg "2326.html" which will all break as soon as mindat updates their architecture).

Suggest: add the type, supply the URL as the identifier.

Alternate: add it to site identifier, HTML-wrap those in the UI when they look like URLs.

I'm not sure I see any advantage to the "3.0" approach here; Mindat (unlike eg genbank) doesn't seem to be issuing identifiers that are made to do things outside of the URL, and they don't much support building URLs around bare identifiers.

[Jegelewicz]

Makes sense, but I just found this too. This USGS thingee has all kinds of cool stuff.....

https://mrdata.usgs.gov/mrds/show-mrds.php?dep_id=10013310

Could we use these with a base URI?

Here is the Arctos locality

https://arctos.database.museum/editLocality.cfm?locality_id=11168466

[dustymc]

Those are formed where a base_url could work, but I'm still not seeing any compelling reasons to add the complexity - the full URL does the same thing, you're never very likely to have "10013310" by itself (or know what it is if you do), it's easy to copy-paste, .....

These seem a very different kind of data than OtherIDs was developed to accommodate. Those are intended to integrate resources that are directly related to individual specimens, where these seem to be information about something related to something related to a specimen and not directly to specimens themselves - right?

I think I'm leaning more towards dumping these all into site identifier (and html-wrapping it when possible) instead of firing up a new concept for every possible vaguely-related thing, but I also can't identify any compelling technical reason to go one way or the other.

[Jegelewicz]

Using Mindat urls as site identifier attribute. Added to documentation.

[Jegelewicz]

Added Mindat identifiers to NMMNHS localities.