Form:MHRM: Difference between revisions

From Disaster Risk Gateway
No edit summary
No edit summary
Tags: Mobile edit Mobile web edit
 
(9 intermediate revisions by 2 users not shown)
Line 8: Line 8:
     <tr>
     <tr>
         <td><strong>Access:</strong></td>
         <td><strong>Access:</strong></td>
         <td>{{{field|Access|input type=dropdown|values=Open,Subscription|mandatory}}}</td>
         <td>{{{field|Access|input type=dropdown|values=Open,Paid|mandatory}}}</td>
     </tr>
     </tr>
     <tr>
     <tr>
Line 15: Line 15:
</p></td>
</p></td>
         <td>{{{field|Link|input type=text}}}</td>
         <td>{{{field|Link|input type=text}}}</td>
    </tr>
  <tr>
        <td><strong>Author(s):</strong> <br>
            <p class="pfFieldDescription" style="font-size:0.7em; color:gray;">Approach authors</p>
        </td>
        <td>{{{field|Author(s)|input type=text}}}</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><strong>Organisation(s)/Authors:</strong></td>
         <td><strong>Organisation(s):</strong> <br>
         <td>{{{field|Organisation(s)/Authors|input type=text}}}</td>
            <p class="pfFieldDescription" style="font-size:0.7em; color:gray;">Authoring organisation (if applicable)</p>
        </td>
         <td>{{{field|Organisation(s)|input type=text}}}</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><strong>Description:</strong></td>
         <td><strong>Description:</strong> <br>
         <td>{{{field|Description|input type=textarea|rows=5|maxlength=500}}}</td>
            <p class="pfFieldDescription" style="font-size:0.7em; color:gray;">Add a brief (less than 350 word) summary of the approach.</p>
     </tr>
            <p class="pfFieldDescription" style="font-size:0.7em; color:gray;">If you would like to add formatting, see '''[[Formatting|<span style="color: var(--myriad-blue)">Formatting</span>]]''' for guidance</p>
         <td>{{{field|Description|input type=textarea|rows=25}}}</td>
     </tr>>
     <tr>
     <tr>
         <td><strong>Technical Considerations:</strong> <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">E.g. coding languages, code packages, input files etc.</p></td>
         <td><strong>Technical Considerations:</strong> <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">E.g. coding languages, code packages, input files etc.</p></td>
Line 34: Line 44:
</table>
</table>


{{{for form}}}
 
'''Please be aware of copyright and ensure that you have not directly copied any text or other materials from a source without permission. Any contributions you make to Disaster Risk Gateway are with the understanding that all materials you provide are publicly available and follow the content standards.'''
'''Please be aware of copyright and ensure that you have not directly copied any text or other materials from a source without permission. Any contributions you make to Disaster Risk Gateway are with the understanding that all materials you provide are publicly available and follow the content standards outlined in the [[Disaster_Risk_Gateway:Terms of Use|<span style="color: var(--myriad-blue)">Terms of Use]]'''
{{{end form}}}
 


{{{end template}}}
{{{end template}}}

Latest revision as of 12:21, 30 May 2025

MHRM

>
Publication Year: Publication Year
Access: Access
Link:

Add link(s) to the approach (e.g. a website, or to a paper)

Link
Author(s):

Approach authors

Author(s)
Organisation(s):

Authoring organisation (if applicable)

Organisation(s)
Description:

Add a brief (less than 350 word) summary of the approach.

If you would like to add formatting, see Formatting for guidance

Description
Technical Considerations:

E.g. coding languages, code packages, input files etc.

Technical Considerations
Key Words:

Add 3 to 5 keywords related to the approach

Key Words


Please be aware of copyright and ensure that you have not directly copied any text or other materials from a source without permission. Any contributions you make to Disaster Risk Gateway are with the understanding that all materials you provide are publicly available and follow the content standards outlined in the Terms of Use


{{{end template}}}