Project

General

Profile

Bug #1866

Synchronization should fail with any AccessPolicy other than public on Tier 1 MNs

Added by Robert Waltz over 12 years ago. Updated over 11 years ago.

Status:
Rejected
Priority:
High
Assignee:
Robert Waltz
Category:
d1_synchronization
Start date:
2011-10-20
Due date:
2013-01-05
% Done:

0%

Milestone:
CCI-1.1.1
Product Version:
*
Story Points:
Sprint:

Description

May want to review this with everyone to make certain it still makes sense.

These objects may be replicated to Tier 4 nodes that will have the ability to allow their owner's to read them.

Propose that this issue be rejected at 09/05/2012 standup meeting

History

#1 Updated by Robert Waltz over 12 years ago

  • Milestone changed from CCI-0.6.4 to CCI-1.0.0

#2 Updated by Dave Vieglais over 12 years ago

  • Position set to 12

#3 Updated by Dave Vieglais about 12 years ago

It is not clear if sync should fail in this situation.

The CN can still register the existence of the object, it just wont be visible to to the public user, which is ironic since the content was served from a public site, but not really an error condition.

#4 Updated by Robert Waltz almost 12 years ago

  • Milestone changed from CCI-1.0.0 to CCI-1.0.2

#5 Updated by Robert Waltz almost 12 years ago

  • Milestone changed from CCI-1.0.2 to CCI-1.0.3
  • Target version set to Sprint-2012.27-Block.4.2

#6 Updated by Ben Leinfelder almost 12 years ago

I'm going to vote 'no' on this too. Sure, it might feel a little odd, but maybe they intend to update the accessPolicy after a month or two on the CN, like lifting an embargo.

#7 Updated by Robert Waltz almost 12 years ago

  • Target version changed from Sprint-2012.27-Block.4.2 to Sprint-2012.29-Block.4.3

Ok, sounds like I can reject this one. But, bring it up formally one of these days in a meeting, make certain everyone is in agreement.

#8 Updated by Dave Vieglais over 11 years ago

  • Milestone changed from CCI-1.0.3 to None
  • Target version changed from Sprint-2012.29-Block.4.3 to Sprint-2012.33-Block.5.1

Deferring this for a discussion item at the CCIT meeting.

It seems reasonable to reject this, but there should be some sort of follow up mechanism that indicates if content has been non-public for longer than some "reasonable" period.

#9 Updated by Robert Waltz over 11 years ago

  • Priority changed from Normal to High

#10 Updated by Robert Waltz over 11 years ago

  • Target version changed from Sprint-2012.33-Block.5.1 to Sprint-2012.35-Block.5.2
  • Due date set to 2012-09-05

#11 Updated by Robert Waltz over 11 years ago

  • Position set to 2
  • Target version changed from Sprint-2012.35-Block.5.2 to Sprint-2012.39-Block.5.4
  • Position deleted (163)

#12 Updated by Robert Waltz over 11 years ago

  • Milestone changed from None to CCI-1.0.5

#13 Updated by Robert Waltz over 11 years ago

  • Milestone changed from CCI-1.0.5 to CCI-1.1

#14 Updated by Robert Waltz over 11 years ago

  • Due date changed from 2012-09-05 to 2012-10-27
  • translation missing: en.field_remaining_hours set to 0.0
  • Target version changed from Sprint-2012.39-Block.5.4 to Sprint-2012.41-Block.6.1

#15 Updated by Robert Waltz over 11 years ago

  • Target version changed from Sprint-2012.41-Block.6.1 to Sprint-2012.44-Block.6.2
  • Milestone changed from CCI-1.1 to CCI-1.1.1
  • Due date changed from 2012-10-27 to 2012-11-10

#16 Updated by Robert Waltz over 11 years ago

  • Due date changed from 2012-11-10 to 2013-01-05
  • Target version changed from Sprint-2012.44-Block.6.2 to Sprint-2012.50-Block.6.4

#17 Updated by Robert Waltz over 11 years ago

  • Status changed from New to Rejected

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)