|
|
| (17 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| In an attempt to simplify the user experience and promote community contribution of article editing and creation, by diverging from the current limitations of editing the articles' source code which currently appear as a mixture of various syntaxes including: HTML, markdown, and complicated parser functions such as: mathematic and string operations, recursive algorithms, comparators, semantic result queries, and more, each with their own documented, but for less technical individuals, potentially intimidating syntax.
| | <div class="panel radius"> |
| | <h3 class="panel-header">Project:Interface [[File:Eye.svg|x20px|right|link=]]</h3> |
| | <ul class="featured-table"> |
|
| |
|
| I have drafted a solution below which describes a suitable data model for storing article content as semantic sub-objects which would be rendered using a master templates for the published article, allowing modification of variables via form interfaces by contributors.
| | <li class="featured list-item"> |
| | <h4 class="media-heading">Substance</h4> |
| | *[[Project:Interface/Substance/Documentation]] |
| | *[[Project:Interface/Substance/Form]] |
| | *[[Project:Interface/Substance/Template]] |
| | </li> |
|
| |
|
| With such interfaces, contributors could easily modify the content of article sections by simply entering data into standardised form fields rather than unnecessarily being presented with the entire article's source code to fiddle with, which undoubtedly makes our current community hesitant to make changes.
| | </ul> |
| | | </div> |
| We already simplify the user experience by providing very basic structural templates, however we would prefer to develop interactive forms which would include categorically specific form-fields and well documented dynamic interfaces.
| |
| | |
| ==Substances==
| |
| ===Abstract===
| |
| This is the introductory paragraph of the article, containing a summary for use in external applications, or so the user can gain an overview of the substance. This section will be used in
| |
| | |
| ===History===
| |
| These sections will be used to give information relating to the substance's history, development, availability, and popularity:
| |
| | |
| * Discovery ''(For example: by whom, what, where, when, and why was it discovered?)''
| |
| ** Development ''(how was the substance developed? derived from naturally occuring parent compound, produced by total synthesis)
| |
| ** Development
| |
| * Availability
| |
| ** Prevalence
| |
| ** Popularity
| |
| * Legality
| |
| | |
| ===Chemistry===
| |
| These sections will be used to discuss the structural and manufacture of substances:
| |
| | |
| * Molecular structure, with regards to its IUPAC name and any derived parent compounds.
| |
| * Properties
| |
| ** Temperatures in degrees Centigrade / Fahrenheit / Kelvin Melting:
| |
| *** Melting point
| |
| *** Vapour point
| |
| *** Flash point (thermal decomposition)
| |
| ** Density
| |
| ** Solubility in common solvents
| |
| * Production
| |
| ** Synthesis
| |
| ** Extraction
| |
| | |
| * Pharmacology
| |
| | |
| * Pharmacokinetics
| |
| ** Bio-availability and metabolism of ideal preparations and routes of administration for various salts, freebase, etc.
| |
| ** Considerations and risks regarding co-administration of substances.
| |
| | |
| In an attempt to simplify the user experience and promote community contribution of article editing and creation, by diverging from the current limitations of editing the articles' source code which currently appear as a mixture of various syntaxes including: HTML, markdown, and complicated parser functions such as: mathematic and string operations, recursive algorithms, comparators, semantic result queries, and more, each with their own documented, but for less technical individuals, potentially intimidating syntax.
| |
|
| |
|
| I have drafted a solution below which describes a suitable data model for storing article content as semantic sub-objects which would be rendered using a master templates for the published article, allowing modification of variables via form interfaces by contributors.
| | Here we attempt to simplify the user experience and promote community contribution of article editing and creation by diverging from the current limitations of editing article source codes which currently appear as a mixture of various syntaxes including HTML and markdown as well as complicated parser functions such as mathematics and string operations, recursive algorithms, comparators, semantic result queries, and more which all result in a potentially intimidating syntax for less technical individuals. |
|
| |
|
| With such interfaces, contributors could easily modify the content of article sections by simply entering data into standardised form fields rather than unnecessarily being presented with the entire article's source code to fiddle with, which undoubtedly makes our current community hesitant to make changes. | | With such interfaces, contributors could easily modify the content of article sections by simply entering data into standardised form fields rather than unnecessarily being presented with the entire article's source code to fiddle with, which undoubtedly makes our current community hesitant to make changes. |
|
| |
|
| We already simplify the user experience by providing very basic structural templates, however we would prefer to develop interactive forms which would include categorically specific form-fields and well documented dynamic interfaces. | | We already simplify the user experience by providing very basic structural templates; however, we would prefer to develop interactive forms which would include categorically specific form fields and well-documented dynamic interfaces. |
| | |
| ==Substances==
| |
| ===Abstract===
| |
| This is the introductory paragraph of the substance article, which should contain a summary for use in API calls such as search engine results, API calls, or so the user can gain an quick overview of the substance.
| |
| | |
| ===Socio-historical factors===
| |
| These fields will be used to give information relating to the substance's history, availability, and popularity:
| |
| | |
| * Research and Development
| |
| ** Discovery ''(who was responsible for, and when the discovery?)''
| |
| ** Development ''(was the substance discovered from plant sources, or developed for medicinal purposes?)''
| |
| * Intended uses
| |
| ** Indications ''(Indicated usages for the substance, in a therapeutic context)''
| |
| ** Counter-indications ''(Counter-indicated usage considerations, including dangerous combinations, in a therapeutic context)''
| |
| * Availability
| |
| ** Emergence ''(When did the substance first become available
| |
| ** Prevalence ''(How widely, and from where is the substance available? Streets, clearnet, darknet markets, etc)''
| |
| ** Popularity ''When
| |
| * Legality
| |
| | |
| ===Chemistry===
| |
| These sections will be used to discuss the structural properties and activity relationships of substances:
| |
| | |
| * Molecular structure
| |
| ** Description of its IUPAC name and comparison to other derivatives of its parent structure
| |
| * Chemical properties
| |
| ** Temperatures in degrees Centigrade / Fahrenheit / Kelvin Melting for:
| |
| *** Melting point
| |
| *** Vapour point
| |
| *** Flash point (thermal decomposition)
| |
| ** Density in Mole
| |
| ** Solubility in common solvents
| |
| * Production
| |
| ** Synthesis
| |
| ** Extraction
| |
| | |
| * Pharmacology
| |
| ** Receptor affinity references, therapeutic usages.
| |
| * Pharmacokinetics
| |
| ** Bioavailability, metabolic-route, and of ideal preparations and routes of administration for various salts, freebase, etc.
| |
| | |
| * Subjective effects (break down of effects using the effect index, gallery of replications, list of experience reports))
| |
| | |
| Subjective effects (break down of effects using the effect index, gallery of replications, list of experience reports))
| |
