<?xml version="1.0" encoding="UTF-8"?>
<!--
Copyright University of Victoria.
$Date: 2020-09-15 12:18:55 -0400 (Tue, 15 Sep 2020) $
$Id: teaching.xml 17525 2020-09-15 16:18:55Z mholmes $
-->
<?xml-model href="../schemas/london_all.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?>
<?xml-model href="../schemas/london_all.sch" type="application/xml" schematypens="http://purl.oclc.org/dsdl/schematron"?>
<?xml-model href="../schemas/london_all.rng" type="application/xml" schematypens="http://purl.oclc.org/dsdl/schematron"?><TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="ethos" version="5.0">
    <teiHeader>
        <fileDesc>
            <titleStmt>
                <title>Project Ethos</title>
                <respStmt>
                    <resp ref="molresp:aut">Author<date notBefore="2021"/></resp>
                    <name ref="mol:JENS1">Janelle Jenstad</name>
                </respStmt>
                <respStmt>
                    <resp ref="molresp:aut">Author<date notBefore="2021"/></resp>
                    <name ref="mol:ELHA1">Tracey El Hajj</name>
                </respStmt>
                <respStmt>
                    <resp ref="molresp:aut">Author<date notBefore="2021"/></resp>
                    <name ref="mol:LEBE1">Kate LeBere</name>
                </respStmt>
                <respStmt>
                    <resp ref="molresp:mrk">Encoder<date notBefore="2021"/></resp>
                    <name ref="mol:LEBE1">Kate LeBere</name>
                </respStmt>
                <respStmt>
                    <resp ref="molresp:pfr">Proofreader<date notBefore="2021"/></resp>
                    <name ref="mol:ROTH4">Molly Rothwell</name>
                </respStmt>
                <respStmt>
                    <resp ref="molresp:prg">Programmer<date notBefore="2011"/></resp>
                    <name ref="mol:HOLM3">Martin Holmes</name>
                </respStmt>
                <respStmt>
                    <resp ref="molresp:pdr">Project Director<date notBefore="1999"/></resp>
                    <name ref="mol:JENS1">Janelle Jenstad</name>
                </respStmt>
            </titleStmt>

            <publicationStmt>
                <publisher><title level="m">The Map of Early Modern London</title></publisher><idno type="URL">http://mapoflondon.uvic.ca/includes.xml</idno><pubPlace>Victoria, BC, Canada</pubPlace><address>
        <addrLine>Department of English</addrLine>
        <addrLine>P.O.Box 3070 STNC CSC</addrLine>
        <addrLine>University of Victoria</addrLine>
        <addrLine>Victoria, BC</addrLine>
        <addrLine>Canada</addrLine>
        <addrLine>V8W 3W1</addrLine>
    </address><date when="2016">2016</date><distributor>University of Victoria</distributor><idno type="ISBN">978-1-55058-519-3</idno><authority>
          <name ref="mol:JENS1">Janelle Jenstad</name>
          <email>london@uvic.ca</email>
        </authority><availability>
            <p>Copyright held by <title level="m">The Map of Early Modern London</title> on behalf of the contributors.</p>
            <licence target="http://creativecommons.org/licenses/by-sa/4.0/">
              <p>This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. </p>
            </licence>
            <p>Further details of licences are available from our
              <ref target="mol:licence">Licences</ref> page. For more
              information, contact the project director, <name ref="mol:JENS1">Janelle Jenstad</name>, for
              specific information on the availability and licensing of content
              found in files on this site.</p>
        </availability>
            </publicationStmt>

            <sourceDesc>
                <p>Born digital.</p>
            </sourceDesc>
        </fileDesc>
        <profileDesc>
            <textClass>
                <catRef scheme="mdt:molDocumentTypes" target="mdt:mdtBornDigital"/>
                <catRef scheme="mdt:molDocumentTypes" target="mdt:mdtParatext"/>
            </textClass>
        </profileDesc>

        <encodingDesc>

            <listPrefixDef>
        <prefixDef ident="mol" matchPattern="(.+)(#.+)?" replacementPattern="../../$1.htm$2">
          <p>Most MoEML documents, or significant fragments with <att>xml:id</att> attributes, can
            be addressed using the <code>mol:</code> prefix and accessed through the web application
            with their id + <code>.xml</code>.</p>
        </prefixDef>
        <prefixDef ident="molagas" matchPattern="(.+)" replacementPattern="https://mapoflondon.uvic.ca/agas.htm?locIds=$1">
          <p>The molagas prefix points to the shape representation of a location on 
            MoEML’s OpenLayers3-based
          rendering of the Agas Map.</p>
        </prefixDef>
        <prefixDef ident="moleebo" matchPattern="([0-9]+)\|([0-9]+)" replacementPattern="http://eebo.chadwyck.com/fetchimage?vid=$1&amp;page=$2&amp;width=1200">
          <p>Links to page-images in the Chadwyck-Healey <title level="m">Early English Books Online</title> (EEBO)
            repository. Note that this is a subscription service, and may not be accessible to those
            accessing it from locations outside member institutions.</p>
        </prefixDef>
        <prefixDef ident="molebba" matchPattern="(.+)" replacementPattern="http://ebba.english.ucsb.edu/ballad/$1">
          <p>Links to page-images in the <title level="m">English Broadside Ballad Archive</title> (EBBA).</p>
        </prefixDef>
        <prefixDef ident="mdt" matchPattern="(.+)" replacementPattern="includes.xml#$1">
          <p>The mdt (MoEML Document Type) prefix used on <gi>catRef</gi>/<att>target</att> points
            to a central taxonomy in the includes file.</p>
        </prefixDef>
        <prefixDef ident="mdtlist" matchPattern="(.+)" replacementPattern="$1.xml">
          <p>The mdtlist (MoEML Document Type listing) prefix used in linking attributes points to a listings page constructed from a category in the central MDT taxonomy in the includes file. There are two variants, one with the plain <att>xml:id</att> of the category, meaning all documents in the specified category, and one with the suffix <q>_subcategories</q>, meaning all subcategories of the category.</p>
        </prefixDef>
        <prefixDef ident="molgls" matchPattern="(.+)" replacementPattern="GLOSS1.xml#$1">
          <p>The molgls (MoEML gloss) prefix used on <gi>term</gi>/<att>corresp</att> points
            to a a glossary entry in the GLOSS1.xml file.</p>
        </prefixDef>
        <prefixDef ident="molvariant" matchPattern="(.*)\|(.+)" replacementPattern="spelling_variants.xml#$2">
          <p>This molvariant prefix is used on <gi>ref</gi>/<att>target</att> attributes during automated 
          generation of gazetteer index files. It points to an element in the generated variant spellings
          listing file which lists all documents which contain a particular spelling variant for a 
          location.</p>
        </prefixDef>
        <prefixDef ident="molajax" matchPattern="(.+)" replacementPattern="../../ajax/$1.xml">
          <p>This molajax prefix is used on <gi>ref</gi>/<att>target</att> attributes during the static build 
          process, to specify links which point to MoEML resources which should not be loaded into the source 
          page during standalone processing; instead, these should be turned into links to the XML source 
          documents, and at HTML page load time, these should be turned into AJAX calls. This is to handle 
          the scenario in which a page such as an A-Z index of the whole site would end up containing 
          virtually the whole site inside itself.</p>
        </prefixDef>
        <prefixDef ident="molstow" matchPattern="(.+)|(.+)" replacementPattern="https://hcmc.uvic.ca/stow/$1/SL$1_$2.jpg">
          <p>The molstow prefix is used on <att>facs</att> attributes to link to the HCMC verison of the Stow facsimiles.
          Usually the first group is the year (1633) and then last is the image number (0001).</p>
        </prefixDef>
        
        <prefixDef ident="molshows" matchPattern="([^\|]+)\|([^\|]+)\|([^\|]+)" replacementPattern="https://hcmc.uvic.ca/~london/images/shows/$1/$2/$3.jpg">
          <p>The molshows prefix is used on <att>facs</att> attributes to link to the copies of page-images
            from mayoral shows stored in the london account on the HCMC server.
            The first group is the year (1633), the second is the source repository, and then last is the image
            file name.</p>
        </prefixDef>
        
        <prefixDef ident="sb" matchPattern="(.+)" replacementPattern="https://johnstowsbooks.library.utoronto.ca/admin/items/show/$1">
          <p>The sb prefix is used on <gi>ref</gi>/<att>target</att> attributes to link to 
          Stow’s Books URLs at UToronto.</p>
        </prefixDef>
      </listPrefixDef>

            <p>Our editorial and encoding practices are documented in detail in the <ref target="mol:praxis">Praxis</ref> section of our website.</p>

        </encodingDesc>

        <revisionDesc status="published">
            <change who="mol:JENS1" when="2021-06-30">Sorted out a list hierarchy problem and
                published document.</change>
            <change who="mol:JENS1" when="2021-06-25">Revised and proofed.</change>
            <change who="mol:LEBE1" when="2021-06-21">Created document.</change>
        </revisionDesc>
    </teiHeader>
    <text>
        <front>
            <docTitle>
                <titlePart type="main">Project Ethos</titlePart>
            </docTitle>
        </front>
        <body>
            <div xml:id="ethos_definition">
                <head>Definition</head>
                <p>Ethos: <quote>The characteristic spirit of a people, community, culture, or era
                        as manifested in its attitudes and aspirations; the prevailing character of
                        an institution or system</quote> (<ref target="mol:OEDI1" type="bibl"><title level="m">OED</title></ref>
                    <term>ethos</term>, n. 2.a).</p>
            </div>
            <div xml:id="ethos_intro">
                <head>Introduction</head>


                <p>This document describes MoEML’s attitudes, values, and aspirations as a project.
                    Building on the collective experience of past and present teams and many open
                    discussions about how we can work collaboratively and respectfully in community,
                    this document outlines the principles that guide us and how they manifest in our
                    daily practice. If our <ref target="mol:praxis">Praxis documentation</ref>
                    captures how we encode and process our research into a website, and our <ref target="mol:mission_statement">Mission Statement</ref> describes how we
                    envision that website contributing long-term to scholarship and public
                    humanities, the <ref target="mol:ethos">Project Ethos</ref> document is the
                    blueprint for how we work together on a daily, weekly, and yearly basis to make
                    the MoEML website possible.</p>

                <p>MoEML strives to create and maintain an environment where everyone is treated
                    with respect and dignity. Documenting our principles and procedures in this
                    full-length document is one way we create that environment.</p>
                <p>MoEML’s ethos applies to all people who are involved in the project, including
                    university faculty, staff, affiliates, and students, at the home university of
                    MoEML or elsewhere.</p>
                <p>Members of the MoEML Team at the University of Victoria are additionally bound by
                    UVic’s equity and diversity policies in all our dealings with UVic students,
                    staff, and faculty. You will find a non-inclusive list of UVic policies <ref target="https://www.uvic.ca/equity/about/policies/index.php">here</ref> and
                    direct links to <ref target="#ethos_resources">select UVic policies at the end
                        of this document</ref>.</p>

                <p>This document begins with an <ref target="#ethos_territory">acknowledgement that
                        MoEML is hosted on unceded, colonized land</ref>. The document then sets out
                        <ref target="#ethos_definitions">definitions</ref>, <ref target="#ethos_principles">general team principles</ref>, and statements on
                        <ref target="#ethos_diversity">diversity, equity, and inclusion</ref>, <ref target="#ethos_credit">giving credit</ref>, <ref target="#ethos_conflict">conflict resolution</ref>, and <ref target="#ethos_hiring">hiring</ref>. We
                    conclude with <ref target="#ethos_resources">links to resources and UVic
                        policies</ref>.</p>

                <p>We choose to share <ref target="mol:ethos">Project Ethos</ref> publicly, in
                    keeping with our project principle of openness. We invite other projects to
                    adopt and adapt it. In keeping with our <ref target="#ethos_credit">own
                        principle of giving credit</ref>, we’d be glad to be given credit if you do
                    adopt or adapt this document.</p>
            </div>
            <div xml:id="ethos_territory">
                <head>Territorial Acknowledgement</head>
                <p>We acknowledge, with respect, that MoEML is built and hosted on the traditional
                    and unceded territories of the Songhees, Esquimalt, and WSÁNEĆ peoples whose
                    historical relationships with the land continue to this day. We acknowledge that
                    MoEML focuses on the city that funded and launched the first English colonial
                    activities that have been and continue to be so destructive to Indigenous
                    peoples around the world. We acknowledge, with respect, that many contributors
                    to MoEML live on colonized lands, some unceded and some governed by treaties
                    that have been honoured more in the breach than the observance. We commit to
                    speaking this truth as a part of the necessary reconciliation work that we must
                    do, both in the MoEML project and in our lives.</p>
            </div>
            <div xml:id="ethos_definitions">
                <head>Definitions</head>
                <list rend="numbered">
                    <item>Project Director: The overall academic lead of the project, with expertise
                        in the <soCalled>big picture</soCalled> and with a long <soCalled>project
                            memory</soCalled>. The Director has ultimate responsibility for
                        financial, employment, equity, and scholarly matters; in that role, she
                        seeks advice from various offices on campus, listens to other team members,
                        and makes the tough calls when necessary. The project also has Assistant
                        Directors who take the lead on subdomains of the project.</item>
                    <item>Principal Investigator: The lead applicant on a grant application. Often
                        but not always the Project Director.</item>
                    <item>Project Manager: The person in charge of planning the daily, weekly, and
                        monthly work of the project and monitoring the finances, in conjunction with the
                        Project Director. Often helps with grant applications. Fills in gaps in the
                        project expertise as needed.</item>
                    <item>Team Members: The members of the <name ref="mol:TEAM1" type="org">MoEML
                            team</name>, including the Project Director(s) and Assistant Directors,
                        Project Manager(s), Developers(s), Research Associates, Research Assistants,
                        and any other person fulfilling a role on the MoEML project.</item>
                    <item>Contributors: The people and/or projects that contribute scholarly content
                        to MoEML who are not a part of the <name ref="mol:TEAM1" type="org">MoEML
                            team</name>.</item>
                    <item>Project: The collaborative enterprise of MoEML as a whole.</item>
                    <item>Accommodation: The services and/or tools that can help reduce barriers and
                        provide different ways of working.</item>
                    <item>HCMC: <ref target="https://www.uvic.ca/humanities/hcmc/index.php">Humanities Computing and Media Centre</ref> at the University of
                        Victoria.</item>
                    <item>HUMS: <ref target="https://www.uvic.ca/humanities/">Faculty of
                            Humanities</ref> at the University of Victoria.</item>
                    <item>UVic: <ref target="https://www.uvic.ca/">University of Victoria</ref> in
                        Victoria, British Columbia, Canada.</item>
                </list>
            </div>
            <div xml:id="ethos_principles">
                <head>General Team Principles</head>
                <list rend="numbered">
                    <item>As an academic project, funded by <ref target="https://www.sshrc-crsh.gc.ca/home-accueil-eng.aspx">SSHRC</ref>,
                        and staffed by students at various stages of their studies, MoEML is
                        committed to the ongoing learning and development of its members.</item>
                    <item>MoEML acknowledges that every member of the team has and will develop
                        specific areas of expertise and interest.</item>
                    <item>MoEML acknowledges that a large digital project requires many domains of
                        expertise. All this expertise is equally necessary to the ultimate
                        achievement of the project outcomes.</item>
                    <item>MoEML acknowledges that we are all learners. We take the time to teach
                        each other the things we have learned in the course of our work.</item>
                    <item>MoEML is committed to giving credit where credit is due.</item>
                    <item>Our team structure is flat.</item>
                    <item>All team members are free to assume particular tasks and redefine their
                        roles. All team members take responsibility for identifying gaps between how
                        things are and how they could be. We then work together to realize the
                        possibilities we envision. (See <ref target="mol:JENS11" type="bibl">Jenstad
                            and Takeda 2018</ref>.)</item>
                </list>
            </div>
            <div xml:id="ethos_diversity">
                <head>On Diversity, Equity, and Inclusion</head>
                <list rend="numbered">
                    <item>We are all learners. <list rend="numbered">
                            <item>MoEML provides training for newly hired members.</item>
                            <item>Team members have the right to receive all necessary training to
                                complete their work.</item>
                            <item>MoEML provides new team members with detailed documentation that
                                has been carefully developed, and constantly updated, with the
                                various expertise levels in mind.</item>
                            <item>MoEML assigns senior members to work with junior team members to
                                help with training and to answer questions as they arise. If the
                                assigned senior member is not available, the new member may speak to
                                any other member of the team, so long as they are available and
                                qualified to address their questions.</item>

                            <item>MoEML publishes documentation and training material.</item>
                            <item>MoEML allows for people to move to another part of the project,
                                either to mobilize their skills more effectively or to learn
                                something new, so long as all the people involved in the
                                change agree.</item>
                            <item>MoEML provides a team environment where individuals are available
                                to train each other as needed. For example, if we have an expert
                                technical writer on the team, and another individual is interested
                                in such skill, the technical writer will provide training and
                                support to the person interested in learning.</item>
                            <item>MoEML encourages team members to post questions to the general
                                channel of the team’s virtual working space (Microsoft Teams for
                                example), especially if the rest of the team would benefit from the
                                conversation.</item>
                        </list></item>

                    <item>Teamwork is key to the project’s success. <list rend="numbered">
                            <item>MoEML embraces the diversity of skills and backgrounds represented
                                by the team members.</item>
                            <item>MoEML treats various skills as equally important and valuable to
                                the project (including but not limited to computational, digital,
                                scholarly, editorial, bibliographical, historical, geographical,
                                textual, financial, and managerial skills).</item>
                            <item>The Project Director and Project Manager ensure that participants
                                have appropriate time and opportunity to report on their work, raise
                                questions, and contribute to discussion of issues in team meetings.
                                The Project Manager calls for agenda items in advance of meetings
                                and pre-circulates the agenda. The Project Director chairs team
                                meetings.</item>
                            <item>The Project Director makes sure that the person most qualified to
                                address an issue is the one to lead the discussion. For example, the
                                expert on documentation will address documentation questions/issues,
                                unless they ask for support in the matter.</item>
                        </list>
                    </item>
                    <item>Student success—academic and professional—is key to the project’s success.
                            <list rend="numbered">
                            <item>MoEML accommodates students’ interests in particular skills
                                through flexibility in role distribution.</item>
                            <item>MoEML ensures that learning opportunities are offered equally to
                                all team members.</item>
                            <item>MoEML prioritizes the education of student team members. In cases
                                of a conflict between the requirements of their education (classes,
                                urgent deadlines, meetings with professors or TAs) and the
                                requirements of their work, MoEML encourages students to prioritize
                                their schooling.</item>
                        </list></item>
                    <item>Research assistants have a right to be treated equitably and fairly. <list rend="numbered">
                            <item>The Project Director offers equitable rates of pay, matching or
                                exceeding the <ref target="https://www.uvic.ca/hr/assets/docs/cupe-4163-component-1--2-ta-appendix---academic--scientific-assistants---2019-2021.pdf">CUPE 4163</ref> negotiated rates.</item>
                            <item>MoEML assigns roles based on people’s skills, expertise, and
                                desire to obtain new skills. No person is given a task or role
                                because of gender, race, sexual orientation, or status in the
                                university hierarchy.</item>
                        </list></item>
                    <item>Team members treat each other with respect. <list rend="numbered">
                            <item>The Project Director monitors the team to make sure no one person
                                    <soCalled>manages</soCalled> or <soCalled>directs</soCalled>
                                other team members, unless specifically required to do so by their
                                job description.</item>

                            <item>MoEML asks team members to address each other respectfully.</item>
                            <item>MoEML asks team members to give respectful and constructive
                                feedback. Feedback and commentary are not opportunities to shame
                                people or abuse one’s position in the university’s hierarchy.</item>
                            <item>MoEML asks team members to call people by their preferred names
                                and pronouns.</item>
                            <item>The Project Director checks in privately with BIPOC team members,
                                international student team members, and junior team members
                                periodically.</item>
                        </list>
                    </item>
                    <item>MoEML is attentive to the mental health and well being of team members.
                            <list rend="numbered">
                            <item>MoEML encourages team members to take care of their health and
                                family first, their studies second, and their job third.</item>
                            <item>MoEML recognizes that mental health issues are an invisible
                                challenge and that it can be difficult to ask for help. Team members
                                may speak to the Project Director in confidence and do not have to
                                give details of their situation unless they wish to.</item>
                            <item>Team members have the right to have their mental health needs be
                                respected.</item>
                            <item>MoEML works with the team to reset priorities and reassign tasks
                                when a person needs to take time off work.</item>
                        </list>
                    </item>
                    <item>Team members have the right to ask for accommodations to support them in
                        their work. <list rend="numbered">
                            <item>MoEML does not have designated funding for accommodations but
                                supports accommodations for student team members when they can be
                                funded by or obtained from the University of Victoria.</item>
                            <item>The Project Director works with student team members and the <ref target="https://www.uvic.ca/services/cal/">Centre for Accessible
                                    Learning</ref> (CAL) to determine what accommodations are
                                necessary.</item>
                            <item>The Project Director turns first to CAL to acquire the necessary
                                support and technologies.</item>
                            <item>When CAL cannot provide what is needed, the Project Director will
                                work with the student team member, the Humanities Computing and
                                Media Centre (HCMC), the Faculty of Humanities (HUMS), and the
                                University of Victoria Libraries to address the accommodation
                                requirements.</item>
                            <item>Where necessary and feasible and when funding opportunities exist,
                                the Project Director will submit applications to relevant funding
                                bodies or to university offices for funding to purchase the adaptive
                                tools, technologies, and infrastructure needed to accommodate a team
                                member.</item>
                        </list></item>
                    <item>MoEML honours different ways of working. <list rend="numbered">
                            <item>Team members can choose to work independently, in pairs, or in
                                groups, within the requirements of the project’s current objectives
                                and tasks.</item>
                            <item>The Project Director and Project Manager work with team members at
                                UVic to determine the best place of work. Some students will prefer
                                to work on a bookable workstation in HCMC, while others will prefer
                                to work on their own laptops or desktops in another location.</item>
                            <item>Lack of technology is not a barrier to working for MoEML. Team
                                members who need to work outside of the HCMC or remotely but do not
                                have a laptop or desktop should speak with the Project Director to
                                make the appropriate arrangements to borrow a laptop and/or install
                                software, as long as the project has the capacity and funding to
                                provide hardware and software.</item>
                        </list>
                    </item>
                    <item>Team members have the right to privacy and confidentiality. <list rend="numbered">
                            <item>Every team member is asked to respect and keep confidential any
                                other team member’s confidential disclosures.</item>
                            <item>MoEML does not require team members to divulge any aspect of their
                                lived experience. If they do choose to divulge any part of it, other
                                MoEML team members will acknowledge and respect their lived
                                experience.</item>
                            <item>MoEML does not require team members to disclose details of mental
                                health, physical health, or other personal situations. If they do,
                                the Project Director will treat their disclosure as confidential,
                                except as indicated in the next item.</item>
                            <item>The Project Director has a duty of care to student team members
                                and must report to the appropriate campus authorities threats to
                                self, threats to others, abuse of minors, and abuse of power.</item>
                        </list>
                    </item>
                    <item>MoEML is part of a larger institutional ecosystem. <list rend="numbered">
                            <item>MoEML is bound by the equity and diversity policies of the
                                University of Victoria in all its dealings with UVic students,
                                staff, and faculty, including but not limited to the policies listed
                                    <ref target="https://www.uvic.ca/equity/about/policies/index.php">here</ref>.</item>
                            <item>The Project Director seeks advice from the Graduate Advisor, the
                                Associate Dean of Research, the Department of English Equity Committee,
                                and/or <ref target="https://www.uvic.ca/equity/index.php">Equity
                                    &amp; Human Rights (EQHR)</ref> when necessary.</item>
                            <item>All UVic team members have access to the services of the <ref target="https://www.uvic.ca/universitysecretary/senate/appeals/ombudsperson/index.php">Office of the Ombudsperson</ref>.</item>
                        </list></item>
                </list>


            </div>
            <div xml:id="ethos_credit">
                <head>On Giving Credit</head>
                <list rend="numbered">
                    <item>All team members and contributors—regardless of their disciplinary
                        backgrounds and career stages—have the right to have their scholarship and
                        labour acknowledged equally and truthfully. <list rend="numbered">
                            <item>We give credit where credit is due, in keeping with the <ref target="https://hcommons.org/deposits/item/hc:31187/">Collaborators’ Bill of Rights</ref> and <ref target="https://humtech.ucla.edu/news/a-student-collaborators-bill-of-rights/">Student Collaborators’ Bill of Rights</ref>.</item>
                            <item>We do not consider any labour to be mechanical; all labour is
                                critical and worthy of acknowledgement.</item>
                            <item>MoEML does not distinguish between paid and unpaid labour.</item>
                            <item>Every contribution to the project, whether that contribution
                                consists of markup, one or multiple files, an edition, an anthology,
                                and/or development work on the platform, is credited and
                                acknowledged.</item>
                            <item>MoEML team members and contributors take intellectual
                                responsibility for their work, both before and after peer
                                review.</item>
                            <item>MoEML team members and contributors cite their sources accurately,
                                tag quoted material appropriately (with quotation marks in untagged
                                drafts and with the <gi>quote</gi> element in marked-up files), and
                                indicate when they are paraphrasing from source material.</item>
                            <item>MoEML gives credit to peer reviewers when they choose to be named
                                and acknowledged.</item>
                            <item>When MoEML team members deliver conference papers or write
                                publications together, we list the authors in alphabetical order,
                                unless there is reason to list them otherwise. Such reasons include
                                an author writing the bulk of the manuscript and others contributing
                                smaller sections. Note that first authorship is earned only when
                                said author did most of the work (writing, revisions, and
                                editing).</item>
                            <item>Academic seniority is not a reason for first authorship.</item>
                            <item>If the contributions are equal and alphabetical order would
                                normally make the senior scholar first author, the senior scholar
                                may choose to be second or subsequent author for the benefit of
                                their students or early career colleagues.</item>
                        </list>
                    </item>
                    <item>Clear and complete metadata is key to the project’s commitment to
                            <quote>giving credit where credit is due</quote>. <list rend="numbered">
                            <item>MoEML gives granular credit at the level of the XML file, on the
                                    <ref target="mol:team">Team page</ref>, and in the team member
                                or contributor’s entry in the Personography (PERS1.xml), as is
                                appropriate for the nature of the work.</item>
                            <item>MoEML ensures that all team members and contributors have an entry
                                in the project’s <ref target="mol:PERS1">Personography
                                    (PERS1.xml)</ref> with a unique identifier.</item>
                            <item>MoEML ensures that all team members and contributors have an
                                opportunity to write a bio-bibliographical note in their
                                Personography entry that they can update as they work on the
                                project. The bio-bibliographical note may contain a standard
                                academic narrative of qualifications and publications; links to a
                                personal website(s), academic profile(s), and/or publications; and a
                                narrative statement about the contributor’s contributions to the
                                project. Each team member and contributor has the right to write
                                this note and determine what to highlight about their contributions
                                to the project. Team members and early career contributors are
                                particularly encouraged to keep their bio-bibliographical notes
                                up-to-date.</item>
                            <item>Team members add their roles and responsibilities to an XML file
                                by adding a <gi>respStmt</gi> element and corresponding children
                                    (<gi>resp</gi> and <gi>name</gi>) in the file’s
                                    <gi>titleStmt</gi> section. For detailed documentation on adding
                                a <gi>respStmt</gi>, see <ref target="mol:encode_teiHeader#encode_teiHeader_respStmt"><title level="m">Responsibility Statements</title></ref>.</item>
                            <item>MoEML uses the <ref target="https://www.loc.gov/marc/relators/">Library of Congress MARC Code List for Relators</ref> to
                                describe roles when there is congruence between the MoEML role and a
                                role defined in the MARC list (found at <ref target="https://www.loc.gov/marc/relators/relaterm.html">https://www.loc.gov/marc/relators/relaterm.html</ref>). Given
                                the ubiquity of MarcRelators in metadata, the project uses these
                                codes to align with the standards of the fields and disciplines to
                                which the project contributes. Where there is no MARC relator to
                                describe a MoEML role, the project will create a custom value
                                following the pattern set by the Library of Congress. In cases where
                                we cannot find a code that corresponds to a certain role for the
                                project, MoEML will propose a new potential MARC relator to the
                                Library of Congress.</item>
                            <item>Team members who undertake more than one role on a file give
                                themselves multiple <gi>respStmt</gi> elements, one for each
                                role.</item>
                            <item>Team members add <gi>change</gi> elements to the
                                    <gi>revisionDesc</gi> element every time they make substantial
                                changes to a file. The contents of the <gi>change</gi> elements
                                remain in the file’s metadata as a record of the amount and nature
                                of the work that a team member has done in a particular file. The
                                    <gi>change</gi> element supplements the information that can be
                                captured in the <gi>respStmt</gi>.</item>
                            <item>MoEML asks all contributors to follow the principles and practices
                                set out in this <quote>On Giving Credit</quote> section of <ref target="mol:ethos">Project Ethos</ref>, especially those
                                practices pertaining to students.</item>
                            <item>MoEML encourages contributors not working in TEI or Oxygen to
                                create a metadata section at the top of their files, listing
                                research assistant(s) author(s), intellectual contributors,
                                reviewer(s), date(s) of creation, and revision history for everyone
                                who contributed in any way to the creation of the content. This
                                information will be translated by team members into
                                    <gi>respStmt</gi> elements and <gi>change</gi> elements when the
                                file is encoded.</item>
                            <item>MoEML provides appropriate training to new team members on the
                                project’s crediting policy and practices. Minor changes to practice
                                are conveyed to team members by a shared communication channel and
                                immediately added to project documentation. Substantial changes to
                                practice are conveyed via training sessions for team members as well
                                as through project documentation.</item>
                        </list></item>
                    <item>MoEML is committed to giving credit to developers and designers, whose
                        work makes the entire project possible. <list rend="numbered">
                            <item>Developers add their roles and unique identifiers to the top of
                                xsl files</item>
                            <item>Developers and designers are encouraged to document their work in
                                their bio-bibliographical note.</item>
                            <item>MoEML acknowledges developers and designers in publications if
                                their ideas inform the argument made in the publication, even if the
                                developer or designer has not been involved in the process of
                                writing up the ideas for the publication. MoEML’s position is that
                                the publication would not be possible without the developer and/or
                                designer.</item>
                            <item>MoEML lists developers and designers on the <ref target="mol:team">Team</ref> page.</item>



                        </list>
                    </item>
                </list>


            </div>
            <div xml:id="ethos_conflict">
                <head>On Conflict Resolution</head>
                <list rend="numbered">
                    <item>Respectful, supportive, and constructive communication amongst team
                        members is key to the project’s success. <list rend="numbered">
                            <item>MoEML treats disagreements as opportunities for the project to
                                grow and develop.</item>
                            <item>MoEML treats misunderstandings as opportunities for the team
                                members to write clearer documentation.</item>
                            <item>MoEML appreciates diversity in opinion and methodology as drivers
                                of innovation.</item>
                            <item>MoEML encourages team members to share conflicting opinions in a
                                respectful way. All involved parties should also respond in an open
                                and respectful way.</item>
                        </list>
                    </item>
                    <item>Team members have the right to be treated equitably in cases of conflict.
                            <list rend="numbered">
                            <item> While MoEML encourages parties involved in conflict to address
                                the conflict directly with each other, MoEML also acknowledges that
                                direct address is sometimes not possible. If power dynamics affect
                                one or more of the people involved and make them vulnerable, then
                                they are encouraged to seek support from the Project Director and/or
                                (if the parties are UVic staff, faculty, or students) the
                                appropriate people and offices on campus.</item>
                            <item>MoEML holds a vote when there are multiple, irreconcilable
                                positions on a certain issue. The results of the vote are binding,
                                regardless of the academic status of the team members proposing the opposing
                                views.</item>
                        </list>
                    </item>
                    <item>Team members have the right to follow UVic’s established policies and
                        procedures on conflict resolution. MoEML follows UVic’s policies and procedures on conflict
                                resolution. Procedures are divided into 7 categories:
                                Student-Faculty, Student-Staff, Student-Student, Faculty-Staff,
                                Faculty-Faculty, Staff-Staff, and Project Management-Research
                                Assistant. For all student conflicts, the student can choose to
                                visit the <ref target="https://uvicombudsperson.ca/">Office of the
                                    Ombudsperson</ref> at UVic. <list rend="numbered">
                                    <item>Student-Faculty/Staff <list rend="bulleted">
                                            <item>A student seeking support is encouraged to speak
                                                first to the Project Director, who will work with
                                                them on the appropriate process. If the Project
                                                Director needs to speak to the faculty/staff member
                                                in question, they will maintain the student’s
                                                anonymity and respect confidentiality, unless
                                                otherwise requested by the student. The Project
                                                Director may suggest that a graduate-student team
                                                member consult the following people, in the order
                                                listed, if/when necessary, as proposed in section
                                                3.1 of the <ref target="https://www.uvic.ca/graduatestudies/assets/docs/pdfs/policies/graduate-supervision-policy.pdf">UVic Graduate Supervision Policy</ref>:
                                                  <quote>their supervisor(s), supervisory committee
                                                  member(s), Graduate Advisor, Head of the academic
                                                  unit, Associate Dean of Graduate Studies, and the
                                                  Dean of Graduate Studies, until the issue is
                                                  resolved</quote>.</item>

                                            <item>A faculty/staff member seeking support is
                                                encouraged to speak to the Project Director, who
                                                will work with them on the appropriate process, or
                                                liaise with the student regarding the issue flagged.
                                                Note that MoEML is a project that focuses on
                                                training students and supporting them in their
                                                academic and professional careers. The Project
                                                Director and the faculty/staff member are encouraged
                                                to use such opportunities as a teaching moment for
                                                all involved, with the student’s best interests in
                                                mind.</item>
                                        </list>
                                    </item>
                                    <item>Student-Student <list rend="bulleted">
                                            <item>If Student A has an issue with Student B, Student
                                                A is encouraged to approach Student B first, doing
                                                so respectfully and collegially. If approaching
                                                Student B is not an option or the conflict persists,
                                                Student A is encouraged to speak with the Project
                                                Manager. (Historically, MoEML’s project managers are
                                                recent graduates and understand the UVic student
                                                experience.) The Project Manager will confidentially
                                                and respectfully address the issue with Student B,
                                                in a way that does not expose Student A or
                                                exacerbate the issue at hand. If Student A is not
                                                comfortable speaking to the Project Manager, then
                                                they can speak to the Project Director who will
                                                address the issue confidentially and respectfully.
                                                If the Project Director sees it as a teaching moment
                                                for the team, then they may choose to use this
                                                opportunity for everyone’s benefit, though
                                                confidentially and with no reference to Student A or
                                                Student B, nor to the specifics of the case to
                                                maintain the anonymity of both parties.</item>
                                        </list>
                                    </item>
                                    <item>Faculty-Staff <list rend="bulleted">
                                            <item>Faculty and staff members are encouraged to
                                                approach their colleagues first, respectfully and
                                                collegially, in an honest attempt to resolve
                                                conflicts and misunderstandings. If the conflict
                                                remains, then the person reaching out is encouraged
                                                to speak to the Project Director, who will address
                                                the issue respectfully and confidentially.</item>
                                        </list>
                                    </item>
                                    <item>Faculty-Faculty <list rend="bulleted">
                                            <item>Faculty members are encouraged to approach their
                                                colleagues first, respectfully and collegially, in
                                                the case of a conflict, in an honest attempt to
                                                resolve any issues and misunderstandings. If the
                                                conflict remains, then the person reaching out is
                                                encouraged to speak to the Project Director, who
                                                will address the issue respectfully and
                                                confidentially. Faculty may also choose to speak
                                                with the Faculty of Humanities Associate Dean of
                                                Research for the resolution of their conflicts and
                                                misunderstandings, especially if other approaches do
                                                not address the issues in question.</item>
                                        </list>
                                    </item>
                                    <item>Staff-Staff <list rend="bulleted">
                                            <item>Staff members are encouraged to approach their
                                                colleagues first, respectfully and collegially, in an
                                                honest attempt to resolve any conflicts and
                                                misunderstandings. If the conflict remains, then the
                                                person reaching out is encouraged to speak to the
                                                Manager of HCMC, who will address the issue
                                                respectfully and confidentially. If the conflict
                                                persists, staff may want to speak to the Project
                                                Director to seek resolution. Staff may also choose
                                                to speak with Human Resources for the resolution of
                                                their conflicts and misunderstandings, especially if
                                                other approaches do not address the issues in
                                                question.</item>
                                        </list>
                                    </item>
                                    <item>Project Management (Project Director/Project Manager/Lead
                                        Programmer)-Research Assistant <list rend="bulleted">
                                            <item>Research assistants are encouraged to speak first
                                                to the Project Director, who will work with them to
                                                determine the appropriate process. If the Project
                                                Director needs to speak to the project management
                                                member in question, they will maintain the student’s
                                                anonymity and respect confidentiality. If the
                                                Project Director is involved in the conflict, then a
                                                graduate research assistant is encouraged to consult
                                                the following, in the order in which listed, if/when
                                                necessary, as proposed in section 3.1 of the <ref target="https://www.uvic.ca/graduatestudies/assets/docs/pdfs/policies/graduate-supervision-policy.pdf">UVic Graduate Supervision Policy</ref>:
                                                  <quote>starting with their supervisor(s),
                                                  supervisory committee member(s), Graduate Advisor,
                                                  Head of the academic unit, Associate Dean of
                                                  Graduate Studies, and the Dean of Graduate
                                                  Studies, until the issue is
                                                resolved</quote>.</item>
                                            <item>When a project management member seeks to resolve
                                                a conflict, they are invited to speak to the
                                                research assistant in question, respectfully and
                                                collegially. Note that MoEML is a project that
                                                focuses on training students and supporting them in
                                                their academic and professional careers. That said,
                                                the project management members are encouraged to use
                                                such opportunities as a teaching moment for all
                                                involved, with the student’s best interests in
                                                mind.</item>
                                        </list>
                                    </item>
                                </list>
                            </item>
                        </list>
            </div>
            <div xml:id="ethos_hiring">
                <head>On Hiring</head>
                <list rend="bulleted">
                    <item>Candidates have the right to be given equal opportunity and not be
                        discriminated against based on their social or cultural backgrounds, race,
                        gender, or sexual orientation.</item>
                    <item>Candidates have a right to clearly know the requirements and expectations
                        for positions in job postings. <list rend="numbered">
                            <item>MoEML outlines all requirements and expectations in job
                                postings.</item>
                            <item>The selection process begins with the consideration of candidates’
                                eligibility based on the outlined requirements.</item>
                            <item>Shortlisted candidates have a right to be interviewed so they are
                                given an opportunity to discuss qualities and qualifications that were not conveyed in the
                                application, as well as how they would fit within the various MoEML
                                teams and groups. <list rend="bulleted">
                                    <item>The Project Director conducts interviews with the selected
                                        candidates. Where feasible, the grant co-applicant will also
                                        meet and interview the candidates, before the hiring is
                                        finalized.</item>
                                    <item>All interviewees for a position are asked the same set of
                                        questions.</item>
                                    <item>The interviewers time for the interviewee to
                                        ask questions about the project, the team, the working
                                        environment, and other issues. The interviewers will
                                        address these questions sincerely and accurately.</item>
                                    <item>The Project Director ensures that candidates are notified
                                        of the outcome of the interview in a timely fashion. Offers
                                        and rejection letters will be distributed once a decision is
                                        made.</item>
                                    <item>Given the pedagogical nature of the project, the Project
                                        Director is open to discussing the interview questions and
                                        answers with applicants—after the decision is made—as an
                                        opportunity for them to learn from the process as they move
                                        forward in their careers.</item>
                                </list>
                            </item>
                            <item>All team members, but particularly returning team members starting
                                a new contract, have the right to work collaboratively with the
                                Project Director to co-create their contract. <list rend="bulleted">
                                    <item>The Project Director works with team members to
                                        write a contract that works for MoEML and the team
                                        member. To that end, the objectives and outcomes
                                        sections of the contract are tailored to the team
                                        member, so that they can identify their areas of interest
                                        and the skills they are interested in learning.
                                        Once the Project Director and the team member are both
                                        satisfied with the contract, the Project Director and 
                                        team member sign the contract, a copy of which is retained
                                        by the team member as a reference for their work.</item>
                                    <item>The contract is renegotiable at the end of the agreed-upon
                                        term. (See <ref target="mol:moeml_contract"><title level="a">Training and Work Practices
                                        Contract</title></ref>.)</item>
                                </list>
                            </item>


                        </list>
                    </item>
                </list>


            </div>
            <div xml:id="ethos_resources">
                <head>Resources and UVic Policies</head>
                <list rend="numbered">
                    <item><ref target="https://www.uvic.ca/universitysecretary/assets/docs/policies/GV0200_1105_.pdf">UVIC Human Rights, Equity, and Fairness</ref></item>
                    <item><ref target="https://www.uvic.ca/universitysecretary/assets/docs/policies/GV0205_1150_.pdf">Discrimination and Harassment Policy</ref></item>
                    <item><ref target="https://www.uvic.ca/universitysecretary/assets/docs/policies/GV0245.pdf">Sexualized Violence Prevention and Response Policy</ref></item>
                    <item><ref target="https://www.uvic.ca/universitysecretary/assets/docs/policies/AC1205_2340_.pdf">Academic Accommodation and Access for Students with
                        Disabilities</ref></item>
                    <item><ref target="https://www.uvic.ca/universitysecretary/assets/docs/policies/SS9120_6105_.pdf">Policy of Prevention of Violence in the Workplace</ref></item>
                    <item>Relevant <ref target="https://www.sshrc-crsh.gc.ca/home-accueil-eng.aspx">SSHRC policies</ref></item>
                    <item><ref target="https://www.uvic.ca/universitysecretary/assets/docs/policies/GV0235.pdf">UVIC’s Protection of Privacy Policy</ref></item>
                    <item><ref target="https://www.uvic.ca/vpfo/departments/privacy/">Privacy and
                            Access to Information Office</ref></item>
                    <item><ref target="https://www.uvic.ca/students/health-wellness/student-wellness-centre/index.php">UVic Wellness Centre</ref></item>
                    <item><ref target="https://www.uvic.ca/equity/">UVic Equity and Human
                            Rights</ref></item>
                    <item><ref target="https://www.uvic.ca/hr/assets/docs/cupe-4163-component-1--2-ta-appendix---academic--scientific-assistants---2019-2021.pdf">CUPE Pay rates</ref></item>
                    <item><ref target="https://www.bclaws.gov.bc.ca/civix/document/id/complete/statreg/96165_00">BC’s Freedom of Information and Protection of Privacy Act</ref></item>
                    <item><ref target="https://www.loc.gov/marc/relators/relaterm.html">LOC MARC
                            Code List for Relators</ref></item>
                    <item><ref target="https://hcommons.org/deposits/item/hc:31187/">Collaborators’
                            Bill of Rights</ref></item>
                    <item><ref target="https://humtech.ucla.edu/news/a-student-collaborators-bill-of-rights/">Student Collaborators’ Bill of Rights</ref></item>
                    <item><ref target="https://hcommons.org/deposits/objects/hc:26742/datastreams/CONTENT/content">Postdoctoral Bill of Rights</ref></item>
                    <item><ref target="https://www.uvic.ca/graduatestudies/assets/docs/pdfs/policies/graduate-supervision-policy.pdf">Faculty of Graduate Studies Graduate Supervision Policy</ref> (1.5:
                            <quote>To identify appropriately (including through co-authorship) the
                            contributions of all person who may an intellectual or other substantive
                            contribution to publications, conference presentations, exhibitions or
                            other disseminations of scholarly works in a fashion appropriate for the
                            field of study</quote>. Also see 3: Student and Faculty
                        Resources)</item>
                    <item><ref target="https://www.uvic.ca/universitysecretary/assets/docs/policies/AC1200_1320_.pdf">Conflicts of Interest in StudentFaculty Relationships</ref></item>
                </list>
            </div>
        </body>
    </text>
</TEI>