Grouper Developers Forum

["Gettes, Michael" <>]

USDU is supposed to remove the subject from all groups it is a member of as 
part of it’s processing.  So I think 2 is a non-issue.  Different schedules 
for different subject sources is certainly an interesting point and one I 
hadn’t thought of.  As I hope Chris would agree - you should definitely add 
this to the wiki page so it gets taken into account.

/mrg

> On Feb 6, 2019, at 12:59 PM, Black, Carey M. <> wrote:
> 
> Michael,
> 
> RE: 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__spaces.at.internet2.edu_display_Grouper_USDU-2Bdelete-2Bsubjects-2Bafter-2Bunresolvable-2Bfor-2BX-2Bdays&d=DwIFAg&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=EUBHI54mtQDlbcqo5rUTdQ&m=jd3_GrfSb_TB0hg-n5713kPCCOdcxGAYn3lNN_8eYMI&s=vpZ-XmLY7X99xlpW8gs6wkOnd1umdN9oxb7XjTfChl0&e=
> 
> 
> While I understand the idea of this request, there might be some unintended 
> consequences if other things are not considered.
> 
> 1) some subject sources might need to be treated differently than others.
>       Maybe different timelines (remove after N days), 
>       Maybe different logic based on that source. ( some sources may never 
> need cleaned., or only yearly? )
>       Some might expect to see lots of subject changes, others might expect 
> very view. ( so a single "failsafe" might be high for some and low for 
> others.)
> 
> 
> 2) if an USDU subject is still "provisioned" to some downstream system then 
> there may be other problems caused by removing the Subject from the 
> downstream system after the USDU scrubs the subject from grouper.
>       Maybe there needs to be a step that identifies the unresolvable 
> subject that triggers downstream provision/de-provision processes before 
> the subject is removed.
> 
> 
> What are your thoughts along those lines?
> 
> -- 
> Carey Matthew 
>