You are here

exif_helper_page.html.twig in Exif 8

Same filename and directory in other branches
  1. 8.2 templates/exif_helper_page.html.twig
{% if message|trim %}
    <div class="region region-highlighted">
        <div class="messages messages--status" aria-label="Status message" role="contentinfo">
            <h3 class="visually-hidden">Status message</h3>
            {{ message }}
        </div>
    </div>
{% endif %}
<h3>{% trans %}About{% endtrans %}</h3>
<p>{% trans %}The Exif module allows you :{% endtrans %}
<ul>
    <li>{% trans %}extract metadata from an image{% endtrans %}</li>
    <li>{% trans %}to classify your images by settings terms in taxonomy vocabulary{% endtrans %}</li>
</ul>
{% trans %}To classify images, you define <em>vocabularies</em> that contain related
    <em>terms</em>, and then assign the vocabularies to content types. For more information, see the online handbook entry for the
    <a href="{{ taxonomy }}">Taxonomy module</a>.{% endtrans %}
</p>
<h3>{% trans %}Uses{% endtrans %}</h3>
<dl>
    <dt>{% trans %}Creating vocabularies{% endtrans %}</dt>
    <dd>{% trans %}This is optional{% endtrans %}</dd>
    <dd>{% trans %}Users with sufficient <a href="@perm">permissions</a> can create <em>vocabularies</em> through the <a
                href="@taxo">Taxonomy
            page</a>. The page listing the terms provides a drag-and-drop    interface for controlling the order of the terms and sub-terms within a vocabulary, in a hierarchical fashion.{% endtrans %}
        {% trans %}If you want, the exif module can create in the chosen vocabulary (by default "Photographies\' metadata"), the following structure:{% endtrans %}
        <ul class="vocabulary-structure">
            <li>{% trans %}<em>vocabulary</em>: Photographies' metadata{% endtrans %}</li>
            <ul>
                <li>{% trans %}<em>term</em>: iptc{% endtrans %}</li>
                <ul>
                    <li>{% trans %}<em>sub-term</em>: keywords{% endtrans %}</li>
                    <ul>
                        <li>{% trans %}<em>sub-term</em>: Paris{% endtrans %}</li>
                        <li>{% trans %}<em>sub-term</em>: Friends{% endtrans %}</li>
                    </ul>
                </ul>
                <ul>
                    <li>{% trans %}<em>sub-term</em>: caption{% endtrans %}</li>
                    <ul>
                        <li>{% trans %}<em>sub-term</em>: Le louvre{% endtrans %}</li>
                    </ul>
                </ul>
            </ul>
            <ul>
                <li>{% trans %}<em>term</em>: exif{% endtrans %}</li>
                <ul>
                    <li>{% trans %}<em>sub-term</em>: model{% endtrans %}</li>
                    <ul>
                        <li>{% trans %}<em>sub-term</em>: KINON DE800{% endtrans %}</li>
                    </ul>
                </ul>
                <ul>
                    <li>{% trans %}<em>sub-term</em>: isospeedratings{% endtrans %}</li>
                    <ul>
                        <li>{% trans %}<em>sub-term</em>: 200{% endtrans %}</li>
                    </ul>
                </ul>
            </ul>
        </ul>
        <a class="button button-small form-submit" href="helper/vocabulary">{% trans %}create a vocabulary for my
                photos.{% endtrans %}</a>
    </dd>
    <dt>{% trans %}Creating type for Photos{% endtrans %}</dt>
    <dd>{% trans %}To get metadata information of an image, you have to choose on which node type the extraction should be made.{% endtrans %}
        {% trans %}You also have to create fields with specific names using the new Field UI.{% endtrans %}
        {% trans %}The type of the field can be :{% endtrans %}
        <ul>
            <li>{% trans %}<em>text field</em>: extract information and put it in the text field.{% endtrans %}.</li>
            <li>{% trans %}<em>term reference
                field</em>: extract information, create terms and sub-terms if needed and put it in the field.{% endtrans %}
                .
            </li>
        </ul>
        {% trans %}Please, if you want to use term reference field, ensure :{% endtrans %}
        <ul>
            <li>{% trans %}you choose the autocompletion widget and{% endtrans %}</li>
            <li>{% trans %}the "Images" Vocabulary exist.{% endtrans %}</li>
        </ul>
        {% trans %}TIPS : Note for iptc and exif fields that have several values (like field iptc "keywords" as an example), {% endtrans %}
        {% trans %}if you want to get all the values, do not forget to configure the field to use unlimited number of values (by default, set to 1).{% endtrans %}
        {% trans %}if you want, the exif module can create a node type 'Photography' with a image field and some basic
        metadata fields (keywords, model and title).{% endtrans %}<br>
        <a class="button button-small form-submit" href="helper/nodetype">{% trans %}create a
                <b>node</b> content type for my
                            photos.{% endtrans %}</a> <b>OR</b>
        <a class="button button-small form-submit" href="helper/mediatype">{% trans %}create a
                <b>media</b> content type for my
                             photos.{% endtrans %}</a>
    </dd>
</dl>

File

templates/exif_helper_page.html.twig
View source
  1. {% if message|trim %}
  2. <div class="region region-highlighted">
  3. <div class="messages messages--status" aria-label="Status message" role="contentinfo">
  4. <h3 class="visually-hidden">Status message</h3>
  5. {{ message }}
  6. </div>
  7. </div>
  8. {% endif %}
  9. <h3>{% trans %}About{% endtrans %}</h3>
  10. <p>{% trans %}The Exif module allows you :{% endtrans %}
  11. <ul>
  12. <li>{% trans %}extract metadata from an image{% endtrans %}</li>
  13. <li>{% trans %}to classify your images by settings terms in taxonomy vocabulary{% endtrans %}</li>
  14. </ul>
  15. {% trans %}To classify images, you define <em>vocabularies</em> that contain related
  16. <em>terms</em>, and then assign the vocabularies to content types. For more information, see the online handbook entry for the
  17. <a href="{{ taxonomy }}">Taxonomy module</a>.{% endtrans %}
  18. </p>
  19. <h3>{% trans %}Uses{% endtrans %}</h3>
  20. <dl>
  21. <dt>{% trans %}Creating vocabularies{% endtrans %}</dt>
  22. <dd>{% trans %}This is optional{% endtrans %}</dd>
  23. <dd>{% trans %}Users with sufficient <a href="@perm">permissions</a> can create <em>vocabularies</em> through the <a
  24. href="@taxo">Taxonomy
  25. page</a>. The page listing the terms provides a drag-and-drop interface for controlling the order of the terms and sub-terms within a vocabulary, in a hierarchical fashion.{% endtrans %}
  26. {% trans %}If you want, the exif module can create in the chosen vocabulary (by default "Photographies\' metadata"), the following structure:{% endtrans %}
  27. <ul class="vocabulary-structure">
  28. <li>{% trans %}<em>vocabulary</em>: Photographies' metadata{% endtrans %}</li>
  29. <ul>
  30. <li>{% trans %}<em>term</em>: iptc{% endtrans %}</li>
  31. <ul>
  32. <li>{% trans %}<em>sub-term</em>: keywords{% endtrans %}</li>
  33. <ul>
  34. <li>{% trans %}<em>sub-term</em>: Paris{% endtrans %}</li>
  35. <li>{% trans %}<em>sub-term</em>: Friends{% endtrans %}</li>
  36. </ul>
  37. </ul>
  38. <ul>
  39. <li>{% trans %}<em>sub-term</em>: caption{% endtrans %}</li>
  40. <ul>
  41. <li>{% trans %}<em>sub-term</em>: Le louvre{% endtrans %}</li>
  42. </ul>
  43. </ul>
  44. </ul>
  45. <ul>
  46. <li>{% trans %}<em>term</em>: exif{% endtrans %}</li>
  47. <ul>
  48. <li>{% trans %}<em>sub-term</em>: model{% endtrans %}</li>
  49. <ul>
  50. <li>{% trans %}<em>sub-term</em>: KINON DE800{% endtrans %}</li>
  51. </ul>
  52. </ul>
  53. <ul>
  54. <li>{% trans %}<em>sub-term</em>: isospeedratings{% endtrans %}</li>
  55. <ul>
  56. <li>{% trans %}<em>sub-term</em>: 200{% endtrans %}</li>
  57. </ul>
  58. </ul>
  59. </ul>
  60. </ul>
  61. <a class="button button-small form-submit" href="helper/vocabulary">{% trans %}create a vocabulary for my
  62. photos.{% endtrans %}</a>
  63. </dd>
  64. <dt>{% trans %}Creating type for Photos{% endtrans %}</dt>
  65. <dd>{% trans %}To get metadata information of an image, you have to choose on which node type the extraction should be made.{% endtrans %}
  66. {% trans %}You also have to create fields with specific names using the new Field UI.{% endtrans %}
  67. {% trans %}The type of the field can be :{% endtrans %}
  68. <ul>
  69. <li>{% trans %}<em>text field</em>: extract information and put it in the text field.{% endtrans %}.</li>
  70. <li>{% trans %}<em>term reference
  71. field</em>: extract information, create terms and sub-terms if needed and put it in the field.{% endtrans %}
  72. .
  73. </li>
  74. </ul>
  75. {% trans %}Please, if you want to use term reference field, ensure :{% endtrans %}
  76. <ul>
  77. <li>{% trans %}you choose the autocompletion widget and{% endtrans %}</li>
  78. <li>{% trans %}the "Images" Vocabulary exist.{% endtrans %}</li>
  79. </ul>
  80. {% trans %}TIPS : Note for iptc and exif fields that have several values (like field iptc "keywords" as an example), {% endtrans %}
  81. {% trans %}if you want to get all the values, do not forget to configure the field to use unlimited number of values (by default, set to 1).{% endtrans %}
  82. {% trans %}if you want, the exif module can create a node type 'Photography' with a image field and some basic
  83. metadata fields (keywords, model and title).{% endtrans %}<br>
  84. <a class="button button-small form-submit" href="helper/nodetype">{% trans %}create a
  85. <b>node</b> content type for my
  86. photos.{% endtrans %}</a> <b>OR</b>
  87. <a class="button button-small form-submit" href="helper/mediatype">{% trans %}create a
  88. <b>media</b> content type for my
  89. photos.{% endtrans %}</a>
  90. </dd>
  91. </dl>