</ol>
                    </div>
                </div>
            </div>
        </div>
        <section class="content">
            <la:form action="/admin/dict/synonym/">
                <la:hidden property="crudMode"/>
                <la:hidden property="dictId"/>
                <c:if test="${crudMode==2}">
                    <la:hidden property="id"/>
                </c:if>

labels.dict_configuration=Dictionary List
labels.dict_list_title=Dictionary List
labels.dict_list_link=Dictionary
labels.dictionary_name=Name
labels.dictionary_type=Type
labels.dict_synonym_configuration=Synonym List
labels.dict_synonym_title=Synonym List
labels.dict_synonym_list_link=List
labels.dict_synonym_link_create=Create New
labels.dict_synonym_link_edit=Edit
labels.dict_synonym_link_delete=Delete
labels.dict_synonym_link_details=Details

                        </ol>
                    </div>
                </div>
            </div>
        </div>
        <section class="content">
            <la:form action="/admin/dict/synonym/upload" enctype="multipart/form-data">
                <la:hidden property="dictId"/>
                <div class="row">
                    <div class="col-md-12">

    # o procedureSynonymHandlingType: (NotRequired - Default NONE)
    #  You can specify the handling type of procedure synonym.
    #   NONE - No handling. (default)
    #   INCLUDE - It includes procedure synonyms.
    #   SWITCH - It switches all normal procedures to procedure synonyms.
    #
    #; procedureSynonymHandlingType = NONE
    # - - - - - - - - - -/

                                                       items="${synonymItemItems}">
                                                <tr
                                                        data-href="${contextPath}/admin/dict/synonym/details/${f:u(dictId)}/4/${f:u(data.id)}">
                                                    <td>${f:h(data.inputs)}</td>
                                                    <td>${f:h(data.outputs)}</td>

          "seed" : 1,
          "bit" : 2,
          "size" : 64
        },
        "synonym_filter" : {
          "type" : "synonym_graph",
          "synonyms_path": "${fess.dictionary.path}synonym.txt"
        }
      },
      "tokenizer": {
        "japanese_tokenizer": {
          "type": "fess_japanese_tokenizer",
          "mode": "normal",

		</property>
		<!-- Dictionaries -->
		<postConstruct name="addConfigFile">
			<arg>"fess"</arg>
			<arg>"mapping.txt"</arg>
		</postConstruct>
		<postConstruct name="addConfigFile">
			<arg>"fess"</arg>
			<arg>"synonym.txt"</arg>
		</postConstruct>
		<postConstruct name="addConfigFile">
			<arg>"fess"</arg>
			<arg>"ar/protwords.txt"</arg>
		</postConstruct>
		<postConstruct name="addConfigFile">
			<arg>"fess"</arg>

    public static final String LABELS_dictionary_type = "{labels.dictionary_type}";

    /** The key of the message: Synonym List */
    public static final String LABELS_dict_synonym_configuration = "{labels.dict_synonym_configuration}";

    /** The key of the message: Synonym List */
    public static final String LABELS_dict_synonym_title = "{labels.dict_synonym_title}";

    /** The key of the message: List */

    /** The key of the message: Failed to download a synonym file. */
    public static final String ERRORS_failed_to_download_synonym_file = "{errors.failed_to_download_synonym_file}";

    /** The key of the message: Failed to upload a synonym file. */
    public static final String ERRORS_failed_to_upload_synonym_file = "{errors.failed_to_upload_synonym_file}";

#### Index Settings Migration

Fess uses OpenSearch/Elasticsearch internally, so you can:

1. Export index mappings and settings from source
2. Apply custom analyzers in Fess's `fess_config.properties`
3. Create synonym dictionaries in Fess's dictionary directory

---

### Apache Solr

For migrating from Apache Solr:

#### Document Export and Import

**Step 1: Export from Solr**

```bash