StartDate,EndDate,Progress,Duration (in seconds),Finished,RecordedDate,ResponseId,DistributionChannel,UserLanguage,Q3,Q4,Q5,Q5_4_TEXT,Q6,Q6_5_TEXT,Q7,Q8,Q9,Q10,Q11,Q12,Q14,Q15,Q17,Q18,Q19,Q20,Q20_4_TEXT,Q21,Q22,Q23,Q24,Q63,Q25,Q26,Q62,Q27,Q65,Q66,Q28,Q29,Q64,Q30,Q31,Q31_4_TEXT,Q32,Q32_4_TEXT,Q33,Q34,Q36,Q37,Q38,Q38_9_TEXT,Q39,Q40,Q41,Q42,Q42_6_TEXT,Q43,Q44,Q45,Q46,Q48,Q50,Q51,Q52,Q53,Q53_5_TEXT,Q54,Q54_4_TEXT,Q56,Q58,Q58_9_TEXT
Start Date,End Date,Progress,Duration (in seconds),Finished,Recorded Date,Response ID,Distribution Channel,User Language,"Does your organization use separate storage systems for access-only and preservation-only services?
For organizations that have separate preservation storage, all questions in this survey should be answered for the preservation storage only. For organizations where access and preservation storage are the same, all survey questions should be answered for the entire system.",My organization's preservation storage environment and services includes the following elements. Check all that apply.,Which of the following does your organization use in its preservation storage infrastructure? Check all that apply. - Selected Choice,Which of the following does your organization use in its preservation storage infrastructure? Check all that apply. - Other: - Text,Who is involved in managing your organization's own preservation storage infrastructure? Check all that apply. - Selected Choice,Who is involved in managing your organization's own preservation storage infrastructure? Check all that apply. - Other: - Text,How does your organization approach file systems in all your preservation storage? Check all that apply.,"Please explain how your organization defines a ""preservation copy."" If your organization keeps different numbers of copies for different content, please explain.","In general, how many preservation copies of its digital content is your organization keeping across all storage locations? Please enter your answer as a digit.",Does your organization manage different types of content for different lengths of time?,Please describe types of content and how long you keep them.,"Approximately, how much preservation storage space does your organization currently require for one copy of the content that you manage?","Approximately, how much preservation storage space does your organization require for all copies of the content that you manage?","Approximately, how much total preservation storage space does your organization anticipate needing over the next three years for all copies of content that you manage?","Does your organization keep, or plan to keep, copies of digital content in distinct geographic places to protect from specific threats?",Who manages the copies you have (or plan to have) in distinct geographic places? Check all that apply.,Do you have (or plan to have) copies for all or part of your content in distinct geographic places? Check all that apply.,"If you have (or plan to have) copies for all or part of your content in distinct places, what are the specific threats you are protecting against? Check all that apply. - Selected Choice","If you have (or plan to have) copies for all or part of your content in distinct places, what are the specific threats you are protecting against? Check all that apply. - Other: - Text","Why is your organization not currently keeping, or planning to keep, copies of digital content in distinct places?","Please describe any obstacles to your organization keeping copies of digital content in distinct places, such as organizational capacity, lack of funding, difficulties in sending copies to different places, etc.","Excluding distributed storage cooperatives, is your organization using commercial cloud storage service providers (e.g. Amazon, Rackspace, Azure, DuraCloud, etc.) to keep one or more copies of its content?","If your organization is using, considering, or exploring commercial cloud storage service providers for keeping one or more copies of its content, please list specific services your organization is using, considering, or exploring, and why?",Why is your organization not considering or uninterested in using commercial cloud storage service providers?,"Is your organization participating in a distributed storage cooperative or system (e.g. APTrust, Chronopolis, LOCKSS, MetaArchive, etc.)?","Please list the specific distributed storage cooperatives or systems you are participating in, considering, or exploring, and why.",Why is your organization not considering or uninterested in participating in a distributed storage cooperative or system?,"Does your organization participate in any collection cooperatives that have a digital preservation component, such as HathiTrust or Internet Archive/Archive-It?",Please list the collection cooperatives in which your organization participates.,Does your organization store additional copies of the preservation content from these collection cooperatives?,"Excluding distributive cooperatives and third-party cloud services, is your organization contracting out storage services to be managed by another organization or company?","If your organization is considering, exploring, or currently using storage services managed by another company please list the specific services you are considering, exploring, or using, and why?",Why is your organization not considering or uninterested in contracting out storage services managed by another company?,"If your organization hosts, maintains, and controls its own technical infrastructure for preservation storage, is the software that is used to manage this infrastructure open source?",What software does it use to manage this infrastructure? - Selected Choice,What software does it use to manage this infrastructure? - Other: - Text,How is your organization replicating and managing copies (for all of your preservation storage copies)? Check all that apply. - Selected Choice,How is your organization replicating and managing copies (for all of your preservation storage copies)? Check all that apply. - Other: - Text,"My organization has a strong preference to host, maintain, and control its own technical infrastructure for preservation storage (for either some or all preservation copies).","Why or why not does your organization prefer to host, maintain, and control its own technical infrastructure for preservation storage? Please explain.",Does your organization have documented requirements for your preservation storage system(s)?,"What are your organization's requirements for availability of the content you store? If you have different requirements for different collections, please check each option that applies to at least one of your collections.",Which services does your organization currently provide for content in your preservation storage (either in-house or vended services)? Check all that apply. - Selected Choice,Which services does your organization currently provide for content in your preservation storage (either in-house or vended services)? Check all that apply. - Other services (please describe): - Text,What backup and recovery services does your organization provide? Check all that apply.,What kind of security is in place? Check all that apply.,"Does your organization provide different preservation services for different subsets of your content (i.e., specific ""collections,"" or specific format types, or content from specific sources), in preservation storage?",Which services does your organization provide for different subsets? Check all that apply. - Selected Choice,Which services does your organization provide for different subsets? Check all that apply. - Other: - Text,Why doesn't your organization provide different services for different subsets? Check all that apply.,What types of fixity checking practices does your organization follow? Check all that apply.,"If your organization performs fixity checks on all or most of the content you are preserving at fixed intervals, how frequently (in months) do you perform those checks? For example, if your organization performs them monthly enter 1, if every nine months enter 9, if annually enter 12, etc.","If your organization performs fixity checks on a portion of the content you are preserving at fixed intervals, please describe how much content is checked and at what interval (i.e., we do fixity checks on 50% of our total content annually).",My organization has a plan to meet our preservation storage requirements over the next 3 years.,"Digital preservation is a core operational service of my organization (this implies adequate staff, consistent budgetary resources, and policies are in place).",My organization plans to make significant technological changes to its preservation storage environment and services within the next three years.,My organization intends to meet the requirements for a trustworthy digital repository according to external standards within the next three years.,Please indicate the trusted digital repository standard(s) your organization is targeting. Check all that apply. - Selected Choice,Please indicate the trusted digital repository standard(s) your organization is targeting. Check all that apply. - Other: - Text,How does your organization plan to certify or audit its trusted digital repository status? - Selected Choice,How does your organization plan to certify or audit its trusted digital repository status? - Other: - Text,"Is your organization a member of the National Digital Stewardship Alliance (NDSA)?
If you are unsure, visit the NDSA members list.",Which of the following most closely describes the type or function of your organization? - Selected Choice,Which of the following most closely describes the type or function of your organization? - Other (please describe) - Text
5/23/19 9:30,5/23/19 9:37,100,394,TRUE,5/23/19 9:37,R_2rUVYCRGizyxOaG,anonymous,EN,Yes,"Onsite storage,Offsite storage, not managed by my organization (e.g. vendor-managed)",Virtual servers,,"Digital Preservation Team,Department/Unit IT",,"Hardware-based file systems (ntfs, fat, ext, apfs)",W keep a copy on the shared file-server (SANS storage) and then 2 copies on DuraCloude.,3,No,,Under 1 terabyte,Under 1 terabyte,Under 1 terabyte,"Yes, we do",Managed by an external provider (commercial or non-commercial),We have complete separate copies of all our content being managed for preservation in distinct places,"Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",DuraSpace. Integration with Archviematica,,"No, and my organization is uninterested in participating in a distributed storage cooperative or system",,NA,Yes,"Arvchive-It, HathiTrust",No,Not applicable,,,Not applicable,,,,,Neutral,"IT is separate from preservation. IT performs backups, but not specifically preservation orientated.",Yes,Offline availability (i.e. able to retrieve on request within two business days),"Periodic fixity checking,File characterization,File validation,Metadata integration",,,,Yes," Bit-level preservation,Metadata created,Checksums generated",,,We do fixity checks before and after transactions like ingest or data transfer,,,Agree,Disagree,Agree,Disagree,,,,,No,Academic,
5/23/19 9:29,5/23/19 9:42,100,812,TRUE,5/23/19 9:42,R_rejz2EIAUe8Mmbv,anonymous,EN,Yes,"Onsite storage,Offsite storage, not managed by my organization (e.g. vendor-managed),Offsite storage, commercial cloud (for example, AWS)","Physical servers,Virtual servers",,"Digital Preservation Team,Central IT,Contracted",,"Hardware-based file systems (ntfs, fat, ext, apfs)","Three preservation copies geographically and technically disparate with high security and minimal access. Dark copy with no access to archive, only thru digital preservation platform. ",3,No,,1-10 petabytes,1-10 terabytes,1-10 terabytes,"Yes, we do",Managed by our organization,We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",AWS Glacier,,Not applicable,,,No,,,"No, my organization is not considering contracting out storage services which are managed by another organization",,Risk,No,,,,,Strongly Agree,,Yes,"Offline availability (i.e. able to retrieve on request within two business days),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,,,No,,,We don't see a need to provide different services for different subsets,"We do fixity checks before and after transactions like ingest or data transfer,We randomly sample content and check for fixity",,,Strongly Agree,Agree,Disagree,Strongly Agree,ISO 16363 (TDR),,Local audits,,Yes,Museum,
5/23/19 9:34,5/23/19 9:44,100,625,TRUE,5/23/19 9:44,R_1r33KQ09XubsRZE,anonymous,EN,Yes,"Offsite storage, managed by my organization,Offsite storage, commercial cloud (for example, AWS)","Physical servers,Virtual servers,Containers (e.g. Docker, rkt, Kata)",,"Digital Preservation Team,Department/Unit IT",,"Hardware-based file systems (ntfs, fat, ext, apfs),Hybrid file systems (zfs, btrfs)",,3,No,,More than 10 petabytes,More than 10 petabytes,More than 10 petabytes,"Yes, we do",Managed by our organization,We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations)",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",,,"No, and my organization is uninterested in participating in a distributed storage cooperative or system",,,Yes,,No,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,,Some open source,VM Hosting,,Storage appliance,,Strongly Agree,,Yes,Offline availability (i.e. able to retrieve on request within two business days),"Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,"Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",We have tailored security specific to our preservation content,Yes,"File format migration,Metadata created,Checksums generated,Arrangement",,,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly),We store fixity information in an independent system",12,,Agree,Strongly Agree,Strongly Agree,Strongly Disagree,,,,,No,Non-profit,
5/23/19 9:42,5/23/19 10:01,100,1161,TRUE,5/23/19 10:01,R_tWnI1oxx8910vuN,anonymous,EN,Yes,Onsite storage,Physical servers,,Department/Unit IT,,"Software-based file systems (glusterfs, ceph)","replicas serve the purpose of preservation as well as Geo-insurance, in case of catastrophic loss at one site.",2,Yes,"All types, this is an University environment.",More than 10 petabytes,More than 10 petabytes,More than 10 petabytes,"Yes, we do",Managed by our organization,We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"No, and my organization is uninterested in using commercial cloud storage service providers for keeping one or more copies of its content",,"Beside moving data at scale costs a lot on network changes, and furthermore, cloud provides are EXTREMELY slow and COSTLY to return that data to clients when needed. We have very active two-way movement of data requirements.","Yes, my organization currently participates in a distributed storage cooperative or system","These distributed storage cooperatives are internally designed for efficiency and cost control. No commercial opportunities here for the service layer, only hardware.",,Yes,,Yes,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,Because we have in-house expertise.,No,,,,,Strongly Agree,"because we are a very large deployment, often times ahead of 3rd-party organizations, in expertise and scale.",Yes,"Near-line availability (i.e. able to retrieve on request within three hours),High-performance availability (access to large number of simultaneous users/or for HPC)","Secure storage with backup and recovery procedures in place,Version control,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)","Security is applied and managed within the same regulations and rules as other digital content in our organization,We have tailored security specific to our preservation content",No,,,We don't see a need to provide different services for different subsets,We do fixity checks before and after transactions like ingest or data transfer,,,Strongly Agree,Strongly Agree,Neutral,Not Applicable,,,,,Yes,Academic,
5/23/19 10:09,5/23/19 10:21,100,687,TRUE,5/23/19 10:21,R_1GObAuvdLBPtMNg,anonymous,EN,No,"Onsite storage,Offsite storage, not managed by my organization (e.g. vendor-managed)",Physical servers,,"Digital Preservation Team,Department/Unit IT",,I'm not sure,"""AIPs"" as defined by OAIS
Packages of files stored by Archivematica in their original form, not intended for direct use
Files written to tape",3,No,,1-10 terabytes,1-10 terabytes,10-99 terabytes,"Yes, we do","Managed by our organization,Managed by an external provider (commercial or non-commercial)",We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"No, and my organization is uninterested in using commercial cloud storage service providers for keeping one or more copies of its content",,"Concerns over longevity of service providers, and ability to provide fixity checking","No, my organization is not considering participating in a distributed storage cooperative or system",,No need,Yes,Archive-It,Yes,"Yes, my organization currently contracts out storage services which are managed by another organization",,,Yes,,,,,Strongly Agree,,Yes,Near-line availability (i.e. able to retrieve on request within three hours),"Secure storage with backup and recovery procedures in place,Periodic fixity checking,File characterization,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",Security is applied and managed within the same regulations and rules as other digital content in our organization,Yes," Bit-level preservation,File format migration,Metadata created,Checksums generated",,,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly)",3,,Strongly Agree,Agree,Disagree,,,,,,No,Museum,
5/23/19 9:53,5/23/19 10:34,100,2470,TRUE,5/23/19 10:34,R_XoCvuJNOoBNyEXn,anonymous,EN,No,"Onsite storage,Offsite storage, managed by my organization,Offsite storage, not managed by my organization (e.g. vendor-managed)",Physical servers,,"Digital Preservation Team,Department/Unit IT,Contracted",,"Hardware-based file systems (ntfs, fat, ext, apfs),Hybrid file systems (zfs, btrfs)","The preservation copy is the copy that is placed in a named and physically/logically isolated storage device, an event that occurs only after the record(s) have been fully accessioned, processed, metadata has been applied, and a distribution or access copy has been created. ",3,Yes,"Content types include structured and unstructured data: text files, graphics files, video, and structured data sets. Acceptable formats are standardized for each of these and normalized upon ingest. Long-term retention of vital records that may not be permanent is enforced for periods of from 10 to 80 years. ",10-99 terabytes,100-999 terabytes,100-999 terabytes,"Yes, we do","Managed by our organization,Managed by an external provider (commercial or non-commercial)",We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).",,,,"No, my organization is not considering using commercial cloud storage service providers for keeping one or more copies of its content",,"In lieu of developing a completely private cloud, my organization is required to be accountable for the privacy and security of sensitive personal and corporate information that we do not feel can be satisfactorily guaranteed by third party cloud storage vendors. ","No, my organization is not considering participating in a distributed storage cooperative or system",,My organization explored this possibility but found that we were unable to provide IT and system support required for full participation. We would not be opposed to this possibility at some point in the future when we are beyond our initial build out of systems and processes. ,No,,,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,"For reasons of data security and operational accountability, my organization does not anticipate ever using a storage service to manage our data. ",Yes,VM Hosting,,"Software application,Storage appliance,Sneakernet (manual hard drive exchanges) and manual tracking",,Strongly Agree,See answers given earlier to the use of in-house storage and data preservation management.,Yes,"Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files)",We have tailored security specific to our preservation content,No,,,We don't see a need to provide different services for different subsets,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly),Our provider does fixity checking",4,,Strongly Agree,Agree,Disagree,Neutral,,,,,No,Archives,
5/23/19 10:40,5/23/19 10:49,100,575,TRUE,5/23/19 10:49,R_2isvpYZxprdSWJj,anonymous,EN,Yes,"Onsite storage,Offsite storage, consortia/cooperative","Physical servers,Virtual servers",,"Digital Preservation Team,Department/Unit IT",,"Hardware-based file systems (ntfs, fat, ext, apfs),Hybrid file systems (zfs, btrfs)",,3,Yes,,10-99 terabytes,100-999 terabytes,100-999 terabytes,"Yes, we do",Managed by a collaborative arrangement,We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"No, my organization is not considering using commercial cloud storage service providers for keeping one or more copies of its content",,Don't consider it preservation. ,"Yes, my organization currently participates in a distributed storage cooperative or system",Chronopolis,,Yes,HathiTrust,Yes,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,"Have a solution already, no need.",Yes,VM Hosting,,Software application,,Strongly Agree,It is a critical and essential part of the library's responsibility. ,Yes,"Eventual availability only (dark archive/disaster recovery),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",Security is applied and managed within the same regulations and rules as other digital content in our organization,No,,,"We don't see a need to provide different services for different subsets,We have not had requirements for different services","We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly),We store fixity information in an independent system,We use a tamper-resistant fixity check mechanism (e.g. LOCKSS, ACE)",1.5,,Agree,Agree,Neutral,Neutral,,,,,Yes,Academic,
5/23/19 10:33,5/23/19 10:58,100,1483,TRUE,5/23/19 10:58,R_ba0PcgTQ45U6EcF,anonymous,EN,No,"Onsite storage,Offsite storage, commercial cloud (for example, AWS)",Physical servers,,Department/Unit IT,,I'm not sure,"A preservation copy is an original, unaltered copy that isn't accessed except to generate an access copy or to replace a corrupted copy. Right now we only have one preservation copy for most materials although some have a second preservation copy. We are working on having multiple preservation copies for all materials, stored in separate locations.",2,,,1-10 terabytes,1-10 terabytes,1-10 terabytes,"No, but we plan to","Managed by a collaborative arrangement,Managed by an external provider (commercial or non-commercial)",We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,"Getting support within the organization to make digital preservation a priority, getting funding and setting up the infrastructure.","Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",AWS due to its low cost and ease of use.,,"No, but my organization is currently exploring participating in a distributed storage cooperative or system",APTrust due to its academic focus.,,Yes,HathiTrust,No,"No, my organization is not considering contracting out storage services which are managed by another organization",,We are not at a point where this is something under consideration. It could be in the future.,,,,,,Neutral,I don't think we have a preference at the moment and are probably skewed toward outsourcing this work as we don't have enough staff to handle the responsibility.,"No, but we are planning to develop requirements in the next year","Eventual availability only (dark archive/disaster recovery),Near-line availability (i.e. able to retrieve on request within three hours),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,File characterization,Format normalization, format migration, or platform emulation for the purpose of format migration",,"HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files)",Security is applied and managed within the same regulations and rules as other digital content in our organization,No,,,"Services are managed outside of our organization, so we have no control,We have not had requirements for different services","We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly)",1,,Neutral,Disagree,Neutral,Disagree,,,,,Yes,Academic,
5/23/19 10:23,5/23/19 10:59,100,2196,TRUE,5/23/19 10:59,R_2VO8Ykf4CDwSdOA,anonymous,EN,Yes,"Onsite storage,Offsite storage, managed by my organization",Physical servers,,"Department/Unit IT,Central IT",,"Hybrid file systems (zfs, btrfs)","We're still working on this. Generally, we have preservation copies on different servers. Usually, they are uncompressed or minimally compressed. We're working on more copies, but in some cases, we still have only one. This decision is partially made by mission priorities, but partially just by where we ended up saving that type when we started getting digital instead of paper. Fixing this is a high priority, but honestly, we have too many high priorities right now.",2,No,,10-99 terabytes,100-999 terabytes,100-999 terabytes,"No, but we plan to",Managed by our organization,"We have multiple additional copies in distinct places, of which one or more are complete and one or more are partial","Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,"Insufficient staff to manage, difficulties in sending copies to different places, legal and policy issues for us using some cloud solutions.","No, but my organization is currently exploring using commercial cloud storage service providers for keeping one or more copies of its content",Considering Amazon and Microsoft services for government. May be more. This is a high level IT discussion at this point.,,"No, but my organization is currently exploring participating in a distributed storage cooperative or system",Exploring a consortium using ScholarWorks (dSpace) for both preservation and access to a limited subset of content.,,Yes,Archive-It,No,"No, my organization is not considering contracting out storage services which are managed by another organization",,Probably mostly lack of trust. ,No,,,,,Agree,We feel that's the best way to assure it's done in accordance with applicable law and policy.,Yes,"Eventual availability only (dark archive/disaster recovery),Near-line availability (i.e. able to retrieve on request within three hours),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,File validation",,"HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",We have tailored security specific to our preservation content,Yes," Bit-level preservation,File format migration,Metadata created,Checksums generated",,,We randomly sample content and check for fixity,,,Disagree,Disagree,Strongly Agree,Neutral,,,,,No,Government,
5/23/19 10:43,5/23/19 11:00,100,1057,TRUE,5/23/19 11:00,R_27U4eTGUxqro2Om,anonymous,EN,No,"Offsite storage, managed by my organization",Virtual servers,,Department/Unit IT,,I'm not sure,Preservation copies are the original records as transferred to us from our corporate/municipal partners and private donors as well as any normalized copies. We currently have very few normalized copies.,3,No,,1-10 terabytes,10-99 terabytes,10-99 terabytes,"Yes, we do",Managed by our organization,We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"No, but my organization is currently exploring using commercial cloud storage service providers for keeping one or more copies of its content",We are looking at implementing a SaaS service for digital preservation that will likely make use of AWS S3 and Glacier.,,"No, my organization is not considering participating in a distributed storage cooperative or system",,Haven't really explored the space at all. Trying to get a reasonably robust digital preservation repository built first.,No,,,"Yes, my organization currently contracts out storage services which are managed by another organization",Our IT department rents server space from a [DELETED: organization name] data centre near [DELETED: location].,,No,,,,,Neutral,"I would prefer to have some control over hosting, but it's much harder for our IT department to meet international data security and storage standards that are easily met by cloud providers.","No, but we are planning to develop requirements in the next year","Eventual availability only (dark archive/disaster recovery),Offline availability (i.e. able to retrieve on request within two business days),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)",Secure storage with backup and recovery procedures in place,,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files)",Security is applied and managed within the same regulations and rules as other digital content in our organization,No,,,"Our services are not capable of treating content differently,We are working on a plan for providing different services as different requirements arise",We do fixity checks before and after transactions like ingest or data transfer,,,Agree,Neutral,Agree,Disagree,,,,,No,Government,
5/23/19 10:53,5/23/19 11:06,100,787,TRUE,5/23/19 11:06,R_2zI40GuCPFILivK,anonymous,EN,Yes,"Offsite storage, consortia/cooperative","Physical servers,Virtual servers",,"Digital Preservation Team,Department/Unit IT,Central IT",,I'm not sure,,4,Yes,We have not defined this formally. ,10-99 terabytes,10-99 terabytes,100-999 terabytes,"Yes, we do",Managed by an external provider (commercial or non-commercial),We have additional copies for some of our content in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content","Our service provider stores copies on Amazon services. Specifically, I believe, S3 (although I am not totally certain). ",,"No, my organization is not considering participating in a distributed storage cooperative or system",,"We do not have the capacity to serve as a cooperative member, and are limited to the services available to us through our parent institution. ",Yes,"Hathi Trust
Internet Archive
",No,"Yes, my organization currently contracts out storage services which are managed by another organization","[DELETED: organization name]-provided digital preservation repository. We use this because almost all of our collection management software is implemented by [DELETED: organization name] (we have little to no budget to implement our own), and this is the product they offer. ",,Not applicable,,,,,Disagree,We do not have the resources to do so. ,"No, and we do not plan to develop requirements",Near-line availability (i.e. able to retrieve on request within three hours),"Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,Persistent identifiers",,"Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",We have tailored security specific to our preservation content,Yes,Checksums generated,,,"We do fixity checks before and after transactions like ingest or data transfer,Our provider does fixity checking",,,Neutral,Strongly Disagree,Disagree,Strongly Disagree,,,,,No,Archives,
5/23/19 11:23,5/23/19 11:40,100,998,TRUE,5/23/19 11:40,R_zUqx87W34cl6Ej7,anonymous,EN,Yes,"Onsite storage,Offsite storage, managed by my organization",Physical servers,,"Digital Preservation Team,Department/Unit IT,Contracted",,"Hardware-based file systems (ntfs, fat, ext, apfs)","Our ""archival"" copy is saved separately as a duplicate instance of the DIP access file; it may include additional renditions/manifestations of the same expression that is in the DIP but not publicly accessible such as master JPEG2000 files. We differentiated the AIP from ""backups"" - the AIP is the standalone preserved instance of a file; backups can include multiple copies of this file at any given time during data synchronization. ",4,No,,10-99 terabytes,10-99 terabytes,100-999 terabytes,"Yes, we do",Managed by a collaborative arrangement,We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ,Other:",we are striving to protect against all of these but we recognize that our distinct geographically dispersed locations are not as far apart as we truly need them to be to safegaurd against all geographic risks; it is our long-term goal to have a third instance of the data to solve for this,,,"No, but my organization is currently exploring using commercial cloud storage service providers for keeping one or more copies of its content",Looking to utilize Azure to save a third instance of the AIPs; this is currently dependent on our institutional enterprise systems ,,"Yes, my organization currently participates in a distributed storage cooperative or system",We have been a LOCKSS partner for many years ,,Yes,We use Archive-It for web harvesting activities.,No,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,It is a priority of ours to have as few dependencies on other entities as possible to oversee our systems and be able to fully switch from one instance to another in case of an emergency or necessary backup fail over ,Some open source,Other:,COTS,"Storage appliance,Other:",Snapmirror technologies,Strongly Agree,"This provides the highest level of confidence in the ability to failover from one instance of our data to another (not just our copies of files, but our web applications and the software used to provide public access, as well)",Yes,High-performance availability (access to large number of simultaneous users/or for HPC),"Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files)",Security is applied and managed within the same regulations and rules as other digital content in our organization,No,,,We don't see a need to provide different services for different subsets,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly),6,,Strongly Agree,Strongly Agree,Agree,Strongly Agree,ISO 16363 (TDR),,Full certification according to chosen trusted digital repository standards,,Yes,Government,
5/23/19 11:09,5/23/19 11:46,100,2195,TRUE,5/23/19 11:46,R_ZrQMf0EDqbQyeXf,anonymous,EN,Yes,"Onsite storage,Offsite storage, consortia/cooperative,Offsite storage, commercial cloud (for example, AWS)","Physical servers,Virtual servers",,"Digital Preservation Team,Department/Unit IT",,I'm not sure,"The preservation master is the digital object in our preservation system. A preservation copy is an exact copy of the high quality original file that is stored in another safe location. The locations are:
- preservation system and regular backups onsite, monthly copies offsite
- annual tape copy of preservation system content in a secure offsite location
- a cumulative copy of the preservation system content in an internet storage facility",3,Yes,"1. Permanent files for the life of the institution
2. Long term files to be reviewed in 10 years. At that time, discard or make permanent",10-99 terabytes,100-999 terabytes,100-999 terabytes,"Yes, we do","Managed by our organization,Managed by a collaborative arrangement,Managed by an external provider (commercial or non-commercial)",We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",Box,,"No, and my organization is uninterested in participating in a distributed storage cooperative or system",,We feel our current storage plans are sufficient,Yes,,,"No, my organization is not considering contracting out storage services which are managed by another organization",,Not needed,Some open source,,,"Software application,Sneakernet (manual hard drive exchanges) and manual tracking",,Strongly Agree,,Yes,"Eventual availability only (dark archive/disaster recovery),Offline availability (i.e. able to retrieve on request within two business days),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",Security is applied and managed within the same regulations and rules as other digital content in our organization,Yes," Bit-level preservation,File format migration,Metadata created,Checksums generated,Arrangement",,,"We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly),We store fixity information in an independent system",1,,Agree,Agree,Neutral,Neutral,,,,,No,Academic,
5/23/19 11:26,5/23/19 11:54,100,1691,TRUE,5/23/19 11:54,R_1ruysZXkuTjknHj,anonymous,EN,Yes,"Offsite storage, managed by my organization,Offsite storage, consortia/cooperative",Virtual servers,,Central IT,,I'm not sure,There are two types of preservation copies. Digitized material that has been digitized to our preservation standards and born digital content received from producers and processed into the collection. ,4,No,,1-10 terabytes,1-10 terabytes,10-99 terabytes,"Yes, we do","Managed by a collaborative arrangement,Managed by an external provider (commercial or non-commercial)",We have additional copies for some of our content in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"No, but my organization is currently exploring using commercial cloud storage service providers for keeping one or more copies of its content","I don't know, I know our IT department is considering it but not the details.",,Not applicable,,,No,,,"No, my organization is not considering contracting out storage services which are managed by another organization",,We are happy with the systems we have in place. And we wouldn't have the additional resources anyway.,Some open source,,,,,Disagree,"Cost and staff resources (also cost, we can't afford the people with these skills).",Yes,"Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,,"Security is applied and managed within the same regulations and rules as other digital content in our organization,We have tailored security specific to our preservation content",Yes," Bit-level preservation,File format migration",,,"We randomly sample content and check for fixity,Our provider does fixity checking",,,Agree,Agree,Neutral,Disagree,,,,,No,Archives,
5/23/19 11:38,5/23/19 12:32,100,3253,TRUE,5/23/19 12:32,R_3KT8arwWoexdSDG,anonymous,EN,Yes,"Onsite storage,Offsite storage, commercial cloud (for example, AWS)","Physical servers,Virtual servers",,"Digital Preservation Team,Central IT,Contracted",,"Hybrid file systems (zfs, btrfs)","Depends on the origin. Preservation copies for born-digital are the originals or normalized originals or, if pulled off optical media, the disk images. Preservation copies of digitized surrogates are high resolution scans made following best practices (uncompressed, non proprietary formats, etc). We keep additional copies of born digital material and digitized material that are high risk.",2,No,,10-99 terabytes,10-99 terabytes,100-999 terabytes,"Yes, we do",Managed by our organization,We have additional copies for some of our content in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",Amazon Web Services - Cost.,,"No, my organization is not considering participating in a distributed storage cooperative or system",,Cost per TB is typically far greater than self managed through AWS.,Yes,Internet Archive/Archive-it,Yes,"No, my organization is not considering contracting out storage services which are managed by another organization",,,Some open source,VM Hosting,,"Software application,Storage appliance",,Neutral,"Cost at scale, but external parties would be preferable given limited internal staff.","No, but we are planning to develop requirements in the next year",Offline availability (i.e. able to retrieve on request within two business days),"Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)","Security is applied and managed within the same regulations and rules as other digital content in our organization,We have tailored security specific to our preservation content",Yes,"Metadata created,Checksums generated,Arrangement",,,"We do fixity checks on a portion of the content we are preserving at fixed intervals,We randomly sample content and check for fixity,Our provider does fixity checking",,unknown,Neutral,Neutral,Neutral,Disagree,,,,,Yes,Archives,
5/23/19 12:16,5/23/19 12:41,100,1500,TRUE,5/23/19 12:41,R_25XEeo75EGyqW9h,anonymous,EN,Yes,"Onsite storage,Offsite storage, consortia/cooperative,Offsite storage, commercial cloud (for example, AWS)",Physical servers,,Digital Preservation Team,,"Hardware-based file systems (ntfs, fat, ext, apfs)",,8,No,,1-10 terabytes,1-10 terabytes,10-99 terabytes,"Yes, we do",Managed by a collaborative arrangement,We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",AWS,,"Yes, my organization currently participates in a distributed storage cooperative or system",MetaArchive Cooperative,,No,,,"No, my organization is not considering contracting out storage services which are managed by another organization",,,Not applicable,,,,,Disagree,Limited resources for internal technical infrastructure,Yes,Eventual availability only (dark archive/disaster recovery),"Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files)",Security is applied and managed within the same regulations and rules as other digital content in our organization,Yes," Bit-level preservation,Metadata created,Checksums generated,Arrangement",,,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly),We use a tamper-resistant fixity check mechanism (e.g. LOCKSS, ACE)",1,,Agree,Neutral,Agree,Not Applicable,,,,,Yes,Museum,
5/23/19 12:35,5/23/19 12:48,100,778,TRUE,5/23/19 12:48,R_2Vymo4rD8f0bsMR,anonymous,EN,Yes,"Onsite storage,Offsite storage, commercial cloud (for example, AWS)","Physical servers,Virtual servers",,"Digital Preservation Team,Department/Unit IT,Central IT,Contracted",,I'm not sure,a copy that is not accessed other than for purposes of migration or creating derivatives.,2,No,,10-99 terabytes,10-99 terabytes,10-99 terabytes,"No, but we plan to",Managed by an external provider (commercial or non-commercial),We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content","Preservica Amazon S3
MSU purchased Amazon S3 and Glacier",,"No, but my organization is currently exploring participating in a distributed storage cooperative or system",possible statewide [DELETED: location] effort,,Yes,Archive-It,No,"Yes, my organization currently contracts out storage services which are managed by another organization",Preservica - end to end system,,Some open source,Other:,not sure,Software application,,Disagree,Lack of resources and expertise in this specific area,Yes,"Near-line availability (i.e. able to retrieve on request within three hours),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,"Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",Security is applied and managed within the same regulations and rules as other digital content in our organization,No,,,"We have not had requirements for different services,We are working on a plan for providing different services as different requirements arise","We do fixity checks before and after transactions like ingest or data transfer,Our provider does fixity checking",,,Disagree,Neutral,Agree,Agree,TRAC,,Local audits,,Yes,Archives,
5/23/19 13:17,5/23/19 13:52,100,2086,TRUE,5/23/19 13:52,R_2cdaHQIhz1z0SYU,anonymous,EN,Yes,Onsite storage,"Physical servers,Other:",we are looking at service provider options for external copies,"Digital Preservation Team,Department/Unit IT,Central IT,Contracted,Other:",Digital Archives Program ,"Hardware-based file systems (ntfs, fat, ext, apfs)",We use Archivematica so preservation copies are AIPs produced by our use of Archivematica,3,Yes,"We define five levels of preservation commitment that specifies number of preservation copies, extent of preservation metadata, frequency of preservation services. We intend to permanently preserve these five levels of content. We also have some content that is designated for digital asset management rather than ongoing preservation. We determine how long on a case-b y-case basis.",10-99 terabytes,100-999 terabytes,1-10 petabytes,"No, but we plan to",Managed by an external provider (commercial or non-commercial),"We have multiple additional copies in distinct places, of which one or more are complete and one or more are partial","Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ,Other:",address holistic independence in accordance with the DP storage criteria https://osf.io/sjc6u/ ,,Lining up funding has been an issue that we are working on. Having levels of preservation commitment was essential for these discussions. ,"No, but my organization is currently exploring using commercial cloud storage service providers for keeping one or more copies of its content",our levels of preservation commitment inform which copies for which content might be suited to commercial providers specifically cloud service providers. Our current thinking is that option might be managed through an open source provider.,,"No, but my organization is currently exploring participating in a distributed storage cooperative or system",We are at an early stage. ,,Yes,"We are members of HathiTrust - we do not include content we provide to them in our local DP program.
We subscribe to Archive-It - we include this content in our local preservation program, this service acknowledges that they do not provide full preservation",Yes,"No, but my organization is currently exploring contracting out storage services which are managed by another organization",,,Some open source,Other:,TBD - new contract pending,"Software application,Storage appliance,Sneakernet (manual hard drive exchanges) and manual tracking",,Agree,It depends on the level of preservation commitment and these discussions are ongoing,Yes,Not applicable,"Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Persistent identifiers,Other services (please describe):","content-specific preservation strategies above the file level, sustainable DP program management ","Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)","Security is applied and managed within the same regulations and rules as other digital content in our organization,We have tailored security specific to our preservation content",Yes," Bit-level preservation,File format migration,Metadata created,Checksums generated,Arrangement",,,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly),We do fixity checks on a portion of the content we are preserving at fixed intervals",,"Preservation levels of commitment specify frequency - we are finalizing and implementing as I type ...
no answer above because intervals vary by level of commitment ",Strongly Agree,Agree,Agree,Agree,"ISO 16363 (TDR),Data Seal of Approval / CoreTrustSeal",,Other:,"periodic self-assessment plus peer review audits, possibly what you mean by community audits?",Yes,Academic,
5/23/19 10:19,5/23/19 13:56,100,13020,TRUE,5/23/19 13:56,R_24eYEfMON6QVJUB,anonymous,EN,Yes,"Onsite storage,Offsite storage, managed by my organization,Offsite storage, commercial cloud (for example, AWS)","Physical servers,Other:",LTO,"Digital Preservation Team,Department/Unit IT,Central IT,Contracted",,"Software-based file systems (glusterfs, ceph),I'm not sure",Content selected for preservation will be included in the tape library. ,3,Yes,,100-999 terabytes,100-999 terabytes,1-10 petabytes,"Yes, we do","Managed by our organization,Managed by an external provider (commercial or non-commercial)",We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content","Glacier; stability, cost, functionality",,"Yes, my organization currently participates in a distributed storage cooperative or system","HathiTrust, LOCKSS, CLOCKSS, Portico",,Yes,HathiTrust and ArchiveIT (I hadn't thought of it as a cooperative until this survey),Yes,"No, my organization is not considering contracting out storage services which are managed by another organization",,,Yes,,,Software application,,Strongly Agree,"We prefer a hybrid approach, one with fulsome understanding of hardware, software, and geographic control, and one with trusted organizations (collaborative and/or commercial) where those elements might not be fully understood.","No, and we do not plan to develop requirements","Eventual availability only (dark archive/disaster recovery),Near-line availability (i.e. able to retrieve on request within three hours),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files)",We have tailored security specific to our preservation content,No,,,We are working on a plan for providing different services as different requirements arise,We do fixity checks before and after transactions like ingest or data transfer,,,Agree,Agree,Disagree,Disagree,,,,,Yes,Academic,
5/23/19 14:07,5/23/19 14:31,100,1410,TRUE,5/23/19 14:31,R_2tcI6ey7xA9ZUn7,anonymous,EN,No,"Onsite storage,Offsite storage, managed by my organization,Offsite storage, consortia/cooperative","Physical servers,Virtual servers",,"Digital Preservation Team,Department/Unit IT",,"Hardware-based file systems (ntfs, fat, ext, apfs)",,3,No,,10-99 terabytes,10-99 terabytes,100-999 terabytes,"Yes, we do",Managed by a collaborative arrangement,We have complete separate copies of all our content being managed for preservation in distinct places,"Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"No, and my organization is uninterested in using commercial cloud storage service providers for keeping one or more copies of its content",,,"No, my organization is not considering participating in a distributed storage cooperative or system",,,Yes,HathiTrust,No,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,,Yes,VM Hosting,,Sneakernet (manual hard drive exchanges) and manual tracking,,Agree,,"No, but we are planning to develop requirements in the next year","Eventual availability only (dark archive/disaster recovery),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files)",Security is applied and managed within the same regulations and rules as other digital content in our organization,No,,,We are working on a plan for providing different services as different requirements arise,We randomly sample content and check for fixity,,,Not Applicable,Agree,Not Applicable,Disagree,,,,,No,Academic,
5/23/19 14:32,5/23/19 14:46,100,858,TRUE,5/23/19 14:46,R_xgrtJfdeWHveFpf,anonymous,EN,Yes,"Onsite storage,Offsite storage, consortia/cooperative,Offsite storage, commercial cloud (for example, AWS)","Virtual servers,Other:",LTO-7 tapes,"Digital Preservation Team,Department/Unit IT",,I'm not sure,"Preservation copies are typically either original born-digital content as received by Archives and Special Collections, born-digital content after processing, or full-resolution digitization files (typically TIFF, WAV, and ProRes) from tangible images, audiotape, videotape, and film. We also preserve scientific data and scans of theses and other [DELETED: organization name]-produced scholarship; formats of data vary, and the only format of publication-like scholarship, including theses, is generally PDF.",2,No,,10-99 terabytes,10-99 terabytes,10-99 terabytes,"Yes, we do","Managed by our organization,Managed by a collaborative arrangement,Managed by an external provider (commercial or non-commercial)",We have additional copies for some of our content in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations)",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content","Amazon Glacier, Amazon Glacier Deep Archive. We're using these services primarily due to their low cost.",,"Yes, my organization currently participates in a distributed storage cooperative or system","We are participating in Chronopolis, primarily because it was easy to transfer content over to it from DPN when DPN folded.",,Yes,Archive-It,No,"No, my organization is not considering contracting out storage services which are managed by another organization",,Managing our own storage in AWS currently seems feasible.,Not applicable,,,,,Agree,"We are currently planning to maintain preservation copies onsite on tape in addition to hosted copies, in part because we have the tape drives and staffing to do so and it provide redundancy.","No, and we do not plan to develop requirements","Eventual availability only (dark archive/disaster recovery),Offline availability (i.e. able to retrieve on request within two business days)","File validation,Metadata integration",,,,Yes," Bit-level preservation,Metadata created,Checksums generated,Arrangement",,,We do fixity checks before and after transactions like ingest or data transfer,,,Agree,Agree,Disagree,Neutral,,,,,Yes,Academic,
5/23/19 14:40,5/23/19 14:54,100,855,TRUE,5/23/19 14:54,R_3khTlEXQGO8apoI,anonymous,EN,No,"Onsite storage,Offsite storage, commercial cloud (for example, AWS)",Physical servers,,Central IT,,I'm not sure,We don't.,2,No,,1-10 petabytes,1-10 petabytes,1-10 petabytes,"No, but we plan to",Managed by our organization,We have additional copies for some of our content in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",AWS. I don't know that choice was made.,,"No, my organization is not considering participating in a distributed storage cooperative or system",,We don't know enough about them.,Yes,Archive-It,No,"No, but my organization is currently exploring contracting out storage services which are managed by another organization",,,No,,,,,Strongly Disagree,"My organization's IT department prefers ""out of the box"" solutions and outsources a lot of IT work. When we use open source software, a third party hosts it. ","No, but we are planning to develop requirements in the next year","Eventual availability only (dark archive/disaster recovery),Offline availability (i.e. able to retrieve on request within two business days),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)",None,,,,No,,,We are working on a plan for providing different services as different requirements arise,We do not do fixity checks on our content,,,Disagree,Strongly Disagree,Agree,Disagree,,,,,No,Museum,
5/23/19 22:34,5/23/19 22:39,100,316,TRUE,5/23/19 22:39,R_OfJPF8baxLSpncB,anonymous,EN,No,Onsite storage,"Physical servers,Virtual servers",,Central IT,,I'm not sure,Normalised versions (open source formats) and original files. Backup copies as part of IT processes. AV material kept on tape with 3 copies geographically distributed. ,3,Yes,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,No,,
5/24/19 6:11,5/24/19 6:24,100,800,TRUE,5/24/19 6:24,R_1hAUjcgZjtjHdJB,anonymous,EN,Yes,"Offsite storage, managed by my organization",Physical servers,,Digital Preservation Team,,"Hardware-based file systems (ntfs, fat, ext, apfs)",Most recent backup.,2,Yes,"Catalogue of archives.
Digital images of pictures and artifacts.
Permenantly.
",Under 1 terabyte,1-10 terabytes,1-10 terabytes,"Yes, we do",Managed by our organization,We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"No, and my organization is uninterested in using commercial cloud storage service providers for keeping one or more copies of its content",,Perfer not to.,"No, and my organization is uninterested in participating in a distributed storage cooperative or system",,,No,,,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,,Some open source,Other:,,Software application,,Agree,,"No, and we do not plan to develop requirements",Not applicable,None,,,,No,,,We have not had requirements for different services,We do not do fixity checks on our content,,,Agree,Agree,Neutral,Disagree,,,,,No,Non-profit,
5/24/19 6:15,5/24/19 6:32,100,998,TRUE,5/24/19 6:32,R_1GHVYOJaNQCyNRK,anonymous,EN,Yes,"Onsite storage,Offsite storage, consortia/cooperative",Physical servers,,"Department/Unit IT,Other:",[DELETED: organization name],I'm not sure,"If something analog is digitized, it must be a tiff at a resolution of a minimum of 300 dpi. For items captured for social media, we use whatever format we can get. We are still working on a system for document files. Once these are ingested into our repository, access copies are made automatically.",2,Yes,"We are just getting started, but we follow the records retention schedule for each state agency.",Under 1 terabyte,1-10 terabytes,1-10 terabytes,"No, but we plan to",Managed by a collaborative arrangement,We have additional copies for some of our content in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,"A new state-wide computer center is under construction at a location 50 miles southeast of the library/archive, with additional backup in [DELETED: location]. [DELETED: organization name] maintains and extra copy [DELETED: location], and plans on having another site further removed from the east coast.","No, but my organization is currently exploring using commercial cloud storage service providers for keeping one or more copies of its content","ArchiveSocial or a similar vendor to capture social media accounts particularly from the Governor's Office, but also for other state agencies.",,"No, my organization is not considering participating in a distributed storage cooperative or system",,We are tied to our relationship with the [DELETED: organization name] for the near future.,Yes,ArchiveIt,No,"Yes, my organization currently contracts out storage services which are managed by another organization","[DELETED: organizaton name], which is an Islandora/Fedora system operated by the [DELETED: organization name] and is a collaboration between the University and the State Library.",,Not applicable,,,,,Disagree,"We are a small agency within state government, have very limited funds and only 2 1/2 IT staff.","No, but we are planning to develop requirements in the next year",High-performance availability (access to large number of simultaneous users/or for HPC),None,,,,No,,,"Services are managed outside of our organization, so we have no control,Our services are not capable of treating content differently",We store fixity information in an independent system,,,Strongly Disagree,Disagree,Disagree,Disagree,,,,,No,Government,
5/23/19 13:18,5/24/19 7:49,100,66656,TRUE,5/24/19 7:49,R_Ab1raLvPIeA6auB,anonymous,EN,No,"Onsite storage,Offsite storage, managed by my organization","Virtual servers,Containers (e.g. Docker, rkt, Kata)",,"Digital Preservation Team,Department/Unit IT",,"Hardware-based file systems (ntfs, fat, ext, apfs),Hybrid file systems (zfs, btrfs)","Our main digital repository supports both preservation and access functions. It is the appropriate storage solution for both preservation and access copies of all University content curatorially-assessed as possessing persistent value. While some content is represented in terms of variant digital representations intended for preservation and access, respectively, other content consists solely of either preservation or access representations. All three types are equally eligible for long-term stewardship. The default replication strategy calls for 4 independent copies, but certain large media objects are replicated only 3 times to reduce the overall storage capacity footprint and associated cost.",4,No,,100-999 terabytes,1-10 petabytes,1-10 petabytes,"Yes, we do",Managed by our organization,We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"No, but my organization is currently exploring using commercial cloud storage service providers for keeping one or more copies of its content","We are considering the use of Glacier Deep Archive to host a high-density, low-cost dark archival replica. We feel this will provide additional administrative and technical heterogeneity and lower overall storage costs.
",,"Yes, my organization currently participates in a distributed storage cooperative or system","We are a member of HathiTrust and contribute mass digitized monographs and serials to its distributed storage network. We are also consortial subscribers of Archive-It for institutionally-situated web archiving. As part of the [DELETED: consortium name] we also are participating in a pilot project to use a private LOCKSS network to store and preserve web archive materials of common curatorial interest.
",,Yes,,Yes,"No, but my organization is currently exploring contracting out storage services which are managed by another organization",,,Some open source,VM Hosting,,Storage appliance,,Strongly Agree,"We feel we would not be exercising prudent preservation stewardship with having at least one full replica of all content managed in technical infrastructure under our direct control.
",Yes,"Offline availability (i.e. able to retrieve on request within two business days),Near-line availability (i.e. able to retrieve on request within three hours),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,"HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",Security is applied and managed within the same regulations and rules as other digital content in our organization,,,,,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly)",2,,Strongly Agree,Strongly Agree,Strongly Agree,Agree,"TRAC,Data Seal of Approval / CoreTrustSeal",,Other:,We will start with internal self-audit while considering full certification by external bodies,Yes,Academic,
5/24/19 9:19,5/24/19 9:30,100,676,TRUE,5/24/19 9:30,R_W8ayaG01pkCctDX,anonymous,EN,No,Onsite storage,Physical servers,,"Digital Preservation Team,Central IT",,"Hardware-based file systems (ntfs, fat, ext, apfs)",,1,No,,10-99 terabytes,10-99 terabytes,10-99 terabytes,"No, but we plan to","Managed by a collaborative arrangement,Managed by an external provider (commercial or non-commercial)",We have complete separate copies of all our content being managed for preservation in distinct places,"Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,Lack of funding/organizational capacity. Lack of UNDERSTANDING / EDUCATION of administration about geographic/administrative distinct copies for preservation and why this is necessary. ,"No, but my organization is planning to use commercial cloud storage service providers for keeping one or more copies of its content",DuraCloud at [DELETED: consortium name]. Leverage consortium and peer institutions for technical and organizational help/decision-making. Community of practice. ,,"No, but my organization is planning to participate in a distributed storage cooperative or system",Chronopolis-distributed network available via DuraCloud at [DELETED: consortium name],,No,,,"No, but my organization is planning to contract out storage services which are managed by another organization","Chronopolis, via DuraCloud at [DELETED: consortium name]",,No,,,,,Strongly Disagree,"Completely different infrastructure from current IT backup models. No need to replicate this expertise and technology in house, when we can use consortiums and infrastructures already in place. ","No, and we do not plan to develop requirements",Eventual availability only (dark archive/disaster recovery),Secure storage with backup and recovery procedures in place,,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files)",Security is applied and managed within the same regulations and rules as other digital content in our organization,No,,,"Services are managed outside of our organization, so we have no control,Our services are not capable of treating content differently",We do not do fixity checks on our content,,,Strongly Agree,Disagree,Strongly Agree,Neutral,,,,,No,Academic,
5/24/19 10:06,5/24/19 11:10,100,3811,TRUE,5/24/19 11:10,R_YY53Hcox4BLDjHj,anonymous,EN,Yes,"Onsite storage,Offsite storage, managed by my organization",Physical servers,,Department/Unit IT,,"Software-based file systems (glusterfs, ceph)","No formal definition, but preservation copies are monitored for any changes. Notification with manual confirmations are done if any file is modified, before it will be propagated to our secondary remote storage.",6,No,,100-999 terabytes,1-10 petabytes,1-10 petabytes,"No, but we plan to",Managed by an external provider (commercial or non-commercial),We have additional copies for some of our content in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Other:",Service failures by local organizational IT,,Lack of tools to interface with storage services. Must develop them in-house currently.,"No, but my organization is currently exploring using commercial cloud storage service providers for keeping one or more copies of its content","AWS Glacier, AWS Glacier Deep Archive",,"Yes, my organization currently participates in a distributed storage cooperative or system",Currently participating in LOCKSS. Formerly a member of DPN.,,Yes,HathiTrust,No,"No, my organization is not considering contracting out storage services which are managed by another organization",,They would first require vetting and approval from central IT. Currently this limits us to AWS and Azure.,Yes,Manual,,Software application,,Neutral,,"No, and we do not plan to develop requirements","Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking",,"HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",We have tailored security specific to our preservation content,No,,,We have not had requirements for different services,Our provider does fixity checking,,,Neutral,Disagree,Agree,Neutral,,,,,Yes,Academic,
5/24/19 10:56,5/24/19 11:11,100,918,TRUE,5/24/19 11:11,R_2EoafR7KWVdy54U,anonymous,EN,Yes,"Offsite storage, managed by my organization","Physical servers,Virtual servers",,"Digital Preservation Team,Central IT,Contracted",,"Hardware-based file systems (ntfs, fat, ext, apfs)","Preservation copy is the original digital object, and when appropriate as a version migrated into a preservation normalized format, plus accompanying preservation metdata",2,No,,10-99 terabytes,100-999 terabytes,100-999 terabytes,"No, we would like to do this but we do not currently have the ability",,,,,,"Coordinating georemote back-up needs with central IT, which is trying to address this problem for the rest of the organization.
Legislative requirements that our data stay within national borders.",Not applicable,,,Not applicable,,,Yes,"Archive-It
INternet Archive",Yes,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,"Central IT provides adequate storage services at a reasonable cost, without any of the risk of entrusting our data to a 3rd party provider",Some open source,VM Hosting,,"Software application,Storage appliance",,Strongly Agree,Adequate infrastructure and expertise within the organization; lack of trust of 3rd party providers,Yes,"Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)","Security is applied and managed within the same regulations and rules as other digital content in our organization,We have tailored security specific to our preservation content",Yes," Bit-level preservation,File format migration,Metadata created,Checksums generated,Arrangement",,,We do fixity checks before and after transactions like ingest or data transfer,,,Neutral,Strongly Agree,Agree,Agree,"ISO 16363 (TDR),TRAC",,Local audits,,No,Government,
5/24/19 9:46,5/24/19 11:15,100,5347,TRUE,5/24/19 11:15,R_1H1QWrJf2GsMSvY,anonymous,EN,Yes,"Onsite storage,Offsite storage, managed by my organization,Offsite storage, commercial cloud (for example, AWS)","Physical servers,Virtual servers",,Department/Unit IT,,"Hardware-based file systems (ntfs, fat, ext, apfs)",We define an accessible master copy by file type and file location and a copy of that master is made the preservation copy through automated systems.,4,No,,10-99 terabytes,100-999 terabytes,100-999 terabytes,"Yes, we do",Managed by our organization,We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",DropBox,,"No, and my organization is uninterested in participating in a distributed storage cooperative or system",,"Lack of staff and funding, affordable option not available in our region.",Yes,"[DELETED: organization name]
World Digital Library
PA Digital
DPLA",Yes,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,,Yes,VM Hosting,,Software application,,Strongly Agree,,Yes,"Eventual availability only (dark archive/disaster recovery),Offline availability (i.e. able to retrieve on request within two business days)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,"Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",Security is applied and managed within the same regulations and rules as other digital content in our organization,No,,,We have not had requirements for different services,"We do fixity checks before and after transactions like ingest or data transfer,We randomly sample content and check for fixity",,,Strongly Agree,Strongly Agree,Disagree,Disagree,,,,,Yes,Non-profit,
5/24/19 13:12,5/24/19 13:29,100,1017,TRUE,5/24/19 13:29,R_rj5qSpB2BK9iLlf,anonymous,EN,Yes,"Onsite storage,Offsite storage, managed by my organization,Offsite storage, commercial cloud (for example, AWS)","Physical servers,Virtual servers",,"Digital Preservation Team,Central IT",,"Hardware-based file systems (ntfs, fat, ext, apfs)","The preservation file is the highest quality version of the file (for both born-digital and digitized materials). For digitized content, this file is created in an uncompressed, non-proprietary format. A ""preservation copy"" is a duplicate of that file that is managed by the storage layer. The checksum of the file is verified when the first copy is saved to the storage layer to make sure it was fully transferred.",3,No,,100-999 terabytes,1-10 petabytes,1-10 petabytes,"Yes, we do","Managed by our organization,Managed by an external provider (commercial or non-commercial)",We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",AWS,,"No, my organization is not considering participating in a distributed storage cooperative or system",,No specific reason. Just not something we have considered at this point. Would be a harder sell now with the recent failure of DPN.,Yes,"HathiTrust, InternetArchive, Archive-It",No,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,We feel more comfortable managing our own storage and have the resources to do so.,No,,,,,Agree,We feel more comfortable managing our own storage and have the resources to do so.,"No, but we are planning to develop requirements in the next year",Near-line availability (i.e. able to retrieve on request within three hours),"Secure storage with backup and recovery procedures in place,Version control,File characterization,File validation,Metadata integration",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files)",Security is applied and managed within the same regulations and rules as other digital content in our organization,No,,,We have not had requirements for different services,"We do fixity checks before and after transactions like ingest or data transfer,Our provider does fixity checking",,,Agree,Agree,Neutral,Neutral,,,,,No,Other (please describe),"Non-profit, Museum, Archives, Academic, Scientific"
5/24/19 10:34,5/24/19 13:32,100,10700,TRUE,5/24/19 13:32,R_25GeU1GvBEhdjUw,anonymous,EN,Yes,"Onsite storage,Offsite storage, managed by my organization",Physical servers,,"Department/Unit IT,Central IT",,"Hardware-based file systems (ntfs, fat, ext, apfs)","We understand the preservation copy to be a original 'master' file that is most suitable for long-term preservation. In most cases, this is an open source file format for images, audio, video, and text files.
One of the 'preservation copies' is uploaded into a preservation repository (Ex Libris Rosetta), which is stored on local physical servers, where 2 backups are maintained -- 1 is on-site, and another is off-site at another campus location that is in a separate geographic area. ",3,Yes,"Our preservation system, Rosetta, is divided into different repositories. The only repository that has an uncertain length of time for content stored is the research data repository. Research data, although important, doesn't have a designated ""permanency' in the same way that the other repositories have (e.g., digitized images from the university archives, which are most certainly have a permanent status). As a library, we have yet to discuss this type of retention, and what actions need to be taken on research data for long-term access. ",10-99 terabytes,10-99 terabytes,100-999 terabytes,"No, we do not, and we are not pursuing this",,,,,"To be clear - we keep backup copies in another geographic place, but this 'other' place is only 50 miles away. Thus, although it's geographically separate, the disaster threat (flooding) is the same. ",,"No, but my organization is currently exploring using commercial cloud storage service providers for keeping one or more copies of its content",We are continuing to explore Amazon Glacier as a dark storage environment for keep 1 preservation copy. ,,"No, my organization is not considering participating in a distributed storage cooperative or system",,"Funding. We are in a hiring freeze, but we are continuing to build partnerships on campus in order to make-the-case for distributed storage services.",Yes,Archive-It,No,"No, my organization is not considering contracting out storage services which are managed by another organization",,,No,,,,,Strongly Agree,"It allows local practitioners (and scholars) to monitor, review, and take action on items locally rather than working through (or with) another party, which can often complicate the process very quickly.",Yes,"Near-line availability (i.e. able to retrieve on request within three hours),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files)",Security is applied and managed within the same regulations and rules as other digital content in our organization,No,,,We don't see a need to provide different services for different subsets,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly)",0.5,,Disagree,Disagree,Agree,Disagree,,,,,Yes,Academic,
5/24/19 12:46,5/24/19 14:02,100,4518,TRUE,5/24/19 14:02,R_2YMli4BTvoVsMLx,anonymous,EN,Yes,"Onsite storage,Offsite storage, managed by my organization","Physical servers,Virtual servers,Containers (e.g. Docker, rkt, Kata)",,"Digital Preservation Team,Department/Unit IT",,"Hardware-based file systems (ntfs, fat, ext, apfs),Software-based file systems (glusterfs, ceph)","all copies are preservation copies. replication counts are determined by managers, by qualities of the data itself, or by SLAs",5,Yes,all types of content kept forever,More than 10 petabytes,More than 10 petabytes,More than 10 petabytes,"Yes, we do",Managed by our organization,We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"No, and my organization is uninterested in using commercial cloud storage service providers for keeping one or more copies of its content",,vendor lock; unreliability; high cost; general evilness of corporations,"Yes, my organization currently participates in a distributed storage cooperative or system","multiple, but only for small portions of preserved data",,Yes,most all you could list; mainly b/c we are one of them,Yes,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,see prior response to similar question,Yes,Other:,"all of the above, plus others",Other:,all of the above,Strongly Agree,see prior responses to previous preference questions,Yes,"Eventual availability only (dark archive/disaster recovery),Offline availability (i.e. able to retrieve on request within two business days),Near-line availability (i.e. able to retrieve on request within three hours),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users),High-performance availability (access to large number of simultaneous users/or for HPC)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)","Security is applied and managed within the same regulations and rules as other digital content in our organization,We have tailored security specific to our preservation content",Yes," Bit-level preservation,File format migration,Metadata created,Checksums generated,Arrangement",,,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly),We do fixity checks on a portion of the content we are preserving at fixed intervals,We randomly sample content and check for fixity,We store fixity information in an independent system",x,"varies. these fixity questions assume a model where one model/approach applies to all content, which is not the case. multiple interviews/approaches can apply to various types of content or collection (or action) that are too various to enumerate here",Agree,Agree,Neutral,Disagree,,,,,Yes,Non-profit,
5/23/19 9:39,5/24/19 14:32,100,104028,TRUE,5/24/19 14:32,R_33ptq6cjpqWGN4P,anonymous,EN,Yes,"Onsite storage,Offsite storage, managed by my organization,Offsite storage, commercial cloud (for example, AWS)",Physical servers,,"Digital Preservation Team,Department/Unit IT,Central IT",,"Hardware-based file systems (ntfs, fat, ext, apfs)",A peservation copy is the file with the least amount of compression. It varies by format. We keep two backups of all files. For A/V we have 2 or 3 versions of a file in different formats and for images we primarily use TIF. ,2,No,,100-999 terabytes,100-999 terabytes,100-999 terabytes,"No, we would like to do this but we do not currently have the ability",,,,,,Currently finding the right partner or service to use has been a problem. We had planned on using DPN for some of this but now we are in a bit of a standstill. ,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",We only use S3 for a small subset of our content. We use it as a backup of our Institution repository. We also have copies of most of those files on servers on campus as well. ,,"Yes, my organization currently participates in a distributed storage cooperative or system",LOCKSS and Portico. We have started to look into Metaarchive but not real progress has been made their. We use LOCKSS and Portico as a back up of journals and publications that we subscribe to. We have not made much progress yet on determine a service for our cultural heritage material. ,,Yes,Archive-It,No,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,Seems like it would just make things more complicated.,No,,,,,Neutral,This would be more of a question for our central IT people. They don't seem to have too strong of feelings one way or another. ,"No, but we are planning to develop requirements in the next year","Eventual availability only (dark archive/disaster recovery),Near-line availability (i.e. able to retrieve on request within three hours),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)",Secure storage with backup and recovery procedures in place,,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files)",We have tailored security specific to our preservation content,No,,,We don't see a need to provide different services for different subsets,We do fixity checks before and after transactions like ingest or data transfer,,,Agree,Neutral,Neutral,Disagree,,,,,Yes,Academic,
5/24/19 6:21,5/24/19 15:27,100,32786,TRUE,5/24/19 15:27,R_2PdK1i6DwqIN56G,anonymous,EN,Yes,"Offsite storage, managed by my organization,Offsite storage, commercial cloud (for example, AWS)",Physical servers,,Other:,"encargado del área de digitalización
[From Google Translate: digitization area manager]","Hardware-based file systems (ntfs, fat, ext, apfs),I'm not sure","una copia de preservación, es el conjunto información detallada de los archivos, para poder sobrevivir y ser leídos en el futuro, independiente de los soportes de respaldo. asegurando integridad y veracidad de la información. los respaldos los realizamos: copia dobles de los máster de captura,( formatos sin compresion tiff 6.0, con metadatos incrustados iptc) respaldada en disco duro rígido WD black de 4 TB (realizamos dos copias, off line)
[From Google Translate: a copy of preservation, is the set detailed information of the archives, to be able to survive and to be read in the future, independent of the supports of backup. ensuring integrity and truthfulness of the information. the backups are made: double copies of the capture masters, (formats without compression tiff 6.0, with embedded metadata iptc) backed up on hard disk WD dark 4 TB (we make two copies, off line)]",3,Yes,"contenidos : Digitalizaciones de diferentes soportes y documentos patrimoniales,
tenemos conservados archivos de hace 10 años atrás.
[From Google Translate: contents: Digitization of different media and heritage documents,
We have preserved files 10 years ago.]
cuanto tiempo mas los queremos conservar no lo tenemos pensado....",10-99 terabytes,10-99 terabytes,100-999 terabytes,"No, but we plan to",Managed by a collaborative arrangement,We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,"obstaculos
no tenemos lugar físico en otra región donde guardar copias y quien las mantenga o alerte de problemas.
[From Google Translate: obstacles
We have no physical place in another region where to keep copies and who keeps them or alerts them of problems.]","Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content","almacenamiento en google drive
[From Google translate: google drive storage]",,"No, but my organization is planning to participate in a distributed storage cooperative or system",,,No,,,"No, my organization is not considering contracting out storage services which are managed by another organization",,"por los altos costos.
y mantenimiento de las condiciones a largo plazo
[From Google Translate: Because of the high costs.
and maintenance of long-term conditions]
",Not applicable,,,,,Neutral,,Yes,Offline availability (i.e. able to retrieve on request within two business days),Metadata integration,,,,No,,,"We don't see a need to provide different services for different subsets,We have not had requirements for different services",We do not do fixity checks on our content,,,Agree,Agree,Agree,Agree,Other:,"no aplica
[From Google Translate: does not apply]",Local audits,,No,Archives,
5/24/19 17:29,5/24/19 17:44,100,895,TRUE,5/24/19 17:44,R_3Kxs5M2HWYpgj7o,anonymous,EN,Yes,Onsite storage,"Physical servers,Virtual servers",,"Department/Unit IT,Central IT",,I'm not sure,,1,No,,1-10 terabytes,1-10 terabytes,1-10 terabytes,"No, but we plan to",Managed by our organization,"We have multiple additional copies in distinct places, of which one or more are complete and one or more are partial","Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"No, but my organization is currently exploring using commercial cloud storage service providers for keeping one or more copies of its content","DuraCloud, Amazon WS3, Chronopolis. These three are available to us through a consortial statewide membership. ",,"Yes, my organization currently participates in a distributed storage cooperative or system",LOCKSS.,,Yes,"HathiTrust, Digital Public Library of America.",No,"No, but my organization is currently exploring contracting out storage services which are managed by another organization",,,Some open source,,,Software application,,Neutral,,"No, but we are planning to develop requirements in the next year","Eventual availability only (dark archive/disaster recovery),Offline availability (i.e. able to retrieve on request within two business days),Near-line availability (i.e. able to retrieve on request within three hours)",,,,,No,,,We are working on a plan for providing different services as different requirements arise,,,,Neutral,Disagree,Agree,Disagree,,,,,No,Academic,
5/26/19 10:20,5/26/19 11:11,100,3044,TRUE,5/26/19 11:11,R_2zcLOBAiYNiBrhY,anonymous,EN,No,"Onsite storage,Offsite storage, managed by my organization",Virtual servers,,Central IT,,"Hybrid file systems (zfs, btrfs)","A preservation copy is a complete AIP. The AIP contains:
- digital object incl. possibly several versions if the object has been migrated / altered in any way
- full metadata (descriptive, administrative, structural, preservation) incl. possibly several versions if the metadata has been updated
An AIP resides in a dark archive and user access is not granted to it - exception being the digital preservation team who may access the AIP via the digital preservation solution.",2,No,,100-999 terabytes,100-999 terabytes,1-10 petabytes,"Yes, we do",Managed by our organization,We have complete separate copies of all our content being managed for preservation in distinct places,"Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ,Other:",Local disaster threats like fire,,,"No, my organization is not considering using commercial cloud storage service providers for keeping one or more copies of its content",,Currently have our own data center and a second copy in the partnering univerities data center. No need for cloud storage.,"No, my organization is not considering participating in a distributed storage cooperative or system",,"Run our own digital preservation system. Storing data within a distributed storage cooperative would be against some data security regulations, e.g. for preservation-as-a-service, where we preserve data for third parties.",No,,,"No, my organization is not considering contracting out storage services which are managed by another organization",,Focus is on managing data ourselves,Some open source,Manual,,Storage appliance,,Strongly Agree,Independence from other institutions; digital preservation is on of the core activities of the library,Yes,"Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",Security is applied and managed within the same regulations and rules as other digital content in our organization,Yes," Bit-level preservation,File format migration,Metadata created,Checksums generated,Arrangement",,,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly)",12,,Agree,Strongly Agree,Agree,Agree,"Data Seal of Approval / CoreTrustSeal, Nestor Seal for Trustworthy Digital Archives",,Full certification according to chosen trusted digital repository standards,,No,Other (please describe),National Subject Library
5/28/19 6:09,5/28/19 6:19,100,595,TRUE,5/28/19 6:19,R_1hWgwhnoSqfepl1,anonymous,EN,No,"Onsite storage,Offsite storage, managed by my organization,Offsite storage, consortia/cooperative,Offsite storage, commercial cloud (for example, AWS)","Physical servers,Virtual servers,Containers (e.g. Docker, rkt, Kata)",,"Digital Preservation Team,Department/Unit IT,Central IT,Contracted",,"Hardware-based file systems (ntfs, fat, ext, apfs),Software-based file systems (glusterfs, ceph)","The Preservation copy is the thing we commit to preserve. We keep other things like access derivatives, but we don't commit to preserve those long term. For those other things we may make less copies. ",6,Yes,All types of digital content. Committed to keep them forever,1-10 petabytes,1-10 petabytes,More than 10 petabytes,"Yes, we do",Managed by an external provider (commercial or non-commercial),"We have multiple additional copies in distinct places, of which one or more are complete and one or more are partial","Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content","Amazon
Azure
Wasabi
Google",,"Yes, my organization currently participates in a distributed storage cooperative or system",LOCKSS,,Yes,"Archive-it, Hathi-trust",Yes,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,Not sure,Some open source,VM Hosting,,Software application,,Neutral,There are pros and cons either way. It's about risk mitigation and some options are not possible for us so instead we mitigate the risks of the options that are available. ,"No, but we are planning to develop requirements in the next year","Near-line availability (i.e. able to retrieve on request within three hours),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users),High-performance availability (access to large number of simultaneous users/or for HPC)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers,Other services (please describe):",Emulation,"Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",Security is applied and managed within the same regulations and rules as other digital content in our organization,Yes," Bit-level preservation,File format migration,Metadata created,Checksums generated,Arrangement",,,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on a portion of the content we are preserving at fixed intervals,We randomly sample content and check for fixity,We store fixity information in an independent system,We use a tamper-resistant fixity check mechanism (e.g. LOCKSS, ACE),Our provider does fixity checking",,We aim to check our content once per year. ,Neutral,Strongly Agree,Agree,Agree,ISO 16363 (TDR),,Full certification according to chosen trusted digital repository standards,,Yes,Academic,
5/28/19 9:12,5/28/19 9:46,100,2033,TRUE,5/28/19 9:46,R_DiaAkPjQiebn12F,anonymous,EN,Yes,"Onsite storage,Offsite storage, managed by my organization,Offsite storage, consortia/cooperative","Physical servers,Virtual servers",,"Department/Unit IT,Central IT",,I'm not sure,"Copy that is not used for access, on ""dark"" server that is checked for bitrot. ",2,Yes,"Unique digital files - indefinitely
Digitized unique content - 10 years
Digitized common content - 2 years",1-10 terabytes,1-10 terabytes,1-10 terabytes,"Yes, we do","Managed by our organization,Managed by an external provider (commercial or non-commercial)",We have additional copies for some of our content in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",Amazon -- what consortium is using,,"Yes, my organization currently participates in a distributed storage cooperative or system",Chronopolis,,No,,,"Yes, my organization currently contracts out storage services which are managed by another organization",,,Some open source,Manual,,"Software application,Storage appliance",,Agree,Paranoia by administration of others controlling all the files.,"No, but we are planning to develop requirements in the next year",Eventual availability only (dark archive/disaster recovery),"Periodic fixity checking,Version control,Persistent identifiers",,,,Yes," Bit-level preservation,Metadata created",,,We do fixity checks before and after transactions like ingest or data transfer,,,Neutral,Disagree,Neutral,Neutral,,,,,No,Academic,
5/28/19 9:36,5/28/19 10:25,100,2940,TRUE,5/28/19 10:25,R_1r8IUBCbTc3AWRF,anonymous,EN,Yes,"Onsite storage,Offsite storage, commercial cloud (for example, AWS)",Physical servers,,Department/Unit IT,,"Hardware-based file systems (ntfs, fat, ext, apfs),I'm not sure",We treat as-scanned masters as our preservation copy.,2,No,,100-999 terabytes,100-999 terabytes,100-999 terabytes,"Yes, we do",Managed by an external provider (commercial or non-commercial),We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",Amazon Glacier for financial reasons (cheaper).,,"No, my organization is not considering participating in a distributed storage cooperative or system",,We participated in MetaArchive but it was too costly without much benefit.,Yes,Hathi Trust; Internet Archive,Yes,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,Cost,Some open source,Manual,,Software application,,Neutral,"We prefer to host/maintain/control due to cost and available resources, but would be open to having it maintained elsewhere.","No, but we are planning to develop requirements in the next year","Eventual availability only (dark archive/disaster recovery),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,File validation",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",Security is applied and managed within the same regulations and rules as other digital content in our organization,No,,,We don't see a need to provide different services for different subsets,"We do fixity checks before and after transactions like ingest or data transfer,Our provider does fixity checking",,,Agree,Agree,Disagree,Disagree,,,,,No,Academic,
5/28/19 10:21,5/28/19 10:46,100,1472,TRUE,5/28/19 10:46,R_3FXva0rMO0Zzj3T,anonymous,EN,Yes,"Onsite storage,Offsite storage, managed by my organization,Offsite storage, commercial cloud (for example, AWS)","Physical servers,Containers (e.g. Docker, rkt, Kata),Other:",External RAID and hard drives,"Digital Preservation Team,Department/Unit IT,Contracted",,I'm not sure,"All of our copies are ""preservation copies"" - what we store in our preservation system. Preservation-worthy objects are stored in the preservation system. Our digitization unit stores some objects for long-term but not permanent storage, but that is a separate unit and those are considered working copies, important but not vital. For objects stored in our preservation system we have master files stored in Near-line storage (AWS Glacier) and multiple access copies stored in Online storage (AWS S3). All are managed through our preservation system management software. We also maintain local copies as an secondary/tertiary backup on external RAID drives and some network servers.",3,No,,10-99 terabytes,10-99 terabytes,100-999 terabytes,"Yes, we do",Managed by an external provider (commercial or non-commercial),We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content","Our preservation system, Preservica, is built on the AWS Government Cloud and we use both the Glacier and S3 storage tier. Our state's centralized IT unit uses a combination of physical servers and cloud storage through MS Azure and AWS.",,"No, my organization is not considering participating in a distributed storage cooperative or system",,As a state government archive it's not really part of our business model,Yes,Archive-It,Yes,"No, but my organization is planning to contract out storage services which are managed by another organization",Our state centralized IT department contracts out data center management operations. Secondary storage (redundant copies outside our preservation system) will be housed at the state data center potentially using MS Azure,,Some open source,Manual,,"Software application,Storage appliance,Sneakernet (manual hard drive exchanges) and manual tracking",,Neutral,We don't host directly mainly due to the costs of maintaining local infrastructure and due to our state IT regulations which require us to the state's centralized data center for storage. This is why our locally hosted storage (tertiary copies) on external RAID drives.,Yes,"Eventual availability only (dark archive/disaster recovery),Offline availability (i.e. able to retrieve on request within two business days),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users),High-performance availability (access to large number of simultaneous users/or for HPC)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)","Security is applied and managed within the same regulations and rules as other digital content in our organization,We have tailored security specific to our preservation content",No,,,We don't see a need to provide different services for different subsets,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly),We do fixity checks on a portion of the content we are preserving at fixed intervals,We randomly sample content and check for fixity,Our provider does fixity checking",1,50% annually,Agree,Strongly Agree,Neutral,Neutral,,,,,Yes,Government,
5/28/19 11:22,5/28/19 11:32,100,613,TRUE,5/28/19 11:32,R_10Hnio0v3WSJC8C,anonymous,EN,No,"Onsite storage,Offsite storage, commercial cloud (for example, AWS)","Physical servers,Virtual servers",,"Department/Unit IT,Central IT",,I'm not sure,"We do not operate a fully-functional digital preservation environment; preservation copies are the same copies that are utilized for discovery and access. In other words, we don't really use the notion of a preservation copy. ",1,No,,Under 1 terabyte,Under 1 terabyte,Under 1 terabyte,"No, we would like to do this but we do not currently have the ability",,,,,,We do not currently have a functioning digital preservation environment aside from our DSpace repository; we do not maintain dig pres policies or workflows. Staff capabilities and funding are current challenges. ,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",We use Amazon S3 for our digital collections (digitized copies of archival records) and ETDs. ,,"No, my organization is not considering participating in a distributed storage cooperative or system",,"We would likely initiate small, local projects prior to investigating cooperative systems. ",Yes,Archive-It; DPLA ,No,"No, my organization is not considering contracting out storage services which are managed by another organization",,We're not at that phase of program development. ,Not applicable,,,,,Neutral,,"No, but we are planning to develop requirements in the next year",,"Secure storage with backup and recovery procedures in place,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files)",Security is applied and managed within the same regulations and rules as other digital content in our organization,No,,,Our services are not capable of treating content differently,We do not do fixity checks on our content,,,Neutral,Disagree,Agree,Strongly Disagree,,,,,Yes,Academic,
5/28/19 13:30,5/28/19 14:25,100,3278,TRUE,5/28/19 14:25,R_27wgXuQtBsUUlhr,anonymous,EN,Yes,Onsite storage,Physical servers,,"Department/Unit IT,Central IT",,"Hardware-based file systems (ntfs, fat, ext, apfs)","In order for [DELETED: organization name] to declare a HOLDING preserved it must be:
In [DELETED: organization name] Digital Archive is stored at the Preservation Centre (humidity and temperature controlled) under strict access restrictions and 4 levels of physical security.
DP staff have access to the digital holdings.
[DELETED: organization name] Digital Archive is stored at the Preservation Centre in different vaults.
Two (2) copies.
Digital objects are stored on the current long-term preservation storage carriers: LTO4 and LTO6.
Digital objects are checksummed at the point of ingest or earlier if possible. The checksum values are stored alongside the digital object in the [DELETED: organization name] Digital Archive.
Preservation carriers are barcoded and tracked in the Collection Management System as well as the Preservation Masters Database.
Digital preservation metadata is captured in the Preservation Masters Database
A reference to an intellectual description ID number is recorded in the Preservation Masters Database.",2,No,,1-10 petabytes,More than 10 petabytes,More than 10 petabytes,"Yes, we do",Managed by our organization,We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"No, but my organization is currently exploring using commercial cloud storage service providers for keeping one or more copies of its content",Preservica AWS Azure,,"No, my organization is not considering participating in a distributed storage cooperative or system",,Unsure at this point whether we have the legal framework to proceed in this direction.,Yes,Internet Archive (web archive),No,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,Unsure at this time if we have the legal framework to move forward.,No,,,,,Agree,Our preservation infrastructure is managed by another government department and this relationship is dictated by another government Act. ,Yes,Offline availability (i.e. able to retrieve on request within two business days),"Secure storage with backup and recovery procedures in place,Periodic fixity checking,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Other services (please describe):",Secure storage with digital preservation and recovery procedures in place (not backup),"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",Security is applied and managed within the same regulations and rules as other digital content in our organization,No,,,We don't see a need to provide different services for different subsets,"We do fixity checks before and after transactions like ingest or data transfer,We randomly sample content and check for fixity,We store fixity information in an independent system",,,Agree,Agree,Strongly Agree,Agree,ISO 16363 (TDR),,Community audits,,No,Other (please describe),National Library and National Archive
5/28/19 18:29,5/28/19 18:50,100,1259,TRUE,5/28/19 18:50,R_1Nxoy1mPABjrUMZ,anonymous,EN,Yes,"Offsite storage, not managed by my organization (e.g. vendor-managed)","Physical servers,Virtual servers",,"Digital Preservation Team,Department/Unit IT,Contracted",,"Hardware-based file systems (ntfs, fat, ext, apfs)","Highest quality original source element. In the case of proprietary raw formats, we transcode to a preservation format and keep both as preservation assets.",2,No,,1-10 petabytes,1-10 petabytes,1-10 petabytes,"Yes, we do",Managed by an external provider (commercial or non-commercial),We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).",,,,"No, but my organization is currently exploring using commercial cloud storage service providers for keeping one or more copies of its content",,,"No, my organization is not considering participating in a distributed storage cooperative or system",,,Yes,Archive-It,No,"Yes, my organization currently contracts out storage services which are managed by another organization",,,Not applicable,,,,,Strongly Disagree,Do not have enough dedicated IT staff or space onsite.,Yes,Offline availability (i.e. able to retrieve on request within two business days),"Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",We have tailored security specific to our preservation content,No,,,"We don't see a need to provide different services for different subsets,We have not had requirements for different services,We are working on a plan for providing different services as different requirements arise","We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly),Our provider does fixity checking",6,,Strongly Agree,Strongly Agree,Agree,Not Applicable,,,,,Yes,Archives,
5/29/19 2:07,5/29/19 2:47,100,2355,TRUE,5/29/19 2:47,R_1DP9iMiOTVsRkLn,anonymous,EN,No,"Offsite storage, managed by my organization,Offsite storage, consortia/cooperative","Physical servers,Virtual servers",,"Digital Preservation Team,Department/Unit IT,Central IT",,"Hybrid file systems (zfs, btrfs)",Our AIPs are stored in two non-colocated servers and there is very restricted access to these. We are also part of the LOCKSS programme.,2,No,,1-10 terabytes,1-10 terabytes,10-99 terabytes,"No, but we plan to",Managed by our organization,We have additional copies for some of our content in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,At present we keep our content on two non co-located servers but in the same general geographic location (ie on our campus). We may move to a hosted service - we are currently looking at this - which would be two non-geographically co-located servers off site. This is more driven by administrative needs (a hosted service would provide infrastructure support) and cost (internal storage is cheaper) than other considerations.,"No, but my organization is currently exploring using commercial cloud storage service providers for keeping one or more copies of its content",We are looking at Arkivum or Artefactual hosted services who use commercial storage but as previously mentioned this is more about the need for infrastructure support than driven by the need for more robust storage.,,"Yes, my organization currently participates in a distributed storage cooperative or system",LOCKSS - but only for our scholarly publications,,No,,,"No, but my organization is currently exploring contracting out storage services which are managed by another organization",,,Yes,VM Hosting,,"Software application,Storage appliance",,Neutral,We would probably marginally prefer to host the service ourselves so that we could tailor it precisely to the use cases we have but we do not currently have the institutional IT support resource to sustain this so are seeking external hosting. We do not have strong feelings about this - the resource has to come from somewhere and it is best provided by those who are experts in the field where ever they are based.,Yes,"Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration",,"Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",Security is applied and managed within the same regulations and rules as other digital content in our organization,No,,,We are working on a plan for providing different services as different requirements arise,"We do fixity checks before and after transactions like ingest or data transfer,We store fixity information in an independent system,We use a tamper-resistant fixity check mechanism (e.g. LOCKSS, ACE)",,,Agree,Agree,Agree,Disagree,,,,,No,Archives,
5/29/19 6:35,5/29/19 6:59,100,1442,TRUE,5/29/19 6:59,R_26gXPaEKdAyVTzI,anonymous,EN,No,"Onsite storage,Offsite storage, managed by my organization,Offsite storage, commercial cloud (for example, AWS)","Physical servers,Virtual servers,Other:",Tape,Digital Preservation Team,,"Hardware-based file systems (ntfs, fat, ext, apfs)","The preservation copy is equivalent to an AIP. It is stored in bags with checksums in dark storage with automated backups, annual fixity checking, and restricted access. ",3,No,,100-999 terabytes,1-10 petabytes,More than 10 petabytes,"Yes, we do","Managed by our organization,Managed by an external provider (commercial or non-commercial)","We have multiple additional copies in distinct places, of which one or more are complete and one or more are partial","Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content","AWS Glacier because we have around 800 TB and growing, including many large files (300GB). Glacier + our in house AIP storage is more affordable than working with Preservica or DPN (when operational). ",,"No, my organization is not considering participating in a distributed storage cooperative or system",,,Yes,Archive-It,No,"No, my organization is not considering contracting out storage services which are managed by another organization",,Costs have been prohibitive ,Yes,Manual,,Storage appliance,,Agree,"We prefer to collaborate with campus IT, which offers affordable solutions. We also prefer to use open source tools when possible.","No, but we are planning to develop requirements in the next year","Eventual availability only (dark archive/disaster recovery),Offline availability (i.e. able to retrieve on request within two business days),Near-line availability (i.e. able to retrieve on request within three hours),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,File validation,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",Security is applied and managed within the same regulations and rules as other digital content in our organization,Yes," Bit-level preservation,File format migration,Metadata created,Checksums generated,Arrangement",,,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on a portion of the content we are preserving at fixed intervals",,we do fixity checks on 40% of our content annually,Neutral,Disagree,Agree,Strongly Disagree,,,,,Yes,Academic,
5/29/19 13:04,5/29/19 13:45,100,2494,TRUE,5/29/19 13:45,R_1r7GG3NK5JRm7I9,anonymous,EN,No,"Onsite storage,Offsite storage, commercial cloud (for example, AWS)",Virtual servers,,"Digital Preservation Team,Department/Unit IT,Central IT",,"Hardware-based file systems (ntfs, fat, ext, apfs),I'm not sure","Master bitstreams and metadata are considered 'preservation copies'; derivatives are not. Currently, the same number of copies are kept for all preservation files.",3,No,,10-99 terabytes,10-99 terabytes,100-999 terabytes,"No, but we plan to","Managed by a collaborative arrangement,Managed by an external provider (commercial or non-commercial)",We have additional copies for some of our content in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,"Lack of funding, organizational capacity (e.g. resources to develop appropriate workflows)","Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content","AWS Glacier, Azure",,"No, but my organization is currently exploring participating in a distributed storage cooperative or system","MetaArchive, APTrust: cooperatives run by peer institutions, using a commonsense approach to preservation services",,Yes,HathiTrust,No,"No, my organization is not considering contracting out storage services which are managed by another organization",,We have more suitable options locally and with peer/cloud services,Some open source,VM Hosting,,Sneakernet (manual hard drive exchanges) and manual tracking,,Strongly Agree,"Since we're responsible for the stewardship of the content, we want the greatest amount of trust and control over the systems managing that content.",Yes,"Eventual availability only (dark archive/disaster recovery),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Version control,File characterization,File validation,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files)","Security is applied and managed within the same regulations and rules as other digital content in our organization,We have tailored security specific to our preservation content",No,,,We are working on a plan for providing different services as different requirements arise,"We store fixity information in an independent system,Our provider does fixity checking",,,Agree,Neutral,Strongly Agree,Disagree,,,,,Yes,Academic,
5/29/19 21:00,5/29/19 22:03,100,3753,TRUE,5/29/19 22:03,R_xrBy5zDqDAaqAfv,anonymous,EN,Yes,"Offsite storage, managed by my organization,Offsite storage, commercial cloud (for example, AWS)","Physical servers,Virtual servers",,"Digital Preservation Team,Central IT,Contracted",,"Hardware-based file systems (ntfs, fat, ext, apfs),Hybrid file systems (zfs, btrfs)","A preservation copy is a digitized or born-digital object, either as the original digital object created (preservation master) or a modified master (for example, cropped or noise-reduced) requiring long-term retention and protection.",2,No,,100-999 terabytes,100-999 terabytes,1-10 petabytes,"Yes, we do","Managed by our organization,Managed by an external provider (commercial or non-commercial)",We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content","Geographic redundancy (Replication), disaster recovery, storage, data management and reporting",,"No, my organization is not considering participating in a distributed storage cooperative or system",,"Data sovereignty issue, lack of local distributed storage cooperative solutions, just replaced our storage systems recently.",Yes,Internet Archive / ArchiveIt,Yes,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,"Data sovereignty, statutory responsibility for the management of our stored content",No,,,,,Agree,"Data sovereignty, statutory responsibility for the management of the content stored on these technical storage infrastructure.",Yes,"Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers,Other services (please describe):","Virus and Malware checking, create derivatives, delivery ","Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)","Security is applied and managed within the same regulations and rules as other digital content in our organization,We have tailored security specific to our preservation content",No,,,We don't see a need to provide different services for different subsets,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly),We store fixity information in an independent system,We use a tamper-resistant fixity check mechanism (e.g. LOCKSS, ACE),Our provider does fixity checking",12,,Agree,Strongly Agree,Disagree,Neutral,,,,,No,Government,
5/30/19 7:38,5/30/19 8:02,100,1443,TRUE,5/30/19 8:02,R_2rGAced6d00Q6F4,anonymous,EN,Yes,"Onsite storage,Offsite storage, managed by my organization","Physical servers,Virtual servers",,"Central IT,Contracted",,"Hardware-based file systems (ntfs, fat, ext, apfs),Software-based file systems (glusterfs, ceph)","For any content, the preservation copy is the the format that we are relying upon primarily for preservation purposes (e.g., master negatives are our preservation copies for microfilm).
Where the preservation copy is digital, we have a master file (the content in its original format) and any number of migrated master files (the content converted to another format) to distribute/lessen preservation risk. The number of migrated masters that exist (if indeed any exist) are contingent on the properties of the master file and the preservation risks associated with those properties (format and version, size, codec, unique features such as spreadsheet macros, etc.).
Digital files, including both preservation copies and other valuable collections-related files (e.g., digitized paper collections) are backed up at varying rates and to varying media according to a tiered schedule. Digital preservation copies are backed up annually, and are stored in Preservica AND on local servers.",12,Yes,"We deal with both digital collections (preservation copies, digitized analog collections, convenience/access-only copies) that have a permanent retention; these collections can have restriction statements of varying terms. We also manage the institutional records center; those materials have retention periods that range from a year to permanent.",10-99 terabytes,100-999 terabytes,100-999 terabytes,"Yes, we do","Managed by our organization,Managed by an external provider (commercial or non-commercial)",We have additional copies for some of our content in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",Preservica Cloud Edition (storage on AWS). We chose preservica for the combination of expandable storage and preservation tools.,,"No, and my organization is uninterested in participating in a distributed storage cooperative or system",,Doesn't fit well with the size and nature of our collections,No,,,"Yes, my organization currently contracts out storage services which are managed by another organization",We have contracted offsite storage for offline digital media (backup tapes).,,Not applicable,,,,,Neutral,"We have both onsite and offsite technical infrastructure, with the infrastructure managed by staff and vendors. We chose this approach to further distribute the risks to our permanent collections -- a vendor can disappear and we can recover, but our building could go up in flames and we could still recover. This approach also allows us to manage resource allocation, so that we can devote more resources to more valuable and at-risk content (e.g., expensive but powerful Preservica PLUS onsite storage PLUS tape backups) and fewer resources to other content (e.g., only on tape refreshed periodically).",,"Eventual availability only (dark archive/disaster recovery),Offline availability (i.e. able to retrieve on request within two business days),Near-line availability (i.e. able to retrieve on request within three hours),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)","Security is applied and managed within the same regulations and rules as other digital content in our organization,We have tailored security specific to our preservation content",Yes," Bit-level preservation,File format migration,Metadata created,Checksums generated,Arrangement",,,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly),We store fixity information in an independent system,Our provider does fixity checking",12,,Strongly Agree,Agree,Disagree,Not Applicable,,,,,Yes,Historical society,
5/30/19 15:53,5/30/19 16:12,100,1138,TRUE,5/30/19 16:12,R_3ehlvckY1eCIx2q,anonymous,EN,Yes,"Offsite storage, managed by my organization,Offsite storage, consortia/cooperative,Offsite storage, commercial cloud (for example, AWS)","Physical servers,Virtual servers",,"Digital Preservation Team,Department/Unit IT,Contracted",,I'm not sure,"A preservation copy is one distinct copy, on one specific architecture. For better or worse, despite what is going on ""under the hood"" our copy in AWS Glacier counts as only a single copy, even though AWS reports that ""Data is automatically distributed across a minimum of three physical Availability Zones that are geographically separated within an AWS Region."" ",3,No,,10-99 terabytes,10-99 terabytes,100-999 terabytes,"Yes, we do","Managed by our organization,Managed by a collaborative arrangement,Managed by an external provider (commercial or non-commercial)",We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content","AWS S3 and Glacier. We run our Archivematica instance full stack on AWS, so it makes it easy to use Glacier as the storage. ",,"Yes, my organization currently participates in a distributed storage cooperative or system","We subscribed to Chronopolis after DPN failed. We considered other options like AP Trust, but had to make the decision fairly quickly so went with Chronopolis, at least on a temporary basis, to give us more time. We only duplicate our most at-risk or valuable content to this service. ",,Yes,HathiTrust,No,"No, my organization is not considering contracting out storage services which are managed by another organization",,"We have a complicated enough system as it is! We use campus resources, which is kind of a grey area--they aren't a libraries organization but it is still internal. ",Some open source,Manual,,"Software application,Sneakernet (manual hard drive exchanges) and manual tracking",,Disagree,"IT is very expensive in Seattle, and we get a better value by using infrastructure managed elsewhere, saving our internal resources for other things. It makes copyright, IP, and security more of a concern, but the trade-offs have been worth it. ","No, but we are planning to develop requirements in the next year",Offline availability (i.e. able to retrieve on request within two business days),"Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",We have tailored security specific to our preservation content,Yes," Bit-level preservation,Metadata created,Checksums generated,Arrangement",,,"We do fixity checks before and after transactions like ingest or data transfer,Our provider does fixity checking",,,Agree,Disagree,Agree,Disagree,,,,,Yes,Academic,
5/28/19 6:56,5/31/19 11:18,100,274915,TRUE,5/31/19 11:18,R_28YtNcHpptTwjJ5,anonymous,EN,Yes,"Onsite storage,Offsite storage, managed by my organization,Offsite storage, not managed by my organization (e.g. vendor-managed),Offsite storage, consortia/cooperative","Physical servers,Virtual servers",,"Digital Preservation Team,Department/Unit IT,Central IT,Contracted",,"Hardware-based file systems (ntfs, fat, ext, apfs),Hybrid file systems (zfs, btrfs),Software-based file systems (glusterfs, ceph)",The highest quality original of a file or its migrated form if the original is not kept. ,5,No,,100-999 terabytes,1-10 petabytes,1-10 petabytes,"Yes, we do","Managed by our organization,Managed by an external provider (commercial or non-commercial)",We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"No, but my organization is planning to use commercial cloud storage service providers for keeping one or more copies of its content",Oracle Cloud,,"No, but my organization is currently exploring participating in a distributed storage cooperative or system",,,Yes,HathiTrust; Internet Archive; Portico,Yes,"No, my organization is not considering contracting out storage services which are managed by another organization",,Need to maintain strict control on materials.,No,,,,,Strongly Agree,Ability to preserve stricter controls over the materials. Lower cost for higher amounts of data. Maintain standards. ,Yes,"Eventual availability only (dark archive/disaster recovery),Offline availability (i.e. able to retrieve on request within two business days),Near-line availability (i.e. able to retrieve on request within three hours),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,File characterization,File validation",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)","Security is applied and managed within the same regulations and rules as other digital content in our organization,We have tailored security specific to our preservation content",Yes," Bit-level preservation,File format migration,Metadata created,Checksums generated,Arrangement",,,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on a portion of the content we are preserving at fixed intervals,We randomly sample content and check for fixity,Our provider does fixity checking",,12,Strongly Agree,Strongly Agree,Strongly Agree,Strongly Agree,"ISO 16363 (TDR),TRAC,Data Seal of Approval / CoreTrustSeal,Other:","Only care about the standards, not certifications per say. Already have the Data Seal of Approval.",Local audits,,Yes,Academic,
6/3/19 9:13,6/3/19 9:36,100,1342,TRUE,6/3/19 9:36,R_3s55dfukZ650VaD,anonymous,EN,Yes,"Onsite storage,Offsite storage, managed by my organization,Offsite storage, commercial cloud (for example, AWS)","Physical servers,Other:",LTO Tape,Department/Unit IT,,I'm not sure,"A preservation copy is a copy of the files and associated minimum metadata, which is primarily PREMIS with a little dublin core. We make the same number of copies for anything that goes in the preservation system, with the understanding that it should only be ingested into the preservation system if it is worth that level of preservation.",3,No,,1-10 petabytes,1-10 petabytes,1-10 petabytes,"Yes, we do","Managed by our organization,Managed by an external provider (commercial or non-commercial)","We have multiple additional copies in distinct places, of which one or more are complete and one or more are partial","Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content","AWS, because it is convenient and affordable. It is only being used by one of our departments and they are in the early stage of implementing it.",,"No, but my organization is currently exploring participating in a distributed storage cooperative or system","Considering putting a component of our holdings in APTrust. This would be as part of a collaboration with another institution that is currently a member of APTrust and would exchange some of their space in APTrust for space in our local preservation storage system.
The purpose would be for us to get some content outside of the state for risk management. Because of the size of our holdings, it isn't affordable for us to get a copy of all content out of the state.",,No,,,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,We have the capacity to do it in-house and want to retain local control for security reasons. It also seems more affordable and we have concerns about the time required to transfer over a petabyte to another company if we did go that route.,No,,,,,Agree,Keep control for privacy and security reasons. Know for sure what is happening to our content. Keeping control over core functions in our workflow and being able to customize it however we see fit.,"No, and we do not plan to develop requirements","Eventual availability only (dark archive/disaster recovery),Offline availability (i.e. able to retrieve on request within two business days)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,Metadata integration,Persistent identifiers",,"HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",Security is applied and managed within the same regulations and rules as other digital content in our organization,No,,,We have not had requirements for different services,We do fixity checks before and after transactions like ingest or data transfer,,,Strongly Agree,Neutral,Disagree,Strongly Disagree,,,,,Yes,Academic,
6/3/19 10:56,6/3/19 11:24,100,1668,TRUE,6/3/19 11:24,R_1JJwtdh0sLCAk9L,anonymous,EN,,,,,,,,,,,,100-999 terabytes,100-999 terabytes,1-10 petabytes,"No, we would like to do this but we do not currently have the ability",,,,,,"Right now, there's a lack of funding. Also, a lack of a clear understanding as to how that tertiary copy should be managed. Cloud? If so, which provider? Something else? What?","No, but my organization is currently exploring using commercial cloud storage service providers for keeping one or more copies of its content","We aren't quite to that level. I believe we've been collecting very basic information from providers such as Amazon, Google, etc. ",,"No, my organization is not considering participating in a distributed storage cooperative or system",,"We were DPN members and found that, even before they went under, it was a struggle to have our needs met because we have a large amount of data to preserve. They had begun to address our needs for a third copy but went under before we could explore that. We are open to distributed storage cooperative but haven't yet found the right fit for us. Perhaps it would be something homegrown and/or regional? ",Yes,We are Archive-It members and preserve websites using that service. ,Yes,"No, my organization is not considering contracting out storage services which are managed by another organization",,"At this time, we are able to manage our own needs. ",No,,,,,Agree,We need to access at least one of the copies on a regular basis for patron request purposes. ,Yes,Near-line availability (i.e. able to retrieve on request within three hours),"Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files)",We have tailored security specific to our preservation content,No,,,We are working on a plan for providing different services as different requirements arise,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly)",12,,Neutral,Neutral,Neutral,Agree,"ISO 16363 (TDR),TRAC",,Local audits,,Yes,Academic,
6/3/19 11:24,6/3/19 11:45,100,1245,TRUE,6/3/19 11:45,R_4TQx1IAWTyB3PVf,anonymous,EN,Yes,"Offsite storage, managed by my organization","Physical servers,Other:",Off-site LTO tape backup ,Department/Unit IT,,"Hardware-based file systems (ntfs, fat, ext, apfs),I'm not sure","A preservation copy would be a copy that was ingested into our digital preservation software, and for which the master copy resides on the associated server. ",3,No,,100-999 terabytes,100-999 terabytes,1-10 petabytes,"No, we would like to do this but we do not currently have the ability",,,,,,"At this time, we do not have ongoing funding to accomplish this. We are investigating our options, though. ","No, but my organization is currently exploring using commercial cloud storage service providers for keeping one or more copies of its content",We aren't at this point in our process yet. ,,"No, my organization is not considering participating in a distributed storage cooperative or system",,"As far as I know we are not actively seeking a cooperative to join. We were members of DPN and found that the size of our archive, the types of materials we collect, and the fact that we were interested in a third copy only (rather than having all three copies distributed) made being a member cost-prohibitive. However, DPN planned some changes (right before they went under) that were promising for users such as ourselves. Perhaps a future cooperative will be able to meet our needs. ",Yes,Archive-It,Yes,"No, my organization is not considering contracting out storage services which are managed by another organization",,We are able to meet our own storage needs at this time. ,No,,,,,Neutral,,Yes,"Eventual availability only (dark archive/disaster recovery),Offline availability (i.e. able to retrieve on request within two business days),Near-line availability (i.e. able to retrieve on request within three hours)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files)",We have tailored security specific to our preservation content,No,,,We are working on a plan for providing different services as different requirements arise,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly)",12,,Neutral,Agree,Agree,Agree,"ISO 16363 (TDR),TRAC",,Local audits,,Yes,Academic,
6/3/19 11:49,6/3/19 12:11,100,1326,TRUE,6/3/19 12:11,R_31seyDKgYFBh14v,anonymous,EN,Yes,"Onsite storage,Offsite storage, not managed by my organization (e.g. vendor-managed),Offsite storage, consortia/cooperative,Offsite storage, commercial cloud (for example, AWS)",Physical servers,,"Department/Unit IT,Central IT",,"Hardware-based file systems (ntfs, fat, ext, apfs),Software-based file systems (glusterfs, ceph)","A preservation copy (e.g., archival TIFF), is generally content of the highest resolution or data quality that could also be in the form of an original file or data format.",4,No,,100-999 terabytes,100-999 terabytes,100-999 terabytes,"Yes, we do","Managed by our organization,Managed by an external provider (commercial or non-commercial)",We have additional copies for some of our content in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",We are currently using a combination of Dternity (Fujifilm) cloud backup and Amazon Web Services for geographically distributed copies of on-premise preservation storage.,,"Yes, my organization currently participates in a distributed storage cooperative or system",APTrust for additional preservation storage backup for infrastructure and organizational threats,,Yes,HathiTrust,No,"No, my organization is not considering contracting out storage services which are managed by another organization",,Existing services and partnerships are currently sufficient,Some open source,Other:,"Dternity, open source software code written locally",Storage appliance,,Neutral,Looking to reduce overhead for local resources,Yes,Near-line availability (i.e. able to retrieve on request within three hours),"Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",Security is applied and managed within the same regulations and rules as other digital content in our organization,Yes," Bit-level preservation,Metadata created,Checksums generated,Arrangement",,,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on a portion of the content we are preserving at fixed intervals,We randomly sample content and check for fixity,We store fixity information in an independent system,Our provider does fixity checking",,We do fixity checking on 25% of our content annually,Strongly Agree,Agree,Neutral,Agree,"ISO 16363 (TDR),Data Seal of Approval / CoreTrustSeal",,Local audits,,No,Academic,
6/3/19 11:27,6/3/19 13:20,100,6750,TRUE,6/3/19 13:20,R_3O3mYUjxRnI8Jd5,anonymous,EN,No,"Onsite storage,Offsite storage, not managed by my organization (e.g. vendor-managed),Offsite storage, consortia/cooperative","Physical servers,Virtual servers",,"Digital Preservation Team,Department/Unit IT,Central IT",,"Hardware-based file systems (ntfs, fat, ext, apfs)","A preservation copy is a copy of the master, the version of record. The numbers of preservation copies retained (and geolocations) vary, based on the level of preservation commitment assigned to the content.",3,Yes,"Level 1, bit-level preservation while the object is in the collection
Level 2, bit-level and information-level preservation is in the collection
Level 3, highest-level of preservation, while the object is in the collection
Collections and content can be deaccessioned at any time, in which case it would be removed.",10-99 terabytes,100-999 terabytes,100-999 terabytes,"Yes, we do",Managed by a collaborative arrangement,We have additional copies for some of our content in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"No, and my organization is uninterested in using commercial cloud storage service providers for keeping one or more copies of its content",,"Cost to move to the cloud, to stay in the cloud, to serve from the cloud, to migrate out of the cloud.","Yes, my organization currently participates in a distributed storage cooperative or system","APTrust, MetaArchive, LOCKSS, CLOCKSS, Portico",,Yes,"HathiTrust, ArchiveIt",Yes,"Yes, my organization currently contracts out storage services which are managed by another organization",IronMountain stores tape backups.,,Not applicable,,,,,Agree,Control over the collections environment is necessary for proper stewardship and sustainability.,"No, but we are planning to develop requirements in the next year","Near-line availability (i.e. able to retrieve on request within three hours),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)",Secure storage with backup and recovery procedures in place,,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files)",Security is applied and managed within the same regulations and rules as other digital content in our organization,Yes,"File format migration,Metadata created,Arrangement",,,"We do fixity checks before and after transactions like ingest or data transfer,Our provider does fixity checking",,,Agree,Neutral,Agree,Strongly Disagree,,,,,Yes,Academic,
6/4/19 8:57,6/4/19 9:39,100,2491,TRUE,6/4/19 9:39,R_2WBYSOVasf4VIAK,anonymous,EN,,,,,,,,,,,,,,,"Yes, we do",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,Not Applicable,,,,,Yes,,
6/4/19 9:58,6/4/19 10:40,100,2527,TRUE,6/4/19 10:40,R_6X5OsJj7dATH53X,anonymous,EN,No,"Onsite storage,Offsite storage, managed by my organization","Physical servers,Virtual servers",,"Digital Preservation Team,Other:","digital preservation stakeholder group, made up of members from several library and IT departments","Hardware-based file systems (ntfs, fat, ext, apfs)","We define preservation copy as the file (within a fileset for an asset) which is of the best quality/highest resolution/richest digital copy of the resource. We also produce derivative access copies (eg MP3 files, JPG files) for use in our online access repository. ",3,Yes,"We keep ingest copies (eg RAW camera files) for a project typically while the ingest phase is still active, and then render access copies and preservation master files from those. The preservation master files, access copies, their sidecar checksums, and object photos are what are kept longterm. ",1-10 terabytes,10-99 terabytes,10-99 terabytes,"No, but we plan to","Managed by our organization,Managed by an external provider (commercial or non-commercial)",We have additional copies for some of our content in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,"One of the major challenges that our preservation program has been facing is organizational IT department change, but I suspect we are in good company. The central campus IT is in the process of making major changes to shared network storage and is working to establish cloud storage (AWS) as a campus service, which obviously we would like participate in. Although in the meantime we manage multiple copies of our digital assets on hard drives, network storage, and less-than-ideal cloud products, this uncertainty and change makes longer term planning challenging. Maintaining collegial and open communication with the digital infrastructure in order to keep our needs on their agenda has been critical. ","No, but my organization is planning to use commercial cloud storage service providers for keeping one or more copies of its content","We are considering either AWS S3 or Glacier or both, depending on the campus service service configuration that plays out within the next fiscal year for the central campus IT. It may end up being that one copy is stored in S3, one in Glacier, one on local hard drives or tape. ",,"No, but my organization is currently exploring participating in a distributed storage cooperative or system",We are exploring APTrust due to connections between our Dean of Libraries and UVA. Participation would provide added redundancy/security for certain classes of assets. ,,Yes,"Archive-it
HathiTrust",No,"No, but my organization is currently exploring contracting out storage services which are managed by another organization",,,Some open source,VM Hosting,,"Software application,Sneakernet (manual hard drive exchanges) and manual tracking",,Agree,The main factors for this include budgetary restrictions (not able to shoulder the cost of outsourcing these activities) and security/privacy concerns for some content. ,"No, but we are planning to develop requirements in the next year","Eventual availability only (dark archive/disaster recovery),Offline availability (i.e. able to retrieve on request within two business days),Near-line availability (i.e. able to retrieve on request within three hours),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",Security is applied and managed within the same regulations and rules as other digital content in our organization,Yes," Bit-level preservation,File format migration,Metadata created,Checksums generated,Arrangement",,,"We do fixity checks before and after transactions like ingest or data transfer,We randomly sample content and check for fixity,We store fixity information in an independent system",,,Agree,Disagree,Strongly Agree,Neutral,,,,,Yes,Academic,
6/3/19 11:45,6/4/19 11:24,100,85137,TRUE,6/4/19 11:24,R_5zQtiVGtGCtMcvv,anonymous,EN,Yes,"Offsite storage, managed by my organization,Offsite storage, not managed by my organization (e.g. vendor-managed)","Physical servers,Other:",LTO tape backup,Department/Unit IT,,"Hardware-based file systems (ntfs, fat, ext, apfs),I'm not sure","A preservation copy is one which is ingested into our digital preservation system software, checksums run and validated, pertinent metadata info extracted and actions run on, then housed on associated servers. We keep two co-located copies on spinning disk and one tape backup in a separate location (but in same disaster area).
",3,No,,100-999 terabytes,100-999 terabytes,1-10 petabytes,"No, we would like to do this but we do not currently have the ability",,,,,,"Lack of funding, lack of cohesive future plan that everyone agrees on.","No, but my organization is currently exploring using commercial cloud storage service providers for keeping one or more copies of its content",We aren't quite to that point yet. Just beginning to explore the option...,,"No, my organization is not considering participating in a distributed storage cooperative or system",,"We were DPN members. DPN wasn't able to meet our needs due to our larger size, though there were some interesting plans to help with this that were never realized before DPN went under. So, I guess at this point, we may be a bit gun shy and also not aware of any cooperatives that would make sense for us, given our size and specific needs. ",Yes,Archive-It,Yes,"No, my organization is not considering contracting out storage services which are managed by another organization",,"At this time, we are able to manage our own needs. However, we are open to changes in the future.",No,,,,,Agree,It's working well now. We also need frequent access to our materials.,Yes,"Eventual availability only (dark archive/disaster recovery),Offline availability (i.e. able to retrieve on request within two business days),Near-line availability (i.e. able to retrieve on request within three hours)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files)",We have tailored security specific to our preservation content,No,,,We are working on a plan for providing different services as different requirements arise,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly)",12,,Neutral,Agree,Agree,Agree,"ISO 16363 (TDR),TRAC",,Local audits,,Yes,Academic,
6/4/19 10:43,6/4/19 11:42,100,3581,TRUE,6/4/19 11:42,R_3JzrubC0VZPsLkC,anonymous,EN,,,,,,,,,,,,1-10 petabytes,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,No,,
6/4/19 11:27,6/4/19 11:43,100,990,TRUE,6/4/19 11:43,R_2DV8Lvwvj5pZXt5,anonymous,EN,Yes,"Offsite storage, managed by my organization,Offsite storage, not managed by my organization (e.g. vendor-managed)","Physical servers,Other:",LTO tape backup,"Digital Preservation Team,Department/Unit IT",,"Hardware-based file systems (ntfs, fat, ext, apfs),I'm not sure","A preservation copy is one for which fixity is created before it is ingested into our digital preservation management system, fixity is validated upon ingest, certain actions are taken on (metadata extraction, virus check, etc.) and is stored on associated servers. Currently, we have two spinning disk copies that are co-located and one LTO tape backup in another location (but same disaster threat).",3,No,,100-999 terabytes,100-999 terabytes,1-10 petabytes,"No, but we plan to","Managed by our organization,Managed by a collaborative arrangement,Managed by an external provider (commercial or non-commercial)",We have additional copies for some of our content in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,"We have a very small portion of our content in multiple places at this time (only Archive-It files currently) but have plans for all content (or most) to be kept in different locations. Lack of funding, as well as a cohesive plan of action is what keeps us from achieving this goal. ","No, but my organization is currently exploring using commercial cloud storage service providers for keeping one or more copies of its content",We haven't gotten to that point in the process yet.,,"No, my organization is not considering participating in a distributed storage cooperative or system",,"We were DPN members and found that our needs were not being met by DPN due to our size and the fact that we needed only one copy of our data held rather than three. I should note, though, that there was a plan in place for users like us that was never realized due to DPN's dissolution. ",Yes,Archive-It,Yes,"Yes, my organization currently contracts out storage services which are managed by another organization","We are not actively considering adding new services, but Archive-It stores our web archive. Also, we still contract with a tape backup provider for LTO tape storage. ",,No,,,,,Agree,"At this time, we're able to do it. Also, we need frequent access to data (at the specific file level rather than complete bags) and are not sure how easy that would be in another situation. ",Yes,"Eventual availability only (dark archive/disaster recovery),Offline availability (i.e. able to retrieve on request within two business days),Near-line availability (i.e. able to retrieve on request within three hours)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",We have tailored security specific to our preservation content,No,,,We are working on a plan for providing different services as different requirements arise,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly)",12,,Neutral,Agree,Agree,Neutral,,,,,Yes,Academic,
6/4/19 13:24,6/4/19 13:51,100,1662,TRUE,6/4/19 13:51,R_12nfYcmr0sJjSLM,anonymous,EN,Yes,"Offsite storage, consortia/cooperative",Virtual servers,,"Digital Preservation Team,Central IT",,I'm not sure,The best quality digital copy that we have for an item.,2,No,,1-10 terabytes,10-99 terabytes,10-99 terabytes,"No, we would like to do this but we do not currently have the ability",,,,,,Lack of finding is the major problem.,"No, but my organization is planning to use commercial cloud storage service providers for keeping one or more copies of its content",,,"No, but my organization is planning to participate in a distributed storage cooperative or system",,,Yes,,No,"Yes, my organization currently contracts out storage services which are managed by another organization",We are using consortium storage service.,,Not applicable,,,,,Strongly Disagree,"We don't have staff who can do this, and even if we hire one we may not be able to keep that person.","No, and we do not plan to develop requirements","Eventual availability only (dark archive/disaster recovery),Offline availability (i.e. able to retrieve on request within two business days),Near-line availability (i.e. able to retrieve on request within three hours)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files)",Security is applied and managed within the same regulations and rules as other digital content in our organization,No,,,We don't see a need to provide different services for different subsets,Our provider does fixity checking,,,Strongly Disagree,Strongly Disagree,Strongly Disagree,Neutral,,,,,Yes,Academic,
5/29/19 14:00,6/4/19 14:15,100,519297,TRUE,6/4/19 14:15,R_1guTx4HLx4gf9Ie,anonymous,EN,Yes,"Onsite storage,Offsite storage, consortia/cooperative,Offsite storage, commercial cloud (for example, AWS)",Virtual servers,,"Digital Preservation Team,Central IT",,"Hardware-based file systems (ntfs, fat, ext, apfs)","For born digital materials, we preserve the original bitstream, and in cases where applicable, the normalized version of the file(s). For digitized materials in decent condition, the analog version is the preservation copy, and the digitized files are ingested into our preservation repository but not sent to our distributed digital preservation system. Our A/V-specific policies are in progress.",4,No,,1-10 terabytes,10-99 terabytes,100-999 terabytes,"Yes, we do",Managed by a collaborative arrangement,We have additional copies for some of our content in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"No, but my organization is planning to use commercial cloud storage service providers for keeping one or more copies of its content","Some of our preservation storage + systems will be in AWS, as part of a larger move toward hosting our archival systems in the cloud.",,"Yes, my organization currently participates in a distributed storage cooperative or system",We have been a member of the MetaArchive Cooperative since 2014.,,Yes,,,"No, my organization is not considering contracting out storage services which are managed by another organization",,,Yes,VM Hosting,,"Software application,Storage appliance",,Agree,,Yes,"Eventual availability only (dark archive/disaster recovery),Near-line availability (i.e. able to retrieve on request within three hours),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",Security is applied and managed within the same regulations and rules as other digital content in our organization,Yes," Bit-level preservation,File format migration,Metadata created,Checksums generated,Arrangement",,,"We do fixity checks before and after transactions like ingest or data transfer,Our provider does fixity checking",,,Strongly Agree,Strongly Agree,Strongly Agree,Neutral,,,,,Yes,Archives,
6/4/19 14:22,6/4/19 14:39,100,1015,TRUE,6/4/19 14:39,R_1rdM3V072Vb0wTv,anonymous,EN,No,Onsite storage,"Physical servers,Virtual servers",,"Department/Unit IT,Central IT",,"Hardware-based file systems (ntfs, fat, ext, apfs)","Read-only access, may or may not be directly viewable by general public.",3,Yes,Most content stored indefinitely. ,1-10 terabytes,1-10 terabytes,10-99 terabytes,"No, we do not, and we are not pursuing this",,,,,"Backups are stored off site, but we have not considered multiple active copies.",,"No, my organization is not considering using commercial cloud storage service providers for keeping one or more copies of its content",,"Currently maintaining multiple backup copies (including cloud backups) is considered sufficient. Expense, security, and the relatively small size of our preservation digital collection are reasons we are not currently pursuing active storage in the cloud.","No, my organization is not considering participating in a distributed storage cooperative or system",,Same answer as previous question.,Yes,HathiTrust,No,"No, my organization is not considering contracting out storage services which are managed by another organization",,Question has not come up.,Some open source,VM Hosting,,"Software application,Storage appliance",,Agree,"Relatively small size of our digital collections makes self-hosting practical, and cost-effective.","No, but we are planning to develop requirements in the next year","Eventual availability only (dark archive/disaster recovery),Offline availability (i.e. able to retrieve on request within two business days),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files)",Security is applied and managed within the same regulations and rules as other digital content in our organization,Yes," Bit-level preservation,File format migration,Metadata created,Checksums generated",,,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly),1,,Neutral,Agree,Neutral,Neutral,,,,,No,Academic,
6/4/19 15:31,6/4/19 15:46,100,943,TRUE,6/4/19 15:46,R_3prkXfZVMpXjXvM,anonymous,EN,Yes,Onsite storage,"Physical servers,Virtual servers",,"Digital Preservation Team,Department/Unit IT,Central IT",,I'm not sure,"Our organization does not have a consistent definition of ""preservation copy"". In this survey I am referring to copies that are only accessible to staff onsite.",4,No,,1-10 terabytes,10-99 terabytes,10-99 terabytes,"No, we would like to do this but we do not currently have the ability",,,,,,"Organizational capacity (essentially a lack of funding, which results in a lack of staff capacity to execute this kind of plan)","No, and my organization is uninterested in using commercial cloud storage service providers for keeping one or more copies of its content",,security and cost,"No, my organization is not considering participating in a distributed storage cooperative or system",,We would like to but we lack the staff capacity to explore the options,Yes,"Open Language Archives Consortium (metadata only, no storage)",No,"No, my organization is not considering contracting out storage services which are managed by another organization",,no particular reason,Some open source,,,,,Strongly Agree,"If it's out of our control, then it's a fixed cash expense, leaving us more vulnerable to data loss if our budget is cut.",Yes,"Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files)",Security is applied and managed within the same regulations and rules as other digital content in our organization,No,,,Our services are not capable of treating content differently,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly),,,Agree,Strongly Agree,Agree,Disagree,,,,,No,Academic,
6/4/19 17:20,6/4/19 21:21,100,14422,TRUE,6/4/19 21:21,R_3G7jMSfi0jxCaIo,anonymous,EN,Yes,"Onsite storage,Offsite storage, commercial cloud (for example, AWS)","Virtual servers,Containers (e.g. Docker, rkt, Kata)",,"Department/Unit IT,Central IT",,"Hardware-based file systems (ntfs, fat, ext, apfs)",,3,No,,1-10 petabytes,1-10 petabytes,10-99 terabytes,"Yes, we do",Managed by an external provider (commercial or non-commercial),We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations)",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",,,"No, and my organization is uninterested in participating in a distributed storage cooperative or system",,As a private institution this does not form part of our ongoing strategy and part of our content is not appropriate for access reasons for distributing to external institutions.,No,,,"Yes, my organization currently contracts out storage services which are managed by another organization",Management of a geographically distributed copy of our archive in te Cloud,,No,,,,,Strongly Agree,"Historically our policy has been to host and manage our preservation archive to effect full control of the risks, recently we have outstsourced some part but we will always want to host and manage at least one of the sites",Yes,Offline availability (i.e. able to retrieve on request within two business days),"Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration",,"Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",We have tailored security specific to our preservation content,No,,,We don't see a need to provide different services for different subsets,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly)",12,,Strongly Agree,Strongly Agree,Strongly Agree,Disagree,,,,,No,Non-profit,
6/5/19 2:37,6/5/19 2:57,100,1172,TRUE,6/5/19 2:57,R_1LidI3mNcEP5ltr,anonymous,EN,Yes,"Offsite storage, not managed by my organization (e.g. vendor-managed)",Physical servers,,"Digital Preservation Team,Contracted",,I'm not sure,,2,No,,10-99 terabytes,100-999 terabytes,100-999 terabytes,"Yes, we do",Managed by an external provider (commercial or non-commercial),We have complete separate copies of all our content being managed for preservation in distinct places,"Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).",,,,"No, and my organization is uninterested in using commercial cloud storage service providers for keeping one or more copies of its content",,,"No, and my organization is uninterested in participating in a distributed storage cooperative or system",,,No,,,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,,Not applicable,,,,,Not Applicable,,"No, and we do not plan to develop requirements",Eventual availability only (dark archive/disaster recovery),"Secure storage with backup and recovery procedures in place,File characterization,Metadata integration,Other services (please describe):",Fixity check on ingest,"Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",We have tailored security specific to our preservation content,No,,,We have not had requirements for different services,"We do fixity checks before and after transactions like ingest or data transfer,Our provider does fixity checking",,,Not Applicable,Agree,Not Applicable,Strongly Agree,ISO 16363 (TDR),,Full certification according to chosen trusted digital repository standards,,No,Other (please describe),EU Institution
6/5/19 5:52,6/5/19 6:04,100,775,TRUE,6/5/19 6:05,R_2t59FC9Kia1OYZA,anonymous,EN,Yes,"Onsite storage,Offsite storage, not managed by my organization (e.g. vendor-managed),Offsite storage, commercial cloud (for example, AWS)",Physical servers,,"Department/Unit IT,Contracted",,"Hardware-based file systems (ntfs, fat, ext, apfs)",We use a three-copy strategy with two onsite and one off-site. The off-site copy is our preservation copy.,3,Yes,"Digital satellite data - forever
Analog and digital aerial dta - 40 years",More than 10 petabytes,More than 10 petabytes,More than 10 petabytes,"Yes, we do",Managed by an external provider (commercial or non-commercial),We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",Amazon. Based on a contract our parent organization has.,,"No, my organization is not considering participating in a distributed storage cooperative or system",,Assets sufficiently covered through existing procedures.,No,,,"Yes, my organization currently contracts out storage services which are managed by another organization",Using the U.S. National Archives and Records Administration (NARA) Federal Records Center services through a contract.,,Some open source,VM Hosting,,"Software application,Storage appliance",,Agree,Better able to control our mandate.,Yes,"Offline availability (i.e. able to retrieve on request within two business days),Near-line availability (i.e. able to retrieve on request within three hours),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users),High-performance availability (access to large number of simultaneous users/or for HPC)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files)",Security is applied and managed within the same regulations and rules as other digital content in our organization,No,,,"We don't see a need to provide different services for different subsets,We have not had requirements for different services","We do fixity checks before and after transactions like ingest or data transfer,We randomly sample content and check for fixity",,,Not Applicable,Strongly Agree,Neutral,Strongly Agree,Data Seal of Approval / CoreTrustSeal,,Full certification according to chosen trusted digital repository standards,,No,Government,
6/5/19 11:13,6/5/19 11:42,100,1709,TRUE,6/5/19 11:42,R_3PAFYpk7NZCc9kr,anonymous,EN,No,"Onsite storage,Offsite storage, managed by my organization,Offsite storage, consortia/cooperative",Virtual servers,,Department/Unit IT,,None of the above,We have public access data and permanent cold storage for digital preservation. Public access are usually lower resolution for website display.,3,Yes,"Most digital copies are PDF, MOV, JPEG, GIF, WAV, and MP3. Active user directories also house these and MS Office type files.",100-999 terabytes,100-999 terabytes,1-10 petabytes,"Yes, we do","Managed by our organization,Managed by a collaborative arrangement",We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"No, but my organization is currently exploring using commercial cloud storage service providers for keeping one or more copies of its content","We are looking at Amazon Cloud for long term cold storage, but do not currently have the budget. Some of our user systems, that are grant based, currently run in the cloud, the rest in geographically different locations.",,"No, my organization is not considering participating in a distributed storage cooperative or system",,"Too expensive, we have a small budget.",No,,,"No, but my organization is currently exploring contracting out storage services which are managed by another organization",,,Some open source,VM Hosting,,Software application,,Strongly Agree,"Cost effective compared to long term read/write in the cloud or through collaboration with other organizations. Some grant based collaboration is cost effective and has been implemented for some digital storage, but only a fraction of our total digital archives.","No, but we are planning to develop requirements in the next year","Online availability (i.e. instant online access for ""moderate"" number of simultaneous users),High-performance availability (access to large number of simultaneous users/or for HPC)","Secure storage with backup and recovery procedures in place,File characterization,File validation,Metadata integration",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",We have tailored security specific to our preservation content,Yes,"Metadata created,Checksums generated,Arrangement",,,"We do fixity checks before and after transactions like ingest or data transfer,We randomly sample content and check for fixity",,,Agree,Disagree,Strongly Agree,Neutral,,,,,No,Academic,
6/5/19 12:24,6/5/19 13:07,100,2566,TRUE,6/5/19 13:07,R_U9l3Zf2fng496Fz,anonymous,EN,Yes,"Onsite storage,Offsite storage, commercial cloud (for example, AWS)","Virtual servers,Other:",Network storage (CIFS mounts),"Digital Preservation Team,Department/Unit IT,Central IT",,"Hardware-based file systems (ntfs, fat, ext, apfs),Software-based file systems (glusterfs, ceph)","Preservation copy for us is a package for the intellectually described object that includes:
- for born digital content: the file in format as received, plus normalized versions for safer future footing (if applicable), optional delivery derivatives, identifiers to system of record for description (both collection and item level), and some modest technical metadata.
- for digitized content: a high resolution master file named in such a way as to coordinate with the physical analog material, optional delivery derivatives, identifiers to system of record for description (both collection and item level), and some modest technical metadata. ",3,No,,10-99 terabytes,100-999 terabytes,100-999 terabytes,"Yes, we do",Managed by our organization,We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content","Using Amazon AWS/S3 currently. We have a campus contract wit this cloud provider, and we can leverage that to provide a cost effective second instance for our preservation copies.
Looking into using Wasabi - it is supposed to be a completely independent vendor, to provide both geographic and commercial diversity to our storage.
Looking into using Azure for the same reason.",,"Yes, my organization currently participates in a distributed storage cooperative or system",LOCKSS - this only covers eJournal titles.,,Yes,HathiTrust,No,"Yes, my organization currently contracts out storage services which are managed by another organization",,,Yes,VM Hosting,,Software application,,Neutral,"We actually have somewhat of a tension in our organization. Those of us in digital preservation want local control to avoid the opacity of vendor provided storage, and the unfortunate ""disappearances"" of data that are somewhat commonplace during storage migrations. However, our budget department feels that the price-point on local storage is too forbidding, and has vetoed the use of funds for the purchase of local storage. This is the same direction of our campus in general - towards cloud services, so we are expecting our currently provisioned local storage to eventually give way to additional cloud solutions. This means we will be migrating to an all-cloud solution over the next few years. ",Yes,"Eventual availability only (dark archive/disaster recovery),Offline availability (i.e. able to retrieve on request within two business days)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,Metadata integration",,"Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",We have tailored security specific to our preservation content,No,,,"Our services are not capable of treating content differently,We have not had requirements for different services","We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on a portion of the content we are preserving at fixed intervals",,"We use a rolling wall for periodic fixity checks - the content that has not had checks in the longest time is checked in the next batch. A batch runs every three days. All content gets checked at the very least annually, and usually more frequently than that. ",Neutral,Neutral,Strongly Agree,Strongly Disagree,,,,,Yes,Academic,
6/3/19 6:21,6/5/19 13:16,100,197689,TRUE,6/5/19 13:16,R_2WBfNCvQaNDBtX2,anonymous,EN,Yes,"Onsite storage,Offsite storage, consortia/cooperative,Offsite storage, commercial cloud (for example, AWS)","Physical servers,Virtual servers,Containers (e.g. Docker, rkt, Kata),Other:","Feedback on question: is a CMS storage infrastructure? This question might be clearer if it simply said ""preservation infrastructure"" as ""storage"" is confusing. ","Digital Preservation Team,Department/Unit IT,Central IT",,"Hardware-based file systems (ntfs, fat, ext, apfs),Hybrid file systems (zfs, btrfs),I'm not sure","We don't use the phrase ""preservation copy"" but would likely consider this to be ""preservation master"" or something similar. We don't have an organizational definition, but a master copies (or instance, as we might refer to it locally) do follow a workflow where different content is assigned different levels of preservation based on the valuation of that content by collaborative teams in the Library. This valuation process may result in different numbers of copies for different.",5,Yes,"Research data needs to be kept in accord with the grant, but then researchers make decisions about what needs to be kept after that. For our other types of collections, we make determinations based on the value of the collection itself, which may contain many different ""types"" of content, and based on those collection decisions and any legal commitments, we don't a defined limit on how long we keep them.",100-999 terabytes,100-999 terabytes,100-999 terabytes,"Yes, we do","Managed by our organization,Managed by a collaborative arrangement,Managed by an external provider (commercial or non-commercial)",We have additional copies for some of our content in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"No, but my organization is planning to use commercial cloud storage service providers for keeping one or more copies of its content","S3, Glacier - we've decided not to use local infrastructure for some content.
",,"Yes, my organization currently participates in a distributed storage cooperative or system","Participating in currently:
AP Trust
HathiTrust
Archive-IT
LOCKSS
CLOCKSS",,Yes,"Archive-It
Hathitrust
CLOCKSS
LOCKSS",Yes,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,No articulated need currently.,Yes,VM Hosting,,"Software application,Storage appliance",,Agree,The only places that this is not true is in our use of commercial cloud providers.,Yes,"Eventual availability only (dark archive/disaster recovery),Offline availability (i.e. able to retrieve on request within two business days),Near-line availability (i.e. able to retrieve on request within three hours),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users),High-performance availability (access to large number of simultaneous users/or for HPC)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)","Security is applied and managed within the same regulations and rules as other digital content in our organization,We have tailored security specific to our preservation content",Yes," Bit-level preservation,File format migration,Metadata created,Checksums generated,Arrangement",,,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly),We use a tamper-resistant fixity check mechanism (e.g. LOCKSS, ACE),Our provider does fixity checking",3,,Strongly Agree,Agree,Agree,Agree,"ISO 16363 (TDR),Data Seal of Approval / CoreTrustSeal",,Community audits,,Yes,Academic,
6/5/19 13:47,6/5/19 13:53,100,369,TRUE,6/5/19 13:53,R_diCVYCOkm6s0yGJ,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,No,,
6/5/19 15:02,6/5/19 15:17,100,889,TRUE,6/5/19 15:17,R_3dXJlzVFBaCNbx7,anonymous,EN,Yes,"Onsite storage,Offsite storage, managed by my organization","Physical servers,Virtual servers",,"Department/Unit IT,Central IT",,"Hardware-based file systems (ntfs, fat, ext, apfs),Hybrid file systems (zfs, btrfs)","""Preservation copy"" is defined as a copy that is accessed only when the access copy is defective. ",3,No,,10-99 terabytes,100-999 terabytes,100-999 terabytes,"Yes, we do",Managed by our organization,We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"No, but my organization is planning to use commercial cloud storage service providers for keeping one or more copies of its content",AWS or Azure,,"No, my organization is not considering participating in a distributed storage cooperative or system",,Cost prohibitive ,No,,,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,We prefer to manage our own assets.,No,,,,,Strongly Agree,,Yes,"Eventual availability only (dark archive/disaster recovery),Offline availability (i.e. able to retrieve on request within two business days),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users),High-performance availability (access to large number of simultaneous users/or for HPC)",Secure storage with backup and recovery procedures in place,,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files)",Security is applied and managed within the same regulations and rules as other digital content in our organization,No,,,"Our services are not capable of treating content differently,We are working on a plan for providing different services as different requirements arise",We randomly sample content and check for fixity,,,Strongly Agree,Agree,Strongly Agree,Neutral,,,,,No,Academic,
5/23/19 9:30,5/23/19 9:30,2,12,FALSE,6/6/19 9:30,R_3MJosNmM1UUagwK,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
6/5/19 6:56,6/6/19 9:36,100,95957,TRUE,6/6/19 9:36,R_2v7Kn7JfaXgmOmH,anonymous,EN,Yes,"Onsite storage,Offsite storage, managed by my organization",Virtual servers,,Department/Unit IT,,I'm not sure,,2,Yes,,1-10 terabytes,10-99 terabytes,10-99 terabytes,"No, we do not, and we are not pursuing this",,,,,,,"No, but my organization is currently exploring using commercial cloud storage service providers for keeping one or more copies of its content",,,"Yes, my organization currently participates in a distributed storage cooperative or system",,,No,,,"No, my organization is not considering contracting out storage services which are managed by another organization",,,No,,,,,Agree,,"No, but we are planning to develop requirements in the next year","Eventual availability only (dark archive/disaster recovery),Offline availability (i.e. able to retrieve on request within two business days),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,,,Yes,Metadata created,,,Our provider does fixity checking,,,Agree,Disagree,Agree,Neutral,,,,,No,Academic,
5/23/19 9:35,5/23/19 9:48,2,761,FALSE,6/6/19 9:48,R_2QJR2t030tV9gnV,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 9:52,5/23/19 9:52,2,7,FALSE,6/6/19 9:52,R_Wewh6LL0RRB5TMt,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 9:29,5/23/19 9:52,2,1382,FALSE,6/6/19 9:53,R_2ymEx5Q7WBiROYz,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 9:54,5/23/19 9:54,2,28,FALSE,6/6/19 9:54,R_viSWyB2Ag4OB5QZ,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 9:54,5/23/19 9:55,2,47,FALSE,6/6/19 9:55,R_3MtXAa7N1ykQV1X,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 9:42,5/23/19 9:58,0,939,FALSE,6/6/19 9:58,R_2qBK88uomxd6Ad1,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 9:56,5/23/19 9:58,2,96,FALSE,6/6/19 9:58,R_2y93wYIkErh14Ot,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 10:09,5/23/19 10:10,2,21,FALSE,6/6/19 10:10,R_2zGUVhyf88ev3ap,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 10:05,5/23/19 10:16,73,612,FALSE,6/6/19 10:16,R_1QKHjpiBofkclgA,anonymous,EN,No,"Offsite storage, not managed by my organization (e.g. vendor-managed),Offsite storage, commercial cloud (for example, AWS)",Virtual servers,,Digital Preservation Team,,I'm not sure,,,No,,1-10 terabytes,1-10 terabytes,1-10 terabytes,"No, we would like to do this but we do not currently have the ability",,,,,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",,,"No, my organization is not considering participating in a distributed storage cooperative or system",,,No,,,"No, but my organization is currently exploring contracting out storage services which are managed by another organization",,,Not applicable,,,,,Strongly Disagree,,"No, but we are planning to develop requirements in the next year","Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)",,,,,No,,,,,,,,,,,,,,,,,
5/23/19 10:21,5/23/19 10:23,2,94,FALSE,6/6/19 10:23,R_VI0DNQ6ccQF7D3P,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 10:27,5/23/19 10:27,2,4,FALSE,6/6/19 10:27,R_b4oPfYKuWBgXaKd,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 10:28,5/23/19 10:30,2,100,FALSE,6/6/19 10:30,R_1DzNoYV5DsQOqjQ,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 10:26,5/23/19 10:32,2,401,FALSE,6/6/19 10:33,R_1Pcv6aDie1BPyER,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 10:34,5/23/19 10:43,2,529,FALSE,6/6/19 10:43,R_3fxeeQjbU5nTKYW,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 10:45,5/23/19 10:46,23,53,FALSE,6/6/19 10:46,R_PzelMxf16rbWhvr,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 10:42,5/23/19 10:59,2,1013,FALSE,6/6/19 10:59,R_3CZcUAienrG1l8f,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 11:17,5/23/19 11:19,16,132,FALSE,6/6/19 11:19,R_23VrpJmVYV1i4HH,anonymous,EN,Yes,"Offsite storage, commercial cloud (for example, AWS)",,,"Digital Preservation Team,Central IT",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/28/19 14:46,6/6/19 11:21,100,765290,TRUE,6/6/19 11:21,R_6X6n0IBW52T6VlD,anonymous,EN,Yes,"Offsite storage, managed by my organization,Offsite storage, commercial cloud (for example, AWS)",Physical servers,,Central IT,,"Hardware-based file systems (ntfs, fat, ext, apfs)","It depends. For born-digital content, the original file that was received from a donor, in its original format, is the preservation copy. For digitized AV content, the unedited, uncompressed file is the preservation master.",2,No,,100-999 terabytes,100-999 terabytes,100-999 terabytes,"Yes, we do","Managed by our organization,Managed by an external provider (commercial or non-commercial)",We have additional copies for some of our content in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",We use Preservica with Amazon S3 and Glacier to keep copies of our born-digital content and plan to use it for our preservation masters of at-risk digitized materials.,,"No, my organization is not considering participating in a distributed storage cooperative or system",,We have certain restrictions with state spending,Yes,Archive It,No,"No, my organization is not considering contracting out storage services which are managed by another organization",,"We do not have a use for it, other than our current Preservica and Archive It subscriptions.",Not applicable,,,,,Agree,"Ideally, we would like to host our own technical infrastructure so that we would have control over all copies and an ability to get under the hood, but we do not currently have adequate IT support or funding to manage a self-hosted repository environment.",Yes,"Offline availability (i.e. able to retrieve on request within two business days),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users),High-performance availability (access to large number of simultaneous users/or for HPC)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",We have tailored security specific to our preservation content,Yes," Bit-level preservation,File format migration,Metadata created,Checksums generated,Arrangement",,,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on a portion of the content we are preserving at fixed intervals,Our provider does fixity checking",,We currently do monthly fixity checks on our born-digital content in Preservica (performed by provider) and monthly fixity checks on our digitized AV content (using Fixity).,Agree,Disagree,Disagree,Disagree,,,,,Yes,Historical society,
5/23/19 11:21,5/23/19 11:27,50,341,FALSE,6/6/19 11:27,R_1FRhqAWHSli8UVj,anonymous,EN,No,"Onsite storage,Offsite storage, managed by my organization,Offsite storage, commercial cloud (for example, AWS)","Physical servers,Virtual servers",,Other:,Not sure,I'm not sure,,2,No,,1-10 terabytes,1-10 terabytes,10-99 terabytes,"No, we do not, and we are not pursuing this",,,,,"Just starting to build a digital preservation program, and this is not the top priority at this time",,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",,,"No, my organization is not considering participating in a distributed storage cooperative or system",,"Again, just starting",No,,,"No, my organization is not considering contracting out storage services which are managed by another organization",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 11:18,5/23/19 11:27,26,542,FALSE,6/6/19 11:28,R_AHFmPyDi8svJpZL,anonymous,EN,Yes,"Offsite storage, managed by my organization,Offsite storage, not managed by my organization (e.g. vendor-managed)","Physical servers,Virtual servers",,Central IT,,I'm not sure,,1,No,,10-99 terabytes,10-99 terabytes,10-99 terabytes,"No, we would like to do this but we do not currently have the ability",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 11:29,5/23/19 11:38,61,561,FALSE,6/6/19 11:38,R_5ime6a84rZL93Hz,anonymous,EN,Yes,"Onsite storage,Offsite storage, managed by my organization,Offsite storage, consortia/cooperative,Offsite storage, commercial cloud (for example, AWS)",Physical servers,,Digital Preservation Team,,"Hardware-based file systems (ntfs, fat, ext, apfs)",,5,No,,10-99 terabytes,100-999 terabytes,100-999 terabytes,"Yes, we do",Managed by our organization,"We have multiple additional copies in distinct places, of which one or more are complete and one or more are partial","Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",Backblaze B2. Cheap. Good interface. ,,"No, but my organization is currently exploring participating in a distributed storage cooperative or system",Duracloud at [DELETED: consortium name],,Yes,Hathi ArchiveIt,Yes,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,Trust,Some open source,Manual,,Software application,,Agree,Control and trust,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 11:22,5/23/19 11:58,2,2176,FALSE,6/6/19 11:59,R_3LbU4ixyUOMGNHW,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 11:58,5/23/19 11:59,2,85,FALSE,6/6/19 12:00,R_2U5VRQlN8qfERTk,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 12:20,5/23/19 12:21,2,69,FALSE,6/6/19 12:22,R_3HUP8ehZWyB7gwg,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 12:21,5/23/19 12:25,16,233,FALSE,6/6/19 12:25,R_2eUY7qx9gdlF3Ru,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 12:32,5/23/19 12:33,16,33,FALSE,6/6/19 12:33,R_p0KOLbwqsg62ETv,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 10:38,5/23/19 12:41,26,7367,FALSE,6/6/19 12:41,R_WBBPhQfLD4ESu1r,anonymous,EN,No,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 12:46,5/23/19 12:46,2,27,FALSE,6/6/19 12:46,R_3KTKEDMyC7PedtS,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 13:02,5/23/19 13:04,2,72,FALSE,6/6/19 13:04,R_1igKjVEy296PWWn,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 10:46,5/23/19 13:15,55,8963,FALSE,6/6/19 13:15,R_2ydXUxeybPA9GyE,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
6/6/19 9:40,6/6/19 13:36,100,14144,TRUE,6/6/19 13:36,R_2P53TBF81yhT5s3,anonymous,EN,Yes,"Onsite storage,Offsite storage, managed by my organization,Offsite storage, consortia/cooperative,Offsite storage, commercial cloud (for example, AWS)",Virtual servers,,Department/Unit IT,,"Hardware-based file systems (ntfs, fat, ext, apfs)",The master file unedited with minimum processing in the preservation format. ,6,Yes,,1-10 terabytes,10-99 terabytes,10-99 terabytes,"Yes, we do","Managed by our organization,Managed by a collaborative arrangement",We have additional copies for some of our content in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"No, but my organization is planning to use commercial cloud storage service providers for keeping one or more copies of its content",Google Cloud Platform and AWS.,,"Yes, my organization currently participates in a distributed storage cooperative or system",APTrust & LOCKSS,,Yes,HathiTrust,Yes,"No, my organization is not considering contracting out storage services which are managed by another organization",,Our storage services meet our current needs. ,No,,,,,Disagree,We don't have the staffing and interest in building and maintaining the local infrastructure. ,Yes,"Near-line availability (i.e. able to retrieve on request within three hours),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",We have tailored security specific to our preservation content,No,,,"We don't see a need to provide different services for different subsets,We have not had requirements for different services","We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly),We store fixity information in an independent system,We use a tamper-resistant fixity check mechanism (e.g. LOCKSS, ACE),Our provider does fixity checking",3,,Agree,Agree,Disagree,Disagree,,,,,Yes,Academic,
5/23/19 13:41,5/23/19 13:43,16,111,FALSE,6/6/19 13:43,R_3PFsCmBtvjD3Ud5,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 12:49,5/23/19 13:45,23,3320,FALSE,6/6/19 13:45,R_SCOpCzSttGIxWdr,anonymous,EN,Yes,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 14:03,5/23/19 14:03,2,28,FALSE,6/6/19 14:03,R_2vcvucKBDqLyVB5,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 14:04,5/23/19 14:05,2,45,FALSE,6/6/19 14:05,R_XH6UgCSHoGyQJRn,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 14:10,5/23/19 14:17,81,432,FALSE,6/6/19 14:17,R_4NQZUywUjoaFOuZ,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 14:30,5/23/19 14:31,2,76,FALSE,6/6/19 14:31,R_3EAwZysgngMM5gU,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 14:29,5/23/19 14:31,2,149,FALSE,6/6/19 14:31,R_2qmbGlOFL5mOzSP,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 15:07,5/23/19 15:13,2,320,FALSE,6/6/19 15:13,R_3Jygvnrp4CUsMJZ,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 15:11,5/23/19 15:14,23,203,FALSE,6/6/19 15:15,R_2bJeSAhdeiqe1ND,anonymous,EN,No,"Onsite storage,Offsite storage, managed by my organization",Physical servers,,Central IT,,None of the above,,,No,,Under 1 terabyte,1-10 terabytes,10-99 terabytes,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
6/6/19 14:53,6/6/19 15:18,100,1536,TRUE,6/6/19 15:18,R_2WBWAqtWC8pEr3f,anonymous,EN,Yes,"Onsite storage,Offsite storage, managed by my organization",Physical servers,,"Digital Preservation Team,Central IT",,"Hardware-based file systems (ntfs, fat, ext, apfs)","A ""preservation copy"" refers to the set of files that form our version of an AIP. This includes: 1) the originally received and accessioned digital content, 2) all the metadata generated regarding that content, its acquisition, authenticity, integrity, completeness, rights, administration, etc., and 3) any preservation master versions of that original content. For example, a set of 10 5.25"" floppy diskettes containing 50 Wordstar files will be accessioned and those diskettes kept in standard collections storage. However, the ""preservation copy"" refers to the contents, the 50 Wordstar files as they are kept in our digital repository together with elements 2 and 3 described above. A preservation master version of a Wordstar file would be a PDF (file format migration).
There are three copies kept, 2 in one location (onsite) and the third is offsite.",3,No,,10-99 terabytes,100-999 terabytes,100-999 terabytes,"No, we do not, and we are not pursuing this",,,,,Not a central IT priority.,,"No, but my organization is currently exploring using commercial cloud storage service providers for keeping one or more copies of its content",,,"No, my organization is not considering participating in a distributed storage cooperative or system",,,Yes,Internet Archive/Archive-It,Yes,"No, but my organization is currently exploring contracting out storage services which are managed by another organization",,,Some open source,Manual,,"Software application,Storage appliance,Sneakernet (manual hard drive exchanges) and manual tracking",,Strongly Agree,,"No, but we are planning to develop requirements in the next year",Offline availability (i.e. able to retrieve on request within two business days),"Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files)",Security is applied and managed within the same regulations and rules as other digital content in our organization,No,,,"Services are managed outside of our organization, so we have no control,Our services are not capable of treating content differently","We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly),We store fixity information in an independent system",1,,Disagree,Disagree,Agree,Agree,"ISO 16363 (TDR),TRAC",,Local audits,,No,Museum,
5/23/19 16:19,5/23/19 16:19,2,9,FALSE,6/6/19 16:20,R_10wQbyekiuvHseM,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 18:12,5/23/19 18:14,16,159,FALSE,6/6/19 18:15,R_3lteHLbEW1uHNO8,anonymous,EN,Yes,"Onsite storage,Offsite storage, commercial cloud (for example, AWS)",Physical servers,,Other:,operations,"Hybrid file systems (zfs, btrfs)",,,Yes,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 18:15,5/23/19 18:18,92,172,FALSE,6/6/19 18:18,R_2dQFhosDAwKD3UZ,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 18:28,5/23/19 18:32,2,266,FALSE,6/6/19 18:32,R_2l9bvL80xFYJR0l,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 18:28,5/23/19 18:37,55,552,FALSE,6/6/19 18:37,R_1pLl3jRaFVXvvYS,anonymous,EN,Yes,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 19:14,5/23/19 19:16,16,142,FALSE,6/6/19 19:16,R_3qvrxWONYFrF8Py,anonymous,EN,No,Onsite storage,Other:,LTO tapes,"Digital Preservation Team,Central IT",,"Hardware-based file systems (ntfs, fat, ext, apfs)",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
6/6/19 19:24,6/6/19 19:44,100,1180,TRUE,6/6/19 19:44,R_CjF59f7vfzc0uu5,anonymous,EN,Yes,"Onsite storage,Offsite storage, consortia/cooperative,Offsite storage, commercial cloud (for example, AWS)","Physical servers,Virtual servers",,Digital Preservation Team,,I'm not sure,The highest resolution/definition copy in a ubiquitous format stored locally as well as in the Cloud.,3,No,,10-99 terabytes,10-99 terabytes,100-999 terabytes,"Yes, we do",Managed by our organization,We have additional copies for some of our content in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content","Chronopolis, because DPN died, use for first-tier content
DuraCloud, consortial agreement, used for ingest/upload
AWS-Glacier, very cheap, use for second-tier content",,"Yes, my organization currently participates in a distributed storage cooperative or system","Chronopolis, reliable and gives some audit reporting",,Yes,"Internet Archive via Archive-It for web content
HathiTrust for just a few government documents",Yes,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,"We have a very robust, library-internal IT department capable of managing storage and other services.",Yes,Manual,,Software application,,Strongly Agree,Robust IT department using almost exclusively open-source applications and platforms.,"No, but we are planning to develop requirements in the next year",Eventual availability only (dark archive/disaster recovery),"Secure storage with backup and recovery procedures in place,Periodic fixity checking,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files)",We have tailored security specific to our preservation content,Yes," Bit-level preservation,File format migration,Metadata created,Checksums generated,Arrangement",,,We do fixity checks on a portion of the content we are preserving at fixed intervals,,We do fixity checks on approximately 60% every two years or fewer.,Agree,Strongly Agree,Disagree,Agree,TRAC,,Community audits,,Yes,Academic,
5/24/19 0:51,5/24/19 1:22,61,1861,FALSE,6/7/19 1:22,R_2lypZiNQqRUcEw1,anonymous,EN,Yes,Onsite storage,"Physical servers,Virtual servers",,Department/Unit IT,,"Hardware-based file systems (ntfs, fat, ext, apfs)",,2,No,,10-99 terabytes,1-10 petabytes,10-99 terabytes,"Yes, we do",Managed by our organization,We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).",,,,"No, my organization is not considering using commercial cloud storage service providers for keeping one or more copies of its content",,,"No, my organization is not considering participating in a distributed storage cooperative or system",,,No,,,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,,Some open source,Manual,,Storage appliance,,Neutral,,,,,,,,,,,,,,,,,,,,,,,,,
5/24/19 2:41,5/24/19 2:42,2,51,FALSE,6/7/19 2:43,R_eFndK9F4vJcI67n,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/24/19 3:58,5/24/19 4:00,2,104,FALSE,6/7/19 4:01,R_2QDslZnOm0K6XFN,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/24/19 4:31,5/24/19 4:47,92,932,FALSE,6/7/19 4:47,R_zc0TXmr3nOPkpe9,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
6/7/19 4:19,6/7/19 4:49,100,1825,TRUE,6/7/19 4:49,R_2cnDATx9cC1A0uO,anonymous,EN,Yes,"Offsite storage, managed by my organization",Virtual servers,,"Digital Preservation Team,Department/Unit IT,Central IT",,I'm not sure,"A preservation copy, in our case is composed by an structure of directories containing the digital objects we want preservate together with the corresponing metadata.
The metadata arein METS format and describe the structure of directories, its contents, a description of them... Summarising: descriptive, administrative and technical information.",2,No,,Under 1 terabyte,Under 1 terabyte,10-99 terabytes,"Yes, we do",Managed by our organization,We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).",,,,"No, my organization is not considering using commercial cloud storage service providers for keeping one or more copies of its content",,,"No, and my organization is uninterested in participating in a distributed storage cooperative or system",,The volume of information we handle nowdays does not require this approach. May be in the future,Yes,"Tesis Doctorals en Xarxa (TDX)
Revistes Catalanes en Accés Obert ",No,"No, my organization is not considering contracting out storage services which are managed by another organization",,Our university has an IT service that takes care of the storage services of our university and we are satisfied with the result.,No,,,,,Agree,It is an historical matter. Our IT service is very strong at our university and it is the way they work,Yes,"Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,"Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",We have tailored security specific to our preservation content,Yes," Bit-level preservation,File format migration,Metadata created,Checksums generated,Arrangement",,,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly)",3,,Agree,Agree,Neutral,Strongly Agree,ISO 16363 (TDR),,Full certification according to chosen trusted digital repository standards,,Yes,Academic,
5/24/19 1:32,5/24/19 5:28,2,14178,FALSE,6/7/19 5:29,R_10H1rNduvFVxbdj,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/24/19 6:54,5/24/19 6:55,2,10,FALSE,6/7/19 6:55,R_2CU3xPacJUnrJcG,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/24/19 6:55,5/24/19 6:59,16,196,FALSE,6/7/19 6:59,R_2VBzmb6AJ5JbMAD,anonymous,EN,No,Onsite storage,Physical servers,,Digital Preservation Team,,I'm not sure,,1,Yes,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/24/19 7:02,5/24/19 7:04,16,120,FALSE,6/7/19 7:04,R_3IZfM6K4hruaHIc,anonymous,EN,No,"Onsite storage,Offsite storage, managed by my organization","Physical servers,Virtual servers",,"Department/Unit IT,Central IT",,I'm not sure,,3,Yes,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/24/19 6:40,5/24/19 7:05,2,1502,FALSE,6/7/19 7:05,R_tVXIJPhKjW5kCYh,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 10:43,5/24/19 7:34,92,75054,FALSE,6/7/19 7:34,R_V3CBpnGkQEhZufv,anonymous,EN,Yes,,,,,,,,,Yes,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/24/19 7:23,5/24/19 8:59,2,5719,FALSE,6/7/19 8:59,R_32L7lbJG6Pt4vdQ,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
6/7/19 8:13,6/7/19 9:11,100,3494,TRUE,6/7/19 9:11,R_1LvQTWmMpYPAccl,anonymous,EN,No,"Onsite storage,Offsite storage, managed by my organization,Offsite storage, consortia/cooperative","Physical servers,Virtual servers,Containers (e.g. Docker, rkt, Kata)",,Department/Unit IT,,"Hardware-based file systems (ntfs, fat, ext, apfs),Software-based file systems (glusterfs, ceph)","Preservation masters = the file that we intend to preserve into forever;
Provisional Masters = best effort, but not open source or an inherited format, that we would potentially re-digitize or migrate in the future;
Access copies = produced from preservation copies either on the fly or are cached",2,No,,10-99 terabytes,100-999 terabytes,100-999 terabytes,"Yes, we do","Managed by a collaborative arrangement,Managed by an external provider (commercial or non-commercial)",We have additional copies for some of our content in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"No, but my organization is currently exploring using commercial cloud storage service providers for keeping one or more copies of its content",exploring AWS,,"No, but my organization is currently exploring participating in a distributed storage cooperative or system",APTrust and MetaArchive,,Yes,"Hathi, Internet Archive",Yes,"No, but my organization is currently exploring contracting out storage services which are managed by another organization",,,Some open source,VM Hosting,,"Software application,Storage appliance,Sneakernet (manual hard drive exchanges) and manual tracking",,Agree,"The degree of control we have, balanced by the cost of operations","No, but we are planning to develop requirements in the next year","Near-line availability (i.e. able to retrieve on request within three hours),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users),High-performance availability (access to large number of simultaneous users/or for HPC)","Secure storage with backup and recovery procedures in place,File characterization,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files)","Security is applied and managed within the same regulations and rules as other digital content in our organization,We have tailored security specific to our preservation content",No,,,We have not had requirements for different services,We do fixity checks on a portion of the content we are preserving at fixed intervals,,"Unknown at this time. We need to document this process. Some is happening, but at interval and what breadth is unknown.",Neutral,Neutral,Neutral,Disagree,,,,,Yes,Academic,
5/24/19 10:06,5/24/19 10:06,2,50,FALSE,6/7/19 10:07,R_ai73X5iC1J23F8B,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/24/19 8:27,5/24/19 10:56,2,8923,FALSE,6/7/19 10:57,R_R31cavhfFjnd3ot,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/24/19 11:36,5/24/19 11:41,61,278,FALSE,6/7/19 11:41,R_2yabxac9YWE7snA,anonymous,EN,,,,,,,,,,,,,,,,,"We have multiple additional copies in distinct places, of which one or more are complete and one or more are partial",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/24/19 11:46,5/24/19 11:47,2,50,FALSE,6/7/19 11:47,R_2CHdfOgEGpWdWGj,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/23/19 11:56,5/24/19 12:06,2,87036,FALSE,6/7/19 12:07,R_3HoUZKSpCCK0yXE,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/29/19 17:28,6/7/19 12:17,100,758898,TRUE,6/7/19 12:17,R_4YKSyynGNn5r0v7,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,Disagree,Neutral,Agree,Disagree,,,,,Yes,Academic,
6/7/19 12:21,6/7/19 13:05,100,2662,TRUE,6/7/19 13:05,R_2zXYmM0y2vjhQCJ,anonymous,EN,No,"Onsite storage,Offsite storage, managed by my organization,Offsite storage, commercial cloud (for example, AWS)","Physical servers,Virtual servers",,"Digital Preservation Team,Central IT",,"Hardware-based file systems (ntfs, fat, ext, apfs),Software-based file systems (glusterfs, ceph)","Generally speaking, it is a stand alone instance of a digital object which is not an access copy. Files are bagged, monitored for fixity and when possible, format validation is performed. We don't keep different numbers of copies for different collections. ",3,No,,1-10 petabytes,1-10 petabytes,1-10 petabytes,"Yes, we do",Managed by our organization,We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content","AWS, Google Cloud",,"No, my organization is not considering participating in a distributed storage cooperative or system",,,Yes,Archiveit,Yes,"No, my organization is not considering contracting out storage services which are managed by another organization",,,Some open source,VM Hosting,,Storage appliance,,Neutral,Local control provides greater access to monitoring content and predicting costs. The cloud storage in particular has too much variability in costs. ,"No, but we are planning to develop requirements in the next year","Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,File validation,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",We have tailored security specific to our preservation content,Yes," Bit-level preservation,File format migration,Metadata created,Checksums generated,Arrangement",,,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly)",5,,Disagree,Neutral,Agree,Disagree,,,,,Yes,Academic,
5/24/19 13:45,5/24/19 13:46,2,42,FALSE,6/7/19 13:46,R_1i9UQKuBFPid6Ex,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
6/7/19 8:47,6/7/19 13:50,100,18216,TRUE,6/7/19 13:50,R_3fNc45QAnsTs083,anonymous,EN,No,"Onsite storage,Offsite storage, not managed by my organization (e.g. vendor-managed),Offsite storage, commercial cloud (for example, AWS)","Physical servers,Virtual servers,Other:",LTO tape,"Digital Preservation Team,Department/Unit IT,Central IT,Other:",Archival Processing,"Hardware-based file systems (ntfs, fat, ext, apfs)","For born-digital, archival holdings, the ""preservation copy"" is the original file and metadata transferred to archives or special collections upon donation. For digitized content, the ""preservation copy"" is the highest resolution master file.",3,No,,100-999 terabytes,100-999 terabytes,100-999 terabytes,"Yes, we do","Managed by our organization,Managed by an external provider (commercial or non-commercial)",We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",Amazon Web Services Standard S3 and Glacier for digitized; looking to expand this provider to born-digital,,"No, my organization is not considering participating in a distributed storage cooperative or system",,"Our local infrastructure already supports the redundancy, fixity, and geographic diversification. For born-digital, many of the cooperatives are geared toward static preservation storage and we need to be able to recall the data for processing. Therefore, there are more complications with versioning control in cooperatives.",Yes,"HathiTrust, Archive-It",Yes,"Yes, my organization currently contracts out storage services which are managed by another organization",LTO tape with Iron Mountain; the service provides a secondary storage medium and another geographic region,,No,,,,,Strongly Agree,"Contracting with external providers greatly benefits us for redundancy and geographic diversification. But despite contracts, true emergency situations and events beyond our control or the companies’ control are still a risk factor. Having a copy of the data in our local infrastructure, under our own control, with fast retrieval reduces the reliance on external parties to steward our data in good faith alone.",Yes,"Eventual availability only (dark archive/disaster recovery),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,"Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",Security is applied and managed within the same regulations and rules as other digital content in our organization,Yes," Bit-level preservation,File format migration,Metadata created,Checksums generated,Arrangement,Other:",File format identification,,"We do fixity checks before and after transactions like ingest or data transfer,Our provider does fixity checking",,,Agree,Agree,Agree,Disagree,,,,,Yes,Academic,
6/7/19 14:58,6/7/19 15:19,100,1245,TRUE,6/7/19 15:19,R_1CqeHKAo8RfvVvd,anonymous,EN,No,"Onsite storage,Offsite storage, managed by my organization","Physical servers,Virtual servers",,Department/Unit IT,,"Hardware-based file systems (ntfs, fat, ext, apfs),Software-based file systems (glusterfs, ceph)",A first class object in our preservation repository.,3,No,,100-999 terabytes,1-10 petabytes,1-10 petabytes,"Yes, we do",Managed by our organization,We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).",,,,"No, but my organization is planning to use commercial cloud storage service providers for keeping one or more copies of its content",GCP and AWS archival storage to provide a relatively cheap copy of the repository in a geographically and potentially technologically distinct solution.,,"No, my organization is not considering participating in a distributed storage cooperative or system",,"We already are a preservation oriented collection cooperative, so it is difficult to add value for our members by participating in another similar organization.",No,,,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,No business case.,Some open source,Manual,,"Software application,Storage appliance",,Strongly Agree,Liability concerns and to maintain full control.,"No, and we do not plan to develop requirements","Eventual availability only (dark archive/disaster recovery),High-performance availability (access to large number of simultaneous users/or for HPC)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)","Security is applied and managed within the same regulations and rules as other digital content in our organization,We have tailored security specific to our preservation content",No,,,We have not had requirements for different services,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly),We store fixity information in an independent system",3,,Strongly Agree,Strongly Agree,Disagree,Strongly Agree,"ISO 16363 (TDR),TRAC",,Full certification according to chosen trusted digital repository standards,,No,Academic,
6/7/19 14:44,6/7/19 15:30,100,2737,TRUE,6/7/19 15:30,R_2fdoFsSyzUBYlz7,anonymous,EN,No,"Onsite storage,Offsite storage, consortia/cooperative,Offsite storage, commercial cloud (for example, AWS)","Physical servers,Virtual servers",,"Department/Unit IT,Central IT",,"Hardware-based file systems (ntfs, fat, ext, apfs),Software-based file systems (glusterfs, ceph)",Any first class object deposited in a repository whose purpose includes digital preservation. The quality of preservation actions and policy employed by the repositories we run and use may vary widely.,3,Yes,"All content except for research data has a ""forever"" promise. Research data has a 10 year promise.",10-99 terabytes,100-999 terabytes,100-999 terabytes,"No, but we plan to",Managed by a collaborative arrangement,We have additional copies for some of our content in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,Funding. Staffing. Solutions for effectively tracking where content is deposited. ,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",To reduce cost and add geographic and technological diversity for the purpose of increasing resiliency.,,"Yes, my organization currently participates in a distributed storage cooperative or system",APTrust.,,Yes,HathiTrust.,Yes,"No, but my organization is currently exploring contracting out storage services which are managed by another organization",,,Some open source,Manual,,"Software application,Storage appliance",,Neutral,"We do not have a business case that requires us to run our own preservation infrastructure, so we make decisions based on value and service.","No, and we do not plan to develop requirements","Eventual availability only (dark archive/disaster recovery),Near-line availability (i.e. able to retrieve on request within three hours),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users),High-performance availability (access to large number of simultaneous users/or for HPC)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Metadata integration,Persistent identifiers",,"HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files),Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",Security is applied and managed within the same regulations and rules as other digital content in our organization,Yes," Bit-level preservation,File format migration,Metadata created,Checksums generated",,,"We do fixity checks before and after transactions like ingest or data transfer,We do fixity checks on a portion of the content we are preserving at fixed intervals,We store fixity information in an independent system,Our provider does fixity checking",,,Agree,Agree,Agree,Strongly Disagree,,,,,Yes,Academic,
5/24/19 23:16,5/24/19 23:17,2,15,FALSE,6/7/19 23:17,R_2Bu5YTHgTERjyXi,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/25/19 19:02,5/25/19 19:16,2,839,FALSE,6/8/19 19:16,R_W3D99j7tQKBA2CR,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/26/19 4:10,5/26/19 4:11,2,25,FALSE,6/9/19 4:11,R_2VyJXaLydHseqnW,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/26/19 12:38,5/26/19 12:39,2,69,FALSE,6/9/19 12:39,R_7Qf3WKiliVCy1tD,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/26/19 23:08,5/26/19 23:09,2,26,FALSE,6/9/19 23:09,R_22oduWFNdTE1Ia1,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/27/19 7:00,5/27/19 7:07,16,408,FALSE,6/10/19 7:08,R_31FuqvemAxdqo5w,anonymous,EN,No,"Onsite storage,Offsite storage, managed by my organization","Physical servers,Virtual servers",,Central IT,,"Hardware-based file systems (ntfs, fat, ext, apfs),I'm not sure",,,No,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
6/10/19 7:04,6/10/19 7:13,100,512,TRUE,6/10/19 7:13,R_3F4gRaoq5CBlYII,anonymous,EN,Yes,"Offsite storage, commercial cloud (for example, AWS)",Physical servers,,Digital Preservation Team,,I'm not sure,"Preservation copies are copies in a sustainable format kept for long term storage. Right now, our preservation workflows are in their infancy stage, so there are a different number of copies kept because of inconsistency in workflow. Digitized material generally only has one preservation copy, while born-digital content has two.",2,No,,1-10 terabytes,1-10 terabytes,10-99 terabytes,"Yes, we do",Managed by an external provider (commercial or non-commercial),We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations)",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",Amazon Aws,,"No, but my organization is planning to participate in a distributed storage cooperative or system",APTrust because of our relationship with [DELETED: organization name] and our participation in other related activities. We will be joining APTrust within the next few months.,,Yes,Archive-It,No,"No, and my organization is uninterested in contracting out storage services which are managed by another organization",,Haven't explored.,Not applicable,,,,,Agree,"We want some control, but have limited staff time to dedicate to it.","No, but we are planning to develop requirements in the next year",Near-line availability (i.e. able to retrieve on request within three hours),"Periodic fixity checking,File characterization,File validation,Format normalization, format migration, or platform emulation for the purpose of format migration,Persistent identifiers",,,,Yes,"File format migration,Checksums generated,Arrangement",,,We do fixity checks before and after transactions like ingest or data transfer,,,Agree,Disagree,Agree,Strongly Disagree,,,,,No,Academic,
5/27/19 7:13,5/27/19 7:15,2,93,FALSE,6/10/19 7:15,R_2335UsYA96d1ESm,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/27/19 7:01,5/27/19 8:13,55,4351,FALSE,6/10/19 8:14,R_2ukndxDH1G9IUwh,anonymous,EN,Yes,"Onsite storage,Offsite storage, managed by my organization","Physical servers,Containers (e.g. Docker, rkt, Kata)",,Department/Unit IT,,"Hybrid file systems (zfs, btrfs),Software-based file systems (glusterfs, ceph)",,3,No,,More than 10 petabytes,More than 10 petabytes,More than 10 petabytes,"No, but we plan to",Managed by a collaborative arrangement,We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,"No, my organization is not considering using commercial cloud storage service providers for keeping one or more copies of its content",,,"No, but my organization is currently exploring participating in a distributed storage cooperative or system",,,Yes,,No,"No, my organization is not considering contracting out storage services which are managed by another organization",,,Yes,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/27/19 8:36,5/27/19 8:37,2,107,FALSE,6/10/19 8:38,R_42a6SfDLFmo3oYh,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/27/19 13:44,5/27/19 13:45,40,59,FALSE,6/10/19 13:46,R_2VBBWiFYytRDw3W,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/27/19 14:20,5/27/19 14:22,2,109,FALSE,6/10/19 14:22,R_xbFTMLKVOIUopnH,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/27/19 14:58,5/27/19 15:11,0,756,FALSE,6/10/19 15:11,R_1KveEJ8JULfQk8A,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
6/10/19 10:14,6/10/19 16:06,100,21076,TRUE,6/10/19 16:06,R_Xw8adnB5BOnL9MB,anonymous,EN,No,"Onsite storage,Offsite storage, not managed by my organization (e.g. vendor-managed),Offsite storage, commercial cloud (for example, AWS)","Physical servers,Virtual servers",,"Digital Preservation Team,Department/Unit IT,Contracted",,"Hardware-based file systems (ntfs, fat, ext, apfs)","A preservation copy is defined as an object that is stored in a separate geographic location. In our case, the underlying technology in use differs across geographic locations as well. Amazon S3, in [DELETED: organization location], and OpenStack Swift in southern California.",2,No,,100-999 terabytes,100-999 terabytes,100-999 terabytes,"Yes, we do",Managed by our organization,We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations)",,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content","Amazon S3, Amazon Glacier",,"No, but my organization is currently exploring participating in a distributed storage cooperative or system","Our organization has considered use of the DAT protocol in the recent past (late 2018), in conjunction with distributed peer-to-peer storage. However we have no plans to move forward with it at the moment. This may of course change in the future.",,Yes,"HathiTrust, Archive-It",No,"No, but my organization is currently exploring contracting out storage services which are managed by another organization",,,Some open source,VM Hosting,,Software application,,Neutral,"Our digital repository software was designed close to 10 years ago. Some of the advantages it provides now, were novel back then, including use of system files to restructure the central database in case of a catastrophic failure. Long term usage of the system has led to adoption by multiple upstream services, and customers across university campuses. It has become ingrained to the point that switching to an externally hosted solution would require a great deal of effort. That said, modernization or optimizations to the system are not out of the question, and would provide a less costly and robust solution in the near term. Hidden costs in an externally hosted system are of course factors to under consideration as well.
In terms of core infrastructure, upon which said software operates, an established process for resource allocation also exists in our organization. This makes spinning up and monitoring cloud-hosted VMs straightforward, while extant funding pathways allow for increasing or decreasing usage (within reason).",Yes,"Near-line availability (i.e. able to retrieve on request within three hours),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Periodic fixity checking,Version control,Metadata integration,Persistent identifiers",,"Recovery is done using multiple preservation copies (i.e., if a file is missing or bad on one preservation copy, another preservation copy is used to replace the missing or bad file)",We have tailored security specific to our preservation content,No,,,We don't see a need to provide different services for different subsets,We do fixity checks on all content we are preserving at fixed intervals (e.g. monthly),0,,Agree,Agree,Neutral,Agree,Data Seal of Approval / CoreTrustSeal,,Full certification according to chosen trusted digital repository standards,,Yes,Academic,
5/27/19 16:30,5/27/19 16:30,2,20,FALSE,6/10/19 16:31,R_1Qc5uVDGmVuwOOU,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/27/19 16:26,5/27/19 16:40,2,823,FALSE,6/10/19 16:40,R_3rHQLtKymg44wWE,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
6/7/19 12:57,6/10/19 16:59,100,273694,TRUE,6/10/19 16:59,R_r3CpBRoKwne4uxb,anonymous,EN,Yes,"Onsite storage,Offsite storage, commercial cloud (for example, AWS)",Virtual servers,,"Digital Preservation Team,Other:","This is not a formalized team, but includes IT & Digital Assets Manager",I'm not sure,"Our preservation copies are primarily images, and so we use 16 bit TIFs for preservation & 8 bit TIFs for access. For born-digital art, preservation copies are ones that are not used for exhibition and should be unchanged from how they were delivered by the artist.",2?,No,,1-10 terabytes,,1-10 terabytes,"No, we would like to do this but we do not currently have the ability",,,,,,,"Yes, my organization currently uses commercial cloud storage service providers for keeping one or more copies of its content",Azure replication (back-up) of our virtual servers.,,"No, my organization is not considering participating in a distributed storage cooperative or system",,Simply have not pursued or been aware of this option.,No,,,"No, my organization is not considering contracting out storage services which are managed by another organization",,This would require funding and resourcing (staff time) to pursue.,No,,,,,Disagree,Staffing and resourcing -- it may simply not be feasible for us to build and maintain the infrastructure over time.,"No, and we do not plan to develop requirements","Eventual availability only (dark archive/disaster recovery),Offline availability (i.e. able to retrieve on request within two business days),Near-line availability (i.e. able to retrieve on request within three hours),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)","Secure storage with backup and recovery procedures in place,Metadata integration",,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files),HDD, SDD, tape, cloud for specified period (i.e., copies of files put on specific media outside your preservation storage, for the purpose of backing up and recovering files)",Security is applied and managed within the same regulations and rules as other digital content in our organization,No,,,"We don't see a need to provide different services for different subsets,We have not had requirements for different services",We do not do fixity checks on our content,,,Neutral,Neutral,Neutral,Disagree,,,,,No,Museum,
5/28/19 7:33,5/28/19 7:34,2,71,FALSE,6/11/19 7:35,R_4Gjt8Zpc6snHpIZ,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/28/19 9:39,5/28/19 10:14,61,2092,FALSE,6/11/19 10:14,R_2PzKtyKP67h0s5i,anonymous,EN,Yes,"Onsite storage,Offsite storage, not managed by my organization (e.g. vendor-managed)","Physical servers,Other:",Born digital materials are sometimes housed on-site on the media in which it arrived.,"Department/Unit IT,Central IT,Contracted",,I'm not sure,"My organization is an archive. A preservation copy of digital materials can be one of two things. A digitized copy of a physical item made available for patron use, or a born digital files received as donations. ",,No,,100-999 terabytes,100-999 terabytes,1-10 petabytes,"Yes, we do","Managed by our organization,Managed by a collaborative arrangement,Managed by an external provider (commercial or non-commercial)",We have complete separate copies of all our content being managed for preservation in distinct places,"Geographic threats (e.g., distance, earthquakes, hurricanes, volcanoes, environmental circumstances or events, governmental or sociopolitical locations),Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).,Technological threats (e.g., failure or lack of independence in media, hardware, software or operating systems; failure of technical services delivered by a supplier; ",,,,Not applicable,,,,,,Yes,Texas Digital Libraries,Yes,,,,Some open source,,,,,Agree,,,,,,,,,,,,,,,,,,,,,,,,,
6/11/19 12:25,6/11/19 13:33,100,4064,TRUE,6/11/19 13:33,R_Y33LIvdrd4WNsn7,anonymous,EN,Yes,Onsite storage,Physical servers,,Central IT,,I'm not sure,"Preservation copy is the first one has been created. They have been stored in a onsite server. we have access copy that was stored in Internet Archives, CONTENTdm, and a sever.",1,No,,10-99 terabytes,10-99 terabytes,10-99 terabytes,"No, but we plan to",Managed by an external provider (commercial or non-commercial),We have additional copies for some of our content in distinct places,"Organizational threats (e.g., administrative or operational failures; financial, legal or regulatory circumstances or events; information security vulnerabilities; obsolescence of technology, infrastructure or suppliers; concentration of technology, infrastructure or suppliers).",,,"lack of funding, lack of support from IT department, not managing the servers (IT department manages the servers)","No, my organization is not considering using commercial cloud storage service providers for keeping one or more copies of its content",,lack of funding ,"No, and my organization is uninterested in participating in a distributed storage cooperative or system",,,Yes,Internet Archives,No,"No, my organization is not considering contracting out storage services which are managed by another organization",,We have 90TB server space that is manage by IT department,Not applicable,,,,,Agree,,"No, but we are planning to develop requirements in the next year","Near-line availability (i.e. able to retrieve on request within three hours),Online availability (i.e. instant online access for ""moderate"" number of simultaneous users)",Secure storage with backup and recovery procedures in place,,"Full, incremental, snapshots for specified period (i.e., conventional IT practices to back up and recover files)",Security is applied and managed within the same regulations and rules as other digital content in our organization,No,,,We have not had requirements for different services,We do not do fixity checks on our content,,,Strongly Agree,Agree,Agree,Agree,ISO 16363 (TDR),,Local audits,,No,Archives,
5/28/19 14:13,5/28/19 14:26,2,755,FALSE,6/11/19 14:26,R_2v0wqzJZCATyNk5,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/28/19 14:46,5/28/19 14:46,16,23,FALSE,6/11/19 14:46,R_z372T7ZqWqYdHFL,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/29/19 8:03,5/29/19 8:06,16,128,FALSE,6/12/19 8:06,R_1KeaKDuWvZnufgE,anonymous,EN,No,"Offsite storage, commercial cloud (for example, AWS)",Other:,don't know,Other:,archives librarian,I'm not sure,"We don't have the money to do much preservation. We have about 4300 documents digitized and stored at vendor's computer in different state. If something happened to our print/analog archives collection, that would be our preservation of those documents.",1,No,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/29/19 8:34,5/29/19 8:35,2,73,FALSE,6/12/19 8:36,R_1jpTBuSTJRqmh04,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/28/19 7:14,5/29/19 8:38,0,91484,FALSE,6/12/19 8:39,R_1hJR6pA1VqXeku0,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/28/19 7:07,5/29/19 11:37,2,102639,FALSE,6/12/19 11:38,R_1NgJB0kCDmqYnfi,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/29/19 13:47,5/29/19 13:48,35,78,FALSE,6/12/19 13:48,R_31uEyv3VThiifh3,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/29/19 15:41,5/29/19 15:41,2,9,FALSE,6/12/19 15:41,R_2PsYQgLYKsCcIVZ,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/28/19 7:26,5/30/19 7:55,2,174533,FALSE,6/13/19 7:55,R_1GCSRHNk0sgDPIA,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/30/19 10:11,5/30/19 10:11,2,21,FALSE,6/13/19 10:11,R_28TDNv7zcQvp95g,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/31/19 4:49,5/31/19 4:52,2,187,FALSE,6/14/19 4:52,R_1DNKMCgZeebvfW7,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
5/31/19 7:35,5/31/19 7:35,2,7,FALSE,6/14/19 7:36,R_1JCsTTRvAmQ8J39,anonymous,EN,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,