[IPT] Fwd: Auto-discard notification

"Markus Döring (GBIF)" mdoering at gbif.org
Wed Sep 15 12:38:08 CEST 2010


[forwarded to list]

Begin forwarded message:

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.gbif.org/pipermail/ipt/attachments/20100915/47dddde5/attachment.html 


More information about the IPT mailing list