<?xml version="1.0" encoding="UTF-8"?>
<!--
Copyright University of Victoria.
$Date: 2021-08-03 11:36:07 -0700 (Tue., 03 Aug. 2021) $
$Id: social_media.xml 19728 2021-08-03 18:36:07Z klebere $
-->
<?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" version="5.0" xml:id="social_media">

    <teiHeader>
        <fileDesc>

            <titleStmt>
                <title>Social Media Guidelines</title>

                <respStmt>
                    <resp ref="molresp:aut">Author<date when="2013"/>
                    </resp>
                    <name ref="mol:JENS1">Janelle Jenstad</name>
                </respStmt>
                <respStmt>
                    <resp ref="molresp:aut">Author<date when="2013"/>
                    </resp>
                    <name ref="mol:MCFI1">Kim McLean-Fiander</name>
                </respStmt>
                <respStmt>
                    <resp ref="molresp:mrk"> Encoder <date when="2013-11-12"/>
                    </resp>
                    <name ref="mol:LAND2">Tye Landels</name>
                </respStmt>
            <respStmt>
<resp ref="molresp:dtm">Data Manager<date notBefore="2015"/></resp>
<name ref="mol:LAND2">Tye Landels</name>
</respStmt>
<respStmt>
               <resp ref="molresp:prg">Junior Programmer<date notBefore="2015"/></resp>
               <name ref="mol:TAKE1">Joey Takeda</name>
            </respStmt>
            <respStmt>
               <resp ref="molresp:prg">Programmer<date notBefore="2011"/></resp>
               <name ref="mol:HOLM3">Martin Holmes</name>
            </respStmt>
            <respStmt>
               <resp ref="molresp:rth">Associate Project Director<date notBefore="2015"/></resp>
               <name ref="mol:MCFI1">Kim McLean-Fiander</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:mdtDocumentationEditorial"/>
            </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:TAKE1" when="2015-06-23">Standardized <gi>respStmt</gi>s for JENS1, MCFI1, and HOLM3 and added TAKE1 as Junior Programmer.</change>
            <change who="mol:LAND2" when="2015-06-04">Added index terms.</change>
         <change who="mol:HOLM3" when="2014-09-29">Added XInclude for <gi>listPrefixDef</gi> in the header.</change>
         <change who="mol:HOLM3" when="2013-12-19">Added global publicationStmt through XInclude.</change>
            <change who="mol:LAND2" when="2013-11-12">Created document.</change>
        </revisionDesc>
    </teiHeader>
    <text>
        <front>
            <docTitle>
                <titlePart type="main"> Social Media Guidelines </titlePart>
            </docTitle>
        </front>
        <body>
            <div xml:id="social_media_culture">
                <head>MoEML’s Social Media Culture</head>
                <index indexName="documentation_manual">
                    <term>content guidelines</term>
                    <term>social media</term>
                    <term>twitter</term>
                    <term>tweets</term>
                    <term>facebook</term>
                    <term>news briefs</term>
                    <term>blog</term>
                    <term>social media culture</term>
                    <term>values on social media</term>
                    <term>social media ethos</term>
                </index>
                <p>Our aim in our social media activities is to model a collegial working
                    environment in academia. With that in mind, we have determined that MoEML’s social media (Facebook, Twitter, our onsite <title level="a">News
                    Briefs</title>, and our <title level="a">Blog</title>) should be used as follows: </p>
                <list rend="bulleted">
                    <head>To Celebrate</head>

                    <item>successes of past and present MoEML team members
                        (including editorial and advisory board members). Examples: <list rend="bulleted">
                            <item>contributor publishes an article on the MoEML site</item>
                            <item>contributor or supporter publishes something in the wider media
                                    (e.g., we wrote a brief post about MoEML editorial board member <name ref="mol:LUND1">Mary Ann Lund</name> who wrote an article on <ref target="https://www.the-tls.co.uk/articles/public/richard-crookback/"><title level="m">Richard
                                            III</title> for the <title level="j">Times
                                            Literary Supplement</title></ref>).</item>

                        </list>
                    </item>
                    <item>new resources: we like to support other DH projects by celebrating their
                        successes (e.g., <ref target="https://www.bessofhardwick.org/"><title level="m">Bess of Hardwick Letters</title> project</ref>; <ref target="http://alturl.com/8eix9"><title level="m">WEMLO – Women’s Early
                                Modern Letters Online</title></ref>).</item>
                    <item>new early modern <soCalled>finds</soCalled> in London (e.g. archaeological finds; London playtexts discovered)</item>
                    <item>MoEML project milestones (e.g., today, after 11
                        months of hard work, the MoEML team finished
                        encoding the 1633 edition of John Stow’s <title level="m">The Survey of
                            London</title>).</item>
                    <item>team members, old and new: hellos and farewells (e.g., welcome new team
                        members; say thanks, goodbye, and good luck to departing team members).</item>
                </list>
                <list rend="bulleted">
                    <head>To Inform</head>

                    <item>followers about anything relevant to early modern London,
                        especially if we can add a link.</item>
                </list>
                <list rend="bulleted">
                    <head>To Self-Market</head>

                    <item>
                        MoEML’s content and capabilities: offer ways people
                        can use MoEML for their own research or just for
                        fun and tie these sorts of posts in with our <title level="a">Encyclopedia</title> or <title level="a">Library</title> texts (e.g.,
                        Did you know that MoEML’s search function
                        automatically looks for short-s and long-ſ variants?; Did you know that
                        Cheapside is mentioned 256 times in our project?; If you want to know where
                        Crosby House was, MoEML can tell you!) </item>
                </list>
                <list rend="bulleted">
                    <head>To Provide Project Updates</head>

                    <item>E.g., MoEML has just uploaded a new article on
                        Bear Baiting in the MoEML
                        <title level="a">Encyclopedia</title></item>
                </list>

                <div xml:id="social_media_other">
                    <head>Other Types of Posts/Tweets</head>
                    <index indexName="documentation_manual">
                        <term>content guidelines</term>
                        <term>social media</term>
                        <term>twitter</term>
                        <term>tweets</term>
                        <term>facebook</term>
                        <term>news briefs</term>
                        <term>blog</term>
                        <term>social media culture</term>
                        <term>values on social media</term>
                        <term>social media ethos</term>
                        <term>other types of posts/tweets</term>
                        <term>London-related content</term>
                    </index>
                    <p>If you come across something (another tweet, an article, a news story, <foreign xml:lang="la">et cetera</foreign>)
                        that makes you think of MoEML (because it’s
                        something about London, the early modern period, digital humanities, or maps, say), then it’s probably worth tweeting/posting. If it piques your interest
                        as a MoEML RA, then it will probably be of interest
                        to other early modernists. Always try to link what you tweet/post back to
                            MoEML. E.g., if we are having discussions at our weekly team meetings about how to track work
                        flow and you then find an article in HASTAC about work flow, connect the
                        two: <quote>MoEML team members have recently been
                        discussing ways to track our work flow and we found that the following
                        HASTAC article helpful in clarifying our process.</quote> </p>
                </div>

            </div>
            <div xml:id="social_media_etiquette">
                <head>MoEML Etiquette</head>
                <index indexName="documentation_manual">
                    <term>content guidelines</term>
                    <term>social media</term>
                    <term>twitter</term>
                    <term>tweets</term>
                    <term>facebook</term>
                    <term>news briefs</term>
                    <term>blog</term>
                    <term>social media culture</term>
                    <term>values on social media</term>
                    <term>social media ethos</term>
                    <term>etiquette on social media</term>
                    <term>politeness on social media</term>
                    <term>manners on social media</term>
                </index>
                <list rend="bulleted">
                    <item>Do not complain.</item>
                    <item>Do not criticize team members, collaborators, contributors, scholars, other projects, or our project, either explicitly or implicitly.</item>
                    <item>In the reviews that we post on our blog, maintain scholarly neutrality when assessing the value and utility of other scholars’ work. A balanced review is ultimately more valuable to the creators of those resources than a glowing review that overlooks weakness, or a negative review that doesn’t acknowledge strengths.</item>
                    <item>Do not tag people in photos or posts if they have indicated that they prefer not to be tagged.</item>
                    <item>Be exquisitely polite.</item>
                </list>
            </div>
            <div xml:id="social_media_frequency_style">
                <head>Frequency and Style of Posts/Tweets</head>
                <index indexName="documentation_manual">
                    <term>content guidelines</term>
                    <term>social media</term>
                    <term>twitter</term>
                    <term>tweets</term>
                    <term>facebook</term>
                    <term>news briefs</term>
                    <term>blog</term>
                    <term>posts on social media</term>
                    <term>frequency of social media posts</term>
                    <term>frequency of tweets</term>
                    <term>style of social media posts</term>
                    <term>style of tweets</term>
                </index>
                <list rend="bulleted">
                    <item>Avoid tweeting/posting the same format (e.g., a letter or a quotation) on
                        a daily basis. Instead, offer a wide variety of posts and/or have occasional
                        bursts of tweets/posts. For self-marketing purposes, we can remind people of
                        features of the website that have recently been updated or improved.</item>
                    <item>Post/tweet in a targeted way. For example, when we’re ready for the new
                        web design launch, we may do a flurry of social media posts in the week leading up to the launch,
                        a countdown approach to the launch, teasers that tell users what’s in store,
                        and then a big splash of posting/tweeting once we know it has launched
                        successfully.</item>
                </list>
            </div>
            <div xml:id="social_media_formatting">
                <head>Formatting Tweets</head>
                <index indexName="documentation_manual">
                    <term>content guidelines</term>
                    <term>social media</term>
                    <term>twitter</term>
                    <term>tweets</term>
                    <term>style of tweets</term>
                    <term>formatting tweets</term>
                    <term>grammar</term>
                    <term>jargon</term>
                </index>
                <list rend="bulleted">
                    <item>Grammar: aim for perfection!</item>
                    <item>Social media jargon is okay (e.g., for a tweet: <quote>cd hv</quote> for <quote>could have</quote>
                        is fine).</item>
                    <item>Always put your initials in parentheses after your tweet (JJ, KMF, QM, ZV).</item>
                    <item>Tag people in Facebook photos, unless they have indicated they don’t wish
                        to be tagged. Tagged images reach a wider audience.</item>
                </list>
                <p>Bear in mind that tweets and Facebook posts provide a live news feed to the
                        <title level="a">Home Page</title> of the newly designed MoEML website and also appear on the <title level="a">News</title>
                    pages. </p>
            </div>
            <div xml:id="social_media_blog">
                <head>The MoEML Blog</head>
                <index indexName="documentation_manual">
                    <term>content guidelines</term>
                    <term>social media</term>
                    <term>blog</term>
                    <term>posts on social media</term>
                </index>
                <list rend="bulleted">
                    <item>We use the <title level="a">Blog</title> for longer news stories (longer
                        than one usually finds in Facebook or in our <title level="a">News
                            Briefs</title>) about project developments, challenges we’ve
                        encountered, our working practices, and reflections on our work.</item>
                    <item>Some of our blog posts will be reviews of other projects, digital tools, books, resources, or articles. Digital scholarship is still under-reviewed and under-reported. We can provide a service both to cognate projects and to our users by reviewing other resources, especially digital ones.</item>
                </list>
            </div>
            <div xml:id="social_media_resources">
                <head>Related Resources</head>
                <index indexName="documentation_manual">
                    <term>content guidelines</term>
                    <term>social media</term>
                    <term>twitter</term>
                    <term>tweets</term>
                    <term>facebook</term>
                    <term>news briefs</term>
                    <term>blog</term>
                    <term>further reading</term>
                    <term>more information</term>
                    <term>related resources</term>
                </index>
                <p>Kathleen Fitzpatrick, <title level="a">If You Can’t Say Anything Nice</title>.
                    <ref target="http://kfitz.info/if-you-cant-say-anything-nice/">Blog post</ref>.</p>
                <p>Ryan Cordell, <title level="a">Mea Culpa: On Conference Tweeting, Politeness, and
                    Community Building</title>. <ref target="http://www.chronicle.com/blogs/profhacker/mea-culpa-on-conference-tweeting-politeness-and-community-building/45861">Blog post</ref>.</p>
            </div>
        </body>
    </text>
</TEI>