https://mwiki.costasano.club/index.php?action=history&feed=atom&title=ICT%3ADrupal_Standard%3A_Field_naming_Convention 2026-04-17T19:46:58Z Revision history for this page on the wiki MediaWiki 1.45.1 https://mwiki.costasano.club/index.php?title=ICT:Drupal_Standard:_Field_naming_Convention&diff=1551&oldid=prev 2026-03-22T15:59:36Z

<p>Created page with &quot;== ICT Standard: Field Naming Conventions == To ensure the &#039;&#039;&#039;Heritage Tweaks&#039;&#039;&#039; module functions correctly and the database remains organized, all new fields must follow this dual-naming convention. === 1. The Prefix Rule (Namespace) === All field machine names must start with a two-character code representing the &#039;&#039;&#039;Content Type&#039;&#039;&#039;. * &#039;&#039;&#039;Pattern:&#039;&#039;&#039; &lt;code&gt;field_xx_fieldname&lt;/code&gt; (where &lt;code&gt;xx&lt;/code&gt; is the unique prefix). * &#039;&#039;&#039;Example:&#039;&#039;&#039; &lt;code&gt;field_sa_name&lt;/cod...&quot;</p> <p><b>New page</b></p><div>== ICT Standard: Field Naming Conventions ==<br /> <br /> To ensure the &#039;&#039;&#039;Heritage Tweaks&#039;&#039;&#039; module functions correctly and the database remains organized, all new fields must follow this dual-naming convention.<br /> <br /> === 1. The Prefix Rule (Namespace) ===<br /> All field machine names must start with a two-character code representing the &#039;&#039;&#039;Content Type&#039;&#039;&#039;.<br /> * &#039;&#039;&#039;Pattern:&#039;&#039;&#039; &lt;code&gt;field_xx_fieldname&lt;/code&gt; (where &lt;code&gt;xx&lt;/code&gt; is the unique prefix).<br /> * &#039;&#039;&#039;Example:&#039;&#039;&#039; &lt;code&gt;field_sa_name&lt;/code&gt; for Sanatoria, &lt;code&gt;field_pa_surname&lt;/code&gt; for Patients.<br /> * &#039;&#039;&#039;Benefit:&#039;&#039;&#039; Prevents naming collisions and makes Configuration Management (CM) easier to filter.<br /> <br /> === 2. The Suffix Rule (Functional Hook) ===<br /> Any text field intended to store a historical date in &lt;code&gt;dd/mm/yyyy&lt;/code&gt; format must end with the suffix &lt;code&gt;_day&lt;/code&gt;.<br /> * &#039;&#039;&#039;Pattern:&#039;&#039;&#039; &lt;code&gt;field_xx_customname_day&lt;/code&gt;<br /> * &#039;&#039;&#039;Example:&#039;&#039;&#039; &lt;code&gt;field_sa_foundation_day&lt;/code&gt;<br /> * &#039;&#039;&#039;Logic:&#039;&#039;&#039; The PHP function &lt;code&gt;heritage_tweaks_date_validate&lt;/code&gt; automatically scans for this suffix to apply:<br /> ** Automatic UI Placeholders (dd/mm/yyyy).<br /> ** RegEx format validation.<br /> ** Calendar sanity checks (Leap years/invalid months).<br /> <br /> === Summary Table for Successors ===<br /> {| class=&quot;wikitable&quot;<br /> ! Field Purpose !! Required Suffix !! Resulting Behavior<br /> <br /> |-<br /> | Standard Text || (None) || Normal Drupal behavior<br /> |-<br /> <br /> | Historical Date || &#039;&#039;&#039;_day&#039;&#039;&#039; || Text-entry with DD/MM/YYYY validation<br /> |}<br /> <br /> [[Category:ICT Standards]] [[Category:Database Design]]</div>

Mngr