Popular pages
Showing below up to 139 results starting with #1.
View (previous 250 | next 250) (20 | 50 | 100 | 250 | 500)
- Main Page (150,126 views)
- Definition of AIP (30,764 views)
- CLOCKSS: Extracting Triggered Content (28,692 views)
- LOCKSS: Format Migration (26,809 views)
- CLOCKSS: Ingest Pipeline (26,654 views)
- CLOCKSS: Box Operations (26,402 views)
- LOCKSS: Polling and Repair Protocol (25,900 views)
- LOCKSS: Software Development Process (17,136 views)
- CLOCKSS: Logging and Records (16,419 views)
- LOCKSS: Basic Concepts (16,238 views)
- LOCKSS: Extracting Bibliographic Metadata (15,526 views)
- LOCKSS: Property Server Operations (14,316 views)
- CLOCKSS: Threats and Mitigations (12,741 views)
- Definition of SIP (12,222 views)
- LOCKSS: Metadata Database (9,723 views)
- 3) Organizational Infrastructure (9,307 views)
- CLOCKSS: Succession Plan (7,283 views)
- CLOCKSS: Hardware and Software Inventory (7,115 views)
- CLOCKSS: Business Plan Overview (6,782 views)
- Definition of DIP (6,776 views)
- CLOCKSS: Business History (6,532 views)
- 3.3.3 Documented history of changes (6,031 views)
- CLOCKSS: Preservation Strategy (5,746 views)
- CLOCKSS: Governance and Organization (5,498 views)
- CLOCKSS: Designated Community (5,257 views)
- CLOCKSS: Collection Development (5,220 views)
- 4) Digital Object Management (5,169 views)
- CLOCKSS: Budget and Planning Process (5,109 views)
- CLOCKSS: Access Policy (5,095 views)
- 5) Infrastructure and Security Risk Management (5,018 views)
- CLOCKSS: Mandatory Responsibilities (4,998 views)
- 3.5.1.3 Policies about preservation responsibility (4,732 views)
- 4.2.7 Content Information is understandable for Designated Community at the time of AIP creation (3,846 views)
- CLOCKSS: Mission Statement (3,719 views)
- 3.3.5 Information integrity measurements (3,588 views)
- 5.1.2 Manage the number and location of copies of all digital objects (3,413 views)
- 3.1.1 Mission statement (3,343 views)
- 3.5.2 Track and manage property rights/restrictions (3,327 views)
- 3.3.2 Preservation policies (3,321 views)
- 3.5.1.4 Policies about liability and rights challenges (3,306 views)
- 3.3.4 Commit to transparency (3,304 views)
- 3.4.3 Risk, benefit, investment, expenditure (3,294 views)
- 4.2.1.2 Definition of each AIP (3,291 views)
- 3.4.1 Business planning processes (3,270 views)
- 3.1.2 Preservation strategic plan (3,269 views)
- 3.1.2.1 Succession, contigency, escrow plans (3,259 views)
- 3.4.2 Financial transparency, compliance, and audits (3,249 views)
- 3.1.3 Collection policy (3,246 views)
- 3.3.1 Designated community (3,236 views)
- 3.2.1.2 Appropriate number of staff (3,220 views)
- 3.2.1.1 Identified and established duties (3,219 views)
- 3.3.6 Self-assessment and external certification (3,198 views)
- 3.2.1 Identified duties and appointed staff (3,195 views)
- 3.2.1.3 Professional development program (3,173 views)
- 3.5.1 Contracts or deposit agreements for content (3,172 views)
- 5.1.1.1.5 Software technologies appropriate to the services it provides to its designated communities (3,158 views)
- 4.2.5.1 Tools or methods to identify the file types of all objects (3,156 views)
- 3.3.2.1 Review and update preservation policies (3,140 views)
- 3.1.2.2 Monitor environment for time to deploy succession, contingency, escrow (3,130 views)
- 5.1.1.4 Process to record and react to the availability of new security updates based on a risk-benefit assessment (3,122 views)
- 4.3.4 Provide evidence of the effectiveness of its preservation activities (3,105 views)
- 3.5.1.2 Completeness of agreements with depositors (3,090 views)
- 3.5.1.1 Contracts or deposit agreements for preservation rights (3,080 views)
- 5.1.1.1.1 Hardware technologies appropriate to the services it provides to its designated communities (3,042 views)
- 4.6.1 Comply with Access Policies (3,034 views)
- 5.1.1.5 Defined processes for storage media and/or hardware change (e.g., refreshing, migration) (2,225 views)
- 5.1.1.2 Adequate hardware and software support for backup functionality sufficient for preserving the repository content and tracking repository functions (2,160 views)
- 5.1.1.3.1 Record and report to its administration all incidents of data corruption or loss, and steps shall be taken to repair/replace (2,155 views)
- 4.2.9 Independent mechanism for verifying the integrity of the content (2,092 views)
- 5.1.1.3 Effective mechanisms to detect bit corruption or loss (2,089 views)
- 4.4.1.1 Preserve the Content Information of AIPs (2,055 views)
- 5.1.2.1 Mechanisms in place to ensure any/multiple copies of digital objects are synchronized (2,050 views)
- 4.4.2.1 Procedures for all actions taken on AIPs (2,041 views)
- 5.2.3 Staff shall have delineated roles, responsibilities, and authorizations related to implementing changes (2,038 views)
- 4.2.7.1 Processes for testing understandability for Designated Community of the Content Information of AIPs (2,031 views)
- 4.4.1.2 Actively monitor the integrity of AIPs (2,008 views)
- 4.3.1 Documented preservation strategies relevant to its holdings (2,002 views)
- 4.2.3 Document final disposition of all SIPs (1,937 views)
- 4.2.1.1 Identify which definition applies to which AIP (1,924 views)
- 4.1.5 Verify SIPs for completeness and correctness (1,923 views)
- 4.2.4.2 System of reliable linking/resolution services in order to find identified objects (1,921 views)
- 4.4.2.2 Demonstrate that any actions taken on AIPs were compliant with the specification of those actions (1,915 views)
- 4.1.7 Provide depositor with responses (1,901 views)
- 4.1.3 Recognition and parsing of SIPs (1,896 views)
- 4.1.2 Specify content information at deposit (1,892 views)
- 4.2.4.1 Uniquely identify each AIP (1,887 views)
- 4.1.4 Verify the identity of the Producer (1,886 views)
- 4.5.3 Create bi-directional linkages between each AIP and its descriptive information (1,880 views)
- 4.2.4 Convention that generates persistent, unique identifiers for AIPs (1,872 views)
- 4.2.6.1 Documented processes for acquiring PDI (1,872 views)
- 4.2.6.3 PDI is persistently associated with Content Information of AIP (1,862 views)
- 4.1.1 Identify content information and information properties (1,860 views)
- 5.1.1.1.2 Procedures in place to monitor and receive notifications when hardware technology changes are needed (1,857 views)
- 4.2.4.1.5 System of identifiers is adequate now and in the future (1,855 views)
- 4.2.6 Documented processes for acquiring PDI for associated Content Information (1,855 views)
- 5.1.1.6 Identified and documented critical processes that affect its ability to comply with its mandatory responsibilities (1,853 views)
- 5.1.1.1 Employ technology watches or other technology monitoring notification systems (1,853 views)
- 4.2.5.2 Tools or methods to determine what Representation Information is necessary for understandability (1,850 views)
- 4.2.3.1 Procedures if a SIP is not incorporated or discarded (1,848 views)
- 4.2.7.2 Execute testing process of Content Information of AIPs (1,845 views)
- 4.2.4.1.4 Provide a list of all identifiers and check for duplications (1,842 views)
- 5.2.2 Implemented controls to adequately address each of the defined security risks (1,837 views)
- 4.2.5 Tool and resources to provide authoritative Representation Information for all objects (1,835 views)
- 5.1.1.1.6 Procedures in place to monitor and receive notifications when software changes are needed (1,834 views)
- 4.1.6 Obtain sufficient control over digital objects (1,831 views)
- 4.2.8 Verify each AIP for completeness and correctness (1,831 views)
- 4.2.1 Associated definition for each AIP or class of AIPs (1,827 views)
- 4.2.5.3 Have access to the requisite Representation Information (1,825 views)
- 4.3.3.1 Mechanisms for creating, identifying or gathering any extra Representation Information required (1,824 views)
- 4.2.4.1.1 Have unique identifiers (1,821 views)
- 5.1.1.6.2 Process for testing and evaluating the effect of changes to the repository's critical processes (1,821 views)
- 4.1.8 Records of actions and processes related to acquisition (1,820 views)
- 5.1.1.1.3 Procedures in place to evaluate when changes are needed to current hardware (1,809 views)
- 4.2.2 Description of how AIPs are constructed from SIPs (1,804 views)
- 4.2.7.3 Bring Content Information of AIP up to level of understandability if it fails testing (1,804 views)
- 5.2.1 Maintain a systematic analysis of security risk factors associated with data, systems, personnel, and physical plant (1,797 views)
- 4.2.6.2 Execute documented processes for acquiring PDI (1,795 views)
- 5.1.1.1.8 Procedures, commitment and funding to replace software when evaluation indicates the need to do so (1,786 views)
- 4.1.1.2 Record of content information and information properties that we will preserve (1,786 views)
- 5.1.1 Identify and manage the risks to its preservation operations and goals associated with system infrastructure (1,784 views)
- 4.2.4.1.2 Assign and maintain persistent identifiers of the AIP and its components (1,783 views)
- 5.1.1.1.4 Procedures, commitment and funding to replace hardware when evaluation indicates the need to do so (1,782 views)
- 4.3.3 Mechanisms to change preservation plans as a result of its monitoring activities (1,772 views)
- 4.3.2.1 Mechanisms for monitoring and notification when Representation Information is inadequate for the Designated Community to understand the data holdings (1,772 views)
- 4.5.1 Specify minimum information requirements to enable the Designated Community to discover and identify material (1,757 views)
- 4.2.4.1.3 Describe any processes for changes to identifiers (1,756 views)
- 4.3.2 Mechanisms for monitoring its preservation environment (1,754 views)
- 4.2.10 Contemporaneous records of actions and administration processes relevant to AIP creation (1,748 views)
- 5.1.1.1.7 Procedures in place to evaluate when changes are needed to current software (1,747 views)
- 5.1.1.6.1 Documented change management process that identifies changes to critical processes that potentially affect the repository's ability to comply with its mandatory responsibilities (1,744 views)
- 4.4.1 Specifications for how the AIPs are stored down to the bit level (1,741 views)
- 4.1.1.1 Procedures for identifying information properties that we will preserve (1,735 views)
- 4.5.2 Capture or create minimum descriptive information for each AIP (1,719 views)
- 5.2.4 Suitable written disaster preparedness and recovery plan(s), including at least one off-site backup of all preserved information together with an offsite copy of the recovery plan(s) (1,707 views)
- 4.6.2 Follow policies and procedures that enable the dissemination of digital objects that are traceable to the originals (1,701 views)
- 4.2.5.4 Tools or methods to ensure that Representation Information is persistently associated with objects (1,699 views)
- 4.4.2 Contemporaneous records of actions and administration processes that are relevant to storage and preservation of the AIPs (1,692 views)
- 4.6.1.1 Log and review all access management failures and anomalies (1,667 views)
- 4.6.2.1 Record and act upon problem reports about errors in data and responses from users (1,571 views)