Format Of Terms Solr Document

THL Toolbox > Developers' Zone > Ruby on Rails Development > Tibetan Dictionary > Format of Dictionary Solr Document

Format of Solr Document Generated by Terms Dictionary

Contributor(s): Andres Montano

Main Document

Here are the fields for Terms Dictionary in the main document. Remember to also consult the Common Solr Fields for All Knowledge Maps.

  • tree: terms
  • associated_subjects: array of subject names. Tag will hold an empty array if no subjects associated.
  • associated_subjects_ids: array of subject ids. Tag will hold an empty array if no subjects associated.
  • etymologies_ss: array of etymologies.
  • block_type: ['parent']
  • related_terms_branch_{branch uid}_header: prioritized name for branch
  • related_terms_branch_{branch uid}_subjects_{subject id}_citation_{citation fields}: prefix of citation data for related subject. See citation section for all fields.
  • related_terms_branch_{branch uid}_subjects_{subject id}_time_units_ss: array of time units for related subject formatted as a string. Tag would be available if array is not empty.
  • related_terms_branch_{branch uid}_subjects_{subject id}_note_{note id}_{note fields}: prefix of note data for related subject. See note section for all fields.
  • etymology_{etymology id}_content_s: content of etymology.
  • etymology_{etymology id}_type_{subject uid}_s: name of etymology type
  • etymology_{etymology id}_note_{note id}_{note fields}: prefix of note data for etymology. See note section for all fields
  • etymology_{etymology id}_citation_{citation fields}: prefix of citation data for etymology. See citation section for all fields.
  • associated_subjects_{branch id}_ls: array of subject ids. Tag will hold an empty array if no subjects associated.
  • associated_subjects_{branch id}_ss: array of subject names. Tag will hold an empty array if no subjects associated.
  • passage_{passage fields}: prefix of passage data. See passage section for all fields.
  • translation_equivalent_{translation equivalent id}_content_s: content of translation equivalent
  • translation_equivalent_{translation equivalent id}_language_s: language of translation equivalent
  • translation_equivalent_{translation equivalent id}_language_code_s: language code of translation equivalent
  • translation_equivalent_{translation equivalent id}_citation_{citation fields}: prefix of citation data for translation equivalent. See citation section for all fields.

Subdocuments

Here are the subdocuments for Terms Dictionary. Remember to also consult the Common Solr Fields for All Knowledge Maps.

Relations

  • id: {uid of current}_{relation type code}_{id of related} (symmetric for parent relations and asymmetric for child relations; opposite from label!). For a list of relation types see external link: http://terms.kmaps.virginia.edu/admin/feature_relation_types .
  • related_uid_s: related uid
  • origin_uid_s: uid of current
  • block_child_type: ['related_terms']
  • related_terms_id_s: related uid
  • related_terms_header_s: prioritized name based on default view. id would be used if no name is available.
  • related_terms_path_s: path based on default perspective or closest to it in the form of "{id of grandparent}/{id of parent}/{id of current}" (for however many levels there are)
  • related_terms_relation_label_s: relation type label (asymmetric for parent relations and asymmetric for child relations; opposite for code!).
  • related_terms_relation_code_s: relation type code (symmetric for parent relations and asymmetric for child relations; opposite from label!).
  • related_kmaps_node_type: '{parent|child}' (depending if subdocument is for parent relation or child relation)
  • block_type: ['child'] (refers to child in the solr "subdocument sense"; independent if subdocument is for parent of child relation)
  • related_terms_relation_source_code_s: if the related term is meant to be displayed under other dictionaries, the code for the legacy dictionary is specified here. For a list of all dictionaries (including the below "in-house" sources) see:
  • or fetch through the API:
  • related_terms_relation_citation_{citation fields}: prefix of citation data for relation. See citation section for all fields.
  • related_terms_relation_time_units_ss: array of time units for relation formatted as a string. Tag would be available if array is not empty.
  • related_terms_note_{note id}_{note fields}: prefix of note data for relation. See note section for all fields
  • related_terms_branch_{branch uid}_header: prioritized name for branch
  • related_terms_branch_{branch uid}_subjects_headers_t: array of prioritized name for all related subjects under branch
  • related_terms_branch_{branch uid}_subjects_uids_t: array of uids for all related subjects under branch

Definitions

  • id: {uid of current}_definitions-{definition id}
  • origin_uid_s: {uid of current}
  • block_child_type: ['related_definitions']
  • related_definitions_source_s: name of "legacy" source for citation. Refers to third-party dictionaries that where imported as a single field (such as Rangjung Yeshe). For the list of dictionaries see info sources API above.
  • related_definitions_in_house_source_s: name of "in-house" source for citation. Usually this refers to third-party dictionaries that where parsed into relevant fields (such as David Higgins). For the list of dictionaries see info sources API above.
  • related_definitions_content_{writing system code}u: definition content. Note that now part of the tag is the writing system used (for better indexing). Currently solr supports: _content_hansu, _content_hantu, _content_tibtu and _content_latinu for definitions.
  • related_definitions_path_s: path of definitions tree in the form of "{id of grandparent}/{id of parent}/{id of current definition}" (for however many levels there are)
  • related_definitions_level_i: size of path
  • related_definitions_language_s: name of definition language
  • related_definitions_language_code_s: code of definition language
  • related_definitions_etymologies_ss: array of etymologies
  • block_type: ['child']
  • related_definitions_etymology_{etymology id}_content_ss: content of etymology
  • related_definitions_etymology_{etymology id}_type_{subject id}_s: name of subject representing etymology type if available, else tag won't be included.
  • related_definitions_etymology_{etymology id}_note_{note id}_{note fields}: prefix of note data for etymology. See note section for all fields.
  • related_definitions_author_s: author name if available, else tag won't be included.
  • related_definitions_numerology_i: numerology if available, else tag won't be included.
  • related_definitions_tense_s: tense if available, else tag won't be included.
  • related_definitions_citation_{citation fields}: prefix of citation data for definition. See citation section for all fields.
  • related_definitions_note_{note id}_{note fields}: prefix of note data for relation. See note section for all fields
  • related_definitions_branch_{branch uid}_header: prioritized name for branch
  • related_definitions_branch_{branch uid}_subjects_headers_t: array of prioritized name for all related subjects under branch
  • related_definitions_branch_{branch uid}_subjects_uids_t: array of uids for all related subjects under branch
  • related_definitions_passage_{passage fields}: prefix of passage data for related definition. See passage section for all fields.
  • related_definitions_passage_translation_{passage translation fields}: prefix of passage translation data for related definition. See passage translation section for all fields.
  • related_definitions_model_sentence_{sentence id}_content_t: model sentences associated to definition.
  • related_definitions_model_sentence_{sentence id}_translation_{language code}_content_t: translation for model sentence.

Recordings

  • id: {uid of current}_definitions-{definition id}
  • block_child_type: ['terms_recording']
  • block_type: ['child']
  • origin_uid_s: {uid of current}
  • recording_url: url for recording
  • recording_dialect_s: name of recording dialect
  • recording_dialect_uid_s: uid of recording dialect (dialect is a subject)

Specific Sections

Passage fields

  • {prefix}_passage_{passage_id}_content_t: content of passage.
  • {prefix}_passage_{passage_id}_citation_{citation fields}: prefix of citation data for passage. See citation section for all fields.
  • {prefix}_passage_{passage_id}_passage_translation_{passage translation fields}: prefix of passage translation data for passage. See passage translation section for all fields.
  • {prefix}_passage_{passage_id}_note_{note id}_{note fields}: prefix of note data for passage. See note section for all fields.

Passage Translation fields

  • {prefix}_passage_translation_{passage_translation_id}_content_t: content of passage translation.
  • {prefix}_passage_translation_{passage_translation_id}_language_s: language of passage translation.
  • {prefix}_passage_translation_{passage_translation_id}_language_code_s: language code of passage translation.
  • {prefix}_passage_translation_{passage_translation_id}_citation_{citation fields}: prefix of citation data for passage translation. See citation section for all fields.
  • {prefix}_passage_translation_{passage_translation_id}_note_{note id}_{note fields}: prefix of note data for passage translation. See note section for all fields.

Provided for unrestricted use by the external link: Tibetan and Himalayan Library