Changes between Version 10 and Version 11 of RdsMaintenanceProcedureTest

Timestamp:

02/04/14 15:12:37 (10 years ago)

Author:

lhella (IP: 85.221.54.157)

Comment:

--

RdsMaintenanceProcedureTest

@@ -21 +21 @@
 When a Change request (CR) is received from a Proposer in an RD Update File with the specified RD Input Format, the submitted CR is entered into the PCA RDL Request Log with status identifier "'''''submitted'''''" and the Proposer is automatically notified. The Proposer needs to be a registered user and submit the CR to the RDS Operations Support Ticket system ([http://rdssupport.posccaesar.org/newticket link]). The Proposer must be clearly identified, and can e.g. be an individual, a project, a company. If the Proposer is a group, a main person of contact should be identified (by name and email address).
 
-Link to beskrivelse + validation
-
-Link to prosesside som forteller om proposals and development/staging area location
-
-=== Preparation for evaluation ===
-The CR is checked for completeness and consistency by the PCA RD Maintenance Team staff. This includes ensuring that all mandatory administrative and meta-data entries are appropriately filled-in and that any necessary accompanying items are of a quality sufficient for evaluation.  This check is fully automated.
-
--> obs sufficient quality? sjekkes det her? da er det automatisk + manuelt?
-
-If this initial check is satisfactory the CR is given status identifier "'''''for evaluation'''''" and the Proposer is notified about the status update. When a CR has passed this initial check, the content will be uploaded to the PCA Development endpoint. If the CR is deemed not to be satisfactory, the Proposer is notified with the reason(s) for rejection. This shall take place within a maximum of '''''5 (five) working days''''' after receiving the CR (after the status identifier was set to "submitted").
+Information about a CR is available here. 
 
 === Evaluation of the Change Request ===
-If the quality of the information in the Work Package (CR) is satisfactory, the PCA RD Maintenance Team Staff sets the status of the Change Request to "'''''for validation'''''" and notifies the Proposer about status update. If the CR is deemed not to be satisfactory, the Proposer is notified with the reason(s) for rejection. Notification shall take place within '''''5 (five) working days''''' after initial acceptance of the CR (after the status identifier was set to "for evaluation").
+The CR is checked for completeness and consistency by the PCA RD Maintenance Team staff. This includes ensuring that all mandatory administrative and meta-data entries are appropriately filled-in and that any necessary accompanying items are sufficient for evaluation.  This check is fully automated.
+
+If this initial check is satisfactory the CR is given status identifier "'''''for evaluation'''''" and the Proposer is notified about the status update. When a CR has passed this initial check, the content will be uploaded to the PCA Development endpoint. If the CR is deemed not to be satisfactory, the Proposer is notified with the reason(s) for rejection. 
+
+If the quality of the information in the CR is satisfactory, the PCA RD Maintenance Team Staff sets the status of the Change Request to "'''''for validation'''''" and notifies the Proposer about status update. If the CR is deemed not to be satisfactory, the Proposer is notified with the reason(s) for rejection. 
 
 If considered practical, the PCA RD Maintenance Team Staff may decide to combine items under more than one CR into one Work Package, or to separate items submitted under one CR into several Work Packages, in order to assign relevant parts of the CR (database items) to (one or more) relevant PCA SIGs.
 
 === Preparation for validation ===
-The PCA SIG Validation Team Responsible determines whether the Change Request (Work Package) is within the scope of the PCA RDL and valid for evaluation (or should be rejected),
-
-Notification shall be sent to the PCA RD Maintenance Team within '''''5 (five) working days''''' after receiving the Work Package (10 working days after the status identifier was set to "for validation").
+The PCA SIG Validation Team Responsible determines whether the Change Request (Work Package) is within the scope of the PCA RDL and valid for evaluation (or should be rejected).
 
 === Validation of the Change Request ===
 For the validation to be satisfactory (valid) more than half (a simple majority) of the PCA SIG Validation Team members must approve the proposed updates. If the Proposer of a CR is a SIG, then a team for validation must be assigned by the PCA TAB. The team must consist of domain experts that has been part of developing the CR, external domain experts and ISO 15926 experts.
 
-This must be completed within a maximum of '''''30 (thirty) working days''''' after the PCA SIG Validation Team sends its decision about the Work Package (CR) back to the PCA RD Maintenance Team.
-
 === Resolution of the CR ===
-Given evaluation of the PCA SIG Validation team, the Work Package may be
+Given evaluation of the PCA SIG Validation team, the Change Request may be
 
  * approved for inclusion in the PCA RDL and uploaded to the PCA staging area
@@ -55 +46 @@
  * rejected
 
-The decision of the PCA SIG Validation Team is communicated back to the PCA RD Maintenance Team within '''''five (5) working days''''' after the necessary number of members has completed their validation.
+The decision of the PCA SIG Validation Team is communicated back to the PCA RD Maintenance Team after the necessary number of members has completed their validation.
 
 === Implementation of CR ===
-After a CR is approved (either directly or after required modification), the PCA RD Maintenance Team staff uploads/changes any required in the PCA RDL, sets the status identification to "resolved" and notifies the Proposer about planned inclusion of CR to the production endpoint. This shall take place within '''''10 (ten) working days''''' receiving the decision of acceptance by the PCA SIG Validation was received by the PCA RD Maintenance Team
-
-Thus the maximum total time from receiving an initial Change Request to Implementation (given that everything is accepted on first pass) shall be '''''60 (sixty) working days'''''.
-
-''The note should probably continue the process description with description of tasks for normal database procedure. This is not required for PCA RD Maintenance procedure, but important for presentation of procedure to ISO.''
+After a CR is approved (either directly or after required modification), the PCA RD Maintenance Team staff uploads/changes any required in the PCA RDL production endpoint, sets the status identification to "resolved" and notifies the Proposer about planned inclusion of CR to the production endpoint. 
 
 == Definition and clarification of terms ==
@@ -79 +66 @@
  * Proposer
  * Change Request (CR)
- * Work Package
  * Original Procedure
  * Normal database procedure