[Go-essp-tech] Access control for data with different QC Level

[Bryan Lawrence]

Hi Martina

We definitely need to formalise some of this, so thanks for bringing it 
up.

What I had thought we were proposing was that L2 and L3 data have 
effectively the same restrictions ...

... but your fundamental point (I think) is how do we assign the QC, and 
how does the security software get that information? Ie what is the 
workflow that needs to exist. We do need to bottom that out.

Thanks
Bryan

On Monday 19 July 2010 13:43:59 Martina Stockhause wrote:
> Hi all,
> 
> I had a little discussion with Estani about how the different and
> changing access constraints on the data depending on their QC levels
> are realized. It came out that we don't really know.
> 
> We have on the one hand the user with a special role e.g.
> "scientific, non-commercial user", who has access to data on QC L3
> like every registered user and QC L2 because of his role. On the
> other hand, the data has a quality attribute (QC Level or QC Flag),
> which defines the access restriction of the data. For data access a
> mechanism has to check user role and data attribute, before access
> is granted or denied.
> 
> How does the data get this quality attribute?
> How is the user role checked against this quality attribute?
> 
> For QC L3 we don't need that mechanism, because every registered user
> has access to all CMIP5 data, but for QC L1 and L2 exist such access
> restrictions.
> 
> Thanks a lot,
> Martina
> 
> 
> _______________________________________________
> GO-ESSP-TECH mailing list
> GO-ESSP-TECH at ucar.edu
> http://mailman.ucar.edu/mailman/listinfo/go-essp-tech

-- 
Bryan Lawrence
Director of Environmental Archival and Associated Research
(NCAS/British Atmospheric Data Centre and NCEO/NERC NEODC)
STFC, Rutherford Appleton Laboratory
Phone +44 1235 445012; Fax ... 5848; 
Web: home.badc.rl.ac.uk/lawrence