<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body smarttemplateinserted="true">
<div id="smartTemplate4-quoteHeader">Hi Tomasz,<br>
<br>
I've been looking into adding ResourceSync functionality into
EPrints and have made a start on an EPrints 3.4 ingredient.
Unfortunately I've not had the time to make a lot of progress and
so it consists of just a couple of scripts so far, but I've
created a new GitHub repository at
<a class="moz-txt-link-freetext" href="https://github.com/eprints/resourcesync">https://github.com/eprints/resourcesync</a> where we might be able to
pool our efforts. <br>
<br>
Whilst the intention is to define this as a 3.4 ingredient,
ingredients may be easily backported into 3.3 as they consist of a
collection of configuration files, scripts and plugins that can be
added to the appropriate directories in a 3.3 repository. <br>
<br>
Many thanks,<br>
<br>
Will<br>
<br>
<hr>
<b>From:</b> Tomasz Neugebauer Via Eprints-tech
<a class="moz-txt-link-rfc2396E" href="mailto:eprints-tech@ecs.soton.ac.uk"><eprints-tech@ecs.soton.ac.uk></a>
[<a class="moz-txt-link-abbreviated" href="mailto:eprints-tech@ecs.soton.ac.uk">eprints-tech@ecs.soton.ac.uk</a>]
<b>Sent:</b> 10 January 2019 22:31
<b>To:</b> Eprints-tech <a class="moz-txt-link-rfc2396E" href="mailto:eprints-tech@ecs.soton.ac.uk"><eprints-tech@ecs.soton.ac.uk></a>
<b>Subject:</b> [EP-tech] ResourceSync and EPrints
<br>
</div>
<div class="replaced-blockquote"
cite="mid:EMEW3|de8caececf43de4c99ad25864478f887v0A6cF14eprints-tech-bounces|ecs.soton.ac.uk|73e51d7211d144f9a2ca77a11f6cfadc@ums-sgw-mbs1.concordia.ca"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Tahoma",sans-serif;}
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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Tahoma",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Tahoma",sans-serif;}
@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]-->
<div class="WordSection1">
<p class="MsoNormal">ResourceSync (<a
href="https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.openarchives.org%2Frs%2Ftoc&data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7C58fda4379e854b0a19df08d6774b6f6a%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=%2B9HkPmFP%2B%2FwjMw2lvvYFcENgL5JFjF200vxB9%2FzuvSE%3D&reserved=0"
originalsrc="http://www.openarchives.org/rs/toc"
shash="zeX3EJFuUCFipUMHXAU1aysFBdsA8q+cTm+cRLIZK9ULaEJwuCdgA0nYA63Kstaf039orckLy6hJCtQeq60QiraV0flNB+Pm4YlbjXKARx5Np/8BCFQ63wwc2ojVxa5ggbPbtvC6ScbStkxuRA+1qa+ZP029mmKbTOROVL/MZmg="
moz-do-not-send="true">http://www.openarchives.org/rs/toc</a>)
is recommended by COAR as a next generation repository
technology in their report (<a
href="https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fngr.coar-repositories.org%2Ftechnology%2Fresourcesync%2F&data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7C58fda4379e854b0a19df08d6774b6f6a%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=RsfpvwTXXsKT5AR%2B9T1gcE96cobrezSBvid6TmqPrbg%3D&reserved=0"
originalsrc="http://ngr.coar-repositories.org/technology/resourcesync/"
shash="ECeW5103EhFnqcfqP6ndKIgqOtpvUd248m23E0uNdrVqjkPLcCcIfh52imOhkN2TaWu5QWX4MwG5kvcohg1HEF2vi9ROhPQadc4VpaoLiGEToGX8EfGVEQtG9JjOD7H+qj2zLp64spY1V2y9wtCeTr4PqRlcRUZdEaO6kmy3l68="
moz-do-not-send="true">http://ngr.coar-repositories.org/technology/resourcesync/</a>)
<o:p></o:p></p>
<p class="MsoNormal">ResourceSync is a synchronization
framework, a successor of the OAI-PMH protocol that is faster,
reliable, scalable and allows real-time notification (and
recovering of missed messages). ResourceSync is already
implemented in DSpace.<o:p></o:p></p>
<p class="MsoNormal">Is anyone in the EPrints community working
on ResourceSync for EPrints?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Tomasz<o:p></o:p></p>
</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>
</div>
<br>
</body>
</html>