| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| en:eebo:multiword [2016/09/28 15:49] – veronikapojarova | en:eebo:multiword [2016/09/28 16:40] – veronikapojarova |
|---|
| ====== Searching the corpus ====== | ====== Searching the corpus ====== |
| |
| If searching for one specific form such as //is arrived//, we may use the [[en:manualy:kontext:novy_dotaz|basic query]] as described in our [[en:eebo:first_query|first lesson ]]. | If searching for one specific form such as //is arrived//, we may use the //Phrase// query type as described in our [[en:eebo:first_query|first lesson ]]. |
| |
| However, in this case we want to find all the possible variants, //am come//, //are come// the query can be written in [[en:pojmy:dotazovaci_jazyk|CQL]] (Corpus Query Language) using a number of regular expressions. Furthermore, the CQL query mode in the [[en:kontext| KonText]] interface is case sensitive, and therefore both variants should be included in the query in order for us to obtain as many relevant hits as possible. | However, in this case we want to find all the possible variants, //am come//, //are come// the query can be written in [[en:pojmy:dotazovaci_jazyk|CQL]] (Corpus Query Language) using a number of regular expressions. Furthermore, the CQL query mode in the [[en:kontext| KonText]] interface is case sensitive, and therefore both variants should be included in the query in order for us to obtain as many relevant hits as possible. |
| ''([word="am"]|[word="are"]|[word="is"])[word="arrived"]'' | ''([word="am"]|[word="are"]|[word="is"])[word="arrived"]'' |
| |
| If we want the search to include both variants, i.e. //be// and //have//, we can include all of the possible forms in the query. Furthermore, we want to include all the possible spelling variants (see our [[en:eebo:orthography_spelling|second lesson]]). The final query could look like this: | If we want the search to include both variants, i.e. //be// and //have//, we can include all of the possible forms in the query. Furthermore, we want to include all the possible spelling variants (see [[en:eebo:orthography_spelling|Lesson Two]]). The final query could look like this: |
| |
| ''([word="am"]|[word="are"]|[word="[iy]s"]|[word="has"]|[word="ha[uv]e"])[word="ar?ri[uv]ed"]'' | ''([word="am"]|[word="are"]|[word="[iy]s"]|[word="has"]|[word="ha[uv]e"])[word="ar?ri[uv]ed"]'' |
| |
| {{:en:eebo:eebo_pic_08.png?direct&300 |}} | {{:en:eebo:eebo_pic_08.png?direct&300 |}} |
| | |
| | By selecting the positive filter, we can view the node forms individually, e.g. all the instances of //have arrived//. Alternately, we can conduct a separate search for all the variants with the auxiliary //have// and all those with the auxiliary //be//. |
| | |
| | A number of things can be done at this stage, including a survey of the i.p.m. by period. |
| | |
| | Frequency → Text Types on the menu bar shows us a list of frequencies by period and by decade. By default, the results are ordered by frequency. By clicking on the text doc.decade we can order the results chronologically. |
| | |
| | [[en:eebo:competing_forms|Lesson Three]] gives an example of how such data could be converted into a graph. |
| |
| |
