<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
        {font-family:Wingdings;
        panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
tt
        {mso-style-priority:99;
        font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
        {mso-style-name:msonormal;
        mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
span.EmailStyle20
        {mso-style-type:personal-reply;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="white" lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;mso-fareast-language:EN-US">Auto lookups would be helpful. For the moment the repository manager just wants to consolidate the two repeatable fields we have but still be able
 to qualify what they are, print, E, link etc – I think my approach is going to be to add a “type” dropdown to the Print ISSN field; we’ll work to move the existing E ISSN’s over. So back to my first question – will adding this dropdown to an existing field
 compromise the data it holds at all?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;mso-fareast-language:EN-US"><o:p>&nbsp;</o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"> eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk]
<b>On Behalf Of </b>martin.braendle@id.uzh.ch<br>
<b>Sent:</b> 20 April 2017 13:10<br>
<b>To:</b> eprints-tech@ecs.soton.ac.uk<br>
<b>Subject:</b> Re: [EP-tech] Sub types on fields<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p>&nbsp;</o:p></p>
<p><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">Hi Andrew,</span><br>
<br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">for migration, you could add a new compound field with sub_name issn and type, sub_name type be of type set, with options &quot;print&quot;, &quot;online&quot;, and &quot;link&quot;.</span><br>
<br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">Then write a script that copies over the values of your print and online issn fields to the new field and sets the type accordingly.</span><br>
<br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">However, I share the concern of John. Academics or submitters (e.g. institute secretaries) do not care whether an ISSN is ISSN (P), ISSN (E) or ISSN (L) - this is something for librarians. It's merely
 used to identify a journal if it may have an ambiguous name. The problem ist that the right information is entered at the right place, at best using autocompletion (see
</span><a href="https://wiki.eprints.org/w/Autocompletion"><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">https://wiki.eprints.org/w/Autocompletion</span></a><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">&nbsp;).</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">I also like his idea of promoting a prefered value to the default field (which is used for export).</span><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">For autocompletion of journal information, we use a sophisticated method: A journal database (JDB) that is used during the submission process in the &nbsp;publication repository (ZORA) for journal name
 lookups. It originally came from the university's requirement to track the refereed status of journals. The JDB itself is a separate EPrints repository.</span><br>
<br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">A journal record contains</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">- all ISSN variants, if available</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">- title variants, including ISO-abbreviated titles</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">- refereed status</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">- rights and embargo information, either entered manuall or nightly updated via Sherpa/RomEO API lookup</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">- link to a publisher record</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">- Source import information</span><br>
<br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">Example: </span><a href="http://www.jdb.uzh.ch/14208/"><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">http://www.jdb.uzh.ch/14208/</span></a><br>
<br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">During journal name lookup (which can be done using journal title, abbreviated title or another title variant, or ISSN), the JDB ID and the official title and publisher name are copied over to the
 ZORA record. The issn field is set from the three ISSN fields in JDB in the priority L &gt; P &gt; E. The JDB ID is further used in the upload stage to look up copyright details and Sherpa/RoMEO conditions from the JDB. If we need to aggregate records in ZORA via
 ISSN (e.g. for statistical reasons), we again look up first the JDB ID and use it for searches in ZORA.</span><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">Best regards,</span><br>
<br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">Martin</span><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">--</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">Dr. Martin Brändle</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">Zentrale Informatik</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">Universität Zürich</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">Stampfenbachstr. 73</span><br>
<span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif">CH-8006 Zürich</span><br>
<br>
<img border="0" width="16" height="16" style="width:.1666in;height:.1666in" id="Picture_x0020_1" src="cid:image001.gif@01D2B9E8.8D4D99B0" alt="Inactive hide details for John Salter ---20/04/2017 12:45:56---I was going to suggest something similar - like the way the date"><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif;color:#424282">John
 Salter ---20/04/2017 12:45:56---I was going to suggest something similar - like the way the datesdatesdates plugin works. See: https</span><br>
<br>
<span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif;color:#5F5F5F">Von: </span>
<span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">John Salter &lt;</span><a href="mailto:J.Salter@leeds.ac.uk"><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">J.Salter@leeds.ac.uk</span></a><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">&gt;</span><br>
<span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif;color:#5F5F5F">An: </span>
<span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">&quot;</span><a href="mailto:eprints-tech@ecs.soton.ac.uk"><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">eprints-tech@ecs.soton.ac.uk</span></a><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">&quot;
 &lt;</span><a href="mailto:eprints-tech@ecs.soton.ac.uk"><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">eprints-tech@ecs.soton.ac.uk</span></a><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">&gt;</span><br>
<span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif;color:#5F5F5F">Datum:
</span><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">20/04/2017 12:45</span><br>
<span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif;color:#5F5F5F">Betreff:
</span><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">Re: [EP-tech] Sub types on fields</span><br>
<span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif;color:#5F5F5F">Gesendet von:
</span><a href="mailto:eprints-tech-bounces@ecs.soton.ac.uk"><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">eprints-tech-bounces@ecs.soton.ac.uk</span></a><o:p></o:p></p>
<div>
<div class="MsoNormal">
<hr size="2" width="100%" noshade="" style="color:#8091A5" align="left">
</div>
</div>
<p class="MsoNormal"><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D">I was going to suggest something similar - like the way the datesdatesdates plugin works.</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D">See:
</span><a href="https://github.com/eprintsug/datesdatesdates/blob/master/lib/cfg.d/zz_datesdatesdates_triggers.pl#L3-L45"><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#0563C1">https://github.com/eprintsug/datesdatesdates/blob/master/lib/cfg.d/zz_datesdatesdates_triggers.pl#L3-L45</span></a><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D">It chooses the *<b>best</b>* (most published) date to promote to the default field - which works well with export plugins that reference the default 'date' field.</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&nbsp;</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D">Do your academics know whether an ISSN is print or online? Do you trust them to assert this accurately?</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&nbsp;</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D">I'd possibly apply the logic:</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D">If there's only one ISSN in your repeatable field, promote that to the default ISSN field.</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D">If there are two (or more), prefer one.</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&nbsp;</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D">*<b>But</b>* really you should be thinking about exposing all this data to other downstream systems (which would mean altering export plugins to output multiple ISSNs…)</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&nbsp;</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D">Cheers,</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D">John</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&nbsp;</span><br>
<b><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">From:</span></b><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">&nbsp;</span><a href="mailto:eprints-tech-bounces@ecs.soton.ac.uk"><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">eprints-tech-bounces@ecs.soton.ac.uk</span></a><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">
 [</span><a href="mailto:eprints-tech-bounces@ecs.soton.ac.uk"><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">mailto:eprints-tech-bounces@ecs.soton.ac.uk</span></a><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">]
<b>On Behalf Of </b>Adam Field<b><br>
Sent:</b>&nbsp;20 April 2017 10:09<b><br>
To:</b>&nbsp;</span><a href="mailto:eprints-tech@ecs.soton.ac.uk"><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">eprints-tech@ecs.soton.ac.uk</span></a><b><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif"><br>
Subject:</span></b><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">&nbsp;Re: [EP-tech] Sub types on fields</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">&nbsp;</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">You could have a Print ISSN field and an Online ISSN field, and then an ISSN field which is virtual (or automatic) and selects an appropriate ISSN from the two and returns it. &nbsp;That way the user
 would have two explicitly labelled fields, but the behavior of the issn field could be programmatically controlled.</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">&nbsp;</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">--</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">Adam</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">&nbsp;</span> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><b><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">From:
</span></b><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">&lt;</span><a href="mailto:eprints-tech-bounces@ecs.soton.ac.uk"><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#0563C1">eprints-tech-bounces@ecs.soton.ac.uk</span></a><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">&gt;
 on behalf of Andrew Beeken &lt;</span><a href="mailto:anbeeken@lincoln.ac.uk"><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#0563C1">anbeeken@lincoln.ac.uk</span></a><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">&gt;<b><br>
Reply-To: </b>&lt;</span><a href="mailto:eprints-tech@ecs.soton.ac.uk"><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#0563C1">eprints-tech@ecs.soton.ac.uk</span></a><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">&gt;<b><br>
Date: </b>Wednesday, 19 April 2017 15:21<b><br>
To: </b>&quot;</span><a href="mailto:eprints-tech@ecs.soton.ac.uk"><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#0563C1">eprints-tech@ecs.soton.ac.uk</span></a><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">&quot; &lt;</span><a href="mailto:eprints-tech@ecs.soton.ac.uk"><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#0563C1">eprints-tech@ecs.soton.ac.uk</span></a><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">&gt;<b><br>
Subject: </b>[EP-tech] Sub types on fields</span><br>
<span style="font-size:10.0pt">&nbsp;</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">Hello!</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">&nbsp;</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">So, I’m trying to sort out an issue in our EPrints where we have two ISSN fields – a Print ISSN and an Online ISSN. The problem with these is that neither of these fields are the ACTUAL ISSN which
 causes some issues on both output as well as making adding records clunky to ensure that academics put their ISSN in the correct field.</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">&nbsp;</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">What I’m looking at doing is adding a “Type” dropdown to the Print ISSN definition that can toggle the ISSN to Print or Online, change the phrase on the Print ISSN field to just identify it as
 an ISSN (it’s already repeatable) and make sure that the ISSN field is included in the export. There are a few potential “gotcha’s” with this that I’m concerned about.</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">&nbsp;</span> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span style="font-size:10.0pt;font-family:Symbol">·
</span><span style="font-size:10.0pt">&nbsp;</span><span style="font-size:10.0pt;font-family:Symbol">
</span><span style="font-size:10.0pt">&nbsp;</span><span style="font-size:10.0pt;font-family:Symbol">
</span><span style="font-size:10.0pt">&nbsp;</span><span style="font-size:10.0pt;font-family:Symbol">
</span><span style="font-size:10.0pt">&nbsp;</span><span style="font-size:10.0pt;font-family:Symbol">
</span><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">Will doing this jeapordise the existing data in any way?</span><br>
<span style="font-size:10.0pt;font-family:Symbol">· </span><span style="font-size:10.0pt">&nbsp;</span><span style="font-size:10.0pt;font-family:Symbol">
</span><span style="font-size:10.0pt">&nbsp;</span><span style="font-size:10.0pt;font-family:Symbol">
</span><span style="font-size:10.0pt">&nbsp;</span><span style="font-size:10.0pt;font-family:Symbol">
</span><span style="font-size:10.0pt">&nbsp;</span><span style="font-size:10.0pt;font-family:Symbol">
</span><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">If I set the default to “Print” will this default any pre-existing records to a Print type?</span><br>
<span style="font-size:10.0pt;font-family:Symbol">· </span><span style="font-size:10.0pt">&nbsp;</span><span style="font-size:10.0pt;font-family:Symbol">
</span><span style="font-size:10.0pt">&nbsp;</span><span style="font-size:10.0pt;font-family:Symbol">
</span><span style="font-size:10.0pt">&nbsp;</span><span style="font-size:10.0pt;font-family:Symbol">
</span><span style="font-size:10.0pt">&nbsp;</span><span style="font-size:10.0pt;font-family:Symbol">
</span><span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">At the moment we’re looking at manually moving the Online ISSN’s over to the new field, however if there is an easy way to consolidate these two fields I’m all ears!
</span><span style="font-size:10.0pt;font-family:Wingdings">J</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt">
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">&nbsp;</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">Thanks in advance!</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">&nbsp;</span><br>
<span style="font-size:10.0pt;font-family:&quot;Calibri&quot;,sans-serif">Andrew</span><br>
<b><span style="font-size:10.0pt"><br>
The University of Lincoln, located in the heart of the city of Lincoln, has established an international reputation based on high student satisfaction, excellent graduate employment and world-class research.</span></b><br>
<span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif"><br>
The information in this e-mail and any attachments may be confidential. If you have received this email in error please notify the sender immediately and remove it from your system. Do not disclose the contents to another person or take copies.<br>
<br>
Email is not secure and may contain viruses. The University of Lincoln makes every effort to ensure email is sent without viruses, but cannot guarantee this and recommends recipients take appropriate precautions.<br>
<br>
The University may monitor email traffic data and content in accordance with its policies and English law. Further information can be found at:
</span><a href="http://www.lincoln.ac.uk/legal"><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif;color:#0563C1">http://www.lincoln.ac.uk/legal</span></a><span style="font-size:7.5pt;font-family:&quot;Arial&quot;,sans-serif">.</span><br>
*** Options: <a href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech">
<span style="color:#0563C1">http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech</span></a>&nbsp;*** Archive:
<a href="http://www.eprints.org/tech.php/"><span style="color:#0563C1">http://www.eprints.org/tech.php/</span></a>&nbsp;*** EPrints community wiki:
<a href="http://wiki.eprints.org/"><span style="color:#0563C1">http://wiki.eprints.org/</span></a>&nbsp;*** EPrints developers Forum:
<a href="http://forum.eprints.org/"><span style="color:#0563C1">http://forum.eprints.org/</span></a>&nbsp;<tt><span style="font-size:10.0pt">*** Options:
</span></tt><a href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech"><span style="font-size:10.0pt;font-family:&quot;Courier New&quot;">http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech</span></a><span style="font-size:10.0pt;font-family:&quot;Courier New&quot;"><br>
<tt>*** Archive: </tt></span><a href="http://www.eprints.org/tech.php/"><span style="font-size:10.0pt;font-family:&quot;Courier New&quot;">http://www.eprints.org/tech.php/</span></a><span style="font-size:10.0pt;font-family:&quot;Courier New&quot;"><br>
<tt>*** EPrints community wiki: </tt></span><a href="http://wiki.eprints.org/"><span style="font-size:10.0pt;font-family:&quot;Courier New&quot;">http://wiki.eprints.org/</span></a><span style="font-size:10.0pt;font-family:&quot;Courier New&quot;"><br>
<tt>*** EPrints developers Forum: </tt></span><a href="http://forum.eprints.org/"><span style="font-size:10.0pt;font-family:&quot;Courier New&quot;">http://forum.eprints.org/</span></a><span style="font-size:10.0pt;font-family:&quot;Courier New&quot;"><br>
<br>
</span><o:p></o:p></p>
</div>
</body>
</html>