Changes between Version 11 and Version 12 of RdsMaintenanceProcedureTest
- Timestamp:
- 02/04/14 15:22:55 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
RdsMaintenanceProcedureTest
v11 v12 19 19 20 20 === Initiation of Change Request === 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).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, company or a project, a main person of contact should be identified (by name and email address). 22 22 23 Information about a CR is available here. 23 Information about a CR is available here. 24 24 25 25 === Evaluation of the Change Request === 26 The CR is checked for completeness and consistency by the PCA RD Maintenance Team staff . Thisincludes 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.26 The CR is checked for completeness and consistency by the PCA RD Maintenance Team staff, and the CR is given status identifier "'''''for evaluation'''''". This step 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. 27 27 28 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.28 If this initial check is satisfactory 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. 29 29 30 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. 30 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. 31 31 32 32 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. 33 33 34 === Preparation for validation===34 === Validation of the Change Request === 35 35 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). 36 36 37 === Validation of the Change Request === 38 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. 37 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 validation team 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. 39 38 40 39 === Resolution of the CR === … … 46 45 * rejected 47 46 48 The decision of the PCA SIG Validation Team is communicated back to the PCA RD Maintenance Team 47 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. 49 48 50 49 === Implementation of CR === 51 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. 50 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. 52 51 53 52 == Definition and clarification of terms == … … 63 62 * PCA RD Maintenance Team 64 63 * PCA SIG RD Validation Team 65 * PCA SIG Responsible -> refereres ikke til noe sted66 64 * Proposer 67 65 * Change Request (CR) 66 * Work Package 68 67 * Original Procedure 69 68 * Normal database procedure
