On Fri, May 18, 2012 at 01:14:14PM -0700, Mark Diggory wrote:
> >
> >  If the permission is
> > a local policy then admin.s can alter it at will; but an embargo expresses
> > some other organization's policy and can't be altered without
> > negotiation.  The AIP must express (machine-readably) *why* the policy
> > is present, or we have lost important information.
> 
> 
> Additionally, while I agree its the managers responsibility to negotiate
> such external details, its impractical to try to engineer that level of
> policy negotiation and description into DSpace itself.  To be clear, when
> working on code in DSpace, the first and foremost activity should be
> engineering a content management system that is simple and works well.
>  Describing higher level policies an institution or third party may have
> for embargo of an object are probably better served as additional attached
> Bitstreams/Licenses or additional metadata in the Item record, not explicit
> ResourcePolicies used for access control.  This was not our goal in
> extending them.

So, I'm not seeing the place in the AIP from which we would recover
the fact that a given resource policy was automatically generated from
some other datum and *must not be manually altered*, at least not
without a warning.  I don't want DSpace to negotiate embargos; I just
don't want it to forget what it did about them.

-- 
Mark H. Wood, Lead System Programmer   [email protected]
Asking whether markets are efficient is like asking whether people are smart.

Attachment: pgpnsqafnlVim.pgp
Description: PGP signature

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to