Michael Feldstein wrote:
> Hello all,
>
> I'm interested in finding out how well Bodington's access privileges
> capabilities would map to uPortal's Person Attributes Group Store
> (PAGS). Has anybody looked at this?
Not until I read your email.
From a very quick look PAGS seems to be giving users attributes (eg
year of study, course, etc) and then giving users a workflow to define a
group from these attributes (eg I'd like a group of all students who
started before 1999 and are studying chemistry). This means that as long
as the attributes exist users should be able to create a group that
matches their needs. One hurdle I see in PAGS is that all parties
involved need to have a very clear idea about what all the attributes
are used for and what the various values mean (eg at oxford we have a
status field but to get all college staff members you need people with a
status of staff or senem (senior member)), if an institution can
simplify the attributes then using PAGS seems a flexible way to define
groups.
I'm also not sure what would be the implications for data protection and
it may be that some attributes should have access controls on them to
prevent abuse.
At the moment Bodington depends on the ability to be able to find all
members of a group and from the documentation it seems that this isn't
currently allowed.
Bodington allows users access to some user attributes but doesn't
provide a query language to dynamically create groups from these
attributes. Bodington does however allow user defined groups.
Permissions in Bodington are then applied to the selected groups.
--
-- Matthew Buckett, VLE Developer
-- Learning Technologies Group, Oxford University Computing Services
-- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/
|
