<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://digitalcollections.lakeheadu.ca/items?output=omeka-xml&amp;page=49&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-09-03T00:54:24+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>49</pageNumber>
      <perPage>10</perPage>
      <totalResults>13551</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="8024" public="1" featured="0">
    <fileContainer>
      <file fileId="8847">
        <src>https://digitalcollections.lakeheadu.ca/files/original/d2ef705d40e5c9448dffc88f8a72a39a.jpg</src>
        <authentication>166104ec0e8b5a2aa4c6801f4229d2f6</authentication>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="20125">
                  <text>Ken Armson fonds</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="49">
              <name>Subject</name>
              <description>The topic of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="20126">
                  <text>Forestry</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="20127">
                  <text>A collection of thousands of photographic slides depicting Ken Armson's work in the field of forestry, 1952-1995. </text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="39">
              <name>Creator</name>
              <description>An entity primarily responsible for making the resource</description>
              <elementTextContainer>
                <elementText elementTextId="20128">
                  <text>Ken Armson</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="40">
              <name>Date</name>
              <description>A point or period of time associated with an event in the lifecycle of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="20129">
                  <text>1952-1995</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="47">
              <name>Rights</name>
              <description>Information about rights held in and over the resource</description>
              <elementTextContainer>
                <elementText elementTextId="20130">
                  <text>These images have been digitized and shared on this site with permission. Most are still under copyright. </text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65898">
                <text>80 year balsam fir-spruce stand</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65899">
                <text>Forest Products Industry</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65900">
                <text>80 year balsam fir-spruce stand. NB. moss-covered stump in foreground. Repap, Miramichi</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65901">
                <text>Ken Armson</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65902">
                <text>1991-07</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65903">
                <text>JPG</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65904">
                <text>Still image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="65905">
                <text>Armson-Silviculture-2082</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="38">
            <name>Coverage</name>
            <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
            <elementTextContainer>
              <elementText elementTextId="65906">
                <text>Canada - New Brunswick - Miramichi</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="7231" public="1" featured="0">
    <fileContainer>
      <file fileId="7899">
        <src>https://digitalcollections.lakeheadu.ca/files/original/e9098d33af6f35b719740e7b0d8bae65.jpg</src>
        <authentication>097f2570a23c3dbddf353eda1ab01340</authentication>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="20125">
                  <text>Ken Armson fonds</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="49">
              <name>Subject</name>
              <description>The topic of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="20126">
                  <text>Forestry</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="20127">
                  <text>A collection of thousands of photographic slides depicting Ken Armson's work in the field of forestry, 1952-1995. </text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="39">
              <name>Creator</name>
              <description>An entity primarily responsible for making the resource</description>
              <elementTextContainer>
                <elementText elementTextId="20128">
                  <text>Ken Armson</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="40">
              <name>Date</name>
              <description>A point or period of time associated with an event in the lifecycle of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="20129">
                  <text>1952-1995</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="47">
              <name>Rights</name>
              <description>Information about rights held in and over the resource</description>
              <elementTextContainer>
                <elementText elementTextId="20130">
                  <text>These images have been digitized and shared on this site with permission. Most are still under copyright. </text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="58600">
                <text>A "wooden" tractor built by loggers.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="58601">
                <text>Forest Products Industry</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="58602">
                <text>A "wooden" tractor built by loggers. BC Forest Products, Port Renfrew Person is Dunc Naysmith</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="58603">
                <text>Ken Armson</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="58604">
                <text>1980-06</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="58605">
                <text>Jpeg</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="58606">
                <text>Photograph</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="58607">
                <text>Armson-Silviculture-1609</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="38">
            <name>Coverage</name>
            <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
            <elementTextContainer>
              <elementText elementTextId="58608">
                <text>Canada-British Columbia-Port Renfrew</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="12333" public="1" featured="0">
    <fileContainer>
      <file fileId="15227">
        <src>https://digitalcollections.lakeheadu.ca/files/original/4398b20565848717951ea049acd111f7.jpg</src>
        <authentication>6eaa13c9b442c2d0f70d5bd3a8f3da30</authentication>
      </file>
    </fileContainer>
    <collection collectionId="1">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1">
                  <text>Thunder Bay Finnish Canadian Historical Society Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="49">
              <name>Subject</name>
              <description>The topic of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="2">
                  <text>Finnish-Canadians</text>
                </elementText>
                <elementText elementTextId="3">
                  <text>Life in Thunder Bay</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="4">
                  <text>Photographs collected by the Thunder Bay Finnish Canadian Historical Society from a wide range of collectors, documenting Finnish immigration to and life in Thunder Bay. </text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="39">
              <name>Creator</name>
              <description>An entity primarily responsible for making the resource</description>
              <elementTextContainer>
                <elementText elementTextId="5">
                  <text>Thunder Bay Finnish Canadian Historical Society</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="45">
              <name>Publisher</name>
              <description>An entity responsible for making the resource available</description>
              <elementTextContainer>
                <elementText elementTextId="6">
                  <text>Lakehead University Library</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="101477">
                <text>MG8_D784Ii348&#13;
formerly MG8_D784Hi348</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="101808">
                <text>A boy with a dog and a fish</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="101809">
                <text>People</text>
              </elementText>
              <elementText elementTextId="101810">
                <text>Recreation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="101811">
                <text>Lifestyles: A boy with a dog and a fish. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="101812">
                <text>JPG</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="101813">
                <text>Still image</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="15244" public="1" featured="0">
    <fileContainer>
      <file fileId="18848">
        <src>https://digitalcollections.lakeheadu.ca/files/original/e1d28c3954b0b86da2eab801a3993c14.pdf</src>
        <authentication>0395f4c0685afc6201bcd50f44c51cbc</authentication>
        <elementSetContainer>
          <elementSet elementSetId="4">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="52">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="129249">
                    <text>I

•
A BRIEF TO THE COMMISSION
ON UNIVERSITY GOVERNMENTAL ORGANIZATION

of Lakehead University

by

W. D. R. ELDON,

Thunder Bay, Ontario.
January 31, 1972.

Ph.D.

�I
I
I
I
I
I
I

I

I
I
I

CONTENTS PAGE

CONTENTS

PAGE

Structure in Perspective

1

The Environment

3

Student Requirements

5

The Faculty

6

The Department

7

The Dean

9

Faculties

10

The President

11

Administrative Services

14

Board and Senate -- One Tier or Two?

15

The Board of Governors

18

The Senate

19

Committees

21

Summary of Suggestions

24

�January 31, 1972

A BRIEF TO THE COMMISSION
ON UNIVERSITY GOVERNMENTAL ORGANIZATION
of Lakehead University

by

W.

D.

R. ELDON,

Ph.D.

Structure in Perspective
"Well-intentioned men can make any system of government work,
but in the absence of good men even a good system will not work".
This saying suggests that there are factors of greater importance
than structure in making an organization work effectively and fulfill
its aims.

It also suggests that there may be a choice of several

systems of government for any given institution.

The system

favoured (over other Equally workable systems) may reflect the prevailing priorities and values of members of the community.

My

suggestions regarding a governmental structure for lakehead
University necessarily reflect my own priorities and values,

and it

is hoped that any collision with other ideas as to structure will
generate useful debate and a happy outcome.
Ideally,

the structure of government of the University should

provide for democratic express ion of ideas and decisions on academic

�I
I
I
I
I
I
I
I

•I
I
I
I

I
I
I
I
I

- 2 policy.

It should facilitate the effective carrying out of policy and

allocation of resources to different parts of the University operation.
The structure should permit anyone to identify clearly who has
responsibility for what,
too,

and who has authority over what.

Ideally

the responsibility of an individual or committee should not be

greater than its authority.

The student and the professor should

have a strong voice in the affairs of the University,

but the burden

of committee work should be sufficiently restrained to permit the
student to graduate and the professor to teach.
The present structure government provides some genuine
opportunities for democracy and some illusions of democracy,

some

clarity in the division of functions but some troublesome areas of
confusion.

The Senate, for example, is not sufficiently representative

of the University community.

The Board is not sufficiently repre-

sentative of the citizens and potential clientele in the area the
University serves.
unresolved,

There are genuine differences of viewpoint,

as to where authority does rest or should rest and as

to how authority should be exercised.

The channels of communication

between student and professor are not always as open as they should
be,

despite the presence of students on committees in many departments.

Nor is there a satisfactory rapport between some faculty and something
known as "The Administration".
Some of the difficulties lie deeper than the present system of
organization,

but result from unresolved differences in philosophy

about what a university is and how it should be run.

This state is

�- 3 not surprising in view of the substantial changes that have swept
over North American universities in the past decade.
time,

At the same

it is well to air and debate these matters in the context of the

current review of governmental organization of the University.
a welcome opportunity to update the system if it needs it,

I

It is

and to

ensure that it will serve the modern objectives of the University.
The Environment

I

The key to the environment in which Lakehead University must
operate in the next ten years is to be found in the trends of the
past decade.

During this time the government sector of our society

and economy has increased its power at the expense of the private
sector in a variety of ways.

Govern.mental control has increased in

such areas as ecology and consumer affairs,

I

I
I
I

and private business

is understandably worried by a mass of complex federal legislation
in taxation,

labour relations and competition policy,

all of which

seems designed to restrict its freedom and decrease its opportunities.
Large multi-national companies appear best fitted to weather the
storm,

so that increasingly a university graduate must make his

career in big business or big government.
In the universities themselves in the past decade we have witnessed a growth in governmental control over university financing and
the introduction of graduate programs.

These trends are likely to

carry through into the coming decade.

Privately financed institutions

such as Waterloo Lutheran University and Trinity College ( Toronto)
will probably succumb and conform to the provincial government's

�I
I
I
I
I
I
I
I
I
I
I
I
I
I

- 4 non-sectarian system.

The draft report of the Wright Commission

on Post-Secondary Education recommends a further giant step in
the direction of governmental decision-making on matters dear
to university faculties and senates.
The report cannot be ignored.
report will just "go away".

Neither Dr.

Wright nor his

It may be true that some of the Wright

recommendations were intended as trial balloons and subject to revision after public reaction,

hence the description "draft report".

But public tolerance of high educational costs and public support
for independent universities is at a low ebb.

The government

has recently been re-elected with a strong majority.
to centralization may prove to be irresistible.

The trend

And the government

may well hold the line on educational spending except at Queen's
Park itself.

If these tendencies continue,

within the next ten years uni-

versity senates will lose much of their present power to add or
delete programs or faculties even at the undergraduate level.
Academic staff will come much closer to being civil servants,

I
with

the president something of a branch manager.
In this environment there will be a premium on two things:

I
I

I
I
I

first,

the ability of the institution to deal successfully with Queen's

Park, and second,
region it serves.

the political strength of the institution in the
More community involvement and responsiveness

to community needs will be required.

This the Board in its present

form can only partially supply since its concern is more with finance
than with academic programs.

II

I

�- 5 -

I

Internally,

with the likelihood of continuing financial

stringency, a constant need to prove "efficiency" will be the price paid
by the University for avoiding direct intervention and operation of
the universities from Toronto.

Thus the pres sure to delete low

priority programs will intensify.

I
I
I
I

Student Requirements
Ontario universities are experiencing the early stages of
changes in the structure of demand for university academic programs.
Arts programs are losing ground.

Students will not indefinitely

enroll in large numbers in programs that have no relevance to the
job market.

In a society increasingly controlled by government,

lawyers and accountants should do well.

Since health and welfare

programs can be expected to grow and cost more,

earnings in the

various branches of medicine and dentistry should continue to
Bright prospects for medical graduates are already

improve.

leading to crowding in some American medical schools.

Ecology can

be expected to provide increasing governmental demands for personnel.
At Lakehead certain science subjects, forestry,

business, nursing

and any new pre-medical programs may be expected to be growth
points.

Lakehead University does not offer certain programs that

may be attractive to students -- law,
dentistry.

medicine as such, and

The University will have to be in a position to take

advantage of new opportunities that will attract government support.
Also the University will have to become more proficient in restructuring its program to respond to changing student needs.

�I
I
I
I
I
I
I
I
I
I

•
-I

- 6 Furthermore, if Grade 13 is eliminated or if there is a
province-wide move to reduce university undergraduate training
to three years,
necessary.

additional adjustments in curriculum will become

A somewhat younger and less mature student population

may have rather different requirements.
empowered to grant degrees,

If community colleges are

another suggestion in the Wright re-

port, the competition for students may intensify.

The complex

set of possible developments in the Province may force the
universities to think hard about ways of preventing their degeneration
into glorified high schools.
Many requirements of university students may continue as
before:

the need to learn a capacity for independent study and

research, to associate together in a residential environment away
from home,

to mature.

The University structure should facilitate

the meeting of all these requirements,

changing or unchanging.

The Faculty
Students will adapt readily to the changes in the institution and
in the Province.

Their needs are in part the cause of change.

I
I

the more responsive the institution is to the environment,

'I

an end and not an end in himself.

I

But

the greater

the discomfort that many faculty members may experience.
The dilemnB of the faculty member is that he is a means to
The student is the client.

student enrolment in a program falls,
peril of becoming "redundant".

the faculty member is in

In a hard financial climate,

especially if there is limited growth in total enrolment, faculty

If

�I

I
I
I
I
I
I

- 7 members in particular fields and in fact whole departments may
see their expectations wither.

If the pinch is provinoo-wide,

the institution of tenure will not protect redundant faculty.

The

challenge for the University is to adjust staff numbers to the
requirements of changing academic programs without an annual
upheaval.

The University should explore the possibilities of

assisting tenured and probationary faculty who wish to remain at
the University in readjusting their qualifications to make this
possible.

Satisfactory career opportunities may not lie in their

chosen field,

and some means should be found of assisting the

transition to a revised career in the case of a faculty member
left high and dry by an ebb-tide.
The faculty association-trade union approach will not be the
best response to the problem of faculty members made nervous
by change.

Carried too far,

the trade-union spirit can spoil a

university.

Should a professor have to worry about spending more

time with his students than union rules allow?

If the university

community meets the problems caused by change head-on and seeks
solutions that encourage adaptation and improve job-security, there

I

is no need to extend the s cop~ of operation of the faculty association
or to give it specific recognition in the broad policy-making or
government of the institution.
The Department
Many of the important issues bearing upon the structure of
university government arise within the context of the academic department or faculty.

For example,

the chairman is responsible for

�- 8 academic leadership and for the day to day functioning of the department.
How far do his responsibility and authority extend?
a vote in his depa~tment?

I
I

Can he over ride

To what extent should he share the

responsibility for making departmental policy with committees of
faculty and students?
to recall?

Should he be elected?

Should he be subject

Should he represent his faculty as their obedient spokes-

man, or should he take the views of his colleagues as "advice"?
Should he carry out the policies of the University in his department?
What are the limits of departmental autonomy?

I

The problem is to strike a balance between the legitimate
desire of every member of the department to have some voice
in matters which affect him and the need to recognize that some
academic staff members have greater experience and better judgment
than others when it comes to developing and implementing departmental policy.

Some possible dangers are that an over-developed

committee system may enable inexperienced juniors to override
more experienced senior academics,

or that timid mediocrity in

a department may prevent the upgrading of staff.

In addition,

too

many departmental problems end up on the president's desk because
either (a) no one accepts the responsibility for solving the~,

or (b)

no one has authority to make a final decision.
There is accordingly much merit in granting a chairman the
authority he needs to carry out his responsibilities for developing and
operating the department.

The dean should have a distinct influence

in guiding the choice of a department chairman,

and should be able

�I
I
I
I
I
I
I
I

- 9 to intervene decisively where a department is in a troubled state.
The recall of a chairman should not be an intra-departmental matter.
The chairman should be able to count on the support of the dean
in implementing University policies in his department.
members of the department,

including the students,

In turn,

the

should be able

to offer advice and assist in the developing of departmental policies.
The Dean
The present role of a dean at Lakehead University is ambivalent.

Different and incompatible views exist as to what his

role should be.

Is he mainly a "faculty man",

faculty and a chairman of his chairmen?

a spokesman for his

Or is his role primarily

that of a senior administrator who applies the policy of the

I
I

University in his faculty?
The uncertainty as to what the dean's role is or should be,
or differences in the way that different deans interpret their role,
have caused a double dose of mistrust.

The more senior admi-

nistrators may come to feel that they cannot rely on a dean to
implement policy, while faculty members believe that the dean is
a "tool of the administration" rather than the champion they
expect him to be.
The modern role of a dean is an in-between one,
a time when all authority is questioned.
a chairman.

difficult in

But so is the role of

We must recognize the inadequacy of a situation where

deans and chairmen may be tempted to solve problems by running
before the prevailing wind.

My own preference is for giving the

dean sufficient authority to carry out his responsibilities to lead

�I
I
I
I
I

- 10 his faculty,
faculty,

to balance inter-departmental considerations within his

and to apply university policies within his faculty.

The opportunity for CUGO to enunciate the appropriate role
of deans and departmental chairmen is of crucial importance to
the University.

No other matter is of such vital importance for

faculty morale and for the quality of the academic program.
Faculties
The organization of departments into faculties is not static if
the relative importance of programs and student enrolments is
changing.

There is no significant monetary saving to be achieved

by consolidating existing departments or faculties into larger units.
For example, the dean of a super-faculty is likely to require an
associate dean and more secretaries.
however,

In the next few years,

some regrouping of faculties would seem to be necessary

for more effective operation.
than one faculty,

No department should be part of more

since double voting power gives such a· department

an unfair weight in the counsels of the university.
on,

new faculties may be €Stablished,

As time goes

particularly if some of the

professional schools should grow into much larger units.
In the near future the University might well assess whether a
dean should be appointed to oversee graduate studies.

The advantage

lies in his ability to deal on even terms with other graduate deans
in the Province.

Also one person in this role can give focus to

graduate activity in the University,

with a budget to help him

promote the most promising directions of postgraduate endeavour.

�I

- 11 The same need may well exist with respect to research
activity.

Especially if the Wright recommendations for separate

funding of research and teaching are adopted,

it might be advantageous

to have a director of this branch of university activity supervising
internal grants for research purposes.

Probably it would be

advisable to consider the appointment of a single Dean of Graduate
Studies and Research to fill both roles.
The President
The demands upon the president are numerous and heavy,

I

and the structure of government of the University should facilitate
the institution gaining the utmost value from his aptitudes and talents.
His desk should not be cluttered with trivia.

His time should not

be consumed with routine supervisory tasks that he can delegate to
others.

He should have mobility in the sense of being able to turn

his attention to whatever matter is of greatest importance at the

I
I
I
I

time, whether it be persuading the government to adopt a new
academic program,

raising funds from external sources,

the image of the University in the area it serves,

improving

or developing a

strong alumni organization.
The president by reason of the variety of matters that may
properly come to his attention has a better overall view of the
University than anyone else.

He should understand budgeting and

accounting and sense the effects of alternative allocations of
resources to faculties or functions within the University.
He should represent the University to the community, and deliver

�I
I
I
I
I
I
I

- 12 innumerable speeches and meet as many citizens as he can.
In addition he must interpret the University's needs to the government
and join with other university presidents in developing common
strategies for dealing with governments.

Within the University he

should interpret the University to itself.

He should crystallize

opinion,

define objectives and plan development.

The president

has prime responsibility for the operation, financing,
public relations of the University.

planning and

Although the power and prestige

of a university president has greatly diminished in the past decade,
his role is still the most crucial one for the university.

I
I

The structure of government,

where the president is involved,

should therefore permit him to perform his many-sided role and to
provide leadership to the university community over a broad f rent.

If he is to do so effectively,

he must simultaneously be sheltered

from routine problems that others should solve and yet be accessible

I
I
I

to currents of opinion in the student body, faculty and community.
One of the hazards of the presidency is isolation, and so the structure
of government must facilitate communication between the president
and the large number of people who make up the body of the
university.
Effective functioning of the presidency depends to an important
extent upon deans and department chairmen working effectively.

If

they abdicate their responsibilities, power over matters which

should be worked out within the department or faculty will pass to
the president's office.

When decisions are made in the wrong place,

�I
I
I
I
I
I
I
I
I
I

- 13 the effects are bad all round.

phenomenon of academic vice-presidents results partly from the
fact that the president needs more hands and someone on whom he
can rely consistently.
A clear definition of the role,
of deans and department chairmen,

I
I

responsibilities and authority
and a system that draws

highly qualified people to those positions is therefore of vital importance if the president is to play his proper role in the university.
There is no single organization chart that can be drawn on
the basis of these comments,

but a few examples will suffice.

Just as the president in the academic area should be kept free of
matters that should be delegated to a dean of department chairman,
so in the administrative services area he should be freed from the
mechanics of running the power plant, the cafeteria,
ion of junior personnel.

I
I

The growth of the relatively new

and the select-

If the focus of the president's activity is

mainly in the academic side or in the community relations,

then

day to day reporting by administrative heads should be delegated by
the president to someone else,

such as an administrative vice-

president.
On the other hand,

the structure of government should enable

the president to involve himself directly in the work of policy-making
committees such as committees of the senate and board of governors.
We should retain at Lakehead the existing formula which allows
either the President or Vice-President to sit as an ex-officio member
of important committees of Senate.

�I
I
I

- 14 It is of great importance that the president should not be
isolated from the students.

This is difficult to provide for in the

formal structure of government of the University.
he will meet students in university committees,
small number.
and to sample

I
I
I
I
I
I
I
I

I

To some extent

but only a relatively

The president's ability to mingle with the students
their opinions will ordinarily depend upon himself.

But he will more easily keep his door open for students if he can
delegate most routine tasks to others.
To keep open his channels of communication with students and
faculty,

the president may wish to establish ad hoc advisory committees

for short periods of time.

Committees to advise the president on

academic and student matters should ordinarily be established for
a particular short term purpose.

Most academic questions can be

satisfactorily handled through the standing committees of Senate,
but a president would be unduly limited in seeking advice if he
could deal only with the formally established standing committees.
Although these general observations can be made regarding
the structure of university government as it relates to "a
president", different people occupying the presidency can be expected
to function in different ways. and to adopt different practices when it
comes to delegating routine tasks,

meeting with committees,

and

seeking student opinion.

I

Administrative Services
The administrative and financial branches of the University
on the whole now report directly to the President.

I

committees of faculty and students,

Certain standing

such as the computer services

�I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I

I

- 15 committee and the library committee,

ensure some influence by

the academic community over the policies of some of the service
branches.

By and large the faculty do not intervene in the day

to day workings of these departments which are responsible to
the President.
Unless the president has a particular aptitude and interest in
these departments,

he may prefer to have an officer deputed to

supervise these functions.

A Vice-President of Finance and

Administration would free the president to concentrate on academic
and community matters vital to the development of the institution.
Such an appointment should be seriously considered.
The expertise of the heads of the academic service departments
should command respect.

Their morale will suffer if they are

subjected to academic intervention in their operations on a haphazard
basis.

Because academic committees change membership in whole

or in part from year to year,
consistent policies,
need arises.

they may not be able to adopt

or even to develop a policy at all when the

An adequate representation from the appropriate

service departments may,
of membership and policy.

however,

ensure the necessary continuity

A committee of heads of service de-

partments should be encouraged to develop consistent policies where
such are needed across these departments.
Board and Senate - - One Tier or Two?
The present division of labour between the Board of Governors
and the Senate of Lakehead University allows each group to concentrate on what it presumably does best.

The practical background

.I

�- 16 -

•
•
•
•
•I
I
I
I
I
I
I
I
I

I
I
I

of the community representatives on the Board equips them to deal
with the finance and business aspects of the institution.
representatives also have an external,

community perspective on

the university which is quite different from the internal,
perspective of the members of Senate.

These

academic

At one time universities

commonly did not have an academic senate at all,

but only a certain

number of academic staff sitting on a senate that was largely appointed
from outside the academic community.

The rather recent develo-

ment of an academic senate has brought purely academic viewpoints
to bear upon problems and questions in the academic area.

The

merits of the present system are largely the benefits of specialization
and control by academicS over academic matters.
A question has arisen as to whether the Board and Senate
might be grouped into one governing body,

a system recently adopted

at the University of Toronto but rejected by the University of Waterloo.
Representatives of the community would sit with administrators, faculty
members and students in a single governing body that would handle
the financial and community matters now dealt with by the Board,
as well as the academic matte rs now within the purview of the
Senate.

External opinion would thus be brought to bear upon academic

questions such as addition of new programs and the academic timetable,

while academic opinion could be focussed directly on budgets,

endowments,

and pension plans.

Board and Senate would not exist,

Jurisdictional disputes between
and all major decisions of the

University would be scrutinized by both practically-oriented and

�I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I

- 17 academically-oriented people.
Several considerations suggest,
careful assessment of pros and cons,

however,

the advisability of a

and particularly of the weight

of membership to be given to various groups before an unicameral
system is recommended.
powers,

A unicameral body would have very large

not subject to a sober review by a second body within the

University.

The nature and quality of its decisions and com -

promises could vary widely depending upon the relative strength
of membership representing such diverse groups as junior and
senior professors,

departments or faculties,

employees, administrators,

other university

local businessmen and representatives

of the provincial government.

Also,

there are both advantages

and disadvantages to the involvement of businessmen in academic
decisions and of academics in financial decisions:
hand,

each may learn from the other,

on the one

but on the other hand the

advantages of specialization may be lost by involving people in
matters they know little about.

At the same time,

if the powers

of both Board and Senate are truncated in the future by the more
detailed intervention of the Province in internal university affairs,
the matter of o~ tier or two may be of little moment.
Assuming, however,

that significant decisions remain to be

made by the University internally,

the crucial consideration may

be that community representatives now on the Board of Governors
could not afford the additional time needed to become informed
and involved in purely academic matters.

Nor could a sufficient

�I
I
I
I
I
I
I
I
I
I
I
I
I
I

- 18 -

number of faculty members or students afford the time needed to sit
through what would amount to the combined deliberations of the
Board and Senate, plus those of the existing committees of each
body.
Furthermore, the present two-tier system is capable of
modification short of actually combining Board and Senate into
one body.

The University community sees rather little of the Board

and may be inclined to dismiss it too lightly.

The credibility

of the Senate might improve if it were more fully representative
of the University community.
The Board of Governors
The Board members,

with full-time occupations elsewhere,

can harly be expected to spend much more time than they do on
the University's business. Consistent with this time limitation, however, it would be desirable to increase the number of formal and
informal links between the Board and the University community.
There are many ways of accomplishing this,

but one of the formal

devices possible is to establish periodically

a committee of Board

members to "visit" some branch of the University.
might be purely a Board committee,
Senate group.

The committee

or it might be a joint Board-

The idea is an adaptation from a custom at Harvard

University, whereby a committee of the Board of Overseers is
established to "visit" a department or school of that University.
By talking with the faculty and students in some depth, the Board
committee gains an insight into the problems and needs of some branch

�- 19 of the University.
Another possibility is to establish joint Board-Senate committees
to examine some of the areas where the work of the two bodies
adjoins or overlaps.

Perhaps a joint committee on Board-Senate

relations could make some useful suggestions about the sharing of
views,

I
I
I

information and proposals and about the lines of communication

between the two bodies.
The Board of Governors is presently of a manageable size for
doing its business,

but even so much of its work is handled by its

executive committee which meets more frequently than the full
Board.

An enlargement in the size of the

Board, together with a

policy of paying expenses of members from more remote points,
might make this body more representative of the North Western
Ontario area which the University serves.

I

I

The enlargement of

the Board from about 30 to around 40 members would make it
possible to establish more Board committees to work with members
of the University community.

Provided the faculty have some

representation on the Board,

it is likely neither necessary nor

desirable to increase the number of faculty members sitting on the
Board.

The chief value of the Board is to bring the experience of

the community into the affairs of the Universi~y.
The Senate
The composition of the Senate, however,

should be revised to

make it more effectively represent the University community.
Particularly important,

at present the student members are effectively

�- 20 muffled by the faculty.

A substantial increase in their numbers,

say from two to six representatives,

would make it possible for

their views to come to the surface.
It would also be desirable to ensure that the representation
of elected faculty members should more closely reflect the proportion of staff members and students in each of the four faculties.

I
II

-I
I
I
I

-I

If each faculty is effectively represented,

there is probably no

need for the chairman of every department or school of the
University to sit on the Senate at once.

On the other hand,

the

Comptroller and a few of the heads of service departments might
well be added to the membership of the Senate.

Substantially

enlarging the total size of the Senate would likely make it unwieldly,
though an increase in membership from about 40 to 50 might
improve the quality of debate rather than the reverse.
The procedures of the Senate would benefit from some revision.

The executive committee of the Senate might well play a

more active role in sifting items placed on the agenda.

The

debate over minutes from committees occupies a disproportionate
amount of time in the Senate,

and the procedure of reviewing

all committee minutes should be abandoned.

Rather,

chairmen of

committees should take the initiative in advancing particular matters
for Senate approval,

or should report matters of interest to the

full Senate when they feel such reports are needed.
Further, the Senate should not be allowed to become a forum
for questioning the President on the performance of the administrators

�I
I
I
I
I
I
I
I

- 21 An adversary

of the University or on the actions of the Board.
system of political parties,

government and opposition,

is inappro-

priate for governing the academic affairs of a university
The Vice-Chancellor,
institution,

as the operative academic head of the

should continue to preside over the meetings of the

Senate.
On balance, I am inclined to believe that the effectiveness
of both the Board and the Senate can be increased,
can be more links between them.

and that there

There is no need to rush into

a unicameral governing body which could quickly become a deep
disappointment.

It would be wiser to wait and observe the

experience of the University of Toronto with such a body.

Also,

the design of an eventual governing structure for the University
should await the final outcome of government action on recommendations of the Wright Commission on Post-Secondary Education.
Committees
The poor reputation of committees is embodied in such

I
I

statements as "Committees always work badly",

size of committee is one", or "A camel is a horse designed by
a committee".

'
~

I
II

"The optimum

Yet the institution of the committee,

ingrained in university life,

does provide a mechanism for bringing

different viewpoints to bear on a problem,
divergences of view.

now deeply

and for dealing with

The success of a committee depends upon

the manner in which divergences of view are expounded and
received.

The committee system presupposes that the irritant

�I

- 22 grain of sand in the oyster will often start the pearl.
Committees are better for arriving at an appropriate policy

I
I
I
I
I
I
I
I
I
I
I
I

I

than for carrying out necessary but unpopular measures in a
speedy and decisive fashion.
should be recognized,

The limitations of a committee

and the device should not be overworked.

At all levels of the university -- department, faculty,

and

university as a whole -- committees have their valuable place.
Students and faculty members should participate at all these levels
of decision-making relating to policy.

Such activity in policy-

making is entirely consistent with a system that allows deans and
department chairmen to carry out their day to day responsibilities;
there is a workable balance between consultation with committees
and the exercise of discretion by the responsible official.
Because committees are generally representative (and should
be) of a variety of interests,

they may find it difficult to design

bold or innovative proposals or to establish priorities that affect
some program, department,

or faculty adversely.

It is often

more satisfactory if leadership in such matters comes from the
president, the dean,

or the department chairman.

Yet the uni-

versity community is entitled to have important plans affecting the
development of the university discussed by the appropriate committees.
The inclusion of students on committees can be an important
part of their training and education.
becomes an exercise in frustration,

Even when committee work
the student benefits from

participation and learns a lesson in realism.

In addition, the value

�- 23 of student viewpoints to the work of a committee can be very conA committee discussing problems in liaison with high

sider able.

II
I

II
I
I

I
I
I

I
I
I
I
I

I
I
I
I

schools , for example,

in practice must seek advice from people

who have recently come from high schools.

A student also has

more experience of Professor X's classroom and teaching ability
than any other staff member has.
ment of staff,

salaries,

In some areas such as appoint-

promotion,

and tenure,

the experience of

the student and his particular relationship with the individual cases
coming before a committee may make it advisable for membership
to be reserved to faculty members and administrators.

But even

here I would not shut the door on student participation.
The structure of committees in the University is constantly
in need of review and updating.

No blueprint for committees can

be established for the years ahead.

It may

for the Senate or a faculty to establish a
to prune the dead wood.

II

occasionally be necessary

committee on committees 11

The load of committee work on a faculty

member can interfere at times grievously with his research,
teaching,

and sessions with students.

Herein lies the chief need

to keep the committee structure under control,

and possibly in

some instances to insist that a faculty member take a breather from
committee work!
As new needs develop in the University,
be formed.

new committees will

Some may be called into being to deal with new situations

confronting the University because of provincial government policies.
The need to reassess teaching methods,

the crucial importance of

high school liaison, the need to involve the community more deeply

�- 24 in the University all may be expected to lead to the formation of
new committees in the next few years.
Summary of Suggestions
My analysis of the needs of the Lakehead University in the
next few years suggests the desirability of definition of roles,
of thinking chead and of evolution rather than radical re-shaping of
the structure of university government.

The specific recommendations

that emerge from this analysis should be interpreted as suggestions

I
I

I
I
I
I

that help to stir the pot,

not as my final conclusions.

The main

suggestions are these:
1.

The University should examine the feasibility of
providing satisfactory career opportunities for
probationary and tenured faculty where changing
student requirements for courses would otherwise
make them "redundant".
The opportunity would
not necessarily lie in the staff member's chosen
field.

2. The University should enunciate, possibly initially
through the Commission on University Governmental
Organization, what the responsibilities and authority
of deans and academic department chairmen should
be.
These officials should have sufficient
authority to exercise academic leadership and to
implement University policies in their respective
faculties or departments.
At the same time,
staff and students should play a significant role
in developing these academic policies.
,3 . The appointment of a Dean of Graduate Studies
and Research should be studied.

Ill

I
II

II

4.

The President or Vice-President should continue
to sit as ex officio members of most Senate committees.

5.

The appointment of a Vice-President of Finance and
Administration should be considered.

6. A committee of heads of service departments should
be encouraged to develop,

wherever appropriate,

�- 25 -

6. cont'd.
consistent policies across these departments.
7.

The number of formal and informal links between
the Board of Governors and the University community should be increased.
Periodically, a Board
or joint Board-Senate committee should be formed
to "visit" a department, school or faculty of the
University.

8. A joint committee on Board-Senate relations
should be established.

9. The Board of Governors should be enlarged to
provide broader representation from the area
served by the University and to permit more
Board committees to work with members of the
University community.
10. The composition of the Senate should be revised and
the total membership somewhat enlarged to make
it represent more effectively the students,
academic staff, faculties and administrative service
departments of the University.
11.

The procedures of the Senate should be revised to
provide for the more effective discussion of
questions refer red by Senate committees.

12. The question of whether the Board of Governors and
Senate should be joined in a single governing body
should be left in abeyance pending further experience
with a unicameral system at the University of Toronto
and until government action is taken on the final
recommendations of the Wright Commission on PostSecondary Education.

In an analysis of governing structures, not enough can be
said about people who make the structure work.

In a modern

university the number of people involved in the government of a
university is much greater than it was 20 years ago.
participate.

Students

Faculty members register their opinions and make

�I

I

I

- 26 rules and policies in committee.
dean or president,

whether chairman,

must consult innumerable interested constituen-

cies within the university,
Relations of

Administrators,

and must be responsive to their needs.

trust must exist between the constituent parts

of the university or any structure will tend to become unworkable.
At Lakehead the attractive campus is a good base for a university
of excellent quality in the Northland.

The governing structure can

be made to facilitate growth and effective responses
challenges.

to future

But it is the spirit of the University community

itself that will guarantee the future.

Thunder Bay, Ontario
January 31, 1972.

�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="4">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="618">
                  <text>Lakehead University Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="619">
                  <text>Photographs from Lakehead University's history: people, events,  and campus. </text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="130411">
                <text>A Brief to the Commission on University Governmental Organization of Lakehead University</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="130412">
                <text>Universities</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="130413">
                <text>A Brief to the Commission on University Governmental Organization of Lakehead University by W D R Eldon, PhD, January 31 1972.  The brief includes discussions about the university structure, administrative roles, committees and a summary of suggestions. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="130414">
                <text>W D R Eldon, PhD</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="130415">
                <text>1972-01-31</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="130416">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="130417">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="130418">
                <text>Text</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="130419">
                <text>lu-15h</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="38">
            <name>Coverage</name>
            <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
            <elementTextContainer>
              <elementText elementTextId="130420">
                <text>Canada - Ontario - Thunder Bay</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="15137" public="1" featured="0">
    <fileContainer>
      <file fileId="18720">
        <src>https://digitalcollections.lakeheadu.ca/files/original/71ac477e706daf8e3bdb6e521992a6e2.pdf</src>
        <authentication>6987e19718e04e5ea64182d9fa29684c</authentication>
        <elementSetContainer>
          <elementSet elementSetId="4">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="52">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="128769">
                    <text>C

1ffi HR. ][IE 1P'

'I[' (0) 'Il' 1HI.IE

$

JE: Im"A 'lr .IE

«» 1P'

IL.AJK.EIIII.IE A.1ID UIJ:Im" IIWlE liL$ II 1r W

cc:@:im- &lt;em: moo nooG

'Il' 1HIE IL. AJK..IE 1HI.IE.A\. ID&gt; lIDOOIIWlE ffi.$ II'Il' W m.m; W 1I1E Wl

�The Lakehead University Review was conceived
some five months ago by the authors of this brief.

We reflected on the apparent lack of success of
previous attempts to produce a journal 9 the then Chairman of the
Publications Committee having deemed the task "impossible".

We

further reflected on the somewhat embarrassing situation created
by the fact that the students had taken the initiative in this field
by publishing the widely-circulated Essays from Lakehead.

By mid-August we had decided that the publication

(

of a scholarly journal at Lakehead University would not be impossible.
We agreed that in the short~run, the Review would contribute to the
academic life of the University and the intellectual development of
t he area; in the long-run, it could take its place among the major
Canadian interdisciplinary reviews o

Having decided that the idea was academically feasible 9
we then had informal discussions with a commercial printer to
determine the approximate cost of printing and binding a journal of
some one hundred pages.

With this data 9 we prepared a preliminary

budget which we then presented to the President who encouraged us
to pursue the idea even further.

�-2-

We decided not to involve the University officially
until we were certain that the content of the first number would
warrant Senate endorsement.

Therefore, we decided to undertake

the preparation of the Review independent! y with the intention that
when the first number was ready to go to press, we would seek
the support of the University by requesting that the Senate select
an editorial board.

We also decided that the Review should be a
biannual publication.

With a target date of March, 1968 (the second

number to appear in October, 1968) in mind, it seemed pointless

(

to invite manuscripts from the entire faculty of the University.
Firstly, many were not available in the late summer and were not
expected back on campus until mid-September.

Secondly, we felt

that many potential contributers would be unwilling to devote time
and energy to preparing a scholarly paper for a journal which at this
stage existed only in our minds.

Thirdly, if we were to adhere to

the somewhat strict timetable imposed by the printer, we needed to
know who was willing to contribute for the first number and provide
them with rather exacting deadlines.

With this in mind, we approached several members
of the faculty whom we knew had recently completed some research

(

�-3-

and discussed with them the idea of publishing their results in the
Review.

We were further encouraged by the enthusiasm with which

the idea was received, and we greatly appreciate the efforts put
forth by these persons on such short notice.

As a result, we now feel that we have assembled an
excellent initial number, one which will undoubtedly set the
standard for future issues.

The contents of this number would

include the following articles:

Elizabeth Arthur - The Landing and the Plot
John G. Rideout - Shelley's Image of Methe r and Child

(
Lewis Smith - The Indian and Negro in Mark Twain:

Stereotype or Reality')

Douglas R. Lindsay - Migration and Persistence of Certain Arctic-Alpine
Plants in the Lake Superior Region of Ontario
George J. Merrill - The Pre-Armada Years:
Sentiment

Literature of Patriotic

We also contacted numerous publishing companies and
invited them to contribute books for review.

The book review section

will include:

T. B. Miller - Canada -- Unity in Diversity, by P. G. Cornell et al
P. G. Panikar - Economic History of Europe, by M. Postan

�-4-

A. Alexander - 1867: Disraeli, Gladstone and Revolution, by Maurice
Cowling
E. Eager - Mitch Hepburn, by Neil McKentey
I. G. Davies - Pullman - an Experiment in Industrial Order and
Community Planning, by Stanley Buder
A. 0. Menhart - Cry Ararat, by P. K. Page
G. J. Merrill - Fools of Time, by Northrop Frye

Initially we had intended to have this first number
published at Lakehead University, but now that the contents have
been assembled and negotiations with the printer completed, we
sincerely feel that it is worthy of publication~ Lakehead University.

We now solicit the support of the Senate of Lakehead
University for this undertaking.

In addition, as we should like to

send out requests for manuscripts for the second number to all
faculty in the very near future, we ask that the Senate appoint an
Editorial Board to review the quality of future submissions to ensure
t hat standards remain high.

Respectfully submitted,

A. ALEXANDER.

J. D. LEACH.

******************************************************************

�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="4">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="618">
                  <text>Lakehead University Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="619">
                  <text>Photographs from Lakehead University's history: people, events,  and campus. </text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="128854">
                <text>A Brief to the Senate of Lakehead University Concerning the Lakehead University Review</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="128855">
                <text>Universities</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="128856">
                <text>Brief by Alan Alexander and James D. Leach regarding the Lakehead University Review, an academic journal that they hope to establish with the formal support of Lakehead University. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="128857">
                <text>Lakehead University</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="128858">
                <text>1967</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="128859">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="128860">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="128861">
                <text>Text</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="38">
            <name>Coverage</name>
            <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
            <elementTextContainer>
              <elementText elementTextId="128862">
                <text>Canada - Ontario - Port Arthur</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="9090" public="1" featured="0">
    <fileContainer>
      <file fileId="11271">
        <src>https://digitalcollections.lakeheadu.ca/files/original/3493a16b90348ad2ee3b4202131ac288.jpg</src>
        <authentication>8d1a3a7c1df798927dd4279d95ccb8f6</authentication>
      </file>
    </fileContainer>
    <collection collectionId="1">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1">
                  <text>Thunder Bay Finnish Canadian Historical Society Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="49">
              <name>Subject</name>
              <description>The topic of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="2">
                  <text>Finnish-Canadians</text>
                </elementText>
                <elementText elementTextId="3">
                  <text>Life in Thunder Bay</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="4">
                  <text>Photographs collected by the Thunder Bay Finnish Canadian Historical Society from a wide range of collectors, documenting Finnish immigration to and life in Thunder Bay. </text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="39">
              <name>Creator</name>
              <description>An entity primarily responsible for making the resource</description>
              <elementTextContainer>
                <elementText elementTextId="5">
                  <text>Thunder Bay Finnish Canadian Historical Society</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="45">
              <name>Publisher</name>
              <description>An entity responsible for making the resource available</description>
              <elementTextContainer>
                <elementText elementTextId="6">
                  <text>Lakehead University Library</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74692">
                <text>A building in Sunshine</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74693">
                <text>Architecture</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74694">
                <text>A building in Sunshine, 1937.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74695">
                <text>1937</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74696">
                <text>JPG</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74697">
                <text>Still image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="74698">
                <text>MG8_D13Ai52</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="38">
            <name>Coverage</name>
            <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
            <elementTextContainer>
              <elementText elementTextId="74699">
                <text>Canada - Ontario - Sunshine</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="3447" public="1" featured="0">
    <fileContainer>
      <file fileId="3890">
        <src>https://digitalcollections.lakeheadu.ca/files/original/bc4c59392b58a5145ba66f15af870bc1.jpg</src>
        <authentication>5c65242c9cb60002912064fc758f8f95</authentication>
      </file>
    </fileContainer>
    <collection collectionId="4">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="618">
                  <text>Lakehead University Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="619">
                  <text>Photographs from Lakehead University's history: people, events,  and campus. </text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22608">
                <text>A faculty member presenting an award to a student</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22609">
                <text>University Life</text>
              </elementText>
              <elementText elementTextId="22610">
                <text>People</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22611">
                <text>A faculty member presenting an award to a student.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22612">
                <text>Lakehead University Awards</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22613">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="22614">
                <text>UG6-B-III-7</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1508">
        <name>Awards</name>
      </tag>
      <tag tagId="87">
        <name>People</name>
      </tag>
      <tag tagId="76">
        <name>Portrait</name>
      </tag>
      <tag tagId="1429">
        <name>Unidentified Person</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="5675" public="1" featured="0">
    <fileContainer>
      <file fileId="6227">
        <src>https://digitalcollections.lakeheadu.ca/files/original/fa968e2971e227770aeed7fdee48ba87.jpg</src>
        <authentication>4b0d8b9ba23651b967455bf741a2523b</authentication>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="20125">
                  <text>Ken Armson fonds</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="49">
              <name>Subject</name>
              <description>The topic of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="20126">
                  <text>Forestry</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="20127">
                  <text>A collection of thousands of photographic slides depicting Ken Armson's work in the field of forestry, 1952-1995. </text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="39">
              <name>Creator</name>
              <description>An entity primarily responsible for making the resource</description>
              <elementTextContainer>
                <elementText elementTextId="20128">
                  <text>Ken Armson</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="40">
              <name>Date</name>
              <description>A point or period of time associated with an event in the lifecycle of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="20129">
                  <text>1952-1995</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="47">
              <name>Rights</name>
              <description>Information about rights held in and over the resource</description>
              <elementTextContainer>
                <elementText elementTextId="20130">
                  <text>These images have been digitized and shared on this site with permission. Most are still under copyright. </text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="44210">
                <text>A fertilized field showing grass growth</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="44211">
                <text>Forest Products Industry</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="44212">
                <text>Effect of fertilizer applied at time of planting in an old field. N.B. profuse growth of grass, not the spruce. Rolly Field, J.D.Irving.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="44213">
                <text>Ken Armson</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="44215">
                <text>1972-06</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="44216">
                <text>JPEG</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="44217">
                <text>Photograph</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="44218">
                <text>Armson-Silviculture-785</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="38">
            <name>Coverage</name>
            <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
            <elementTextContainer>
              <elementText elementTextId="44219">
                <text>Canada - New Brunswick</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="3384" public="1" featured="0">
    <fileContainer>
      <file fileId="3825">
        <src>https://digitalcollections.lakeheadu.ca/files/original/7a05f265929bff2e345753479e12b8c9.jpg</src>
        <authentication>d5d5498fabfcf6d28ed295b9b0bb5dea</authentication>
      </file>
    </fileContainer>
    <collection collectionId="4">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="618">
                  <text>Lakehead University Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="619">
                  <text>Photographs from Lakehead University's history: people, events,  and campus. </text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22153">
                <text>A formal portrait photo of a graduating student.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22154">
                <text>University Life</text>
              </elementText>
              <elementText elementTextId="22155">
                <text>People</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22156">
                <text>A formal portrait photo of a graduating student.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22157">
                <text>Lakehead University Awards</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22158">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="22159">
                <text>UG6-B-II-32</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1508">
        <name>Awards</name>
      </tag>
      <tag tagId="87">
        <name>People</name>
      </tag>
      <tag tagId="76">
        <name>Portrait</name>
      </tag>
      <tag tagId="1429">
        <name>Unidentified Person</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="2533" public="1" featured="0">
    <fileContainer>
      <file fileId="2712">
        <src>https://digitalcollections.lakeheadu.ca/files/original/3/2533/091019-001.jpg</src>
        <authentication>9cb7b2885ff83b9f447454bbbd15095a</authentication>
      </file>
    </fileContainer>
    <collection collectionId="3">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="436">
                  <text>Finlandia Club Collection </text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="571">
                  <text>Photographs from the Finlandia Club Collection. This collection consists of formal, studio portraits of Finnish immigrants and Finnish-Canadians in the early 20th century.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14051">
                <text>A gathering in front of the Finnish Labour Temple</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14052">
                <text>People</text>
              </elementText>
              <elementText elementTextId="14069">
                <text>Politics</text>
              </elementText>
              <elementText elementTextId="14070">
                <text>Architecture</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14053">
                <text>Black and white photograph of a gathering in front of the Finnish Labour Temple, Tyokansa Newspaper and the Cooperative Trading Company buildings as they appeared circa 1915. Also visible in the photograph is a man standing on the balcony in front of the banner that reads "Sign on balcony reads “Stay Away from Porcupine Ont. _____ Don't be a Strike Breaker ______ Away from Porcupine Ont. The Strike is Still On.”</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14054">
                <text>circa 1915</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14055">
                <text>Public domain</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14056">
                <text>Photograph</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14057">
                <text>Still image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="14058">
                <text>MG3,XIII,84 scan#091019-001</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="1624">
        <name>1914</name>
      </tag>
      <tag tagId="165">
        <name>banner</name>
      </tag>
      <tag tagId="89">
        <name>Children</name>
      </tag>
      <tag tagId="1905">
        <name>Cooperative Trading Company</name>
      </tag>
      <tag tagId="2">
        <name>Finnish Labour Temple</name>
      </tag>
      <tag tagId="1903">
        <name>musical instruments</name>
      </tag>
      <tag tagId="1904">
        <name>Tyokansa newspaper</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
