<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">[forwarded to list]<br><div><br><div>Begin forwarded message:</div><div><br></div><blockquote type="cite"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;">The attached message has been automatically discarded.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(127, 127, 127, 1.0);"><b>From: </b></span><span style="font-family:'Helvetica'; font-size:medium;">"Mihail-Constantin Carausu" <<a href="mailto:MCCarausu@snm.ku.dk">MCCarausu@snm.ku.dk</a>><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(127, 127, 127, 1.0);"><b>Date: </b></span><span style="font-family:'Helvetica'; font-size:medium;">September 15, 2010 12:03:50 GMT+02:00<br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(127, 127, 127, 1.0);"><b>To: </b></span><span style="font-family:'Helvetica'; font-size:medium;">"Tim Robertson \(GBIF\)" <<a href="mailto:trobertson@gbif.org">trobertson@gbif.org</a>>, <<a href="mailto:ipt@lists.gbif.org">ipt@lists.gbif.org</a>><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(127, 127, 127, 1.0);"><b>Subject: </b></span><span style="font-family:'Helvetica'; font-size:medium;"><b>RE: [IPT] Functionality request: ADMIN checking data before GBIFregistration</b><br></span></div><br><br>Dear Tim<br><br>I think the development team's mentioned approach is a workable solution<br>to cover both requirements at this stage.<br>However, I think Hannu (and me) had in mind a kind of "Basket of<br>approvals"-alike functionality in the Admin's (owner of the provider)<br>administration section side: When a Manager has been published a dataset<br>through the IPT, this will automatically trigger a request for approval<br>or submits an yes/no event in the Admin's administration section. The<br>Admin must finally active interfere and approve the dataset publication<br>(e.g. by checking an "Approved" check box in the basket of approvals<br>list with events/datasets in the administration section) at the absolute<br>latest stage (e.g. when GBIF just needs to start to index it, or<br>something like that). Without this final approval the dataset will still<br>be published and visible through the IPT but not visible/searchable on<br>the GBIF data portal. This approach is not necessarily in contradiction<br>with the Manager's ability to autonomously publish datasets within the<br>IPT, only it puts this ability always under control from the central<br>administration section when the dataset has to go to the GBIF data<br>portal. <br>I think both solutions/approaches have obvious advantages and<br>disadvantages while none of them provides a 100% protection against<br>publishing something odd by a (test) user.<br>I have a little question regarding the development team's proposed<br>solutions: is it not possible for the central Admin to enable the<br>publishing ability for some "trusted" managers and disable this for<br>others inside the same instance of the IPT.<br><br>Now I saw Hannu's new message just arrived, sorry for eventually<br>unsynchronized double-crossing messages, but I will send this anyhow.<br><br>Best regards,<br>Mihail<br><br>---------------------------- <br>Mihail Carausu<br>MSc.Eng., Informatics Manager<br>Danish Biodiversity Information Facility (DanBIF)<br>-------------------------------------------- <br><br><br>-----Original Message-----<br>From: <a href="mailto:ipt-bounces@lists.gbif.org">ipt-bounces@lists.gbif.org</a> [mailto:ipt-bounces@lists.gbif.org] On<br>Behalf Of Tim Robertson (GBIF)<br>Sent: 15. september 2010 09:43<br>To: <a href="mailto:ipt@lists.gbif.org">ipt@lists.gbif.org</a><br>Subject: [IPT] Functionality request: ADMIN checking data before<br>GBIFregistration<br><br>Hi all,<br><br>Hannu has raised a request for the following to be satisfied by the IPT:<br><span class="Apple-tab-span" style="white-space:pre"> </span>"- Publishing a resource must be accepted by the owner of the <br>provider. It has happened that a test user publishes something odd <br>which goes all the way to the data portal without nobody controlling <br>it."<br><br>This is a contradiction to the requests of others, and specifically <br>those wishing to promote basic "data hosting centers", who request <br>that a data MANAGER should be able to work autonomously.<br><br>After discussion with the developers the proposal is to implement the <br>following, which we hope satisfies both requirements:<br>In the Administration section, an ADMIN can choose to enable or <br>disable the ability for MANAGERS to register resources with GBIF. By <br>default MANAGERS can register a resource, but an ADMIN can disable <br>this through this check box.<br><br>If anyone has any concerns or comments on this approach, please can <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 href="mailto:IPT@lists.gbif.org">IPT@lists.gbif.org</a><br>http://lists.gbif.org/mailman/listinfo/ipt<br><br><br></blockquote></div><br></body></html>