Long pages
Showing below up to 139 results starting with #1.
View (previous 500 | next 500) (20 | 50 | 100 | 250 | 500)
- (hist) CLOCKSS: Threats and Mitigations [35,990 bytes]
- (hist) CLOCKSS: Ingest Pipeline [28,307 bytes]
- (hist) CLOCKSS: Box Operations [25,176 bytes]
- (hist) Definition of AIP [24,328 bytes]
- (hist) LOCKSS: Software Development Process [20,160 bytes]
- (hist) CLOCKSS: Extracting Triggered Content [20,101 bytes]
- (hist) LOCKSS: Polling and Repair Protocol [19,561 bytes]
- (hist) LOCKSS: Extracting Bibliographic Metadata [18,193 bytes]
- (hist) Definition of SIP [16,581 bytes]
- (hist) LOCKSS: Format Migration [14,701 bytes]
- (hist) CLOCKSS: Logging and Records [13,619 bytes]
- (hist) 4) Digital Object Management [12,313 bytes]
- (hist) LOCKSS: Basic Concepts [10,245 bytes]
- (hist) CLOCKSS: Designated Community [9,165 bytes]
- (hist) LOCKSS: Property Server Operations [7,850 bytes]
- (hist) 5) Infrastructure and Security Risk Management [6,351 bytes]
- (hist) CLOCKSS: Preservation Strategy [6,261 bytes]
- (hist) Definition of DIP [6,110 bytes]
- (hist) LOCKSS: Metadata Database [5,923 bytes]
- (hist) 3) Organizational Infrastructure [5,608 bytes]
- (hist) CLOCKSS: Mandatory Responsibilities [5,163 bytes]
- (hist) Main Page [4,923 bytes]
- (hist) CLOCKSS: Governance and Organization [4,760 bytes]
- (hist) CLOCKSS: Business Plan Overview [4,130 bytes]
- (hist) 4.4.2.2 Demonstrate that any actions taken on AIPs were compliant with the specification of those actions [2,635 bytes]
- (hist) CLOCKSS: Hardware and Software Inventory [2,542 bytes]
- (hist) CLOCKSS: Budget and Planning Process [2,463 bytes]
- (hist) 4.2.4.1.5 System of identifiers is adequate now and in the future [2,093 bytes]
- (hist) 4.2.4 Convention that generates persistent, unique identifiers for AIPs [2,063 bytes]
- (hist) CLOCKSS: Business History [2,015 bytes]
- (hist) 4.2.1.1 Identify which definition applies to which AIP [1,954 bytes]
- (hist) 4.1.6 Obtain sufficient control over digital objects [1,749 bytes]
- (hist) 3.3.3 Documented history of changes [1,683 bytes]
- (hist) 4.5.1 Specify minimum information requirements to enable the Designated Community to discover and identify material [1,649 bytes]
- (hist) 4.2.1.2 Definition of each AIP [1,633 bytes]
- (hist) CLOCKSS: Access Policy [1,597 bytes]
- (hist) 4.2.5.1 Tools or methods to identify the file types of all objects [1,533 bytes]
- (hist) 4.3.3 Mechanisms to change preservation plans as a result of its monitoring activities [1,500 bytes]
- (hist) 4.3.4 Provide evidence of the effectiveness of its preservation activities [1,457 bytes]
- (hist) 5.1.1.1.1 Hardware technologies appropriate to the services it provides to its designated communities [1,412 bytes]
- (hist) 3.3.6 Self-assessment and external certification [1,380 bytes]
- (hist) 5.1.1.1.2 Procedures in place to monitor and receive notifications when hardware technology changes are needed [1,352 bytes]
- (hist) 3.2.1 Identified duties and appointed staff [1,342 bytes]
- (hist) 3.3.4 Commit to transparency [1,333 bytes]
- (hist) 5.1.1.1.5 Software technologies appropriate to the services it provides to its designated communities [1,314 bytes]
- (hist) 4.1.3 Recognition and parsing of SIPs [1,293 bytes]
- (hist) 5.2.3 Staff shall have delineated roles, responsibilities, and authorizations related to implementing changes [1,282 bytes]
- (hist) 5.1.1.1.8 Procedures, commitment and funding to replace software when evaluation indicates the need to do so [1,252 bytes]
- (hist) 5.1.1.2 Adequate hardware and software support for backup functionality sufficient for preserving the repository content and tracking repository functions [1,221 bytes]
- (hist) 5.1.1.6.2 Process for testing and evaluating the effect of changes to the repository's critical processes [1,169 bytes]
- (hist) 5.1.1.1.6 Procedures in place to monitor and receive notifications when software changes are needed [1,150 bytes]
- (hist) 4.3.1 Documented preservation strategies relevant to its holdings [1,123 bytes]
- (hist) 5.1.1.4 Process to record and react to the availability of new security updates based on a risk-benefit assessment [1,090 bytes]
- (hist) 4.2.7 Content Information is understandable for Designated Community at the time of AIP creation [1,072 bytes]
- (hist) 4.5.3 Create bi-directional linkages between each AIP and its descriptive information [1,065 bytes]
- (hist) 3.5.2 Track and manage property rights/restrictions [1,053 bytes]
- (hist) 4.3.2 Mechanisms for monitoring its preservation environment [1,050 bytes]
- (hist) CLOCKSS: Collection Development [1,023 bytes]
- (hist) 4.2.5.3 Have access to the requisite Representation Information [1,019 bytes]
- (hist) CLOCKSS: Succession Plan [1,010 bytes]
- (hist) 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,007 bytes]
- (hist) 3.2.1.1 Identified and established duties [1,006 bytes]
- (hist) 5.1.1.1.4 Procedures, commitment and funding to replace hardware when evaluation indicates the need to do so [976 bytes]
- (hist) 4.4.1.1 Preserve the Content Information of AIPs [973 bytes]
- (hist) 3.4.2 Financial transparency, compliance, and audits [914 bytes]
- (hist) 3.5.1.4 Policies about liability and rights challenges [900 bytes]
- (hist) 4.4.1.2 Actively monitor the integrity of AIPs [892 bytes]
- (hist) 5.1.1 Identify and manage the risks to its preservation operations and goals associated with system infrastructure [869 bytes]
- (hist) 4.6.1 Comply with Access Policies [858 bytes]
- (hist) 5.1.1.5 Defined processes for storage media and/or hardware change (e.g., refreshing, migration) [848 bytes]
- (hist) 4.2.5.2 Tools or methods to determine what Representation Information is necessary for understandability [847 bytes]
- (hist) 4.3.3.1 Mechanisms for creating, identifying or gathering any extra Representation Information required [834 bytes]
- (hist) 5.1.1.6 Identified and documented critical processes that affect its ability to comply with its mandatory responsibilities [834 bytes]
- (hist) 4.2.5.4 Tools or methods to ensure that Representation Information is persistently associated with objects [806 bytes]
- (hist) 3.3.2.1 Review and update preservation policies [775 bytes]
- (hist) 4.6.2.1 Record and act upon problem reports about errors in data and responses from users [773 bytes]
- (hist) 4.4.2.1 Procedures for all actions taken on AIPs [764 bytes]
- (hist) 4.2.6.3 PDI is persistently associated with Content Information of AIP [760 bytes]
- (hist) 4.3.2.1 Mechanisms for monitoring and notification when Representation Information is inadequate for the Designated Community to understand the data holdings [744 bytes]
- (hist) 5.1.2 Manage the number and location of copies of all digital objects [732 bytes]
- (hist) 4.1.4 Verify the identity of the Producer [725 bytes]
- (hist) 4.2.8 Verify each AIP for completeness and correctness [721 bytes]
- (hist) 4.2.7.3 Bring Content Information of AIP up to level of understandability if it fails testing [721 bytes]
- (hist) 4.2.7.2 Execute testing process of Content Information of AIPs [721 bytes]
- (hist) CLOCKSS: Mission Statement [719 bytes]
- (hist) 4.2.7.1 Processes for testing understandability for Designated Community of the Content Information of AIPs [719 bytes]
- (hist) 4.2.6 Documented processes for acquiring PDI for associated Content Information [715 bytes]
- (hist) 3.2.1.3 Professional development program [708 bytes]
- (hist) 4.2.2 Description of how AIPs are constructed from SIPs [694 bytes]
- (hist) 4.2.6.2 Execute documented processes for acquiring PDI [684 bytes]
- (hist) 3.2.1.2 Appropriate number of staff [681 bytes]
- (hist) 3.5.1.3 Policies about preservation responsibility [670 bytes]
- (hist) 4.2.5 Tool and resources to provide authoritative Representation Information for all objects [669 bytes]
- (hist) 4.6.2 Follow policies and procedures that enable the dissemination of digital objects that are traceable to the originals [658 bytes]
- (hist) 4.4.1 Specifications for how the AIPs are stored down to the bit level [652 bytes]
- (hist) 4.6.1.1 Log and review all access management failures and anomalies [642 bytes]
- (hist) 5.1.2.1 Mechanisms in place to ensure any/multiple copies of digital objects are synchronized [627 bytes]
- (hist) 4.1.5 Verify SIPs for completeness and correctness [618 bytes]
- (hist) 4.2.6.1 Documented processes for acquiring PDI [579 bytes]
- (hist) 4.2.3.1 Procedures if a SIP is not incorporated or discarded [569 bytes]
- (hist) 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 [565 bytes]
- (hist) 5.1.1.3 Effective mechanisms to detect bit corruption or loss [565 bytes]
- (hist) 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) [553 bytes]
- (hist) 4.2.9 Independent mechanism for verifying the integrity of the content [546 bytes]
- (hist) 4.2.4.1.4 Provide a list of all identifiers and check for duplications [541 bytes]
- (hist) 4.2.4.1.2 Assign and maintain persistent identifiers of the AIP and its components [520 bytes]
- (hist) 4.5.2 Capture or create minimum descriptive information for each AIP [517 bytes]
- (hist) 4.2.4.1.3 Describe any processes for changes to identifiers [500 bytes]
- (hist) 3.5.1.1 Contracts or deposit agreements for preservation rights [499 bytes]
- (hist) 5.2.2 Implemented controls to adequately address each of the defined security risks [491 bytes]
- (hist) 3.4.1 Business planning processes [477 bytes]
- (hist) 3.3.5 Information integrity measurements [477 bytes]
- (hist) 3.5.1.2 Completeness of agreements with depositors [471 bytes]
- (hist) 4.2.10 Contemporaneous records of actions and administration processes relevant to AIP creation [463 bytes]
- (hist) 4.2.3 Document final disposition of all SIPs [456 bytes]
- (hist) 3.5.1 Contracts or deposit agreements for content [456 bytes]
- (hist) 5.2.1 Maintain a systematic analysis of security risk factors associated with data, systems, personnel, and physical plant [444 bytes]
- (hist) 3.4.3 Risk, benefit, investment, expenditure [442 bytes]
- (hist) 4.4.2 Contemporaneous records of actions and administration processes that are relevant to storage and preservation of the AIPs [435 bytes]
- (hist) 5.1.1.1 Employ technology watches or other technology monitoring notification systems [427 bytes]
- (hist) 4.2.1 Associated definition for each AIP or class of AIPs [416 bytes]
- (hist) 4.1.8 Records of actions and processes related to acquisition [414 bytes]
- (hist) 4.1.7 Provide depositor with responses [414 bytes]
- (hist) 4.1.1 Identify content information and information properties [371 bytes]
- (hist) 4.2.4.1.1 Have unique identifiers [368 bytes]
- (hist) 3.1.2.2 Monitor environment for time to deploy succession, contingency, escrow [345 bytes]
- (hist) 3.1.2.1 Succession, contigency, escrow plans [345 bytes]
- (hist) 4.2.4.1 Uniquely identify each AIP [337 bytes]
- (hist) 3.3.1 Designated community [328 bytes]
- (hist) 4.1.1.1 Procedures for identifying information properties that we will preserve [312 bytes]
- (hist) 4.1.2 Specify content information at deposit [310 bytes]
- (hist) 4.1.1.2 Record of content information and information properties that we will preserve [310 bytes]
- (hist) 4.2.4.2 System of reliable linking/resolution services in order to find identified objects [300 bytes]
- (hist) 3.1.3 Collection policy [281 bytes]
- (hist) 3.1.1 Mission statement [281 bytes]
- (hist) 3.1.2 Preservation strategic plan [270 bytes]
- (hist) 3.3.2 Preservation policies [262 bytes]
- (hist) 5.1.1.1.3 Procedures in place to evaluate when changes are needed to current hardware [251 bytes]
- (hist) 5.1.1.1.7 Procedures in place to evaluate when changes are needed to current software [240 bytes]