Wikidata:Property proposal/electron configuration

From Wikidata
Jump to navigation Jump to search

electron configuration[edit]

Return to Wikidata:Property proposal/Natural science

   Under discussion
Descriptionproperty of an atom (atom (Q9121)) in chemical element (chemical element (Q11344))
Representselectron configuration (Q53859)
Data typeString
Template parameter"electron configuration" in Template:Infobox element
Domainchemical element (Q11344)
Example 1hydrogen (Q556) → 1s1
Example 2helium (Q560) → 1s2
Example 3lithium (Q568) → [He] 2s1
Example 42s2
Example 52s22p1
Example 62s22p2
Example 72s22p3
Example 82s22p4
Example 92s22p5
Example 102s22p6
Example 11[Nе]3s1
Example 123s2
Example 133s23p1
Example 143s23p2
Example 153s23p3
Example 163s23p4
Example 173s23p5
Example 183s23p6
Sourceconfigurations of the elements (data page) Wikipedia: Electron configurations of the elements
Planned useinclude in templates related to chemical elements
Number of IDs in source126
Expected completenesscomplete coverage can be provided
Robot and gadget jobscan be created
See alsoatomic number (P1086), electron configuration (Q53859)


can be used along with atomic number (P1086) instead of electron configuration (Q53859). Was nominated before Wikidata:Property proposal/Archive/38#electron configuration

Jasper Deng
Egon Willighagen
Denise Slenter
Daniel Mietchen
Andy Mabbett
Emily Temple-Wood
Pablo Busatto (Almondega)
Antony Williams (EPA)
Devon Fyson
Samuel Clark
Tris T7
Pictogram voting comment.svg Notified participants of WikiProject Chemistry

Васин Юрий (talk) 18:23, 22 August 2019 (UTC)


  • Pictogram voting comment.svg Comment The proposal mentions "infobox parameter = "electron configuration" in Template:Infobox element". I note that in enwiki, this is not an input parameter but en:Infobox element reads this data directly from data set en:Template:Infobox element/symbol-to-electron-configuration (which allows reuse of this data in other tables & boxes in that wiki). -DePiep (talk) 19:32, 22 August 2019 (UTC)
  • Pictogram voting comment.svg Comment I got very mixed feelings about this. On the one hand, I think such info is useful, but I don't like to have this on elements. I think the more appropriate place is atoms, like ions. The configuration, after all, is depending on whether the molecule is ionized, a radical, etc. --Egon Willighagen (talk) 07:32, 23 August 2019 (UTC)
    • No matter where to use this property in atoms or chemical elements. Any way this information frequently shown in periodic tables Васин Юрий (talk) 10:49, 23 August 2019 (UTC)
    • It could be specified that it is the ground state electron config. of an atom or the electron configuration of a common ionization of said atom. --User123o987name (talk) 06:00, 18 November 2019 (UTC)
  • Pictogram voting comment.svg Comment superscript is not possible in WD, so we would have to use Unicode symbols for this (like in chemical formulae). Maybe we should try to find a way to model this using qualifier(s) so as to the data could be reused in more than one way (like electron configuration = orbital s, qualifier: number of electrons = 2; orbital d, qualifier: no of e = 6 etc. or something). Wostr (talk) 18:31, 23 August 2019 (UTC)
    • I added some examples to explain that UTF will be enough. We need only numbers ¹ ² ³... symbols. Or number can be placed in parentheses, e.g. 2s[2]. I can enter data for all elements by bot or manually. Васин Юрий (talk) 14:32, 24 August 2019 (UTC)
      • I know that Unicode symbols would be sufficient, but I wonder if this is the best way to model this. Wostr (talk) 13:03, 26 August 2019 (UTC)
        • Maybe brackets could be good alternative? Васин Юрий (talk)
          • That's not the question how to write it in a single string, but rather how to make the data re-usable in different ways, without the need to parse a single string of data. Wostr (talk) 14:30, 5 September 2019 (UTC)
  • Please make it clear in every example which item should get which statements. ChristianKl❫ 14:57, 6 September 2019 (UTC)
  • @Wostr - It could be written like 1s2,2s2,2p6,3s2,3p6,4s2,3d5 (for nonionized Mn) or 1s2, 2s2, 2p6, 3s2, 3p6, 4s2, 3d10, 4p6, 5s2, 4d10, 5p6, 6s1, 4f14, 5d9 (for normal Pt). This conceptually makes sense to me, but either of those examples could be written in order of principal energy levels, like 1s2,2s2,2p6,3s2,3p6,3d10,4s1 (not 1s2,2s2,2p6,3s2,3p6,4s1,3d10) for Cu. Or spaces could be used: 1s2 2s2 2p6 3s2 3p6 4s2 3d1 for Sc, 1s2 2s2 2p6 3s2 3p6 3d10 4s2 4p6 4d10 5s1 for Ag --User123o987name (talk) 06:15, 18 November 2019 (UTC)
  • Symbol support vote.svg Support David (talk) 15:18, 12 October 2019 (UTC)
  • Pictogram voting comment.svg Comment I would suggest to use HTML <sup> and </sup> tags used for superscripting, rather than hard-coded unicode. They're probably easier to parse for downstream apps wanting to use the data in different ways. Jheald (talk) 21:40, 13 October 2019 (UTC)
  • I Symbol oppose vote.svg Oppose if the property uses HTML, Symbol support vote.svg Support if it uses unicode. Unicode is easier to parse as it needs no added actions. It automatically works provided the software supports unicode. HTML on the other hand needs the data users to make assumptions about how we format our data.
Anything that has string as a data-type within Wikidata should be understood by data-reusers to be able to used without additional parsing.
If the data-type would be Mathematical expression I would be okay with mathml style formatting as that's to be expected with that datatype. ChristianKl❫ 08:12, 14 October 2019 (UTC)