Mineral Pages Update
From Mindat
| Table of contents |
[edit]
Important
This page is a gathering-place for notes that will be shared with others. Although nothing here is especially confidential, I will not link this into the manual, this is just a working space for some ideas. Feel free to add to this.
[edit]
Mineral Data
We will list here the items of information stored in mineral data records and with it comments as to the way we store data and what we should do to improve it.
[edit]
MySQL table structure
`id` int(11) NOT NULL auto_increment,
`name` varchar(255) default NULL,
`description` mediumtext,
`formula` varchar(255) default NULL,
`idealformula` varchar(255) default NULL,
`impurities` varchar(255) default NULL,
`elements` varchar(255) default NULL,
`sigelements` varchar(255) default NULL,
`ima` tinyint(4) default NULL,
`imayear` int(11) default NULL,
`tlform` varchar(255) NOT NULL default ,
`mindatstatus` int(11) default NULL,
`statusreason` mediumtext,
`cim` varchar(40) default NULL,
`occurrence` mediumtext,
`otheroccurrence` text,
`industrial` varchar(255) NOT NULL default ,
`yeardiscovery` varchar(4) default NULL,
`diapheny` set('Transparent','Translucent','Translucent on thin edges','Opaque') default NULL,
`cleavage` varchar(255) default NULL,
`parting` varchar(255) NOT NULL default ,
`tenacity` enum('brittle','very brittle','sectile','waxy','elastic','fragile','malleable') default NULL,
`colour` varchar(255) default NULL,
`crystalsystem` varchar(255) default NULL,
`csmetamict` tinyint(4) NOT NULL default '0',
`cs` varchar(255) default NULL,
`fracture` varchar(255) default NULL,
`hmin` float(3,1) NOT NULL default '0.0',
`hardtype` tinyint(4) NOT NULL default '0',
`hmax` float(3,1) NOT NULL default '0.0',
`vhnmin` float default NULL,
`vhnmax` float default NULL,
`vhng` int(11) NOT NULL default '0',
`vhns` int(11) NOT NULL default '0',
`luminescence` varchar(255) default NULL,
`lustre` varchar(255) default NULL,
`lustretype` set('Adamantine','Sub-Adamantine','Vitreous','Sub-Vitreous','Resinous','Waxy','Greasy','Silky','Pearly','Metallic','Sub-Metallic','Dull','Earthy') default NULL,
`aboutname` mediumtext,
`other` mediumtext,
`specificgravity` varchar(255) default NULL,
`streak` varchar(255) default NULL,
`uid` int(11) default NULL,
`checkedby` int(11) default NULL,
`varietyof` int(11) default NULL,
`synid` int(11) NOT NULL default '0',
`crystalform` varchar(255) default NULL,
`mingroup` varchar(255) default NULL,
`trans` varchar(255) default NULL,
`strunz1` varchar(4) default NULL,
`strunz2` varchar(4) default NULL,
`strunz3` varchar(4) default NULL,
`strunz4` varchar(4) default NULL,
`series1` int(11) NOT NULL default '0',
`series2` int(11) NOT NULL default '0',
`series3` int(11) NOT NULL default '0',
`sortname` varchar(255) NOT NULL default ,
`dana1` int(11) NOT NULL default '0',
`dana2` char(4) default '0',
`dana3` char(4) default '0',
`dana4` char(4) default '0',
`groupid` int(11) NOT NULL default '0',
`spacing` varchar(64) NOT NULL default ,
`synid2` int(11) NOT NULL default '0',
`notl` tinyint(4) NOT NULL default '0',
`csystem` enum('Isometric','Orthorhombic','Hexagonal','Trigonal','Tetragonal','Monoclinic','Triclinic','Amorphous') default NULL,
`cclass` int(11) NOT NULL default '0',
`spacegroup` int(11) NOT NULL default '0',
`a` float default NULL,
`b` float default NULL,
`c` float default NULL,
`alpha` float default NULL,
`beta` float default NULL,
`gamma` float default NULL,
`va3` float default NULL,
`z` int(11) default NULL,
`dmeas` float NOT NULL default '0',
`dmeas2` float NOT NULL default '0',
`dcalc` float default NULL,
`cleavagetype` enum('None Observed','Poor/Indistinct','Imperfect/Fair','Distinct/Good','Very Good','Perfect') default NULL,
`fracturetype` set('None observed','Irregular/Uneven','Splintery','Hackly','Conchoidal','Sub-Conchoidal','Fibrous','Micaeous','Step-Like') default NULL,
`morphology` mediumtext,
`twinning` mediumtext,
`epitaxidescription` mediumtext,
`xray` mediumtext,
`xraytext` text,
`healthwarning` mediumtext,
`opticaltype` enum('Isotropic','Uniaxial','Biaxial') default NULL,
`opticalsign` enum('+','-','+/-') default NULL,
`opticalalpha` float default NULL,
`opticalbeta` float default NULL,
`opticalgamma` float default NULL,
`opticalomega` float default NULL,
`opticalepsilon` float default NULL,
`opticalalpha2` float default NULL,
`opticalbeta2` float default NULL,
`opticalgamma2` float default NULL,
`opticalepsilon2` float NOT NULL default '0',
`opticalomega2` float NOT NULL default '0',
`opticaln` float default NULL,
`opticaln2` float default NULL,
`optical2vcalc` int(11) default NULL,
`optical2vmeasured` int(11) default NULL,
`optical2vcalc2` float default NULL,
`optical2vmeasured2` float default NULL,
`opticaldispersion` varchar(255) default NULL,
`opticalpleochroism` enum('Non-pleochroic','Not Visible','Weak','Visible','Strong') default NULL,
`opticalpleochorismdesc` varchar(255) default NULL,
`opticalbirefringence` text,
`opticalcomments` varchar(255) default NULL,
`opticalcolour` varchar(255) default NULL,
`opticalinternal` varchar(255) default NULL,
`opticaltropic` enum('Isotropic','Anisotropic') default NULL,
`opticalanisotropism` varchar(255) default NULL,
`opticalanisomin` float default NULL,
`opticalanisomax` float default NULL,
`opticalbireflectance` varchar(255) default NULL,
`opticalbirefmin` float default NULL,
`opticalbirefmax` float default NULL,
`opticalr` mediumtext,
`chemcomments` text,
`chemdata` mediumtext,
`empformula` varchar(255) default NULL,
`thermalbehaviour` varchar(255) default NULL,
`uv` varchar(255) default NULL,
`ir` varchar(255) NOT NULL default ,
`magnetism` enum('Diamagnetic','Paramagnetic','Ferromagnetic','Antiferromagnetic','Ferrimagnetic') default NULL,
`relationship` enum('None apparent','Polymorph of','Isostructural with','Structurally related to','Chemically related to','Analogue of') default NULL,
`typeconserved` varchar(255) default NULL,
`relatedmin` int(11) default NULL,
`relatedcomments` varchar(255) default NULL,
`bestphoto` int(11) NOT NULL default '0',
`references` mediumtext,
`metaphone` varchar(255) NOT NULL default ,
[edit]
id
Each mineral record has a unique identifier, the ID field. This is non-changing, and is used for all internal links within mindat (eg synonym field)
[edit]
name
This is the name of the mineral. The maximum length is 255 characters.
[edit]
notes
- The format for duplicate names is to have the source of the name (usually an author) in parenthesis, eg Bronzite (of Finch)
- The first character of mineral names is capitalized. This is standard throughout mindat and is done simply for visual impact on screen.
[edit]
changes required
- This field is stored in ISO (western) character set. This means that foreign characters are represented by the HTML encoded unicode character sequences. This means that the mineral name 方解石 (the chinese form for Calcite) is actually stored in the database as 方解石 This means that the data is only really valid for the web, and use of data on other systems (eg portable devices) is complicated. We need to change to a better format - the database field needs to be switched to a UTF8 encoding, existing data converted to UTF8, and all pages on the site updated to UTF8 in order to allow display and input. Note - the messageboard is currently working as UTF8.
[edit]
description
This is a free-text format description of the mineral. Descriptions of any reasonable size are allowed.
[edit]
notes
- Content allows HTML formatting (eg bold, tables, etc)
[edit]
changes required
- ISO format, should be converted to UTF8.
- Should we provide a better way to edit this (HTML editor?)
- Should we create a markup content (similar to MediaWiki) rather than using HTML? - would be better for porting to other devices. If so, how do we convert existing data?
- Version history/control for edits to this field would be important. We also could open up editing of this field to a greater number of people than those who could edit physical properties. One drawback of that is people entering in physical data into here because they have no access elsewhere.
[edit]
formula
The chemical formula of the mineral,
[edit]
notes
- The encoding of this is done in a strange way, based on code I originally wrote in 1993.
- notes can be added after the formula eg (where 0.2<x<0.6) but it's important to only use lower-case letters to avoid the system picking up bogus elements (eg a capital W on where being mistaken for Tungsten)
[edit]
changes required
- We need to be clear what goes in here. Is it ideal formula, or real formula? Should Sphalerite be ZnS or (Zn,Fe)S ? We have another field for 'Ideal Formula' so perhaps we should use them both?
[edit]
ideal formula
See above. This isn't really used much (is it used at all?)
This could be a valueable field to have. If you ever start putting chemical analyses in this could be used to determine the ideal chemical composition (most reference works use this)--David Von Bargen 21:47, 6 Mar 2006 (GMT)
[edit]
impurities
A list of common impurities found within this mineral.
[edit]
notes
- There is no indication of how common these are, usual % replacement, what it is replacing, whether it's true chemical replacement within the lattice or due to micro inclusions of another mineral, etc, etc, etc.
[edit]
changes required
- Is this actually of any benefit at all? We don't have much data for this, and it's possibly better dealt with based on real data taken in with Raman data sets etc. Perhaps we remove this field.
- Or fill it in automatically with the differences between real formula and ideal formula? See below
[edit]
elements
A list of all elements within the mineral.
[edit]
notes
- This list is created automatically, and does not need to be edited by hand
- This can be fooled by incorrect notes in the formula fields (see above)
[edit]
changes required
- Should this be based on real formula or ideal formula? Perhaps use the differences between the two into the impurities field, and allow an option on chemical search for searching clean data or real-world data including impurities.
[edit]
sigelements
The idea for this was very similar to the list of elements from the "ideal formula" listed above. It's almost certainly not needed if we change the above.
[edit]
ima
A field that contains a numeric value specifying IMA status. This is one of
0 - "No Data" 1 - "Approved" 2 - "Discredited" 3 - "Rejected" 4 - "Pending Approval" 5 - "Not Approved" 6 - "Valid - first described prior to 1959 (pre-IMA) - 'Grandfathered'" 7 - "Questionable/Doubtful"
[edit]
notes
- This data is based on letter codes given to species as published on the IMA website. It is unclear however how these codes are specified. Does the IMA actually say that something is "Questionable?". As far as I know, there is simply a list of minerals that have been formally approved, formally discredited and formally rejected. Everything else is not strictly an IMA verdict, however it appears the IMA are making some judgements about whether specimens pre 1959 are valid or questionable.
[edit]
changes required
- At very least need to clear up wording for this section so we specify whether it is something that has been formally accepted by the IMA and voted on (eg a mineral discreditation) or has been arbitrarily listed as 'Questionable'
- There is no history of events, eg Approved 1968, Discredited 1975, Re-approved based on new analysis 1993. Is this actually needed?
- A lot of this could be specified in the literature for the mineral. It should have references to the discreditation or approval --David Von Bargen 21:50, 6 Mar 2006 (GMT)
[edit]
ima year
The year (if known) associated with the event above.
[edit]
notes
- Sometimes we may get this wrong, and put the year of publication as the year of approval.
[edit]
changes required
I think we have to assume that this particular data field has poor quality data, and I would like to find a way of getting a clean set of data with all IMA judgements since 1959 and replace the dates.
[edit]
tlform
The form of the material found at the type locality. A text description.
[edit]
notes
- Probably OK, needs to be converted to UTF8 as above.
[edit]
mindatstatus
This field was added to address some concerns over the IMA status previously. This contained what we believed was the validity of a species, which could be:
Definately Not Valid Possibly Not Valid Possibly Valid Definately Valid
[edit]
notes
- The idea was to flag up this that were being talked about as potentially problematical before they had reached a formal stage of discreditation. The biggest issue with this is that a lot of this data was effectively mineralogical 'gossip' rather than proven science, so although the intentions were good (to warn people that something may, at some poing, end up being discredited), the validity of this field is now in doubt.
[edit]
changes required
- We need to decide whether to keep this as it is, to delete it completely, or to change it into a description box that will allow people to leave signed notes saying that they believe there is a validity issue with this species, and why (eg, for Horsfordite, the note could explain that the chemistry looks suspect and the only known specimen appears to be lost).
[edit]
status reason
Meant to be the description as to why the status above has been set. Possibly should keep this one and allow people to add signed notes to this as shown above.
[edit]
changes required
- to UTF8
[edit]
cim
The reference number in Hey's Chemical Index of Minerals (3rd Edition).
[edit]
notes
- Data appears valid and complete.
- no additional entries are being added for new species, it is being left as it was in 1993.
[edit]
occurrence
A text field describing the occurrence
