Contribution State Machine - Revision history

Vreck at 08:03, 25 September 2018

2018-09-25T08:03:39Z

← Older revision		Revision as of 09:03, 25 September 2018
Line 1:		Line 1:
	__TOC__		__TOC__

	~~STILL UNDER CONSTRUCTION: need to describe transitions, flags, and access rights...~~		The contribution state machine illustrates the states that constitute the life cycle of a contribution.

	The ~~picture below~~ illustrates the states that constitute the life cycle of a contribution.

	== States ==		== States ==

Vreck: Following a Question from an ISG ZSM official, I added some details on the "Noted" status, explaining that revising a "Noted" contribution is part of the normal process.

2018-09-25T07:15:50Z

Following a Question from an ISG ZSM official, I added some details on the "Noted" status, explaining that revising a "Noted" contribution is part of the normal process.

← Older revision		Revision as of 08:15, 25 September 2018
Line 1:		Line 1:
	__TOC__		__TOC__

	STILL UNDER CONSTRUCTION: need to describe transitions, flags, and access rights...		STILL UNDER CONSTRUCTION: need to describe transitions, flags, and access rights...

Line 15:		Line 16:
	; ACCEPTED : The group has discussed a contribution that was "For Decision" and decided to accept the proposal AS IT IS, there is no need to improve/update it any further, it is ready for potential implementation. It is hence not possible to revise an accepted contribution.		; ACCEPTED : The group has discussed a contribution that was "For Decision" and decided to accept the proposal AS IT IS, there is no need to improve/update it any further, it is ready for potential implementation. It is hence not possible to revise an accepted contribution.
	: <u>note</u>: ACCEPTED and REJECTED states are only applicable to contributions "''For Decision''"		: <u>note</u>: ACCEPTED and REJECTED states are only applicable to contributions "''For Decision''"
	; NOTED : '''IF''' a contribution is '''''for information''''' or '''''for discussion''''' (no decision requested from the committee) ''NOTED'' is the end-of-life status set by the committee once the contribution has been handled, i.e. either discussed, presented, or sometimes just mentioned.		; NOTED : '''IF''' a contribution is '''''for information''''' or '''''for discussion''''' (no decision requested from the committee) ''NOTED'' is the default end-of-life status that is set by the committee once the contribution has been handled, i.e. either discussed, presented, or sometimes just mentioned. However, a contribution which has been ''NOTED'' may still be ''Revised''.
	: '''IF''' a contribution is '''''for decision''''' (a decision is requested from committee), ''NOTED'' implies that the committee has discussed the proposal without either '''accepting''' nor '''rejecting''' it. This usually means that the committee expects the contribution to be improved (i.e. ''~~revised~~ '') prior to take a decision on it. ~~It is hence possible to revise~~ a contribution ~~that is~~ ''~~Noted~~''.		: '''IF''' a contribution is '''''for decision''''' (a decision is requested from committee), ''NOTED'' implies that the committee has discussed the proposal without either '''accepting''' nor '''rejecting''' it. This usually means that the committee expects the contribution to be improved (i.e. ''Revised'' ) prior to take a decision on it. Hence a contribution which has been ''NOTED'' may still be ''Revised''.
	; REVISED : A contribution is revised as soon as its revision has been reserved. The concept is that a revision improves and/or corrects an existing proposal. Hence once a contribution is in REVISED status it is no longer possible to take a decision on it (''Accept'', or ''Reject'') since the decision will be taken on its revision. Nor is it possible to mark it as NOTED (case of a revision reserved before discussion), because logically, if a contribution is revised before being presented to the group, the group will then discuss the latest revision, not the earlier ones.		; REVISED : A contribution is revised as soon as its revision has been reserved. The concept is that a revision improves and/or corrects an existing proposal. Hence once a contribution is in REVISED status it is no longer possible to take a decision on it (''Accept'', or ''Reject'') since the decision will be taken on its revision. Nor is it possible to mark it as NOTED (case of a revision reserved before discussion), because logically, if a contribution is revised before being presented to the group, the group will then discuss the latest revision, not the earlier ones.
	: <u>note</u>: problem can arise when a user reserves a revision without uploading it --> the committee neither take a decision on the original ''revised'' contribution, nor on its non-available revision...		: <u>note</u>: problem can arise when a user reserves a revision without uploading it --> the committee neither take a decision on the original ''revised'' contribution, nor on its non-available revision...

Vreck: /* States */

2010-09-15T14:30:45Z

States

Vreck: /* Flags */

2010-08-05T14:52:10Z

Flags

← Older revision		Revision as of 15:52, 5 August 2010
Line 24:		Line 24:
	; Handled : Means that the contribution has been discussed/presented/dealt with. This flag is automatically set for the ''rejected'', ''accepted'', and ''Noted'' states. Once set it cannot be cleared hence a contribution that moves from ''Noted'' to ''Revised'' has the ''handled'' flag set which indicates that the contribution was '''revised AFTER the discussion'''. The flag cannot be set when in ''available'' state hence a contribution that moves from ''available'' to ''revised'' does not have the ''Handled'' flag set, which indicates hat the contribution was '''revised BEFORE the discussion'''.		; Handled : Means that the contribution has been discussed/presented/dealt with. This flag is automatically set for the ''rejected'', ''accepted'', and ''Noted'' states. Once set it cannot be cleared hence a contribution that moves from ''Noted'' to ''Revised'' has the ''handled'' flag set which indicates that the contribution was '''revised AFTER the discussion'''. The flag cannot be set when in ''available'' state hence a contribution that moves from ''available'' to ''revised'' does not have the ''Handled'' flag set, which indicates hat the contribution was '''revised BEFORE the discussion'''.
	:: '''IF''' (status = Revised) '''and''' (''Handled'' flag is not set) '''THEN''' the chairman can set the ''Handled'' flag manually, to indicate that the ''Revised'' contribution can be considered as handled.		:: '''IF''' (status = Revised) '''and''' (''Handled'' flag is not set) '''THEN''' the chairman can set the ''Handled'' flag manually, to indicate that the ''Revised'' contribution can be considered as handled.
	; Rev RQ: means that a revision of the contribution is expected. This flag can only be set on the ~~‘noted’~~ state. This gives additional information indicating that the contribution was discussed and that no further decision or conclusion ~~will~~ be reached ~~until~~ the contribution is revised.		; Rev RQ: means that a revision of the contribution is expected. This flag can only be set on the ''noted'' state. This gives additional information indicating that the contribution was discussed and that further decision or conclusion may be reached when the contribution will be revised.

	; Rev PreApp : means that the group pre-approves the revision to come. This is to cope with the case where a contribution was discussed and almost accepted assuming the changes ~~mentionned~~ during the discussion are implemented in the revision. The group trusts the source and does not ask to see the revision. This flag can only be set together with the « Rev RQ » flag.		; Rev PreApp : means that the group pre-approves the revision to come. This is to cope with the case where a contribution was discussed and almost accepted assuming the changes mentioned during the discussion are implemented in the revision. The group trusts the source and does not ask to see the revision. This flag can only be set together with the "Rev RQ" flag.

	== Access Rights ==		== Access Rights ==

Vreck: /* Flags */

2010-08-05T14:49:55Z

Flags

← Older revision		Revision as of 15:49, 5 August 2010
Line 23:		Line 23:

	; Handled : Means that the contribution has been discussed/presented/dealt with. This flag is automatically set for the ''rejected'', ''accepted'', and ''Noted'' states. Once set it cannot be cleared hence a contribution that moves from ''Noted'' to ''Revised'' has the ''handled'' flag set which indicates that the contribution was '''revised AFTER the discussion'''. The flag cannot be set when in ''available'' state hence a contribution that moves from ''available'' to ''revised'' does not have the ''Handled'' flag set, which indicates hat the contribution was '''revised BEFORE the discussion'''.		; Handled : Means that the contribution has been discussed/presented/dealt with. This flag is automatically set for the ''rejected'', ''accepted'', and ''Noted'' states. Once set it cannot be cleared hence a contribution that moves from ''Noted'' to ''Revised'' has the ''handled'' flag set which indicates that the contribution was '''revised AFTER the discussion'''. The flag cannot be set when in ''available'' state hence a contribution that moves from ''available'' to ''revised'' does not have the ''Handled'' flag set, which indicates hat the contribution was '''revised BEFORE the discussion'''.
	:: '''IF''' (status = Revised) '''and''' (''Handled'' flag is not set) '''THEN''' the chairman can set the ''Handled'' flag manually.		:: '''IF''' (status = Revised) '''and''' (''Handled'' flag is not set) '''THEN''' the chairman can set the ''Handled'' flag manually, to indicate that the ''Revised'' contribution can be considered as handled.
	; Rev RQ: means that a revision of the contribution is expected. This flag can only be set on the ‘noted’ state. This gives additional information indicating that the contribution was discussed and that no further decision or conclusion will be reached until the contribution is revised.		; Rev RQ: means that a revision of the contribution is expected. This flag can only be set on the ‘noted’ state. This gives additional information indicating that the contribution was discussed and that no further decision or conclusion will be reached until the contribution is revised.

Vreck: /* Flags */

2010-08-05T14:48:06Z

Flags

← Older revision		Revision as of 15:48, 5 August 2010
Line 22:		Line 22:
	; Postponed: this flag is set manually by the chairman to indicate that the contribution was delayed (presenter not there, lack of time, file not available,etc…). It can be set and cleared indefinitely by the chairman as long as the contribution is in ''Reserved'' or ''Available'' state. When moving away from these states the flag is cleared and can no longer be set.		; Postponed: this flag is set manually by the chairman to indicate that the contribution was delayed (presenter not there, lack of time, file not available,etc…). It can be set and cleared indefinitely by the chairman as long as the contribution is in ''Reserved'' or ''Available'' state. When moving away from these states the flag is cleared and can no longer be set.

	; Handled : Means that the contribution has been discussed/presented/dealt with. This flag is automatically set for the ''rejected'', ''accepted'', and ''Noted'' states. Once set it cannot be cleared hence a contribution that moves from ''Noted'' to ''Revised'' has the ''handled'' flag set which indicates that the contribution was '''revised AFTER the discussion'''. The flag cannot be set when in ''available'' state hence a contribution that moves from ''available'' to ''revised'' does not have the ''Handled'' flag set, which indicates hat the contribution was '''revised BEFORE the discussion'''. '''IF''' status = Revised and ''Handled'' flag not set THEN the chairman can set the ''Handled'' flag manually.		; Handled : Means that the contribution has been discussed/presented/dealt with. This flag is automatically set for the ''rejected'', ''accepted'', and ''Noted'' states. Once set it cannot be cleared hence a contribution that moves from ''Noted'' to ''Revised'' has the ''handled'' flag set which indicates that the contribution was '''revised AFTER the discussion'''. The flag cannot be set when in ''available'' state hence a contribution that moves from ''available'' to ''revised'' does not have the ''Handled'' flag set, which indicates hat the contribution was '''revised BEFORE the discussion'''.
			:: '''IF''' (status = Revised) '''and''' (''Handled'' flag is not set) '''THEN''' the chairman can set the ''Handled'' flag manually.
	; Rev RQ: means that a revision of the contribution is expected. This flag can only be set on the ‘noted’ state. This gives additional information indicating that the contribution was discussed and that no further decision or conclusion will be reached until the contribution is revised.		; Rev RQ: means that a revision of the contribution is expected. This flag can only be set on the ‘noted’ state. This gives additional information indicating that the contribution was discussed and that no further decision or conclusion will be reached until the contribution is revised.

Vreck at 14:45, 5 August 2010

2010-08-05T14:45:05Z

← Older revision		Revision as of 15:45, 5 August 2010
Line 3:		Line 3:

	The picture below illustrates the states that constitute the life cycle of a contribution.		The picture below illustrates the states that constitute the life cycle of a contribution.
	~~[[Image:Contribution State Machine.PNG\|500px\|\|left\|alt=Contribution State Machine\|Contribution State Machine]]~~
	== States ==		== States ==
	; RESERVED : The contribution details have been entered in the system, the file has not yet been uploaded.		; RESERVED : The contribution details have been entered in the system, the file has not yet been uploaded. Next step is to "''Upload/Make Available''" the contribution file. It is also possible to withdraw (cancel) the contribution at this stage.
	Next step is to "''Upload/Make Available''" the contribution file. It is also possible to withdraw (cancel) the contribution at this stage.

	Is is not possible to REVISE a contribution from the RESERVED state since the proposal has not yet been made available.		Is is not possible to REVISE a contribution from the RESERVED state since the proposal has not yet been made available.
	; AVAILABLE : The contribution file is physically present on the server		; AVAILABLE : The contribution file is physically present on the server
			; WITHDRAWN : The submitter of a contribution can decides to withdraw (cancel) his contribution as long as the contribution has not been handled by the committee. As soon as a contribution has been discussed (''Noted'') or if a decision has been taken on it (''Accepted'', or ''Rejected'') it is no longer possible to withdraw it.
			[[Image:Contribution State Machine.PNG\|500px\|\|left\|alt=Contribution State Machine\|Contribution State Machine]]
	; REJECTED : The group has rejected the contribution AS A WHOLE, and does not want to discuss it any further. It is hence not possible to revise a rejected contribution.		; REJECTED : The group has rejected the contribution AS A WHOLE, and does not want to discuss it any further. It is hence not possible to revise a rejected contribution.
	: <u>note</u>: ACCEPTED and REJECTED states are only applicable to contributions "''For Decision''"		: <u>note</u>: ACCEPTED and REJECTED states are only applicable to contributions "''For Decision''"
Line 18:		Line 19:
	; REVISED : A contribution is revised as soon as a revision has been reserved. The concept is that a revision improves and/or corrects an existing proposal. Hence once a contribution is REVISED it is no longer possible to take a decision on it (''Accept'', or ''Reject'') since the decision will be taken on its revision.		; REVISED : A contribution is revised as soon as a revision has been reserved. The concept is that a revision improves and/or corrects an existing proposal. Hence once a contribution is REVISED it is no longer possible to take a decision on it (''Accept'', or ''Reject'') since the decision will be taken on its revision.
	: <u>note</u>: problem can arise when a user reserves a revision without uploading it --> the committee neither take a decision on the original ''revised'' contribution, nor on its non-available revision...		: <u>note</u>: problem can arise when a user reserves a revision without uploading it --> the committee neither take a decision on the original ''revised'' contribution, nor on its non-available revision...

	; WITHDRAWN : The submitter of a contribution can decides to withdraw (cancel) his contribution as long as the contribution has not been handled by the committee. As soon as a contribution has been discussed (''Noted'') or if a decision has been taken on it (''Accepted'', or ''Rejected'') it is no longer possible to withdraw it.


	== Flags ==		== Flags ==
	; Postponed: this flag is set manually by the chairman to indicate that the contribution was delayed (presenter not there, lack of time, file not available,etc…). It can be set and cleared indefinitely by the chairman as long as the contribution is in ''Reserved'' or ''Available'' state. When moving away from these states the flag is cleared and can no longer be set.		; Postponed: this flag is set manually by the chairman to indicate that the contribution was delayed (presenter not there, lack of time, file not available,etc…). It can be set and cleared indefinitely by the chairman as long as the contribution is in ''Reserved'' or ''Available'' state. When moving away from these states the flag is cleared and can no longer be set.

Vreck: /* Flags */

2010-08-05T14:39:30Z

Flags

← Older revision		Revision as of 15:39, 5 August 2010
Line 23:		Line 23:

	== Flags ==		== Flags ==
			; Postponed: this flag is set manually by the chairman to indicate that the contribution was delayed (presenter not there, lack of time, file not available,etc…). It can be set and cleared indefinitely by the chairman as long as the contribution is in ''Reserved'' or ''Available'' state. When moving away from these states the flag is cleared and can no longer be set.

			; Handled : Means that the contribution has been discussed/presented/dealt with. This flag is automatically set for the ''rejected'', ''accepted'', and ''Noted'' states. Once set it cannot be cleared hence a contribution that moves from ''Noted'' to ''Revised'' has the ''handled'' flag set which indicates that the contribution was '''revised AFTER the discussion'''. The flag cannot be set when in ''available'' state hence a contribution that moves from ''available'' to ''revised'' does not have the ''Handled'' flag set, which indicates hat the contribution was '''revised BEFORE the discussion'''. '''IF''' status = Revised and ''Handled'' flag not set THEN the chairman can set the ''Handled'' flag manually.
			; Rev RQ: means that a revision of the contribution is expected. This flag can only be set on the ‘noted’ state. This gives additional information indicating that the contribution was discussed and that no further decision or conclusion will be reached until the contribution is revised.

			; Rev PreApp : means that the group pre-approves the revision to come. This is to cope with the case where a contribution was discussed and almost accepted assuming the changes mentionned during the discussion are implemented in the revision. The group trusts the source and does not ask to see the revision. This flag can only be set together with the « Rev RQ » flag.

	== Access Rights ==		== Access Rights ==

Vreck at 14:18, 5 August 2010

2010-08-05T14:18:02Z

← Older revision		Revision as of 15:18, 5 August 2010
Line 19:		Line 19:
	: <u>note</u>: problem can arise when a user reserves a revision without uploading it --> the committee neither take a decision on the original ''revised'' contribution, nor on its non-available revision...		: <u>note</u>: problem can arise when a user reserves a revision without uploading it --> the committee neither take a decision on the original ''revised'' contribution, nor on its non-available revision...

	; WITHDRAWN : The submitter of a contribution can decides to withdraw (cancel) his contribution as long as the contribution has not been handled by the committee. As soon as a contribution has been discussed (''~~noted~~'') or if a decision has been taken on it (''Accepted'', or ''Rejected'') it is no longer possible to withdraw it.		; WITHDRAWN : The submitter of a contribution can decides to withdraw (cancel) his contribution as long as the contribution has not been handled by the committee. As soon as a contribution has been discussed (''Noted'') or if a decision has been taken on it (''Accepted'', or ''Rejected'') it is no longer possible to withdraw it.


	== Flags ==		== Flags ==
	== Access Rights ==		== Access Rights ==

Vreck at 13:45, 5 August 2010

2010-08-05T13:45:14Z

← Older revision		Revision as of 14:45, 5 August 2010
Line 1:		Line 1:
			__TOC__
	STILL UNDER CONSTRUCTION: need to describe transitions, flags, and access rights...		STILL UNDER CONSTRUCTION: need to describe transitions, flags, and access rights...

	The picture below illustrates the states that constitute the life cycle of a contribution.		The picture below illustrates the states that constitute the life cycle of a contribution.
	[[Image:Contribution State Machine.PNG\|~~600px~~\|\|left\|alt=Contribution State Machine\|Contribution State Machine]]		[[Image:Contribution State Machine.PNG\|500px\|\|left\|alt=Contribution State Machine\|Contribution State Machine]]
	== States ==		== States ==
	; RESERVED : The contribution details have been entered in the system, the file has not yet been uploaded.		; RESERVED : The contribution details have been entered in the system, the file has not yet been uploaded.
Line 21:		Line 22:


	=== Flags ===		== Flags ==
	=== Access Rights ===		== Access Rights ==

← Older revision		Revision as of 15:30, 15 September 2010
Line 7:		Line 7:
	; RESERVED : The contribution details have been entered in the system, the file has not yet been uploaded. Next step is to "''Upload/Make Available''" the contribution file. It is also possible to withdraw (cancel) the contribution at this stage.		; RESERVED : The contribution details have been entered in the system, the file has not yet been uploaded. Next step is to "''Upload/Make Available''" the contribution file. It is also possible to withdraw (cancel) the contribution at this stage.

	Is is not possible to REVISE a contribution from the RESERVED state since the proposal has not yet been made available.		Is is not possible to REVISE a contribution from the RESERVED state since the proposal has not yet been made available (one does not revise something that has not yet been issued).
	; AVAILABLE : The contribution file is physically present on the server		; AVAILABLE : The contribution file is physically present on the server.
	; WITHDRAWN : The submitter of a contribution can ~~decides~~ to withdraw (cancel) his contribution as long as the contribution has not been handled by the committee. As soon as a contribution has been discussed (''Noted'') or if a decision has been taken on it (''Accepted'', or ''Rejected'') it is no longer possible to withdraw it.		; WITHDRAWN : The submitter of a contribution can decide to withdraw (cancel) his contribution as long as the contribution has not been handled by the committee. As soon as a contribution has been discussed (''Noted'') or if a decision has been taken on it (''Accepted'', or ''Rejected'') it is no longer possible to withdraw it.
	[[Image:Contribution State Machine.PNG\|500px\|\|left\|alt=Contribution State Machine\|Contribution State Machine]]		[[Image:Contribution State Machine.PNG\|500px\|\|left\|alt=Contribution State Machine\|Contribution State Machine]]
	; REJECTED : The group has ~~rejected~~ the ~~contribution~~ AS A WHOLE~~, and~~ does not want to discuss it any further. It is hence not possible to revise a rejected contribution.		; REJECTED : The group has discussed a contribution that was "For Decision" and decided to reject the proposal AS A WHOLE. The group does not want to discuss it any further. It is hence not possible to revise a ''rejected'' contribution.
	: <u>note</u>: ACCEPTED and REJECTED states are only applicable to contributions "''For Decision''"		: <u>note</u>: ACCEPTED and REJECTED states are only applicable to contributions "''For Decision''"
	; ACCEPTED : The group has ~~accepted~~ the ~~contribution~~ AS IT IS, there is no need to improve/update it any further, it is ready for potential implementation. It is hence not possible to revise an accepted contribution.		; ACCEPTED : The group has discussed a contribution that was "For Decision" and decided to accept the proposal AS IT IS, there is no need to improve/update it any further, it is ready for potential implementation. It is hence not possible to revise an accepted contribution.
	: <u>note</u>: ACCEPTED and REJECTED states are only applicable to contributions "''For Decision''"		: <u>note</u>: ACCEPTED and REJECTED states are only applicable to contributions "''For Decision''"
	; NOTED : '''IF''' a contribution is '''''for information''''' or '''''for discussion''''' (no decision requested from the committee) ''NOTED'' is the end-of-life status set by the committee once the contribution has been handled, i.e. either discussed, presented, or sometimes just mentioned.		; NOTED : '''IF''' a contribution is '''''for information''''' or '''''for discussion''''' (no decision requested from the committee) ''NOTED'' is the end-of-life status set by the committee once the contribution has been handled, i.e. either discussed, presented, or sometimes just mentioned.
	: '''IF''' a contribution is '''''for decision''''' (a decision is requested from committee), ''NOTED'' implies that the committee has discussed the proposal without either '''accepting''' nor '''rejecting''' it. This usually means that the committee expects the contribution to be improved (i.e. ''revised '') prior to take a decision on it. It is hence possible to revise a contribution that is ''Noted''.		: '''IF''' a contribution is '''''for decision''''' (a decision is requested from committee), ''NOTED'' implies that the committee has discussed the proposal without either '''accepting''' nor '''rejecting''' it. This usually means that the committee expects the contribution to be improved (i.e. ''revised '') prior to take a decision on it. It is hence possible to revise a contribution that is ''Noted''.
	; REVISED : A contribution is revised as soon as a revision has been reserved. The concept is that a revision improves and/or corrects an existing proposal. Hence once a contribution is REVISED it is no longer possible to take a decision on it (''Accept'', or ''Reject'') since the decision will be taken on its revision.		; REVISED : A contribution is revised as soon as its revision has been reserved. The concept is that a revision improves and/or corrects an existing proposal. Hence once a contribution is in REVISED status it is no longer possible to take a decision on it (''Accept'', or ''Reject'') since the decision will be taken on its revision. Nor is it possible to mark it as NOTED (case of a revision reserved before discussion), because logically, if a contribution is revised before being presented to the group, the group will then discuss the latest revision, not the earlier ones.
	: <u>note</u>: problem can arise when a user reserves a revision without uploading it --> the committee neither take a decision on the original ''revised'' contribution, nor on its non-available revision...		: <u>note</u>: problem can arise when a user reserves a revision without uploading it --> the committee neither take a decision on the original ''revised'' contribution, nor on its non-available revision...

	== Flags ==		== Flags ==
	; Postponed: this flag is set manually by the chairman to indicate that the contribution was delayed (presenter not there, lack of time, file not available,etc…). It can be set and cleared indefinitely by the chairman as long as the contribution is in ''Reserved'' or ''Available'' state. When moving away from these states the flag is cleared and can no longer be set.		; Postponed: this flag is set manually by the chairman to indicate that the contribution was delayed (presenter not there, lack of time, file not available,etc…). It can be set and cleared indefinitely by the chairman as long as the contribution is in ''Reserved'' or ''Available'' state. When moving away from these states the flag is cleared and can no longer be set.