PD:Internal CCSDS 652.0-M-1 audit - Revision history

Nuess0r: Entered changes from second review

2016-07-27T20:21:31Z

Entered changes from second review

Nuess0r: Adding the changes from the reviewer

2016-07-27T10:00:47Z

Adding the changes from the reviewer

Nuess0r: Protected "PD:Internal CCSDS 652.0-M-1 audit" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2016-07-26T14:10:05Z

Protected "PD:Internal CCSDS 652.0-M-1 audit" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

Nuess0r: Changed "Some requirements are not fulfilled" with more precise "Minor requirements..."

2016-07-26T14:00:03Z

Changed "Some requirements are not fulfilled" with more precise "Minor requirements..."

Show changes

Nuess0r: converted suggestions into facts

2016-07-11T21:39:09Z

converted suggestions into facts

Nuess0r: fixed small formating typo

2016-07-10T23:58:09Z

fixed small formating typo

Nuess0r: Approval of the internal audit and therefor make it available to the public

2016-07-10T23:56:04Z

Approval of the internal audit and therefor make it available to the public

Show changes

@@ Line 139: / Line 139: @@
 ==== ESSENTIAL DEFINITIONS ====
-In the project and between the project members there is a mutual understanding of the designated communities but it is not precisely defined and therefor the knowledge base of this communities is not known.
+In the project and between the project members there is a mutual understanding of the designated communities but it is not precisely defined and therefor the knowledge base of these communities is not known.
 The same is true for the definition of the content information that has to be preserved.
@@ Line 151: / Line 151: @@
 ==== MANAGEMENT AND PRESERVATION PLANNING ====
-The area of management tasks, strategic planning, development of policies and tracking is also underdeveloped. Also there is no risk assessment installed and consequently there are no processes to observe the technical and legal environment of the repository on a regular basis.
+The area of management tasks, strategic planning, development of policies and tracking is also underdeveloped. Also, there is no risk assessment installed and consequently there are no processes to observe the technical and legal environment of the repository on a regular basis.
 Also missing is a system to plan, manage and track work packages, milestones, issues etc. to support the further development of management and preservation planning.
@@ Line 159: / Line 159: @@
 ==== DIGITAL OBJECT MANAGEMENT ====
-It was already known that the handling of the digital objects in the repository has its risks that are not addressed yet.
+It was already known that the handling of the digital objects in the repository has its risks that have not been addressed yet.
 The digital objects are at risk because there is no system to prevent unintended deletion of objects, there is no off-site backup and there is no system and associated monitoring to guarantee the bit-level correctness of the digital objects now and in the future.
@@ Line 168: / Line 168: @@
 === CONCLUSION ===
-As it was expected a lot of requirements are not fulfilled. But the value of this audit is high because it detected very underdeveloped areas inside the project and as such raises the awareness of these problems. Twelve of them can be easily fixed by documenting what is currently implemented.
+As it was expected a lot of requirements are not fulfilled. However, the value of this audit is high because it detected very underdeveloped areas inside the project and as such raises the awareness of these problems. Twelve issues them can easily be fixed by documenting what is currently implemented.
 It is of high importance to fix the lack of the essential definitions about content information and designated community.
@@ Line 174: / Line 174: @@
 A large field to work on are the regular maintenance and observation tasks of the management and preservation planning. They have to be defined, documented, executed and reviewed.
-On the technical side, the completely missing representation information is a formidable shortcoming for a longterm repository. If this information is collected in the near future and maintained thereafter, the real risk of losing understandability is still relatively low.
+On the technical side, the completely missing representation information is a substantial shortcoming for a longterm repository. If this information is collected in the near future and maintained thereafter, the real risk of losing understandability is relatively low.
 == [[PD:CCSDS_652.0-M-1#ORGANIZATIONAL INFRASTRUCTURE|ORGANIZATIONAL INFRASTRUCTURE]] ==

@@ Line 139: / Line 139: @@
 ==== ESSENTIAL DEFINITIONS ====
-In the project and between the project members there is a common sense of the designated communities but it is not precisely defined together with the knowledge base of this communities.
+In the project and between the project members there is a mutual understanding of the designated communities but it is not precisely defined and therefor the knowledge base of this communities is not known.
 The same is true for the definition of the content information that has to be preserved.
@@ Line 145: / Line 145: @@
 ==== REPRESENTATION INFORMATION ====
-An example of an underdeveloped area, because the whole knowledge of the underlying problems and the concepts to handle them was missing at the beginning of this audit, is the field of representation information. The consequent use of open standards an open source software makes it a bit less critical. But because any representation information is missing it still creates a large risk for the repository.
+An example of an underdeveloped area is the field of representation information, because the awareness of the underlying problems and the concepts to handle them was missing in the project at the beginning of this audit. The consequent use of open standards and open source software makes it a bit less critical. But because any representation information is missing, it still creates a large long term risk for the repository.
 This whole topic has to be addressed in the near future.
@@ Line 151: / Line 151: @@
 ==== MANAGEMENT AND PRESERVATION PLANNING ====
-The area of management tasks, strategic planning, development of policies and tracking if they are applied is also underdeveloped. Also there is no risk assessment installed and therefor there are also no processes to observe the technical and legal environment of the repository.
+The area of management tasks, strategic planning, development of policies and tracking is also underdeveloped. Also there is no risk assessment installed and consequently there are no processes to observe the technical and legal environment of the repository on a regular basis.
-Missing is a system to plan, manage and track work packages, milestones, issues etc. to support the further development of management and preservation planning.
+Also missing is a system to plan, manage and track work packages, milestones, issues etc. to support the further development of management and preservation planning.
-Missing is a system which enables end users and producers to submit feedback where submitters can observe the reactions and actions in response to there feedback.
+Furthermore a system which enables end users and producers to submit feedback and where submitters can observe the reactions and actions in response to their feedback is missing.
 ==== DIGITAL OBJECT MANAGEMENT ====
-It was already known that the handling of the digital objects in the repository has its risks that are not handled yet. The audit clearly showed that.
+It was already known that the handling of the digital objects in the repository has its risks that are not addressed yet.
 The digital objects are at risk because there is no system to prevent unintended deletion of objects, there is no off-site backup and there is no system and associated monitoring to guarantee the bit-level correctness of the digital objects now and in the future.
@@ Line 168: / Line 168: @@
 === CONCLUSION ===
-As it was expected a lot of requirements are not fulfilled. But the value of this audit is high because it detected very underdeveloped areas inside the project and as such raises the awareness of this problems. Twelve of them can be easily fixed by just documenting what is currently implemented.
+As it was expected a lot of requirements are not fulfilled. But the value of this audit is high because it detected very underdeveloped areas inside the project and as such raises the awareness of these problems. Twelve of them can be easily fixed by documenting what is currently implemented.
-Of high importance is to fix the lack of the essential definitions about content information and designated community.
+It is of high importance to fix the lack of the essential definitions about content information and designated community.
 A large field to work on are the regular maintenance and observation tasks of the management and preservation planning. They have to be defined, documented, executed and reviewed.
-On the technical side the completely missing representation information is a no-go for a longterm repository. If this information is collected in the near future and maintained thereafter the real risk of loosing understandability is still low. But there is no excuse to wait.
+On the technical side, the completely missing representation information is a formidable shortcoming for a longterm repository. If this information is collected in the near future and maintained thereafter, the real risk of losing understandability is still relatively low.
 == [[PD:CCSDS_652.0-M-1#ORGANIZATIONAL INFRASTRUCTURE|ORGANIZATIONAL INFRASTRUCTURE]] ==

@@ Line 130: / Line 130: @@
 Of the 108 normative metrics the final status is the following:
-Metrics with all requirements fulfilled: 16<br/>
+Metrics with all requirements fulfilled (green): 16<br/>
-Metrics where Some requirements are not fulfilled: 15<br/>
+Metrics where Some requirements are not fulfilled (orange): 15<br/>
-Metrics with essential requirements not fulfilled: 77
+Metrics with essential requirements not fulfilled (red): 77
@@ Line 153: / Line 153: @@
 The area of management tasks, strategic planning, development of policies and tracking if they are applied is also underdeveloped. Also there is no risk assessment installed and therefor there are also no processes to observe the technical and legal environment of the repository.
-There should be a system to plan, manage and track work packages, milestones, issues etc. to support the further development of management and preservation planning.
+Missing is a system to plan, manage and track work packages, milestones, issues etc. to support the further development of management and preservation planning.
-There should be a system which enables end users and producers to submit feedback where submitters can observe the reactions and actions in response to there feedback.
+Missing is a system which enables end users and producers to submit feedback where submitters can observe the reactions and actions in response to there feedback.
 ==== DIGITAL OBJECT MANAGEMENT ====

@@ Line 683: / Line 683: @@
 From the [[PD:FAQ#What_I.27m_allowed_to_do_with_the_music_files.3F|FAQ]]:<br/>
-''Question: What I'm allowed to do with the music files?<br/>
+''Question: What I'm allowed to do with the music files?''<br/>
-Answer: There is no restriction. You can for ex. redistribute it, copy it, modify it, use it in your own productions, use it as background music and so on.''
+''Answer: There is no restriction. You can for ex. redistribute it, copy it, modify it, use it in your own productions, use it as background music and so on.''
 Unusual for other archives is the fact, that everybody can contribute to the project by supplying additional metadata, context information or by submitting SIPs to the archive. The project is and should be driven by volunteers as it is the base principle of this (and related) archives.

← Older revision	Revision as of 14:10, 26 July 2016
(No difference)