Datasets:
Al-Alcoba-Inciarte
/
Intp_Demo

Dataset card Data Studio Files
xet
 Community
1
text
stringlengths
195
512
preserving digital content. This requirement does not mean that the organization must make information which would make it vulnerable to competitors available, but rather that the organization commits to disclosing its methods for preserving digital content at least to the Designated Community or other appropriate...
er 2011 3.3.5 The repository shall define, collect, track, and appropriately provide its information integrity measurements. Supporting Text This is necessary in order to provide documentation that it has developed or adapted appropriate measures for ensuring the integrity of its holding. Examples of Ways the Rep...
n of the procedures and mechanisms for monitoring integrity measurements and for responding to results of integrity measurements that indicate digital content is at risk; an audit process for collecting, tracking, and presenting integrity measurements; Preservation Policy and workflow documentation. Discussion The...
of its holdings. If protocols, rules and mechanisms are embedded in the repository software, there should be some way to demonstrate the implementation of integrity measures. 3.3.6 The repository shall commit to a regular schedule of self-assessment and external certification. Supporting Text This is necessary in...
dated checklists from self-assessments and/or third-party audits; certificates awarded for compliance with relevant ISO standards; timetables and evidence of adequate budget allocations for future certification. Discussion A one-time check on trustworthiness is not adequate because many things will change over tim...
4.1 The repository shall have short- and long-term business planning processes in place to sustain the repository over time. Supporting Text This is necessary in order to ensure the viability of the repository over the period of time it has promised to provide access to its contents for its Designated Community. E...
l forecasts with multiple budget scenarios; contingency plans; market analysis. Discussion An annual business planning process is commonly accepted as the standard for most organizations. 3.4.2 The repository shall have financial practices and procedures which are transparent, compliant with relevant accounting s...
ward activity that might threaten the economic viability of the repository. Examples of Ways the Repository Can Demonstrate It Is Meeting This Requirement Demonstrated dissemination requirements for business planning and practices; citations to and/or examples of accounting and audit requirements, standards, and pr...
mpliant, and auditable. Confidentiality requirements may prohibit making information about the repository’s finances public, but the repository should be able to demonstrate that it is satisfying the needs of its Designated Community. AUDIT AND CERTIFICATION OF TRUSTWORTHY DIGITAL REPOSITORIES CCSDS 652.0-M-1 Page...
abilities). Supporting Text This is necessary in order to demonstrate that the repository has identified and documented these categories, and actively manages them, including identifying and responding to risks, describing and leveraging benefits, specifying and balancing investments, and anticipating and preparin...
lemented responses (a risk register); technology infrastructure investment planning documents; cost/benefit analyses; financial investment documents and portfolios; requirements for and examples of licenses, contracts, and asset management; evidence of revision based on risk. Discussion The repository should have ...
iate contracts or deposit agreements for digital materials that it manages, preserves, and/or to which it provides access. Supporting Text This is necessary in order to ensure that the repository has the rights and authorizations needed to enable it to collect and preserve digital content over time, make that info...
ecuted deposit agreements and licenses in accordance with local, national, and international laws and regulations; policies on third-party deposit arrangements; definitions of service levels and permitted uses; repository policies on the treatment of ‘orphan works’ and copyright dispute resolution; reports of indepe...
CCSDS 652.0-M-1 Page 3-12 September 2011 Discussion Repositories may need to show evidence that their contracts are being followed. This is especially important for those with third-party deposit arrangements. These arrangements may require the repository to guarantee that relevant contracts, licenses, or depos...
ent. When the relationship between depositor and repository is less formal (e.g., a faculty member depositing work in an academic institution’s preservation repository), documentation articulating the repository’s capabilities and commitments should be provided to each depositor. Repositories engaged in Web harvesti...
equired. Some repositories capture, manage, and preserve access to this material without written permission from the content creators. Others go through the very time-consuming and costly process of contacting content owners before capturing and ingesting information. Ideally, agreements are tracked, linked, manage...
ts transferred shall be documented. Supporting Text This is necessary in order to have sufficient control of the information for preservation and limit the repository’s exposure to liability or legal and financial harm. Examples of Ways the Repository Can Demonstrate It Is Meeting This Requirement Contracts, depo...
ht to change or alter digital information is often restricted by law to the creator, it is important that digital repository contracts and agreements address the need to be able to work with and potentially modify digital objects to keep them accessible. Repository agreements with depositors must specify and/or tran...
ally preventing or slowing the ingest of digital objects at risk, it is acceptable for a digital repository to take in or accept digital objects even with only minimal preservation rights using an open-ended agreement and then deal with expanding to detailed rights later. AUDIT AND CERTIFICATION OF TRUSTWORTHY DIGI...
n agreements with depositors and other relevant parties. Supporting Text This is necessary in order to ensure that the respective roles of repository, producers, and contributors in the depositing of digital content and transfer of responsibility for preservation are understood and accepted by all parties. Exampl...
. Discussion The deposit agreement specifies all aspects of these issues that are necessary for the repository to carry out its function. There may be a single agreement covering all deposits, or specific agreements for each deposit, or a standard agreement supplemented by special conditions for some deposits. The...
perty rights in the digital objects. Agreements may place responsibilities on depositors, such as ensuring that Submission Information Packages (SIPs) conform to some pre-agreed standards, and may allow repositories to refuse SIPs that do not meet these standards. Other repositories may take responsibility for fixin...
te that it does not need such agreements because, for instance, it has a legal mandate for its activities. An agreement should include, at a minimum, property rights, access rights, conditions for withdrawal, level of security, level of finding aids, SIP definitions, time, volume, and content of transfers. One examp...
ate when it accepts preservation responsibility for contents of each set of submitted data objects. Supporting Text This is necessary in order to avoid misunderstandings between the repository and producer/depositor as to when and how the transfer of responsibility for the digital content occurs. AUDIT AND CERTIF...
ssion agreements, deposit agreements, and deeds of gift; confirmation receipt sent back to producer/depositor. Discussion If this requirement is not met, there is a risk that, for example, the original is erased before the repository has taken responsibility for the submitted data objects. Without the understandin...
eserved since they had already been ingested by the repository. For example, for convenience the repository could receive a copy of raw science data from the instrument at the same time the science team gets it, but the science team would have responsibility for it until they turn over responsibility to the final re...
y depend on repository responsibilities as designated in the depositor agreement.) A repository may mark the transfer by sending a formal document, often a final signed copy of the transfer agreement, back to the depositor signifying the completion of the transformation from SIP to AIP process. Other approaches are...
ability and challenges to ownership/rights. Supporting Text This is necessary in order to minimize potential liability and challenges to the rights of the repository. Examples of Ways the Repository Can Demonstrate It Is Meeting This Requirement A definition of rights, licenses, and permissions to be obtained fro...
that do not inhibit preservation; records of relevant legal advice sought and received. Discussion The repository’s Preservation Policies and Preservation Implementation Plans and mechanisms should be vetted by appropriate institutional authorities and/or legal experts to ensure that responses to challenges adhere...
September 2011 3.5.2 The repository shall track and manage intellectual property rights and restrictions on use of repository content as required by deposit agreement, contract, or license. Supporting Text This is necessary in order to allow the repository to track, act on, and verify rights and restrictions rel...
specifies the repository’s requirements and process for managing intellectual property rights; depositor agreements; samples of agreements and other documents that specify and address intellectual property rights; documentation of monitoring by repository over time of changes in status and ownership of intellectual...
ses and contracts to which it is obligated. Whatever the format of the tracking system, it must be sufficient for the institution to track, act on, and verify rights and restrictions related to the use of the digital objects within the repository. AUDIT AND CERTIFICATION OF TRUSTWORTHY DIGITAL REPOSITORIES CCSDS...
ies that the repository will preserve. Supporting Text This is necessary in order to make it clear to funders, depositors, and users what responsibilities the repository is taking on and what aspects are excluded. It is also a necessary step in defining the information which is needed from the information producers...
rvation Policy documents, including written definition of properties as agreed in the deposit agreement/deed of gift; written processing procedures; documentation of properties to be preserved. Discussion This process begins in general with the repository’s mission statement and may be further specified in pre-acc...
documentation. For example, one repository may only commit to preserving the textual content of a document and not its exact appearance on a screen. Another may wish to preserve the exact appearance and layout of textual documents, while others may choose to keep the units of the measurement of data fields and to no...
itory shall have a procedure(s) for identifying those Information Properties that 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 characteristics and proper...
. AUDIT AND CERTIFICATION OF TRUSTWORTHY DIGITAL REPOSITORIES CCSDS 652.0-M-1 Page 4-2 September 2011 Examples of Ways the Repository Can Demonstrate It Is Meeting This Requirement Definitions of the Information Properties which should be preserved; submission agreements/deposit agreements, Preservation Policies...
tent 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 demo...
ent Information and the Information Properties that it will preserve. Supporting Text This is necessary in order to identify in writing the Content Information of the records for which it has taken preservation responsibility and the Information Properties it has committed to preserve for those records based on th...
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 persist the properties to which it has committed. The reposit...
with specific Content Information at the time of its deposit. Supporting Text This is necessary in order that there is a clear understanding of what needs to be acquired from the Producer. AUDIT AND CERTIFICATION OF TRUSTWORTHY DIGITAL REPOSITORIES CCSDS 652.0-M-1 Page 4-3 September 2011 Examples of Ways the Re...
o be ingested, the repository should have written criteria, prepared by the repository on its own or in conjunction with other parties, that specify exactly what digital object(s) are transferred, what documentation is associated with the object(s), and any restrictions on access, whether technical, regulatory, or d...
created by the repository. The level of precision in these specifications will vary with the nature of the repository’s collection policy and its relationship with creators. For instance, repositories engaged in Web harvesting, or those that rescue digital materials long after their creators have abandoned them, c...
the HTTP transactions that captured a site are to be preserved along with the site’s files, and this still constitutes ‘information associated with the digital material’. They may also choose to record the information or decisions—whether taken by humans or by automated algorithms—that led to the site’s being captu...
SIPs. Supporting Text This is necessary in order to be sure that the repository is able to extract information from the SIPs. Examples of Ways the Repository Can Demonstrate It Is Meeting This Requirement Packaging Information for the SIPs; Representation Information for the SIP Content Data, including documente...
egard to the technical construction of its components. For example, the repository needs to be able to recognize a TIFF file and confirm that it is not simply a file with a filename ending in ‘TIFF’. Another example, would be a website for which the repository would need to be able to recognize and test the validit...
ORTHY DIGITAL REPOSITORIES CCSDS 652.0-M-1 Page 4-4 September 2011 is what the repository expected; 2) the Content Information is correctly identified; and 3) the properties of the Content Information to be preserved have been appropriately selected. 4.1.4 The repository shall have mechanisms to appropriately ver...
ys the Repository Can Demonstrate It Is Meeting This Requirement Legally binding submission agreements/deposit agreements/deeds of gift, evidence of appropriate technological measures; logs from procedures and authentications. Discussion The repository’s written standard operating procedures and actual practices mu...
ories will adopt different levels of proof needed; the Designated Community should have the opportunity to review the evidence. 4.1.5 The repository shall have an ingest process which verifies each SIP for completeness and correctness. Supporting Text This is necessary in order to detect and correct errors in the...
ervation Policy and Preservation Implementation Plan documents and system log files from system(s) performing ingest procedure(s); logs or registers of files received during the transfer and ingest process; documentation of standard operating procedures, detailed procedures, and/or workflows; format registries; def...
he data transfer and ingest process. Other sources will include technical and descriptive metadata obtained prior to ingest and may also include expectations set by the depositor, the object producer, a format registry, or the AUDIT AND CERTIFICATION OF TRUSTWORTHY DIGITAL REPOSITORIES CCSDS 652.0-M-1 Page 4-5 Se...
correctness. It can mean simply checking that file formats are what they claim to be (TIFF files are valid TIFF format, for instance), or can imply checking the content. This might involve human checking in some cases, such as confirming that the description of a picture matches the image. This allows the repository...
d actions such as rejecting the transfer, suspending processing until the missing information is received, or simply reporting the errors. Similarly, the definition of ‘completeness’ should be appropriate to a repository’s activities. If an inventory of files was provided by a producer as part of pre-ingest negotia...
of completeness and correctness. One thing that a repository might want to do is check for network drop out or other corruption during the transmission process. 4.1.6 The repository shall obtain sufficient control over the Digital Objects to preserve them. Supporting Text This is necessary in order to ensure that ...
showing the level of physical control the repository actually has. A separate database/metadata catalog listing all of the digital objects in the repository and metadata sufficient to validate the integrity of those objects (file size, checksum, hash, location, number of copies, etc.) Discussion The repository mu...
r Preservation Implementation Plan for that data and to distribute it to their consumers. For example, in cases where SIPs only reference digital objects, the repository must also reference the digital objects or preserve them if the current repository is not committed to such preservation. 4.1.7 The repository sh...
4-6 September 2011 Supporting Text This is necessary in order to ensure that the producer can verify that there are no inadvertent lapses in communication which might otherwise allow loss of SIPs. Examples of Ways the Repository Can Demonstrate It Is Meeting This Requirement Submission agreements/deposit agreeme...
ocessing plan and agreement between the repository and the producer/depositor, the repository must provide the producer/depositor with progress reports at agreed points throughout the ingest process. Repository responses can range from nothing at all to predetermined, periodic reports of the ingest completeness and ...
ufficient. 4.1.8 The repository shall have contemporaneous records of actions and administration processes that are relevant to content acquisition. Supporting Text This is necessary to ensure that such documentation, which may be needed in an audit, is captured and is accurate and authentic. Examples of Ways the...
ts, confirmation receipts sent back to providers. Discussion These records should be created on or about the time of the actions they refer to and are related to actions taken during the Ingest: Acquisition of Content process (4.1). The records may be automated or may be written by individuals, depending on the nat...
E AIP 4.2.1 The repository shall have for each AIP or class of AIPs preserved by the repository an associated definition that is adequate for parsing the AIP and fit for long- term preservation needs. AUDIT AND CERTIFICATION OF TRUSTWORTHY DIGITAL REPOSITORIES CCSDS 652.0-M-1 Page 4-7 September 2011 Supporting T...
.1 The repository shall be able to identify which definition applies to which AIP. Supporting Text This is necessary to ensure that the appropriate definition is used when parsing/interpreting an AIP. Examples of Ways the Repository Can Demonstrate It Is Meeting This Requirement Documentation clearly linking each ...
the two entities. 4.2.1.2 The repository shall have a definition of each AIP that is adequate for long- term preservation, enabling the identification and parsing of all the required components within that AIP. Supporting Text This is necessary in order to explicitly show that the AIPs are fit for their intended p...
s of Ways the Repository Can Demonstrate It Is Meeting This Requirement Demonstration of the use of the definitions to extract Content Information and PDI (Provenance, Access Rights, Context, Reference, and Fixity Information) from AIPs. It should be noted that the Provenance of a digital object, for example, may be...
mentations may, for example, involve some combination of files, databases, and/or documents. Documentation shall relate the AIP component’s contents to the related preservation needs of the repository, with enough detail for the repository’s providers and consumers to be confident that the significant properties of ...
eptember 2011 Information and Provenance can be managed and kept up to date. The repository should clearly identify when new versions of AIPs need to be created in order to keep them fit for purpose. The external dependencies of the AIP should also be recorded. Definitions should exist for each AIP, or class of AIP...
sitories will establish class descriptions that apply to many AIPs. It must be possible to determine which definition applies to which AIP. It may also be necessary for the definitions to say something about the semantics or intended use of the AIPs if this could affect long-term preservation decisions. For example,...
ages intended for viewing by people and has a single definition covering all of its AIPs. (The definition may refer to a local or external definition of the TIFF format.) Repository 2 contains some images, such as medical x-rays, that are intended for computer analysis rather than viewing by the human eye, and other...
pend on the intended use of the image— an action that changes the bit-depth of the image in a way that is not perceivable to the human eye may be satisfactory for real-world photographs but not for medical images, for example. An AIP contains these key components: the primary data object to be preserved, its support...
primary data object: Fixity, Provenance, Context, and Reference. There should be a definition of how these categories of information are linked. 4.2.2 The repository shall have a description of how AIPs are constructed from SIPs. Supporting Text This is necessary in order to ensure that the AIP(s) adequately repres...
clear documentation of how AIPs are derived from SIPs. Discussion In some cases, the AIP and SIP will be almost identical apart from packaging and location, and the repository need only state this. In other cases, complex transformations (e.g., data normalization) may be applied to objects during the ingest proces...
should include documentation that gives a detailed description of the ingest process for each SIP to AIP AUDIT AND CERTIFICATION OF TRUSTWORTHY DIGITAL REPOSITORIES CCSDS 652.0-M-1 Page 4-9 September 2011 transformation, typically consisting of an overview of general processing being applied to all such transfor...
omplex descriptions case by case. Under such circumstances case diaries or logs of actions taken to produce each AIP should be created and maintained. In these cases, documentation should be mapped to individual AIPs, and the mapping should be available for examination. Other repositories that can run a more produc...
le example, two separate processes each produce a TIFF file, it must be clear which process was applied to produce a particular TIFF file. 4.2.3 The repository shall document the final disposition of all SIPs. In particular the following aspect must be checked. 4.2.3.1 The repository shall follow documented procedu...
Ps received have been dealt with appropriately, and in particular have not been accidentally lost. Examples of Ways the Repository can Demonstrate it is Meeting these Requirements System processing files; disposal records; donor or depositor agreements/deeds of gift; provenance tracking system; system log files; pr...
curs; documentation of normalization outcome and how the resulting AIP is different from the SIP(s). Discussion The timescale of this process will vary between repositories from seconds to many months, but SIPs must not remain in an unprocessed limbo-like state forever. The accessioning procedures and the internal...
iptive information should also document the provenance of all digital objects. 4.2.4 The repository shall have and use a convention that generates persistent, unique identifiers for all AIPs. AUDIT AND CERTIFICATION OF TRUSTWORTHY DIGITAL REPOSITORIES CCSDS 652.0-M-1 Page 4-10 September 2011 In particular the f...
tory shall assign and maintain persistent identifiers of the AIP and its components so as to be unique within the context of the repository. 4.2.4.1.3 Documentation shall describe any processes used for changes to such identifiers. 4.2.4.1.4 The repository shall be able to provide a complete list of all such identi...
ts. Supporting Text This is necessary in order to ensure that each AIP can be unambiguously found in the future. This is also necessary to ensure that each AIP can be distinguished from all other AIPs in the repository. Examples of Ways the Repository Can Demonstrate It Is Meeting This Requirement Documentation d...
iquely identified object, regardless of its physical location. Supporting Text This is necessary in order that actions relating to AIPs can be traced over time, over system changes, and over storage changes. Examples of Ways the Repository Can Demonstrate It Is Meeting This Requirement Documentation describing nam...
its materials uniquely and persistently for use both in and outside the AUDIT AND CERTIFICATION OF TRUSTWORTHY DIGITAL REPOSITORIES CCSDS 652.0-M-1 Page 4-11 September 2011 repository. The ‘visibility’ requirement here means ‘visible’ to repository managers and auditors. It does not imply that these unique ident...
aceability. Subsection 4.2.1 requires that the components of an AIP be suitably bound and identified for long-term management, but places no restrictions on how AIPs are identified with files. Thus, in the general case, an AIP may be distributed over many files, or a single file may contain more than one AIP. There...
esources to provide authoritative Representation Information for all of the digital objects it contains. In particular the following aspects must be checked. 4.2.5.1 The repository shall have tools or methods to identify the file type of all submitted Data Objects. 4.2.5.2 The repository shall have tools or method...
presentation Information. 4.2.5.4 The repository shall have tools or methods to ensure that the requisite Representation Information is persistently associated with the relevant Data Objects. Supporting Text This is necessary in order to ensure that the repository’s digital objects are understandable to the Design...
ies); viewable records in local registries (with persistent links to digital objects); database records that include Representation Information and a persistent link to relevant digital objects. Discussion These tools and resources can be held internally or can be shared via, for example, a trusted set of registri...
N OF TRUSTWORTHY DIGITAL REPOSITORIES CCSDS 652.0-M-1 Page 4-12 September 2011 external registries.1 Any such registry is a specialized type of repository, which itself must be certified/trustworthy. The repository may use these types of standardized, authoritative information sources to identify and/or verify th...
h general Representation Information (e.g., format information) and specific Representation Information (e.g., meanings of individual fields within a dataset). Often the general information will be available in an external repository, but the local repository may need to maintain the instance-specific information. ...
o keep all such information locally there may be, for example, a schedule of updates which means that until an update is performed, the local Representation Information is incomplete. This may be regarded as a kind of local caching of, for example, the Representation Information held in registries. Alternatively one...
rmation about any and all Representation Information. Good practice suggests that any locally held Representation Information should also be made available to other repositories via a trusted registry. In addition any item of Representation Information should itself have adequate Representation Information to ensur...
on (PDI) for its associated Content Information and acquire PDI in accordance with the documented processes. In particular the following aspects must be checked. 4.2.6.1 The repository shall have documented processes for acquiring PDI. 4.2.6.2 The repository shall execute its documented processes for acquiring PDI....
rail to support claims of authenticity is available, that unauthorized changes to the digital holdings can be detected, and that the digital objects can be identified and placed in their appropriate context. 1 The Unified Digital Formats Registry (UDFR, http://www.gd...
ON OF TRUSTWORTHY DIGITAL REPOSITORIES CCSDS 652.0-M-1 Page 4-13 September 2011 Examples of Ways the Repository can Demonstrate it is Meeting these Requirements Standard operating procedures; manuals describing ingest procedures; viewable documentation on how the repository acquires and manages Preservation Descr...
nt Information is not corrupted (Fixity) and is findable (Reference Information), but to help ensure the Content Information is adequately understandable by providing a historical perspective (Provenance Information) and by providing relationships to other information (Context Information). The extent of such infor...
t Information of the AIPs is understandable for their Designated Community at the time of creation of the AIP. In particular the following aspects must be checked. 4.2.7.1 Repository shall have a documented process for testing understandability for their Designated Communities of the Content Information of the AIPs...
the AIP up to the required level of understandability if it fails the understandability testing. Supporting Text This is necessary in order to ensure that one of the primary tests of preservation, namely that the digital holdings are understandable by their Designated Community, can be met. (See 4.3 for additiona...
o ensure their understandability to the defined Designated Community; records of such tests being performed and evaluated; evidence of gathering or identifying Representation Information to fill any intelligibility gaps which have been found; retention of individuals with the discipline expertise. Discussion This ...
AND CERTIFICATION OF TRUSTWORTHY DIGITAL REPOSITORIES CCSDS 652.0-M-1 Page 4-14 September 2011 to make sure that the AIPs are understandable to the Designated Community(ies). For example, if documents are written in a dying language and the Designated Community is no longer able to understand the language the doc...
s in a language the Designated Community could understand or dictionaries that would allow the Designated Communities to translate the documents into a language its members understand). 4.2.8 The repository shall verify each AIP for completeness and correctness at the point it is created. Supporting Text This is ...
Demonstrate It Is Meeting This Requirement Description of the procedure that verifies completeness and correctness of the AIPs; logs of the procedure. Discussion The repository should be sure that the AIPs it creates are as they are expected to be by checking them against the associated definition for each AIP or...
and a demonstrably correct process for transforming SIPs into AIPs, then it simply needs to demonstrate that the initial checks were carried out successfully and that the transformation process was carried out without indicating errors. On the other hand repositories that must create unique processes for many of t...