The Bayala Databases

1. MEANING OF BAYALA (baya-la)

‘Baya’ is the Sydney Aboriginal language (BB) word for ‘speak’. With the RECIProcal and/or REFLexive suffix ‘-la’ it becomes ‘speak reciprocally’, or ‘converse’. These databases in a sense ‘converse’ with the user, in that they are intended to interact with him or her. They were begun sometime before 1999. They started out as a simple word list with associated meanings as in a basic foreign-language dictionary. They are the work of Jeremy Macdonald Steele and in 2005 were submitted as part of a Macquarie master’s thesis on the Sydney Aboriginal language. This thesis may be freely downloaded at <http://hdl.handle.net/1959.14/738>.

PURPOSE

The purpose of the databases is to try to find out as much about the Indigneous languages covered as possible. Take for instance the word ‘naabawinya’ used in association with another blog naabawinya.blogspot.com. It derives from the record made by WIlliam Dawes:

Australian	respelt	English	Eng JSM	source
P. Nābaou-ínia Windáyin Tāmunadyēmínga]"	na-ba-wi-nya =	"[I will look at you through the window (because) you refused me (bread)]"	see will I thee:	Dawes (b) [b:32:6.1] [BB]

Dawes wrote it as “Nābaou-ínia”, and this on respelling in its simplest form becomes ‘nabawinya’ (without double letters or hyphens. The databases enable words such as this to be displayed revealing their constituent parts—here stem: na; future tense marker: ba; and two pronouns: wi: ‘I’ and nya: ‘thee’. All four parts of this word can then be separately searched for, and compared with other instances in other words across all the languages covered. They reveal that in south-east Queensland, na still means ‘see’, but in Perth na is an exclamation of surprise: Oh! Ah!.

COMPUTER

The Bayala databases began in a Macintosh user world, with the application Filemaker.  Filemaker’s increasing sophistication enabled these databases gradually to do more. The development was undertaken by someone with no knowledge at the outset and without instruction other than that provided by the database itself. A particular advance made by Filemaker was to become ‘relational’, to make it possible to look into another database. At the end of 2011, this is how the Bayala Databases are:

Fig. 1 Summary of links within the Bayala databases

The graphic illustrates the interrelationships operating for any of the main databases. At 2011 these included:

Language lists

—ALLSYD

—SOUTH

—NORTH

—KAMILAROI

—WIRADHURI

—CURR

—ANTHROPSOC (Antsoc)

—INTERSTATE

—MURUWARI

—NYUNGAR

Reference compilations

—COASTAL (North, South, coastal parts of Curr and Antsoc)

—INLAND (Wiradhuri, Kamilaroi and inland parts of Curr and Antsoc)

Auxiliary

—CAROL VOCAB DETAILS

—DIXON LANGUAGE LISTS

—ELABORATION

—TRANSCRIPTION KEY

—VOCABS PIX

HOW THE DATABASES WORK

There are now tens of thousands of lines, or ‘records’ in the various Bayala databases. Here is a source for one of them. It is a word for ‘water’ as recorded in the ‘Anon’ notebook kept by the early governors, including Governor Phillip of the First Fleet. 

"Ba-do" badu = "Water" water  : Anon (c) [c:26:1] [BB]

The caption to this record shows the following:

“Ba-do”: the original recording in the Australian language

badu: the same, after respelling according to a consistent system

“Water”: the original translation

water: the modern translation

Anon (c): the source

[c:26:1]: notebook, page number, and line number

[BB]: the abbreviation for the language (here ‘Biyal Biyal’, the term used in these databases for ‘the classical language of Sydney’

The summary line used as a caption to the above illusttration is a complex piece of typing, yet it was in fact done with a single key combination of ‘command-shift-z’. This effect was achieved through another software application, QuicKeys.

In the summary list above, note that double quotation marks indicate that the entry captures the original as closely as reasonably possible.

Here is another example, for the future tense of the verb ‘to see’:

"Naabaoú" na-ba-wu = "I shall or will see etc." see will I: Dawes (a) [a:1:13] [BB]

"Naabámi" na-ba-mi = "Thou [wilt see]" see will thou: Dawes (a) [a:1:14] [BB]

Analysis of the first line, by components, as with ‘badu’:

“Naanaoú”: original record

na-ba-wu: respelt (with hyphens)

"I shall or will see etc.": original translation

see will I: modern translation

Dawes (a): source (Dawes’s Notebook ‘a’)

[a:1:14]: notebook, page, line

[BB]: language abbreviation

This is recorded in the ALLSYD database as follows:

As this reproduction is too small to read, the key segments are shown in larger size:

Fig.2. Source information for “Naabaoú” and “Naabámi”

Fig.3. Respelling and analysis of “Naabaoú” and “Naabámi”

Fig.4. Date and translation of “Naabaoú” and “Naabámi”

The colours have little significance. They were applied to distinguish one column from another. There are a large number of columns. Not all columns are used for every entry or record. The colours are applied consistently across all databases. For example, grey is used for original records, a darker shade for the Australian language, lighter for English.Brown is used for respelling; yellow for the standardised English, with shades of yellow for subsidiary parts of the standardised translation.

15. OBTAINING THE DATABASES

15.1 IN LIBRARIES

A copy of the Bayala Databases was included in a pocket on the inside back cover of copies of the thesis ‘The Aboriginal Language of Sydney’ deposited with the following libraries:

—Macquarie University

—University of Sydney

—State Library of New South Wales

—Australian Institute of Aboriginal and Torres Strait Islander Studies

—Tasmanian Museum and Art Gallery

—The National Library of Australia

Those copies were of the databases as they were at the time, in 2006. There has been considerable development since.

15.2 PERSONAL COPIES

First, apologies are extended for the following rigmarole, which reflects the do-it-yourself non-professional nature of this operation. The databases represent about fifteen years’ of personal work and it seems reasonable not to offer them everywhere gratis at not-only-no-cost to the recipient, but a personal further cost to the originator each time in postal charges, time or perhaps in other unforeseen ways. 

Before asking for the databases, note that a user will need Filemaker Pro, and that they were developed on a Macintosh.

Personal copies of the databases may be obtained from <naabawinya@pobox.com> on the basis of fair payment, fair play and fair acknowledgement.

The databases will be provided in accordance with the following schedule:

15.21 PAYMENT

$100 each

ALLSYD

ANTSOC

CURR

INTERSTATE

KAMILAROI

MURUWARI

NORTH

NYUNGAR

SOUTH

WIRADHURI

$50 each

Carol VOCAB DETAILS

Dixon LANGUAGE LISTS

ELABORATION

TRANSCRIPTION KEY

VOCABS PIX

$50: provided the constituent files are obtained

COASTAL

INLAND

Alternatively, $1000 for the whole lot.

15.22 ‘NO COPYING’ UNDERTAKING

The databases will be supplied if the purchaser undertakes in writing not to make copies and give them to anyone else. He or she may, however, make copies for his or her own additional computers.

15.23

The databases will be supplied if the purchaser undertakes in writing to make fair acknowledgement of the ‘Bayala Databases’ by ‘Jeremy Macdonald Steele’ in any writings he or she may produce.

15.3 HOW TO GO ABOUT OBTAINING THE DATABASES

At present there is no mechanism for paying for, and hence obtaining, the databases on line. Accordingly the following procedure should work.

—send an email expressing interest in the particular databases desired to the ‘naabawinya’ email address given above.

—a reply will be sent giving a postal address to use.

—the purchaser (i.e. 'you') then reply to this postal address, including a letter together with:

● the appropriate funds as a cheque or Australia Post Money Order <http://auspost.com.au/personal/sending-money.html?cmpid=moneyorder-google&mkwid=s2JanyLla|what%20is%20money%20order|b|pcrid|6927437906> ;

● a signed undertaking relating to ‘no copying’ and ‘fair acknowledgement’;

● a memory stick for the supply of the databases.

The databases asked for will then be sent on the memory stick provided, to the address on the letter.

After that it can only be hoped that they work at the purchaser’s end for they work perfectly well at the originator’s.

14. HOW THE DATABASES STARTED

The Bayala Databases were conceived of, compiled and developed by Jeremy Steele. They were begun well before August 1999, and probably after JS first saw and began to copy the notebooks of William Dawes in the School of Oriental and African Studies in London, on 5 October 1998. It was not until JS retired in March 1999 that work took on a more consistent pattern of application.

The databases had begun with a simple word-list file entitled ‘Eora Aboriginal words list’. This itself grew out of words noted on bookmarks when reading accounts of the First Fleet days after JS arrived in Sydney from Perth, Italy and England in 1969 aged about 31.

 This was superseded or augmented by ‘Vocabularies Sydney’ into which word items were entered, as in a dictionary. At the outset, where the same word had been recorded by different people, there seemed no point in entering it again; but after a while, when it was noticed that words had been spelt in a variety of ways and sometimes with slightly different ways of expressing their meanings, the idea developed that every recorded reference should be noted, together with associated source details (author, the document in which the reference occurred, page and line numbers, as well as a note as to where one could put one’s hands on the document again — generally a particular ringbinder that the photocopy of the list had been filed in.

SYDNEY AND NSW

A separate database was next begun just for William Dawes, when Dawes who had recorded sentences as well as words became the subject of extensive study. In due course the Dawes file was subsumed into a new enlarged file for all records of the Sydney region, named ALLSYD.

Around this time acquaintance had been made with the historian Keith Vincent Smith, who was researching the Sydney Indigenous people around the time of European contact. He encountered many word lists in the course of his enquiries and passed these on to JS. Numbers of these additional lists provided by Smith related to areas to the south and north of Sydney. Around the same time the works of Lancelot Edward Threlkeld, a missionary based at Lake Macquarie to the northward of Sydney, were found, including: 

Threlkeld, Lancelot Edward. 1834. An Australian Grammar: comprehending the principles and natural rules of the language, as spoken by the Aborigines in the vicinity of Hunter's River, Lake Macquarie, &c. New South Wales. Sydney: Printed by Stephens and Stokes, "Herald Office".

Smith’s vocabularies and the works of Threlkeld necessitated new databases to be developed to accommodate these extra findings. And so the SOUTH (for Dharawal, Gundungara, Wodi Wodi, Dhurga and other languages) and NORTH (for Awabakal, Darkinyung, Worimi, Bundjalung and others) were begun.

With the acquisition of yet more lists, covering territory across the Blue Mountains, yet more databases were required and these became WIRADHURI and KAMILAROI. They were comparable to the NORTH and SOUTH files for the coastal region as they included nearby languages such as Wailwan, Wongayibon, Niyamba and the like.

OTHER DATABASES

In due course even more databases were initiated, of which the following were to become part of the Bayala series:

MURUWARI: a language near the NSW/Qld border, an interest in which was sparked by:

Oates, Lynette Frances. 1988. The Muruwari language. Canberra: Dept. of Linguistics, Research School of Pacific Studies, Australian National University.

NYUNGAR: the language region of south-west Western Australia, an interest in which was prompted by a visit there in 2010, WA being JS’s original home state.

CURR: Words from the New South Wales contained in:

Curr, Edward M., 1886. The Australian Race: Its Origin, Languages, Customs, Place of Landing in Australia, and the Routes by which it spread itself over that continent, Melbourne, John Ferris, Government Printer; London: Turner and Co., Ludgate Hill.  In Four Volumes.

ANTHROPSOC: This mainly included words obtained from the Science of Man journal of the Australian Anthropological Society, and data collected for use by the this society. It also became the principal location for placenames.

INTERSTATE: As interest spread beyond Sydney and New South Wales a new database was required. So ‘Interstate Lists’ was begun, containing words from Queensland, Victoria, Northern Territory, South Australia and Western Australia excluding the Nyungar south-west, and Tasmania.

WHY A DESCRIPTION OF THE BAYALA DATABASES

At the time of beginning this summary, practically no-one had examined the Bayala Databases, although one linguist had done so, and two or three others been provided with copies of them. Copies of the NSW databases had been included as part of the 2005 MA thesis, and the thesis was deposited with about half a dozen major libraries. Other than that, the databases exist in only the one location, and this is where they are maintained and developed. Development of the databases has continued over the period since lodging of the MA thesis 2005.

As the databases have become an increasingly useful and powerful resource, it seemed  that a description of them might be handy should they at some stage become more widely available. People coming to the for the first time might not find them as intuitively easy to operate as their developer might suppose. 

Other users might in time add still other Australian languages: for there is far too much to be done by a single contributor. And in order for such new users to do this, they need to know how the databases are constructed. 

Inevitably one day the current author/developer will not have the will or capacity to continue, and if this considerable work is not to be lost others need to be able to continue and further develop it. This description should make the take easier for them.

<naabawinya> BLOG

Just as the databases have barely been noticed by any members of the public, so to the    ‘naabawinya’ blog. In this blog the author JS has placed short commentaries on topics that have occurred to him as he has probed some of the word lists. It can be found at <naabawinya.blogspot.com>

13. SETTING UP A BAYALA DATABASE

On deciding to create a database, the first thing to do it to create the fields.

Fig. 13.1 A few of the fields in the ALLSYD database

In the illustration above some of the field in use in the ALLSYD database can be seen.

After the fields have been created, changes by addition, amendment and deletion can occur at any time. 

Layouts can then be made, to display the fields in any desired arrangement. In the case of the Bayala databases, colours were added to help distinguish between the many columns used.

Many databases are simple, but not so the Bayala databases, which were able to become increasingly useful through relationships. 

Fig.13.2 Relationships structure of the ALLSYD database

The above illustration reveals the relationships that enable the ALLSYD database to work. The green rectangles to the upper left control the eight Elaboration bars, the yellow rectangles below control theJSM links in the LINKS layout, and the brown rectangle below the control the NoH links in the same layout.  Each of these is connected to the ALLSYD database, which is the tall grey rectangle in the centre on the illustration.

On the right are the various other relationships — for searching, geographical purposes, for the transcription keys. Others control the pictures, the source details, and the special characters.

MAKING A SEARCHER PANEL WORK

Fig. 13.3 Layout for the ALLSYD SEARCHER NoH

Once a layout has been created, it is necessary link all the constituent blank fields to the appropriate field name in the relational link concerned (here, ALLSYD SEARCHER NoH).

If it is done correctly, something like the following will result:

Fig. 13.3 ALLSYD SEARCHER NoH in use: in the bottom right, the word ‘wara’ was entered

Fig. 13.5 ALLSYD SEARCHER NoH in use: next, the word ‘bada’ was entered

SUMMARY LINES

Summary lines have been described earlier, created by the key combination ‘option-shift-Z’. This was used to create:

"Pattadiou" bada-dya-wu = "I eat or have eat [eaten]" eat did I: Anon (c) [c:19:10] [BB]

for the first record in the illustration immediately above. But how does this happen?

It is the result of coding in a program ‘QuicKeys’. The programming is the following:

tell application "FileMaker Pro" set Australian_field to cellValue of cell named "Australian" of current record set suffixDFX1_field to cellValue of cell named "suffix DFX 1" of current record set suffixDFX2_field to cellValue of cell named "suffix DFX 2" of current record set suffixDFX3_field to cellValue of cell named "suffix DFX 3" of current record set suffixDFX4_field to cellValue of cell named "suffix DFX 4" of current record set suffixDFX5_field to cellValue of cell named "suffix DFX 5" of current record set suffixDFX6_field to cellValue of cell named "suffix DFX 6" of current record set suffixTENSE_field to cellValue of cell named "suffix TENSE" of current record set qualifier_field to cellValue of cell named "qualifier" of current record set suffixPRONOUNNOM_field to cellValue of cell named "suffix PRONOUN NOM" of current record set suffixPRONOUNACC_field to cellValue of cell named "suffix PRONOUN ACC" of current record set suffixPRONOUNNOMpost_field to cellValue of cell named "suffix PRONOUN NOM post" of current record set suffix1_field to cellValue of cell named "suffix 1" of current record set suffix2_field to cellValue of cell named "suffix 2" of current record set suffix3_field to cellValue of cell named "suffix 3" of current record set nohyphens_field to cellValue of cell named "no hyphens" of current record set English_field to cellValue of cell named "English" of current record set EnglishJSmain_field to cellValue of cell named "English JS main" of current record set EnglishJSDFXtense_field to cellValue of cell named "English JS DFX tense" of current record set EnglishJSadj_field to cellValue of cell named "English JS adj" of current record set source_field to cellValue of cell named "source" of current record set notebook_field to cellValue of cell named "notebook" of current record set page_field to cellValue of cell named "page" of current record set line_field to cellValue of cell named "line" of current record set langshort_field to cellValue of cell named "langshort" of current record if suffixDFX1_field is not equal to "" then set suffixDFX1_field to "-" & suffixDFX1_field end if if suffixDFX2_field is not equal to "" then set suffixDFX2_field to "-" & suffixDFX2_field end if if suffixDFX3_field is not equal to "" then set suffixDFX3_field to "-" & suffixDFX3_field end if if suffixDFX4_field is not equal to "" then set suffixDFX4_field to "-" & suffixDFX4_field end if if suffixDFX5_field is not equal to "" then set suffixDFX5_field to "-" & suffixDFX5_field end if if suffixDFX6_field is not equal to "" then set suffixDFX6_field to "-" & suffixDFX6_field end if if suffixTENSE_field is not equal to "" then set suffixTENSE_field to "-" & suffixTENSE_field end if if qualifier_field is not equal to "" then set qualifier_field to "-" & qualifier_field end if if suffixPRONOUNNOM_field is not equal to "" then set suffixPRONOUNNOM_field to "-" & suffixPRONOUNNOM_field end if if suffixPRONOUNACC_field is not equal to "" then set suffixPRONOUNACC_field to "-" & suffixPRONOUNACC_field end if if suffixPRONOUNNOMpost_field is not equal to "" then set suffixPRONOUNNOMpost_field to "-" & suffixPRONOUNNOMpost_field end if if suffix1_field is not equal to "" then set suffix1_field to "-" & suffix1_field end if if suffix2_field is not equal to "" then set suffix2_field to "-" & suffix2_field end if if suffix3_field is not equal to "" then set suffix3_field to "-" & suffix3_field end if set cell named "word for word JS" of current record to quote & Australian_field & quote & tab & nohyphens_field & suffixDFX1_field & suffixDFX2_field & suffixDFX3_field & suffixDFX4_field & suffixDFX5_field & suffixDFX6_field & suffixTENSE_field & qualifier_field & suffixPRONOUNNOM_field & suffixPRONOUNACC_field & suffixPRONOUNNOMpost_field & suffix1_field & suffix2_field & suffix3_field & " =" & tab & quote & English_field & quote & tab & EnglishJSmain_field & space & EnglishJSDFXtense_field & space & EnglishJSadj_field & ":" & tab & source_field & " [" & notebook_field & ":" & page_field & ":" & line_field & "] [" & langshort_field & "]" end tell

12. BAYALA DATABASE CONVENTIONS

Typing

The following conventions convey information without affecting to computer’s searching function. Any other form of respelling would reduce the range of finding capability in searches.

bold ng: indicates that this is the /ng/ nasal combination. Where ‘ng’ occurs not in bold, this indicates uncertainty as to whether is is the /ng/ nasal combination (as in English ‘singer’ or ‘n’and ‘g’ separately pronounced as in English ‘finGer’

capital G: indicates that the ‘g’ is separately pronounced and does not form part of an /ng/ nasal combination

capital N: represents the sound /nh/

capital D: represents the sound /dh/

capital A: a long form of the vowel

capital I: a long form of the vowel

capital U: a long form of the vowel

CAPITALS Text in CAPITALS often indicates that it is commentary by the author/compiler [JS].

Filed border A coloured border around a field indicates it is drawing information from another database.

Status field

‘JS’ in the ‘status’ field indicates that the original record has been varied in some way be the database author JS (Jeremy Steele). This occurs when a word is taken from a multiple-word entry and is examined on its own.

Brackets or parentheses

[Square brackets]: indicate a word being examined by JS as parts of a multiple-word original entry. ‘JS’ is shown in the Status field.

{curly brackets}: indicate that an original entry may have multiple words, of which only one word is being examined in the record concerned. The original author’s acronym may be shown in the Status field against such entries.

<Arrow brackets>: used usually to mark internet references

FURTHER LAYOUTS (2)

11.2 SPECIAL ALLSYD LAYOUTS

There are some special layouts confined to the ALLSYD database. These include:

—DATE

—DIACRTITICS

DATE layout

The purpose of this layout is to help identify when a record was made by William Dawes:

Fig. 11.2.1 Extract from the ALLSYD: DATE layout where a date of entry is speculated upon

A search (command-F) was undertaken and an asterisk placed in the second-last blue field (date of entry after) field. Evidence in Dawes’s notebooks suggested that the entries were made after the dates appearing in that field. The next field contained dates that the entry seemed likely to have been made before. This enabled a date of entry (first broad, blue, column) to be guessed, and entered.

DIACRITICS layout

In the DIACRITICS layout, in the illustration below, a search was made in the central red column headed ‘cht i dot’. This brought up all instances in which Dawes used a lowercase ‘i’ including a dot (in contradistinction to an ‘i’ without a dot [ı]), the former signifying the sound as in ‘I, ivy, ire’ and the latter as in ‘in, it, ill’. This was one of the several special usages made use of by Dawes.

Fig. 11.2.2 ALLSYD: DIACRITICS layout: search for ‘cht i dot’

There are six narrow columns in this layout for Dawes’s various usages, and the codings are explained beside the appropriately coloured totals boxes at the bottom of the table. From these boxes it can be seen that there were 151 examples of ‘i dot’ in the Dawes material. Searches would have to be made on teach of the other five columns in turn to arrive at the total numbers for each.

 Dawes made use of three ‘phonological systems’ in transcribing the words he heard used by the local inhabitants. These systems have been numbered i, ii and iii, and the right-hand column shows which was used by Dawes for each of the records featured.

11.3 OTHER LAYOUTS

There are several other special-purpose ALLSYD layouts which were created to undertake various analytical roles, notably on pronouns, other parts of speech, and suffixes.

11. FURTHER LAYOUTS

11.1 PRINCIPAL LAYOUTS

The database description to this point has been based on the OVERVIEW layout. Each database has several other layouts, of which the principal ones are:

—LINKS

—NARROW

—WIDER

The LINKS layout is nearly uniform in presentation across the various databases; the others may vary in certain particulars.

LINKS LAYOUT

The Links layout has a similar format in all the language databases but not identical content. Its purpose is to reveal links a word might have in other areas and in other languages.

At the time of compiling the present description of the Bayala Databases, the databases listed in the left column in the table below had links to those shown in the narrow columns. They could have all linked to all, but to do so would have made the LINKS layout unnecessary large, so a selection was made in each case.

The databases are linked through two fields: No Hyphens (NoH: brown) and ENGLISH JSM (JSM: yellow).

Database

Syd

N

S

Cst

Km

Wi

Mri

Inld

Cur

Ant

Int

Nygr

ALLSYD

x

x

x

x

x

x

x

x

NORTH

x

x

x

x

x

x

SOUTH

x

x

x

x

x

x

COASTAL

x

x

x

x

x

x

x

x

x

KAMILAROI

x

x

x

x

x

x

x

WIRADHURI

x

x

x

x

x

MURUWARI

x

x

x

x

x

x

x

x

x

INLAND

x

x

x

x

x

x

x

x

CURR

x

x

x

x

x

x

ANTSOC

x

x

x

x

x

x

x

INTERSTATE

x

x

x

x

x

NYUNGAR

x

x

x

x

x

x

Table xx In the LINKS layout, each database is linked to those check against its title

The illustration below is a detail of the Links layout for the Allsyd database. It is finding links across the other databases for the word ‘mugu’.

 The JSM column on the right reveals that it has meanings other than the Sydney usage ‘hatchet’:

Fig.11.1 ALLSYD LINKS (part): NoH link field showing ‘mugu’ in other databases (North, South ...)

The illustration is of the top left-hand corner only of the full LINKS layout shown below:

Fig. 11.2 The full LINKS layout for the ALLSYD database

In the Sydney language, ‘mugu’ is the word for ‘hatchet’. This LINKS layout, focussed on the indigenous word, enables the user to find out what ‘mugu’ might mean in other languages.

And if the Sydney word for ‘hatchet’ is ‘mugu’, what is ‘hatchet’ in other languages? The right-hand portion of the following English-focussed LINKS layout gives the answers, as the detail below reveals:

Fig. 11.3 ALLSYD LINKS (part): JSM link field showing ‘hatchet’ in other databases (North, South ...)

While ‘mugu’ was the common feature in the previous portion of the layout, here it is ‘hatchet’, in the yellow JSM column at the far right.

Displayed are only five examples for each of the language databases on view. Scroll bars enable all the other examples for each database to be viewed.

NARROW layout

The NARROW layout is a single-line layout, in which the columns have been made narrow to enable much information to be displayed at a single viewing.

The NARROW layout was one of the early developments of the BAYALA databases and it has largely been superseded by the OVERVIEW layout. However, should users visit it, it may contain some features of interest.

Language occurrence fields bar

Fig. 11.4 Language occurrence check boxes (shades of blue)

In the above illustration, the fourth record, “Tuggarah” in the Australian (grey) column is being examined. The languages this word occurs in ar check in the row of boxes marked at the top, ‘x’ indicating a match, and ‘cl’ indicating not an exact match but ‘close’.

Only a few of the records have been subjected to such a detailed analysis. To find which have been so treated, is simply done by undertaking a search (command-F), and placing an asterisk in any of the language boxes and hitting ‘return’.

Search engine

Fig. 11.5 An NoH, ReS, Aus and JSM search engine

The search engine responds when a word, typed in one of the central searcher fields, exactly matches one of the words in one or more of the fields in the database. The successful search in the illustration was for ‘dugara’ (not ‘dagara’), and yielded the two examples shown, with an indication that there were more, as the scroll bar is grey.

On the left there is room for only two responses for  searches for Aus, ReS and NoH. The right-hand side of the search engine is for JSM responses, fir which five line are provided. The JSM search field is below those five lines, the yellow field, marked ‘COAST LOOKUP JSM’ This early search-engine facility was superseded by the greater searching capability in the OVERVIEW layout.

WIDER layout

The WIDER layout is another single-line presentation. It features a more restricted collection of fields, though several are much wider than in other layouts in order to reveal more of their content.