<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Yes, what John said :)</p>
<p>By the way, for some of our sites, we use the normal views
feature for this. Every /view/ page can have a .include file. eg.
<br>
</p>
<p><a class="moz-txt-link-freetext" href="https://eprints.soton.ac.uk/view/people/bf4af598-26bf-47f4-a0a4-800095a23eb5.html">https://eprints.soton.ac.uk/view/people/bf4af598-26bf-47f4-a0a4-800095a23eb5.html</a></p>
<p>has a matching</p>
<p><a class="moz-txt-link-freetext" href="https://eprints.soton.ac.uk/view/people/bf4af598-26bf-47f4-a0a4-800095a23eb5.include">https://eprints.soton.ac.uk/view/people/bf4af598-26bf-47f4-a0a4-800095a23eb5.include</a>
<br>
</p>
<p>with just the HTML of the main bit in. Handy to include
elsewhere.<br>
</p>
<br>
<div class="moz-cite-prefix">On 21/11/2017 16:49, John Salter wrote:<br>
</div>
<blockquote type="cite"
cite="mid:EMEW3|f76388197185c2b88fd7ea7761a5c099yAKGo314eprints-tech-bounces|ecs.soton.ac.uk|DB6PR0301MB2264CFF56E3CDA846DF3AB3CC4230@DB6PR0301MB2264.eurprd03.prod.outlook.com">
<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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"Times New Roman \,serif";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
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:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle27
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:1414468833;
mso-list-type:hybrid;
mso-list-template-ids:2011484254 -1489461036 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;}
@list l0:level1
{mso-level-start-at:35;
mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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]-->
<div class="WordSection1">
<p>> Both "date" and "datestamp" should be stored in the same
format in EPrints:<o:p></o:p></p>
<p class="MsoNormal"><span
style="color:#1F497D;mso-fareast-language:EN-US">Ah, Mr.
Gutteridge… close, but no cigar! :o)<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="color:#1F497D;mso-fareast-language:EN-US">The 'date'
field normally doesn't include the time component - so the
regex<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">/^(\d{4})-(\d{2})-(\d{2})
(\d{2}):(\d{2}):(\d{2})$/<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">won't
match. This should:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">/^(\d{4})-(\d{2})-(\d{2})$/<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">*<b>BUT</b>*
I'd advise against updating the RSS2 feed to do this. People
may be using it in the way it's intended.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">I'd
subclass the RSS2 feed - adding your new date sorting
method.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">-OR-
configure an author browse view, and use the RSS links
embedded in them (or pull in the .include version of the
view page).<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="color:#1F497D;mso-fareast-language:EN-US">Cheers,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="color:#1F497D;mso-fareast-language:EN-US">John<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </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 style="color:windowtext"
lang="EN-US">From:</span></b><span
style="color:windowtext" lang="EN-US">
<a class="moz-txt-link-abbreviated" href="mailto:eprints-tech-bounces@ecs.soton.ac.uk">eprints-tech-bounces@ecs.soton.ac.uk</a>
[<a class="moz-txt-link-freetext" href="mailto:eprints-tech-bounces@ecs.soton.ac.uk">mailto:eprints-tech-bounces@ecs.soton.ac.uk</a>]
<b>On Behalf Of </b>Christopher Gutteridge<br>
<b>Sent:</b> 21 November 2017 16:28<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:eprints-tech@ecs.soton.ac.uk">eprints-tech@ecs.soton.ac.uk</a>; Andrew Beeken
<a class="moz-txt-link-rfc2396E" href="mailto:anbeeken@lincoln.ac.uk"><anbeeken@lincoln.ac.uk></a><br>
<b>Subject:</b> Re: [EP-tech] Adding items to EP-XML
template<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>That's the correct behaviour for an RSS feed. I'm guessing
the logic of this is that your website has an RSS importer
already that makes it the desired route.<span
style="font-size:12.0pt"><o:p></o:p></span></p>
<p>Both "date" and "datestamp" should be stored in the same
format in EPrints, so you should just have this:<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt;text-indent:36.0pt"><span
style="mso-fareast-language:EN-US">my $datestamp =
$eprint->get_value( "date" );</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="mso-fareast-language:EN-US">
if( $datestamp =~ /^(\d{4})-(\d{2})-(\d{2})
(\d{2}):(\d{2}):(\d{2})$/ )</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="mso-fareast-language:EN-US">
{</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="mso-fareast-language:EN-US">
my $time = timelocal( $6, $5, $4, $3, $2-1, $1 );</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="mso-fareast-language:EN-US">
$item->appendChild( $session->render_data_element(</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="mso-fareast-language:EN-US">
2,</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="mso-fareast-language:EN-US">
"pubDate",</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="mso-fareast-language:EN-US">
EPrints::Time::rfc822_datetime( $time ) ) );</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="mso-fareast-language:EN-US">
}<br>
<br>
So now it's an RSS feed with the dates of the items in the
catalogue, rather than of catalogue records.</span><o:p></o:p></p>
<div>
<p class="MsoNormal">On 21/11/2017 16:05, Andrew Beeken wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Okay,
so the goalposts have shifted on this since talking in
more detail with our ICT team!</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Basically,
our repository feeds our staff directory pages in real
time using the available feeds; specifically this feed:
<a
href="http://eprints.lincoln.ac.uk/cgi/exportview/creators/userid/RSS2/userid.xml"
moz-do-not-send="true">
http://eprints.lincoln.ac.uk/cgi/exportview/creators/userid/RSS2/userid.xml</a>.
I did question why the RSS2 feed was being used and
received the answer that this particular feed formats up a
“Description” which can be pulled straight into the staff
profiles which are then ordered based on the date on the
record. So far, so good, but the issue at hand is those
dates. I initially thought the problem was the format that
the dates were coming out in and proposed that we include
the records pre-formatted citation in the standard XML
feed for them.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">However,
it now transpires that the date on the RSS2 feed is just
plain wrong; it’s using the datestamp, when the record was
created, rather than the date that the article, book etc
was published, as stored in the date field. For the
academics this means that the records on their staff
profile are not in publication order. So we come back to
the decision – use the standard XML file and add the
citation, or change the RSS2 template to use the published
date rather than the created date. ICT would prefer the
latter so that they don’t have to change the staff
directory code.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">I’ve
been taking a look at the latter an I think I’ve found the
chunk in the RSS2 script that deals with the date:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="margin-left:36.0pt;text-indent:36.0pt"><span
style="mso-fareast-language:EN-US">my $datestamp =
$eprint->get_value( "datestamp" );</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">
if( $datestamp =~ /^(\d{4})-(\d{2})-(\d{2})
(\d{2}):(\d{2}):(\d{2})$/ )</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">
{</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">
my $time = timelocal( $6, $5, $4, $3, $2-1, $1 );</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">
$item->appendChild( $session->render_data_element(</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">
2,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">
"pubDate",</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">
EPrints::Time::rfc822_datetime( $time ) ) );</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">
}</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">I
tried tweaking this to change datestamp to date, however
this completely removed the date from the feed. I’m
guessing that this is something to do with how the RegEx
decides to proceed on the if statement. So I thought I’d
see what happened if I just pushed the date straight into
the element which… didn’t work…</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">
$item->appendChild( $session->render_data_element(</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">
2,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">
"pubDate",</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">
EPrints::Time::rfc822_datetime(
$eprint->get_value( "date" ) ) ) );</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">I’m
sure there’s obvious reasons for that which I probably
can’t see (I always feel code dyslexic when I look at
EPrints source for some reason…) Personally I’d prefer to
push the citation in a more capable feed than RSS2 but I
think I’m going to be at the behest of the Staff Directory
here.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"> </span><o:p></o:p></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">From:</span></b><span
lang="EN-US"> <a
href="mailto:eprints-tech-bounces@ecs.soton.ac.uk"
moz-do-not-send="true">
eprints-tech-bounces@ecs.soton.ac.uk</a> [<a
href="mailto:eprints-tech-bounces@ecs.soton.ac.uk"
moz-do-not-send="true">mailto:eprints-tech-bounces@ecs.soton.ac.uk</a>]
<b>On Behalf Of </b>John Salter<br>
<b>Sent:</b> 21 November 2017 14:53<br>
<b>To:</b> <a
href="mailto:eprints-tech@ecs.soton.ac.uk"
moz-do-not-send="true">eprints-tech@ecs.soton.ac.uk</a><br>
<b>Subject:</b> Re: [EP-tech] Adding items to EP-XML
template</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span
style="color:#1F497D;mso-fareast-language:EN-US">></span>
<span lang="EN-US">The XML export just exports all the
fields on an object</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">Unless that field has</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> export_as_xml
=> 0,</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">- like the suggestions
field does by default…</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">What are you trying to
achieve with your export?</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">Personally, I'd
suggest subclassing that plugin, and adding a citation to
it that way - as always, TMTOWTDI!</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">It depends on how and
when you'll be calling the plugin.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">If it's for active,
user-generated requests, Adam's method may be more
suitable, as the processing is done when a record is
saved, rather than when a record is requested.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">Cheers,</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">John</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="color:#1F497D;mso-fareast-language:EN-US"> </span><o:p></o:p></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">From:</span></b><span
lang="EN-US"> <a
href="mailto:eprints-tech-bounces@ecs.soton.ac.uk"
moz-do-not-send="true">
eprints-tech-bounces@ecs.soton.ac.uk</a> [<a
href="mailto:eprints-tech-bounces@ecs.soton.ac.uk"
moz-do-not-send="true">mailto:eprints-tech-bounces@ecs.soton.ac.uk</a>]
<b>On Behalf Of </b>Adam Field<br>
<b>Sent:</b> 21 November 2017 14:34<br>
<b>To:</b> <a
href="mailto:eprints-tech@ecs.soton.ac.uk"
moz-do-not-send="true">eprints-tech@ecs.soton.ac.uk</a><br>
<b>Subject:</b> Re: [EP-tech] Adding items to EP-XML
template</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">Hi Andrew</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> The
XML export just exports all the fields on an object. I
wouldn’t modify it if I were you. The simplest way would
be to add a new field to your item.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> I’m
not sure if virtual fields come out in the XML export, but
if they do, adding a virtual field to your object may be
the easiest way to do this. Alternatively, use an
automatic field and write the citation to it. See </span><o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><span
lang="EN-US"><a
href="https://wiki.eprints.org/w/Training_Video:Virtual_Fields"
moz-do-not-send="true">https://wiki.eprints.org/w/Training_Video:Virtual_Fields</a>
and
<a
href="https://wiki.eprints.org/w/Training_Video:Automatic_Fields"
moz-do-not-send="true">https://wiki.eprints.org/w/Training_Video:Automatic_Fields</a>
</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">--</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">Adam</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><b><span
lang="EN-US">From: </span>
</b><span lang="EN-US"><<a
href="mailto:eprints-tech-bounces@ecs.soton.ac.uk"
moz-do-not-send="true">eprints-tech-bounces@ecs.soton.ac.uk</a>>
on behalf of Andrew Beeken <<a
href="mailto:anbeeken@lincoln.ac.uk"
moz-do-not-send="true">anbeeken@lincoln.ac.uk</a>><br>
<b>Reply-To: </b><<a
href="mailto:eprints-tech@ecs.soton.ac.uk"
moz-do-not-send="true">eprints-tech@ecs.soton.ac.uk</a>><br>
<b>Date: </b>Tuesday, 21 November 2017 14:24<br>
<b>To: </b>"<a
href="mailto:eprints-tech@ecs.soton.ac.uk"
moz-do-not-send="true">eprints-tech@ecs.soton.ac.uk</a>"
<<a href="mailto:eprints-tech@ecs.soton.ac.uk"
moz-do-not-send="true">eprints-tech@ecs.soton.ac.uk</a>><br>
<b>Subject: </b>[EP-tech] Adding items to EP-XML
template</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span
style="font-family:"Times New Roman",serif"
lang="EN-US"> </span><o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><span
lang="EN-US">Hi all,</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span
lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span
lang="EN-US">Just took a dive into the EPrints XML export
template (perl_lib/EPrints/Plugin/Export/XML.pm) to try
and add a node for the records citation to it and I can’t
see where you would do this? Is there somewhere separate
that defines what data it pulls through?</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span
lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span
lang="EN-US">Cheers in advance!</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span
lang="EN-US">Andrew</span><o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span
style="font-size:12.0pt;font-family:"Times New
Roman ,serif",serif" lang="EN-US"><br>
<a href="http://www.lincoln.ac.uk/opendays"
moz-do-not-send="true"><span style="border:solid
windowtext 1.0pt;padding:0cm;text-decoration:none"><img
id="_x0000_i1025"
src="cid:part15.184BFF2C.74194F75@ecs.soton.ac.uk"
alt="Image removed by sender. EF Gold" class=""
width="754" border="0" height="130"></span></a><br>
</span><span
style="font-size:10.0pt;font-family:"Times New
Roman ,serif",serif" lang="EN-US"><br>
<b>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.</b></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span
style="font-size:7.5pt;font-family:"Arial",sans-serif"
lang="EN-US"><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:
<a href="http://www.lincoln.ac.uk/legal"
moz-do-not-send="true">http://www.lincoln.ac.uk/legal</a>.</span><span
style="font-size:12.0pt;font-family:"Times New
Roman ,serif",serif" lang="EN-US">
</span><o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><span
style="font-size:12.0pt;font-family:"Times New Roman
,serif",serif" lang="EN-US">*** Options:
<a
href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech"
moz-do-not-send="true">http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech</a>
*** Archive:
<a href="http://www.eprints.org/tech.php/"
moz-do-not-send="true">http://www.eprints.org/tech.php/</a>
*** EPrints community wiki:
<a href="http://wiki.eprints.org/" moz-do-not-send="true">http://wiki.eprints.org/</a>
*** EPrints developers Forum:
<a href="http://forum.eprints.org/" moz-do-not-send="true">http://forum.eprints.org/</a>
</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times New
Roman",serif"><br>
<br>
<br>
<o:p></o:p></span></p>
<pre>*** Options: <a href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech" moz-do-not-send="true">http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech</a><o:p></o:p></pre>
<pre>*** Archive: <a href="http://www.eprints.org/tech.php/" moz-do-not-send="true">http://www.eprints.org/tech.php/</a><o:p></o:p></pre>
<pre>*** EPrints community wiki: <a href="http://wiki.eprints.org/" moz-do-not-send="true">http://wiki.eprints.org/</a><o:p></o:p></pre>
<pre>*** EPrints developers Forum: <a href="http://forum.eprints.org/" moz-do-not-send="true">http://forum.eprints.org/</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times New
Roman",serif"><br>
<br>
<o:p></o:p></span></p>
<pre>-- <o:p></o:p></pre>
<pre>Christopher Gutteridge -- <a href="http://users.ecs.soton.ac.uk/cjg" moz-do-not-send="true">http://users.ecs.soton.ac.uk/cjg</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>University of Southampton Open Data Service: <a href="http://data.southampton.ac.uk/" moz-do-not-send="true">http://data.southampton.ac.uk/</a><o:p></o:p></pre>
<pre>You should read our Web & Data Innovation blog: <a href="http://blogs.ecs.soton.ac.uk/webteam/" moz-do-not-send="true">http://blogs.ecs.soton.ac.uk/webteam/</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">*** Options: <a class="moz-txt-link-freetext" href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech">http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech</a>
*** Archive: <a class="moz-txt-link-freetext" href="http://www.eprints.org/tech.php/">http://www.eprints.org/tech.php/</a>
*** EPrints community wiki: <a class="moz-txt-link-freetext" href="http://wiki.eprints.org/">http://wiki.eprints.org/</a>
*** EPrints developers Forum: <a class="moz-txt-link-freetext" href="http://forum.eprints.org/">http://forum.eprints.org/</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Christopher Gutteridge -- <a class="moz-txt-link-freetext" href="http://users.ecs.soton.ac.uk/cjg">http://users.ecs.soton.ac.uk/cjg</a>
University of Southampton Open Data Service: <a class="moz-txt-link-freetext" href="http://data.southampton.ac.uk/">http://data.southampton.ac.uk/</a>
You should read our Web & Data Innovation blog: <a class="moz-txt-link-freetext" href="http://blogs.ecs.soton.ac.uk/webteam/">http://blogs.ecs.soton.ac.uk/webteam/</a>
</pre>
</body>
</html>