<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
I think it is more important to fix this at registry than at IPT.
If it is done at registry, it will also work for other types of
providers in one go.<br>
<br>
Hannu<br>
<br>
On 2010-09-15 14:37, Tim Robertson (GBIF) wrote:
<blockquote cite="mid:D77BC814-2FCC-4070-92FF-EB7A7407C134@gbif.org"
type="cite">I missed this one in my previous response,
<div><br>
</div>
<div>This relates to the endorsement model employed in GBIF.
Currently a Node is required to endorse an Institution, after
which any resources made available through that institution are
automatically picked up and indexed in the global portal.</div>
<div><br>
</div>
<div>This discussion actually goes beyond the scope of the IPT,
and into the Registry as Dag and Hannu hint at. For the
purposes of the IPT, I believe the proposed functionality of <b>"</b>a)
The preference would be to allow the ADMIN to provide
Registration privileges to individual MANAGERS " would satisfy
the level of control needed in an IPT installation, but that we
need to consider the cascading endorsement model further in the
registry - e.g. when a node manager endorses an Institution,
should subsequent datasets be automatically detected and
harvested, or should a Node manager be offered that fine grained
control.</div>
<div><br>
</div>
<div>If my understanding above captures this correctly, could I
please propose that the IPT ADMIN/MANAGER level control is
resolved, but this requirement be captured for the Registry
development? Your advice on this is greatly appreciated!</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Tim</div>
<div><br>
</div>
<div><br>
<div><br>
</div>
<div><br>
<div>
<div>On Sep 15, 2010, at 11:47 AM, Hannu Saarenmaa wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><span class="Apple-style-span"
style="border-collapse: separate; color: rgb(0, 0, 0);
font-family: Helvetica; font-style: normal;
font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal; orphans: 2;
text-indent: 0px; text-transform: none; white-space:
normal; widows: 2; word-spacing: 0px; font-size:
medium;">
<div bgcolor="#ffffff" text="#000000" style="font: 10pt
Tahoma,Verdana,sans-serif;">Both of these suggestions
will probably work fine. But controlling things at the
registry as Dag suggest might be more powerful. I
just want to be able to check in advance what
resources gets listed on Data Portal for our
institution. Blocking publishing at IPT may not
achieve this, if there are multiple servers, like
there is.<br>
<br>
Hannu<br>
<br>
On 2010-09-15 10:56, Dag Terje Filip Endresen wrote:
<blockquote
cite="mid:20100915075649.caf7d490@sleipner.nordgen.org"
type="cite">
<div style="text-align: left;">Hi Tim and Hannu,<br>
<br>
Would it be useful to register this setting for
the data provider to the GBRDS - so that the NODE
can set a "default" permission that will allow the
data provider to install an independent IPT
instance to publish from if they wish to. So that
the data hosting center can host datasets from
distributed data providers that themselves may
want to "upgrade" to have their own IPT later on.
The NODE admin could thus get an overview of
resources endorsed by the NODE from the GBRDS...?<br>
<br>
Cheers<br>
Dag<br>
<br>
</div>
<blockquote style="padding-left: 5px; margin-left:
5px; border-left: 2px solid rgb(0, 0, 255);
margin-right: 0px;">
<hr><b>From:</b><span
class="Apple-converted-space"> </span>Tim
Robertson (GBIF) [<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="mailto:trobertson@gbif.org">mailto:trobertson@gbif.org</a>]<br>
<b>To:</b><span class="Apple-converted-space"> </span><a
moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:ipt@lists.gbif.org">ipt@lists.gbif.org</a><br>
<b>Sent:</b><span class="Apple-converted-space"> </span>Wed,
15 Sep 2010 09:43:28 +0200<br>
<b>Subject:</b><span class="Apple-converted-space"> </span>[IPT]
Functionality request: ADMIN checking data before
GBIF registration<br>
<br>
Hi all,<br>
<br>
Hannu has raised a request for the following to be
satisfied by the IPT:<br>
"- Publishing a resource must be accepted by the
owner of the<span class="Apple-converted-space"> </span><br>
provider. It has happened that a test user
publishes something odd<span
class="Apple-converted-space"> </span><br>
which goes all the way to the data portal without
nobody controlling<span
class="Apple-converted-space"> </span><br>
it."<br>
<br>
This is a contradiction to the requests of others,
and specifically<span
class="Apple-converted-space"> </span><br>
those wishing to promote basic "data hosting
centers", who request<span
class="Apple-converted-space"> </span><br>
that a data MANAGER should be able to work
autonomously.<br>
<br>
After discussion with the developers the proposal
is to implement the<span
class="Apple-converted-space"> </span><br>
following, which we hope satisfies both
requirements:<br>
In the Administration section, an ADMIN can choose
to enable or<span class="Apple-converted-space"> </span><br>
disable the ability for MANAGERS to register
resources with GBIF. By<span
class="Apple-converted-space"> </span><br>
default MANAGERS can register a resource, but an
ADMIN can disable<span
class="Apple-converted-space"> </span><br>
this through this check box.<br>
<br>
If anyone has any concerns or comments on this
approach, please can<span
class="Apple-converted-space"> </span><br>
you raise them on this list?<br>
<br>
Many thanks,<br>
Tim<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
IPT mailing list<br>
<a moz-do-not-send="true"
href="mailto:IPT@lists.gbif.org">IPT@lists.gbif.org</a><br>
<a moz-do-not-send="true"
href="http://lists.gbif.org/mailman/listinfo/ipt"
target="_blank">http://lists.gbif.org/mailman/listinfo/ipt</a><br>
</blockquote>
<pre wrap=""><fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
IPT mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:IPT@lists.gbif.org">IPT@lists.gbif.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.gbif.org/mailman/listinfo/ipt">http://lists.gbif.org/mailman/listinfo/ipt</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Hannu Saarenmaa
Head of Unit for Biodiversity Informatics
(yli-intendentti, lajitietotiimi)
Finnish Museum of Natural History
P.O. Box 17 (P.Rautatiekatu 13)
FIN-00014 University of Helsinki
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:hannu.saarenmaa@helsinki.fi">hannu.saarenmaa@helsinki.fi</a>
Telephone +358-9-191-28688
Mobile +358-50-3102689
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.gbif.fi/">http://www.gbif.fi/</a>
</pre>
</div>
</span></blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Hannu Saarenmaa
Head of Unit for Biodiversity Informatics
(yli-intendentti, lajitietotiimi)
Finnish Museum of Natural History
P.O. Box 17 (P.Rautatiekatu 13)
FIN-00014 University of Helsinki
<a class="moz-txt-link-abbreviated" href="mailto:hannu.saarenmaa@helsinki.fi">hannu.saarenmaa@helsinki.fi</a>
Telephone +358-9-191-28688
Mobile +358-50-3102689
<a class="moz-txt-link-freetext" href="http://www.gbif.fi/">http://www.gbif.fi/</a>
</pre>
</body>
</html>