OAIS v3 draft: • the concept of Preservation Objectives has been introduced to allow “Independently Understandable” to be more consistently testable; ==> Need additions to 4.2.5, 4.2.7,
Change 4.2.7 FROM: The repository shall ensure that the Content Information of the AIPs is understandable for their Designated Community at the time of creation of the AIP. TO: The repository shall ensure that the Content Information of the AIPs is understandable for their Designated Community, as exemplified by the associated Preservation Objectives, at the time of creation of the AIP. Also change 4.2.5.2 FROM: The repository shall have tools or methods to determine what Representation Information is necessary to make each Data Object understandable to the Designated Community. TO: The repository shall have tools or methods to determine what Representation Information is necessary to make each Data Object understandable, as exemplified by the associated Preservation Objectives, to the Designated Community. May need changes in the Discussion for each.
Should be 4.2.5.2 instead of 4.2.5 (In reply to David Giaretta from comment #0) > OAIS v3 draft: > • the concept of Preservation Objectives has been introduced to allow > “Independently Understandable” to be more consistently testable; > > ==> Need additions to 4.2.5, 4.2.7,
Change: 4.1.1 The repository shall identify the Content Information and the Information Properties that the repository will preserve. To: 4.1.1 The repository shall identify the Content Information, Preservation Objectives and the Information Properties that the repository will preserve. Also ADD 4.1.1.3 The repository shall have a procedure(s) for identifying those Preservation Objectives for the Content Information it will preserve. Supporting Text This is necessary to establish a clear understanding with depositors, funders, and the repository’s Designated Communities how the repository determines and checks what the Designated Community would be expected to be able to do with the Content Information. These procedures will be necessary to confirm that the Content Information remains understandable/usable. Examples of Ways the Repository Can Demonstrate It Is Meeting This Requirement Definitions of the Preservation Objectives applicable to each Content Information Object; submission agreements/deposit agreements, Preservation Policies, written processing procedures, workflow documentation. Discussion These procedure(s) document the methods and factors a repository uses to determine the aspects of different types of Content Information for which it accepts preservation responsibility to its designated communities. For example, a repository’s procedure may be to use file formats in order to determine the properties it will preserve unless otherwise specified in a deposit agreement. In this case, the repository would be able to demonstrate provenance for objects that may have been the same file format when received but are preserved differently over the long term. 4.1.1.4 The repository shall have a record of the Content Information and the Preservation Objectives that it will preserve. Supporting Text This is necessary in order to identify in writing the Content Information Objects for which it has taken preservation responsibility and the Preservation Objectives it has committed to check for those records based on their Content Information. Examples of Ways the Repository Can Demonstrate It Is Meeting This Requirement Preservation Policies, processing manuals, collection inventories or surveys, logs of Content Information types, acquired preservation strategies, and action plans. Discussion The repository must demonstrate that it establishes and maintains an understanding of its digital collections sufficient to carry out the preservation necessary to ensure the Designated Community(ies) can catty out the specified Preservation Objectives. The repository can use this information to determine the effectiveness of its preservation activities over time.
Also Change FROM 4.2.5.2 The repository shall have tools or methods to determine what Representation Information is necessary to make each Data Object understandable to the Designated Community. TO: 4.2.5.2 The repository shall have tools or methods to determine what Representation Information is necessary to make each Data Object understandable to the Designated Community in ways exemplified by the Preservation Objectives. Also change FROM: 4.2.7 The repository shall ensure that the Content Information of the AIPs is understandable for their Designated Community at the time of creation of the AIP. TO: 4.2.7 The repository shall ensure that the Content Information of the AIPs is understandable for their Designated Community, in ways exemplified by the Preservation Objectives, at the time of creation of the AIP. AL lso change FROM: 4.3.2.1 The repository shall have mechanisms in place for monitoring and notification when Representation Information is inadequate for the Designated Community to understand the data holdings. TO: 4.3.2.1 The repository shall have mechanisms in place for monitoring and notification when Representation Information is inadequate for the Designated Community to understand, in ways exemplified by the Preservation Objectives, the data holdings.
In 3.3.1 add to end of 1st Discussion paragraph "In addition to and associated with the definition of the Designated Community, Preservation Objectives will be defined in relation to the definition of the Designated Community." May also want to review the examples of definitions. In 3.3.2 Discussion From: In another example the repository may be required by the strategic plan to keep its data understandable. The preservation policy might then include information about the expected level of understandability by the repository’s Designated Community for each Archival Information Package. To: In another example the repository may be required by the strategic plan to keep its data understandable by the Designated Communities for the repository's AIPs. The preservation policy might then include information about the expected level of understandability for each Archival Information Package, as exemplified by the associated Preservation Objectives. In 4.2.7 Should probably also rewrite text supporting the metric to bring in Preservation Objectives. Also, should we consider adding examples where the Preservation Objective is not to "understand" the content, but it is being preserved at a level where the content can be "viewed"? In 4.3.2 Supporting Text and Discussion In 4.3.3.1 Supporting Text From: ... ensure that the preserved information remains understandable and usable by the Designated Community ... To: ... ensure that the preserved information remains understandable and usable by the Designated Community, as exemplified by the associated Preservation Objectives ...
(In reply to David Giaretta from comment #1) > Change 4.2.7 > FROM: > The repository shall ensure that the Content Information of the AIPs is > understandable for their Designated Community at the time of creation of the > AIP. > > TO: > The repository shall ensure that the Content Information of the AIPs is > understandable for their Designated Community, as exemplified by the > associated Preservation Objectives, at the time of creation of the AIP. > > Also change > > 4.2.5.2 > FROM: > The repository shall have tools or methods to determine what Representation > Information is necessary to make each Data Object understandable to the > Designated Community. > > TO: > The repository shall have tools or methods to determine what Representation > Information is necessary to make each Data Object understandable, as > exemplified by the associated Preservation Objectives, to the Designated > Community. > > > May need changes in the Discussion for each. I have no problem with this suggested change as written. Would want to see the suggested changes to the Discussion before final approval.
(In reply to David Giaretta from comment #3) > Change: > > 4.1.1 The repository shall identify the Content Information and the > Information Properties that the repository will preserve. > > To: > > 4.1.1 The repository shall identify the Content Information, Preservation > Objectives and the Information Properties that the repository will preserve. > > Also ADD > > 4.1.1.3 The repository shall have a procedure(s) for identifying those > Preservation Objectives for the Content Information it will preserve. > > Supporting Text > This is necessary to establish a clear understanding with depositors, > funders, and the repository’s Designated Communities how the repository > determines and checks what the Designated Community would be expected to be > able to do with the Content Information. These procedures will be necessary > to confirm that the Content Information remains understandable/usable. > > Examples of Ways the Repository Can Demonstrate It Is Meeting This > Requirement > Definitions of the Preservation Objectives applicable to each Content > Information Object; submission agreements/deposit agreements, Preservation > Policies, written processing procedures, workflow documentation. > > Discussion > These procedure(s) document the methods and factors a repository uses to > determine the aspects of different types of Content Information for which it > accepts preservation responsibility to its designated communities. For > example, a repository’s procedure may be to use file formats in order to > determine the properties it will preserve unless otherwise specified in a > deposit agreement. In this case, the repository would be able to demonstrate > provenance for objects that may have been the same file format when received > but are preserved differently over the long term. > > 4.1.1.4 The repository shall have a record of the Content Information and > the Preservation Objectives that it will preserve. > > Supporting Text > This is necessary in order to identify in writing the Content Information > Objects for which it has taken preservation responsibility and the > Preservation Objectives it has committed to check for those records based on > their Content Information. > > Examples of Ways the Repository Can Demonstrate It Is Meeting This > Requirement > Preservation Policies, processing manuals, collection inventories or > surveys, logs of Content Information types, acquired preservation > strategies, and action plans. > > Discussion > The repository must demonstrate that it establishes and maintains an > understanding of its digital collections sufficient to carry out the > preservation necessary to ensure the Designated Community(ies) can catty out > the specified Preservation Objectives. The repository can use this > information to determine the effectiveness of its preservation activities > over time. Not sure the proposed text for 4.1.1. makes sense. Would it make more sense to say "the functionalities of the Content Information listed in the Preservation Objectives"? Suggest modifying this proposed text From: 4.1.1.3 The repository shall have a procedure(s) for identifying those Preservation Objectives for the Content Information it will preserve. To: 4.1.1.3 The repository shall have a procedure(s) for identifying the Preservation Objectives for each set of Content Information it will preserve. STRONGLY OBJECT to the proposed Discussion text for 4.1.1.3. Determining what functionality to preserve is based on the content - not the file format. The same file format can be used to preserve or remove functionality of a given set of Content Information. 4.1.1.4. should also mention Transformational Information Properties. This should also be discussed in the Supporting Text, Examples, and Discussion. NOTE: The numbering for these submetrics may need to be modified depending on the final disposition of Steve's SC to combine the submetrics for 4.1.1.
(In reply to David Giaretta from comment #4) > Also > > Change > FROM > 4.2.5.2 The repository shall have tools or methods to determine what > Representation Information is necessary to make each Data Object > understandable to the Designated Community. > > TO: > 4.2.5.2 The repository shall have tools or methods to determine what > Representation Information is necessary to make each Data Object > understandable to the Designated Community in ways exemplified by the > Preservation Objectives. > > Also change > FROM: > 4.2.7 The repository shall ensure that the Content Information of the AIPs > is understandable for their Designated Community at the time of creation of > the AIP. > > TO: > 4.2.7 The repository shall ensure that the Content Information of the AIPs > is understandable for their Designated Community, in ways exemplified by the > Preservation Objectives, at the time of creation of the AIP. > > AL > lso change > FROM: > 4.3.2.1 The repository shall have mechanisms in place for monitoring and > notification when Representation Information is inadequate for the > Designated Community to understand the data holdings. > > TO: > 4.3.2.1 The repository shall have mechanisms in place for monitoring and > notification when Representation Information is inadequate for the > Designated Community to understand, in ways exemplified by the Preservation > Objectives, the data holdings. Shouldn't the proposed text for 4.2.5.2., 4.2.7. and 4.3.2.1. also mention Transformational Information Properties?
(In reply to John Garrett from comment #5) > In 3.3.1 > add to end of 1st Discussion paragraph > "In addition to and associated with the definition of the Designated > Community, Preservation Objectives will be defined in relation to the > definition of the Designated Community." > > May also want to review the examples of definitions. > > In 3.3.2 Discussion > From: > In another example the repository may be required by the strategic plan to > keep its data understandable. The preservation policy might then include > information about the expected level of understandability by the > repository’s Designated Community for each Archival Information Package. > To: > In another example the repository may be required by the strategic plan to > keep its data understandable by the Designated Communities for the > repository's AIPs. The preservation policy might then include information > about the expected level of understandability for each Archival Information > Package, as exemplified by the associated Preservation Objectives. > > In 4.2.7 > Should probably also rewrite text supporting the metric to bring in > Preservation Objectives. > Also, should we consider adding examples where the Preservation Objective is > not to "understand" the content, but it is being preserved at a level where > the content can be "viewed"? > > In 4.3.2 Supporting Text and Discussion > In 4.3.3.1 Supporting Text > From: > ... ensure that the preserved information remains understandable and usable > by the Designated Community ... > To: > ... ensure that the preserved information remains understandable and usable > by the Designated Community, as exemplified by the associated Preservation > Objectives ... In terms of the proposed change to the Discussion for 3.3.1., the relationship between the Preservation Objectives and the Designated Community is more complex than is suggested by this sentence. A Preservation Objective is directly related to a set of Content Information. It takes into account the Knowledge Base and the desires of the Designated Community to use that particular set of Content Information. In terms of the other proposed changes it would be necessary to bring in discussion of Transformational Information Properties as well as Preservation Objectives. Preservation Objectives are about functionality associated with a particular AIP. TIPs are about properties of the Content Information to be maintained.
(In reply to Mark Conrad from comment #7) > (In reply to David Giaretta from comment #3) > > Change: > > > > 4.1.1 The repository shall identify the Content Information and the > > Information Properties that the repository will preserve. > > > > To: > > > > 4.1.1 The repository shall identify the Content Information, Preservation > > Objectives and the Information Properties that the repository will > preserve. > > > > Also ADD > > > > 4.1.1.3 The repository shall have a procedure(s) for identifying those > > Preservation Objectives for the Content Information it will preserve. > > > > Supporting Text > > This is necessary to establish a clear understanding with depositors, > > funders, and the repository’s Designated Communities how the repository > > determines and checks what the Designated Community would be expected to be > > able to do with the Content Information. These procedures will be necessary > > to confirm that the Content Information remains understandable/usable. > > > > Examples of Ways the Repository Can Demonstrate It Is Meeting This > > Requirement > > Definitions of the Preservation Objectives applicable to each Content > > Information Object; submission agreements/deposit agreements, Preservation > > Policies, written processing procedures, workflow documentation. > > > > Discussion > > These procedure(s) document the methods and factors a repository uses to > > determine the aspects of different types of Content Information for which > it > > accepts preservation responsibility to its designated communities. For > > example, a repository’s procedure may be to use file formats in order to > > determine the properties it will preserve unless otherwise specified in a > > deposit agreement. In this case, the repository would be able to > demonstrate > > provenance for objects that may have been the same file format when > received > > but are preserved differently over the long term. > > > > 4.1.1.4 The repository shall have a record of the Content Information and > > the Preservation Objectives that it will preserve. > > > > Supporting Text > > This is necessary in order to identify in writing the Content Information > > Objects for which it has taken preservation responsibility and the > > Preservation Objectives it has committed to check for those records based > on > > their Content Information. > > > > Examples of Ways the Repository Can Demonstrate It Is Meeting This > > Requirement > > Preservation Policies, processing manuals, collection inventories or > > surveys, logs of Content Information types, acquired preservation > > strategies, and action plans. > > > > Discussion > > The repository must demonstrate that it establishes and maintains an > > understanding of its digital collections sufficient to carry out the > > preservation necessary to ensure the Designated Community(ies) can catty > out > > the specified Preservation Objectives. The repository can use this > > information to determine the effectiveness of its preservation activities > > over time. > > Not sure the proposed text for 4.1.1. makes sense. Would it make more sense > to say "the functionalities of the Content Information listed in the > Preservation Objectives"? > > Suggest modifying this proposed text > > From: > > 4.1.1.3 The repository shall have a procedure(s) for identifying those > Preservation Objectives for the Content Information it will preserve. > > To: > > 4.1.1.3 The repository shall have a procedure(s) for identifying the > Preservation Objectives for each set of Content Information it will preserve. I guess this depends what you mean by "set of Content Information" - if it just means "all Content Information with the same Preservation Objectives" then it is a tautology. I think the point is that if the auditor points to a particular example of Content Information then the repository should be able to say what the Preservation Objectives are. I can understand that you want to make the point that the Preservation Objectives may be the same for many objects then better to make that point in the Discussion. > > STRONGLY OBJECT to the proposed Discussion text for 4.1.1.3. Determining > what functionality to preserve is based on the content - not the file > format. The same file format can be used to preserve or remove functionality > of a given set of Content Information. Yes, well spotted, this was a copy/paste too far. I suggest better text in a consolidated comment below. > > 4.1.1.4. should also mention Transformational Information Properties. This > should also be discussed in the Supporting Text, Examples, and Discussion. Yes, see consolidated suggestions below. > > NOTE: The numbering for these submetrics may need to be modified depending > on the final disposition of Steve's SC to combine the submetrics for 4.1.1.
(In reply to Mark Conrad from comment #9) > (In reply to John Garrett from comment #5) > > In 3.3.1 > > add to end of 1st Discussion paragraph > > "In addition to and associated with the definition of the Designated > > Community, Preservation Objectives will be defined in relation to the > > definition of the Designated Community." > > > > May also want to review the examples of definitions. > > > > In 3.3.2 Discussion > > From: > > In another example the repository may be required by the strategic plan to > > keep its data understandable. The preservation policy might then include > > information about the expected level of understandability by the > > repository’s Designated Community for each Archival Information Package. > > To: > > In another example the repository may be required by the strategic plan to > > keep its data understandable by the Designated Communities for the > > repository's AIPs. The preservation policy might then include information > > about the expected level of understandability for each Archival Information > > Package, as exemplified by the associated Preservation Objectives. > > > > In 4.2.7 > > Should probably also rewrite text supporting the metric to bring in > > Preservation Objectives. > > Also, should we consider adding examples where the Preservation Objective > is > > not to "understand" the content, but it is being preserved at a level where > > the content can be "viewed"? > > > > In 4.3.2 Supporting Text and Discussion > > In 4.3.3.1 Supporting Text > > From: > > ... ensure that the preserved information remains understandable and usable > > by the Designated Community ... > > To: > > ... ensure that the preserved information remains understandable and usable > > by the Designated Community, as exemplified by the associated Preservation > > Objectives ... > > In terms of the proposed change to the Discussion for 3.3.1., the > relationship between the Preservation Objectives and the Designated > Community is more complex than is suggested by this sentence. A Preservation > Objective is directly related to a set of Content Information. It takes into > account the Knowledge Base and the desires of the Designated Community to > use that particular set of Content Information. I propose removing "in relation to the definition of the Designated Community" in the consolidated changes below. > > In terms of the other proposed changes it would be necessary to bring in > discussion of Transformational Information Properties as well as > Preservation Objectives. Preservation Objectives are about functionality > associated with a particular AIP. TIPs are about properties of the Content > Information to be maintained. Consolidated changes below include TIPs fully I hope.
(In reply to Mark Conrad from comment #8) > (In reply to David Giaretta from comment #4) > > Also > > > > Change > > FROM > > 4.2.5.2 The repository shall have tools or methods to determine what > > Representation Information is necessary to make each Data Object > > understandable to the Designated Community. > > > > TO: > > 4.2.5.2 The repository shall have tools or methods to determine what > > Representation Information is necessary to make each Data Object > > understandable to the Designated Community in ways exemplified by the > > Preservation Objectives. > > > > Also change > > FROM: > > 4.2.7 The repository shall ensure that the Content Information of the AIPs > > is understandable for their Designated Community at the time of creation of > > the AIP. > > > > TO: > > 4.2.7 The repository shall ensure that the Content Information of the AIPs > > is understandable for their Designated Community, in ways exemplified by > the > > Preservation Objectives, at the time of creation of the AIP. > > > > AL > > lso change > > FROM: > > 4.3.2.1 The repository shall have mechanisms in place for monitoring and > > notification when Representation Information is inadequate for the > > Designated Community to understand the data holdings. > > > > TO: > > 4.3.2.1 The repository shall have mechanisms in place for monitoring and > > notification when Representation Information is inadequate for the > > Designated Community to understand, in ways exemplified by the Preservation > > Objectives, the data holdings. > > Shouldn't the proposed text for 4.2.5.2., 4.2.7. and 4.3.2.1. also mention > Transformational Information Properties? I don't think 4.2.5.2 or 4.2.7 need to mention TIPs because this is creating the AIPs. However I agree that 4.3.2.1 needs to be changed - see consolidated text below.
The following are my Consolidated Changes including all the previous suggests and comments and also http://review.oais.info/show_bug.cgi?id=310 (which I will mark as a duplicate of this suggested change) Change: In 3.3.1 add to end of 1st Discussion paragraph "In addition to and associated with the definition of the Designated Community, Preservation Objectives will be defined." In 3.3.2 Discussion From: In another example the repository may be required by the strategic plan to keep its data understandable. The preservation policy might then include information about the expected level of understandability by the repository’s Designated Community for each Archival Information Package. To: In another example the repository may be required by the strategic plan to keep its data understandable by the Designated Communities for the repository's AIPs. The preservation policy might then include information about the expected level of understandability for each Archival Information Package, as exemplified by the associated Preservation Objectives. 4.1.1 The repository shall identify the Content Information and the Information Properties that the repository will preserve. To: 4.1.1 The repository shall identify the Content Information and associated Preservation Objectives and Transformational Information Properties that the repository will preserve. Also ADD 4.1.1.3 The repository shall have a procedure(s) for identifying those Preservation Objectives and Transformational Information Properties for the Content Information it will preserve. Supporting Text This is necessary to establish a clear understanding with depositors, funders, and the repository’s Designated Communities how the repository determines and checks what the Designated Community would be expected to be able to do with the Content Information. These procedures will be necessary to confirm that the Content Information remains understandable/usable. The Transformational Information Properties establish a clear understanding of the tests which determine whether a Transformation of an object is acceptable. Examples of Ways the Repository Can Demonstrate It Is Meeting This Requirement Definitions of the Preservation Objectives and Transformational Information Properties applicable to each Content Information Object; submission agreements/deposit agreements, Preservation Policies, written processing procedures, workflow documentation. Discussion These procedure(s) document the methods and factors a repository uses to determine the acceptability of different types of preservation activities for the Content Information for which it accepts preservation responsibility to its designated communities. For example, a repository’s preservation plans and policies may require the Context Data Objects to remain unchanged then as the Designated Community’s Knowledge Base changes, additional Representation Information must be provided; the Preservation Objectives allow the repository to check that enough Representation Information has been supplied. In this case since Transformations will not be allowed then the Transformation Information Properties would be to note that Transformations are not allowed and so the Content Data Objects are to be unchanged. On the other hand if Transformations are allowed by the repository’s plans and policies then the Transformational Information Properties allow the repository to check that the Transformation applied is acceptable. It is well worth noting that Preservation Objectives may be the same for a great many of the separate pieces of Content Information. Similarly the Transformational Information Properties may be the same for many Content Data Objects. 4.1.1.4 The repository shall have a record of the Content Information and the Preservation Objectives that it will preserve. Supporting Text This is necessary in order to identify in writing the Content Information Objects for which it has taken preservation responsibility and the Preservation Objectives it has committed to check for those records based on their Content Information. Examples of Ways the Repository Can Demonstrate It Is Meeting This Requirement Preservation Policies, processing manuals, collection inventories or surveys, logs of Content Information types, acquired preservation strategies, and action plans. Discussion The repository must demonstrate that it establishes and maintains an understanding of its digital collections sufficient to carry out the preservation necessary to ensure the Designated Community(ies) can catty out the specified Preservation Objectives. The repository can use this information to determine the effectiveness of its preservation activities over time. Also Change FROM 4.2.5.2 The repository shall have tools or methods to determine what Representation Information is necessary to make each Data Object understandable to the Designated Community. TO: 4.2.5.2 The repository shall have tools or methods to determine what Representation Information is necessary to make each Data Object understandable to the Designated Community in ways exemplified by the Preservation Objectives. Also change FROM: 4.2.7 The repository shall ensure that the Content Information of the AIPs is understandable for their Designated Community at the time of creation of the AIP. TO: 4.2.7 The repository shall ensure that the Content Information of the AIPs is understandable for their Designated Community, in ways exemplified by the Preservation Objectives, at the time of creation of the AIP. Also change FROM: 4.3.2.1 The repository shall have mechanisms in place for monitoring and notification when Representation Information is inadequate for the Designated Community to understand the data holdings. TO: 4.3.2.1 The repository shall have mechanisms in place for monitoring and notification when Representation Information, or the Context Data Object itself, is inadequate for the Designated Community to understand the data holdings in ways exemplified by the Preservation Objectives. In 4.3.3.1 Supporting Text From: ... ensure that the preserved information remains understandable and usable by the Designated Community ... To: ... ensure that the preserved information remains understandable and usable by the Designated Community, as exemplified by the associated Preservation Objectives ...
*** Bug 310 has been marked as a duplicate of this bug. ***
(In reply to David Giaretta from comment #13) > The following are my Consolidated Changes including all the previous > suggests and comments and also http://review.oais.info/show_bug.cgi?id=310 > (which I will mark as a duplicate of this suggested change) > > Change: > > In 3.3.1 > add to end of 1st Discussion paragraph > "In addition to and associated with the definition of the Designated > Community, Preservation Objectives will be defined." > > > In 3.3.2 Discussion > From: > In another example the repository may be required by the strategic plan to > keep its data understandable. The preservation policy might then include > information about the expected level of understandability by the > repository’s Designated Community for each Archival Information Package. > To: > In another example the repository may be required by the strategic plan to > keep its data understandable by the Designated Communities for the > repository's AIPs. The preservation policy might then include information > about the expected level of understandability for each Archival Information > Package, as exemplified by the associated Preservation Objectives. Shouldn't this mention TIPs as well? > > > 4.1.1 The repository shall identify the Content Information and the > Information Properties that the repository will preserve. > > To: > > 4.1.1 The repository shall identify the Content Information and associated > Preservation Objectives and Transformational Information Properties that the > repository will preserve. > > Also ADD > > 4.1.1.3 The repository shall have a procedure(s) for identifying those > Preservation Objectives and Transformational Information Properties for the > Content Information it will preserve. > > Supporting Text > This is necessary to establish a clear understanding with depositors, > funders, and the repository’s Designated Communities how the repository > determines and checks what the Designated Community would be expected to be > able to do with the Content Information. These procedures will be necessary > to confirm that the Content Information remains understandable/usable. The > Transformational Information Properties establish a clear understanding of > the tests which determine whether a Transformation of an object is > acceptable. > > Examples of Ways the Repository Can Demonstrate It Is Meeting This > Requirement > Definitions of the Preservation Objectives and Transformational Information > Properties applicable to each Content Information Object; submission > agreements/deposit agreements, Preservation Policies, written processing > procedures, workflow documentation. > > Discussion > These procedure(s) document the methods and factors a repository uses to > determine the acceptability of different types of preservation activities > for the Content Information for which it accepts preservation responsibility > to its designated communities. > For example, a repository’s preservation plans and policies may require the > Context Data Objects to remain unchanged then as the Designated Community’s 1. Context should be Content? See later in the paragraph. 2. Data Objects cannot "remain unchanged" if they are to be preserved over the long term. Later in the paragraph it says that the Data Objects cannot be Transformed - not that they must remain unchanged. > Knowledge Base changes, additional Representation Information must be > provided; the Preservation Objectives allow the repository to check that > enough Representation Information has been supplied. In this case since > Transformations will not be allowed then the Transformation Information > Properties would be to note that Transformations are not allowed and so the > Content Data Objects are to be unchanged. > On the other hand if Transformations are allowed by the repository’s plans > and policies then the Transformational Information Properties allow the > repository to check that the Transformation applied is acceptable. > It is well worth noting that Preservation Objectives may be the same for a > great many of the separate pieces of Content Information. Similarly the > Transformational Information Properties may be the same for many Content > Data Objects. > > 4.1.1.4 The repository shall have a record of the Content Information and > the Preservation Objectives that it will preserve. 1. It is not a question of preserving the Preservation Objectives. It is a question of preserving the functionalities of the Content Information as documented in the Preservation Objectives. 2. Shouldn't this include the TIPs as well? > > Supporting Text > This is necessary in order to identify in writing the Content Information > Objects for which it has taken preservation responsibility and the > Preservation Objectives it has committed to check for those records based on > their Content Information. Shouldn't this include the TIPs as well? > > Examples of Ways the Repository Can Demonstrate It Is Meeting This > Requirement > Preservation Policies, processing manuals, collection inventories or > surveys, logs of Content Information types, acquired preservation > strategies, and action plans. The repository should have sets of Preservation Objectives and TIPs that cover every AIP (Content Information?) in its holdings. > > Discussion > The repository must demonstrate that it establishes and maintains an > understanding of its digital collections sufficient to carry out the > preservation necessary to ensure the Designated Community(ies) can catty out "catty" should be "carry" > the specified Preservation Objectives. The repository can use this > information to determine the effectiveness of its preservation activities > over time. > Also > > Change > FROM > 4.2.5.2 The repository shall have tools or methods to determine what > Representation Information is necessary to make each Data Object > understandable to the Designated Community. > > TO: > 4.2.5.2 The repository shall have tools or methods to determine what > Representation Information is necessary to make each Data Object > understandable to the Designated Community in ways exemplified by the > Preservation Objectives. 1. "each Data Object" should be "the Content Information of each AIP" 2. Shouldn't this include the TIPs as well? > > Also change > FROM: > 4.2.7 The repository shall ensure that the Content Information of the AIPs > is understandable for their Designated Community at the time of creation of > the AIP. > > TO: > 4.2.7 The repository shall ensure that the Content Information of the AIPs > is understandable for their Designated Community, in ways exemplified by the > Preservation Objectives, at the time of creation of the AIP. Shouldn't this include the TIPs as well? > > Also change > FROM: > 4.3.2.1 The repository shall have mechanisms in place for monitoring and > notification when Representation Information is inadequate for the > Designated Community to understand the data holdings. > > TO: > 4.3.2.1 The repository shall have mechanisms in place for monitoring and > notification when Representation Information, or the Context Data Object > itself, is inadequate for the Designated Community to understand the data > holdings in ways exemplified by the Preservation Objectives. "Context" should be "Content" > > In 4.3.3.1 Supporting Text > From: > ... ensure that the preserved information remains understandable and usable > by the Designated Community ... > To: > ... ensure that the preserved information remains understandable and usable > by the Designated Community, as exemplified by the associated Preservation > Objectives ... Shouldn't this include the TIPs as well?
(In reply to David Giaretta from comment #13) > The following are my Consolidated Changes including all the previous > suggests and comments and also http://review.oais.info/show_bug.cgi?id=310 > (which I will mark as a duplicate of this suggested change) > > 4.1.1 The repository shall identify the Content Information and the > Information Properties that the repository will preserve. > > To: > > 4.1.1 The repository shall identify the Content Information and associated > Preservation Objectives and Transformational Information Properties that the > repository will preserve. I don't think a change from Information Properties to Transformation Information Properties should be made. Repository should identify all Information Properties it will preserve, not just the TIPs. The same objection can be made several times for the sub-metrics. Skipped changes in 4.3.2 Supporting Text and Discussion From: ... ensure that the preserved information remains understandable and usable by the Designated Community ... To: ... ensure that the preserved information remains understandable and usable by the Designated Community, as exemplified by the associated Preservation Objectives ...
(In reply to Mark Conrad from comment #15) > (In reply to David Giaretta from comment #13) > > The following are my Consolidated Changes including all the previous > > suggests and comments and also http://review.oais.info/show_bug.cgi?id=310 > > (which I will mark as a duplicate of this suggested change) > > > > Change: > > > > In 3.3.1 > > add to end of 1st Discussion paragraph > > "In addition to and associated with the definition of the Designated > > Community, Preservation Objectives will be defined." > > > > > > In 3.3.2 Discussion > > From: > > In another example the repository may be required by the strategic plan to > > keep its data understandable. The preservation policy might then include > > information about the expected level of understandability by the > > repository’s Designated Community for each Archival Information Package. > > To: > > In another example the repository may be required by the strategic plan to > > keep its data understandable by the Designated Communities for the > > repository's AIPs. The preservation policy might then include information > > about the expected level of understandability for each Archival Information > > Package, as exemplified by the associated Preservation Objectives. > > Shouldn't this mention TIPs as well? They are mentioned elsewhere, when we talk about Transformations. > > > > > > 4.1.1 The repository shall identify the Content Information and the > > Information Properties that the repository will preserve. > > > > To: > > > > 4.1.1 The repository shall identify the Content Information and associated > > Preservation Objectives and Transformational Information Properties that > the > > repository will preserve. > > > > Also ADD > > > > 4.1.1.3 The repository shall have a procedure(s) for identifying those > > Preservation Objectives and Transformational Information Properties for the > > Content Information it will preserve. > > > > Supporting Text > > This is necessary to establish a clear understanding with depositors, > > funders, and the repository’s Designated Communities how the repository > > determines and checks what the Designated Community would be expected to be > > able to do with the Content Information. These procedures will be necessary > > to confirm that the Content Information remains understandable/usable. The > > Transformational Information Properties establish a clear understanding of > > the tests which determine whether a Transformation of an object is > > acceptable. > > > > Examples of Ways the Repository Can Demonstrate It Is Meeting This > > Requirement > > Definitions of the Preservation Objectives and Transformational Information > > Properties applicable to each Content Information Object; submission > > agreements/deposit agreements, Preservation Policies, written processing > > procedures, workflow documentation. > > > > Discussion > > These procedure(s) document the methods and factors a repository uses to > > determine the acceptability of different types of preservation activities > > for the Content Information for which it accepts preservation > responsibility > > to its designated communities. > > For example, a repository’s preservation plans and policies may require the > > Context Data Objects to remain unchanged then as the Designated Community’s > > 1. Context should be Content? See later in the paragraph. Yes, a typo > 2. Data Objects cannot "remain unchanged" if they are to be preserved over > the long term. Later in the paragraph it says that the Data Objects cannot > be Transformed - not that they must remain unchanged. This is just an example - i.e. "may require" > > > Knowledge Base changes, additional Representation Information must be > > provided; the Preservation Objectives allow the repository to check that > > enough Representation Information has been supplied. In this case since > > Transformations will not be allowed then the Transformation Information > > Properties would be to note that Transformations are not allowed and so the > > Content Data Objects are to be unchanged. > > On the other hand if Transformations are allowed by the repository’s plans > > and policies then the Transformational Information Properties allow the > > repository to check that the Transformation applied is acceptable. > > It is well worth noting that Preservation Objectives may be the same for a > > great many of the separate pieces of Content Information. Similarly the > > Transformational Information Properties may be the same for many Content > > Data Objects. > > > > 4.1.1.4 The repository shall have a record of the Content Information and > > the Preservation Objectives that it will preserve. > > 1. It is not a question of preserving the Preservation Objectives. It is a > question of preserving the functionalities of the Content Information as > documented in the Preservation Objectives. Surely one needs to know what the Preservation Objectives are. Given those then, if they mention functionalities, Mark's comment would automatically follow. > > 2. Shouldn't this include the TIPs as well? I think these are covered elsewhere. > > > > > Supporting Text > > This is necessary in order to identify in writing the Content Information > > Objects for which it has taken preservation responsibility and the > > Preservation Objectives it has committed to check for those records based > on > > their Content Information. > > Shouldn't this include the TIPs as well? I think these are covered elsewhere. > > > > > Examples of Ways the Repository Can Demonstrate It Is Meeting This > > Requirement > > Preservation Policies, processing manuals, collection inventories or > > surveys, logs of Content Information types, acquired preservation > > strategies, and action plans. > > The repository should have sets of Preservation Objectives and TIPs that > cover every AIP (Content Information?) in its holdings. Yes > > > > > Discussion > > The repository must demonstrate that it establishes and maintains an > > understanding of its digital collections sufficient to carry out the > > preservation necessary to ensure the Designated Community(ies) can catty > out > > "catty" should be "carry" Yes > > > the specified Preservation Objectives. The repository can use this > > information to determine the effectiveness of its preservation activities > > over time. > > Also > > > > Change > > FROM > > 4.2.5.2 The repository shall have tools or methods to determine what > > Representation Information is necessary to make each Data Object > > understandable to the Designated Community. > > > > TO: > > 4.2.5.2 The repository shall have tools or methods to determine what > > Representation Information is necessary to make each Data Object > > understandable to the Designated Community in ways exemplified by the > > Preservation Objectives. > > 1. "each Data Object" should be "the Content Information of each AIP" To avoid some circularity this should be 4.2.5.2 The repository shall have tools or methods to determine what Representation Information is necessary use with the Data Object to make the resulting Information Object understandable to the Designated Community in ways exemplified by the Preservation Objectives. > > 2. Shouldn't this include the TIPs as well? That is covered separately. > > > > > Also change > > FROM: > > 4.2.7 The repository shall ensure that the Content Information of the AIPs > > is understandable for their Designated Community at the time of creation of > > the AIP. > > > > TO: > > 4.2.7 The repository shall ensure that the Content Information of the AIPs > > is understandable for their Designated Community, in ways exemplified by > the > > Preservation Objectives, at the time of creation of the AIP. > > Shouldn't this include the TIPs as well? That is covered separately. > > > > > Also change > > FROM: > > 4.3.2.1 The repository shall have mechanisms in place for monitoring and > > notification when Representation Information is inadequate for the > > Designated Community to understand the data holdings. > > > > TO: > > 4.3.2.1 The repository shall have mechanisms in place for monitoring and > > notification when Representation Information, or the Context Data Object > > itself, is inadequate for the Designated Community to understand the data > > holdings in ways exemplified by the Preservation Objectives. > > "Context" should be "Content" Yes a typo > > > > > In 4.3.3.1 Supporting Text > > From: > > ... ensure that the preserved information remains understandable and usable > > by the Designated Community ... > > To: > > ... ensure that the preserved information remains understandable and usable > > by the Designated Community, as exemplified by the associated Preservation > > Objectives ... > > Shouldn't this include the TIPs as well? See above
(In reply to John Garrett from comment #16) > (In reply to David Giaretta from comment #13) > > The following are my Consolidated Changes including all the previous > > suggests and comments and also http://review.oais.info/show_bug.cgi?id=310 > > (which I will mark as a duplicate of this suggested change) > > > > > 4.1.1 The repository shall identify the Content Information and the > > Information Properties that the repository will preserve. > > > > To: > > > > 4.1.1 The repository shall identify the Content Information and associated > > Preservation Objectives and Transformational Information Properties that > the > > repository will preserve. > > I don't think a change from Information Properties to Transformation > Information Properties should be made. Repository should identify all > Information Properties it will preserve, not just the TIPs. The TIPs ARE the Information Properties it will preserve aren't they. I agree that there could be some overlap between Preservation Objectives and Information Properties but we introduced the latter in order to lead into TIPs. > > The same objection can be made several times for the sub-metrics. > > See above > > > Skipped changes in 4.3.2 Supporting Text and Discussion > From: > ... ensure that the preserved information remains understandable and usable > by the Designated Community ... > To: > ... ensure that the preserved information remains understandable and usable > by the Designated Community, as exemplified by the associated Preservation > Objectives ... Yes
The following are my Consolidated Changes including all the previous suggests and comments. Change: In 3.3.1 add to end of 1st Discussion paragraph "In addition to and associated with the definition of the Designated Community, Preservation Objectives will be defined." In 3.3.2 Discussion From: In another example the repository may be required by the strategic plan to keep its data understandable. The preservation policy might then include information about the expected level of understandability by the repository’s Designated Community for each Archival Information Package. To: In another example the repository may be required by the strategic plan to keep its data understandable by the Designated Communities for the repository's AIPs. The preservation policy might then include information about the expected level of understandability for each Archival Information Package, as exemplified by the associated Preservation Objectives. 4.1.1 The repository shall identify the Content Information and the Information Properties that the repository will preserve. To: 4.1.1 The repository shall identify the Content Information and associated Preservation Objectives and Transformational Information Properties that the repository will preserve. Also ADD 4.1.1.3 The repository shall have a procedure(s) for identifying those Preservation Objectives and Transformational Information Properties for the Content Information it will preserve. Supporting Text This is necessary to establish a clear understanding with depositors, funders, and the repository’s Designated Communities how the repository determines and checks what the Designated Community would be expected to be able to do with the Content Information. These procedures will be necessary to confirm that the Content Information remains understandable/usable. The Transformational Information Properties establish a clear understanding of the tests which determine whether a Transformation of an object is acceptable. Examples of Ways the Repository Can Demonstrate It Is Meeting This Requirement Definitions of the Preservation Objectives and Transformational Information Properties applicable to each Content Information Object; submission agreements/deposit agreements, Preservation Policies, written processing procedures, workflow documentation. Discussion These procedure(s) document the methods and factors a repository uses to determine the acceptability of different types of preservation activities for the Content Information for which it accepts preservation responsibility to its designated communities. For example, a repository’s preservation plans and policies may require the Content Data Objects to remain unchanged then as the Designated Community’s Knowledge Base changes, additional Representation Information must be provided; the Preservation Objectives allow the repository to check that enough Representation Information has been supplied. In this case since Transformations will not be allowed then the Transformation Information Properties would be to note that Transformations are not allowed and so the Content Data Objects are to be unchanged. On the other hand, if Transformations are allowed by the repository’s plans and policies then the Transformational Information Properties allow the repository to check that the Transformation applied is acceptable. It is well worth noting that Preservation Objectives may be the same for a great many of the separate pieces of Content Information. Similarly, the Transformational Information Properties may be the same for many Content Data Objects. 4.1.1.4 The repository shall have a record of the Content Information and the Preservation Objectives that it will preserve. Supporting Text This is necessary in order to identify in writing the Content Information Objects for which it has taken preservation responsibility and the Preservation Objectives it has committed to check for those records based on their Content Information. Examples of Ways the Repository Can Demonstrate It Is Meeting This Requirement Preservation Policies, processing manuals, collection inventories or surveys, logs of Content Information types, acquired preservation strategies, Preservation Objectives, TIPs and action plans. Discussion The repository must demonstrate that it establishes and maintains an understanding of its digital collections sufficient to carry out the preservation necessary to ensure the Designated Community(ies) can carry out the specified Preservation Objectives. The repository can use this information to determine the effectiveness of its preservation activities over time. Also Change FROM 4.2.5.2 The repository shall have tools or methods to determine what Representation Information is necessary to make each Data Object understandable to the Designated Community. TO: 4.2.5.2 The repository shall have tools or methods to determine what Representation Information is necessary use with the Data Object to make the resulting Information Object understandable to the Designated Community in ways exemplified by the Preservation Objectives. Also change FROM: 4.2.7 The repository shall ensure that the Content Information of the AIPs is understandable for their Designated Community at the time of creation of the AIP. TO: 4.2.7 The repository shall ensure that the Content Information of the AIPs is understandable for their Designated Community, in ways exemplified by the Preservation Objectives, at the time of creation of the AIP. 4.3.2 Supporting Text and Discussion From: ... ensure that the preserved information remains understandable and usable by the Designated Community ... To: ... ensure that the preserved information remains understandable and usable by the Designated Community, as exemplified by the associated Preservation Objectives ... Also change FROM: 4.3.2.1 The repository shall have mechanisms in place for monitoring and notification when Representation Information is inadequate for the Designated Community to understand the data holdings. TO: 4.3.2.1 The repository shall have mechanisms in place for monitoring and notification when Representation Information, or the Content Data Object itself, is inadequate for the Designated Community to understand the data holdings in ways exemplified by the Preservation Objectives. In 4.3.3.1 Supporting Text From: ... ensure that the preserved information remains understandable and usable by the Designated Community ... To: ... ensure that the preserved information remains understandable and usable by the Designated Community, as exemplified by the associated Preservation Objectives ...
There are a number of proposed changes in Section 3.3. I think this is highlighting a possible problem there. The Preservation Objectives and the Designated Community are associated with individual AIPs or classes of AIPs. Are these discussions out of place in Section 3?
(In reply to John Garrett from comment #20) > There are a number of proposed changes in Section 3.3. I think this is > highlighting a possible problem there. The Preservation Objectives and the > Designated Community are associated with individual AIPs or classes of AIPs. > Are these discussions out of place in Section 3? I don't see a problem - 3.3 is about Preservation Policy Framework and so should mention things like the need to define Designated Community (3.3.1). Other than that Designated Community and Preservation Objectives are in the discussion text.
DAI20200929 Agree with change in Comment 19 but Change In 3.3.1 add to end of 1st Discussion paragraph "In addition to and associated with the definition of the Designated Community, Preservation Objectives will be defined." to In 3.3.1 add to end of 1st Discussion paragraph "In addition to and associated with the definition of each Designated Community, Preservation Objectives applicable to each AIP or class of AIPs will be defined."