Discussion #2661

Updated by Daniele Francioli over 4 years ago

<p>This discussion describes the registration process needed to insert a registry in the RoR.</p>

<h2><strong>Background</strong></h2>

<p>We decided to split the <strong>Registry descriptor</strong> exchange file&lt;/strong&gt; and the <strong>Register descriptor exchange file </strong>for the following reasons:</p>

<ul>
<li>Avoid a big huge file (difficult to be edited and loaded)</li>
<li>Avoid a big load on the RoR: the RoR will have to read a huge file for each registry - this could increase harvesting time</li>
<li>Allow multi thread execution of the harvesting: the system could potentially contains hundreds of registers to be harvested. Keeping the files separated can allow the split of work load in a multi-thread implementation of the RoR .</li>
</ul>

<h2>Description</h2>

<p>The RoR user interface will have a private area (using ECAS authentication) where you can specify the URL of the <strong>Registry descriptor</strong>.</p> exchange file&lt;/strong&gt;.&lt;/p&gt;

<p>The RoR will accept:</p>

<ul>
<li>the direct URL to the file (e.g. http://inspire.ec.europa.eu/registry/registry.en.rdf)</li>
<li>the content-negotiation approach (e.g http://inspire.ec.europa.eu/registry - HTTP headers: [Accept: application/rdf+xml])</li>
</ul>

<p>For detailed &lt;p&gt;The &lt;strong&gt;Registry exchange file&lt;/strong&gt; will contain this information:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Label&lt;/li&gt;
&lt;li&gt;Description&lt;/li&gt;
&lt;li&gt;Publisher (Label and e-mail)&lt;/li&gt;
&lt;li&gt;Update frequency&lt;/li&gt;
&lt;li&gt;Date of last update (related to the
information related contained in this file. E.g. change of the label, change of the publisher, addition of a register)&lt;/li&gt;
&lt;li&gt;List of URL pointing
to the &lt;strong&gt;Register exchange file&lt;/strong&gt;. Only the registers that need to be included in the federation shall appear in the list. As the Registry and Register descriptor read exchange file, the RoR will accept the URL to the direct file or the content-negotiation approach. To see the details related to this exchange file, have a look at this issue: <a href="https://ies-svn.jrc.ec.europa.eu/projects/inspire-registry/wiki/Registry_federation_requirements">Conformance Classes page</a>.</p> href=&quot;https://ies-svn.jrc.ec.europa.eu/issues/2615&quot;&gt;2615&lt;/a&gt;&lt;a href=&quot;https://ies-svn.jrc.ec.europa.eu/issues/2616&quot;&gt;.&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&amp;nbsp;&lt;/p&gt;

<p>The system will import all the metadata related to the registry, all the metadata for each of the register specified in the list and all the relations between the registers. The registers.&lt;/p&gt;

&lt;p&gt;The
RoR will then start the build of the search index for each of the Registers.</p>

<p>The harvesting &lt;p&gt;This process can will be started manually or can be automatically handled by the RoR based on the update frequency specified in the Registry and Register exchange files (in this case files. This mean that each item could have different update frequency.&lt;/p&gt;

&lt;p&gt;In order to avoid un-useful waste of resources,
the Registry RoR will compare the &amp;quot;last harvest date&amp;quot; and Register descriptor shall be conformant the &amp;quot;item modification date&amp;quot; (if available) before to launch the <a href="https://ies-svn.jrc.ec.europa.eu/projects/inspire-registry/wiki/Registry_federation_requirements#Automatic-Harvesting-Conformance-Class">Automatic Harvesting Conformance class</a>).</p> harvest process.&lt;/p&gt;

&lt;p&gt;The RoR will have also a &amp;quot;manual start&amp;quot; functionalities that will allow the user to manually start the process at any time.&lt;/p&gt;

Back