Criteria
- Price
- Initial subscription price
- Free storage size limit
- Either total price or price per year
- Individuals
- Organizations (including publishers, scientific societies, libraries, funders, and others)
- Size limit
- Default uploaded file size
- Uploaded file size on request
- Number of files that can be stored
- Total allowed storage capacity
- Allowed data types
- Data types
- What is the plan for ensuring that the data type can be read in the future?
- Research restrictions
- Not allowed material
- Research phase
- Research topic requirement
- Like astronomy, biology, archeology and so on
- Access to data
- Conditions that the files have to fulfill
- Tracking users and statistics
- Restricted Access
- Data security
- How many copies of the data are present?
- How protected are the data?
- Location
- Place located
- Accept material from
- Ownership
- Versions
- Safety
- Sustainability
- What is the plan in case the service gets terminated?
- What funding is there?
- How much do the users of the service contribute with
- How high is the risk of the service getting terminated
- Withdrawal of data
- Revocation of DOIs
- Data privacy
- Virus check
- Encryption
- Form restrictions (like corpus, survey etc)
- Policy/Law
- Preservation of data
- Retention period
- Functional preservation
- File preservation
- Fixity and authenticity
- Metadata
- Access and reuse
- License
- Requirement/wishes (Ingest, Data Management, Preservation, Administration, Archival Storage and General)
- Submission Information Package (SIP)
- Record decision relating to SIP
- Identify data objects
- Validate files
- Automated extraction of metadata
- Record related physical material
- Select and configure automation
- Process large numbers of large files
- Fulfills Dublin Core metadata
- Persistent unique internal identifiers
- PDI associated with content information
- PREMIS metadata schema
- Describe data at different levels of granularity
- Maintain relationship between different file representationsStore technical metadata extracted from filesbetween different file representations
- Store technical metadata extracted from files
- The digital archive will fulfill Dublin Core metadata
- The digital archive will guarantee long-term preservation and integrity of the data
- The digital archive will be certified to the Trusted Repositories Audit and Certification standard
- The digital archive will have access controls that can be used to restrict access to sensitive data if this is necessary
- Preservation plans for individual or groups of files
- Automatic checking performed post-migration
- Record actions, migrations and administrative processes
- Disposal of data where appropriate
- Record of what, when and why material got disposed
- StatisticsReporting capabilities so statistics can be collated
- Monitor the integrity using checksums
- Error report when data are lost or corrupted
- Compliant with OAIS
- Integrate with a range of repository or content management systems
- APIs for integrating with other systems
- Incorporate new digital preservation tools as they become available
- Extracting and exporting data and metadata
- Support and technical help is available
- Under active development
- Community of users exists
...
M – must S – should C – could | Requirement | Zenodo | B2SHARE | B2SAFE | Dryad | Dansk Data Arkiv |
INGEST | ||||||
S | The digital archive will enable us to store administrative information relating to the Submission Information Package (SIP) (information and correspondence relating to receipt of the SIP). | The uploaded data is archived as a Submission Information Package | ||||
S | The digital archive will include a means for recording appraisal decisions relating to the Submission Information Package and individual elements within it. | |||||
M | The digital archive will be able to identify and characterise data objects (where appropriate tools exist). | DOI | ||||
S | The digital archive will be able to validate files (where appropriate tools exist). | All data files are stored along with a MD5 checksum of the file content | ||||
S | The digital archive will support automated extraction of metadata from files. | Upcoming feature: Metadata extraction | ||||
S | The digital archive will virus check files on ingest. | |||||
C | The digital archive will be able to record the presence and location of related physical material. | |||||
S | It will be possible to select and configure the required level of automation within the ingest workflow. | |||||
M | The digital archive will be able to process large numbers of files and files that are large in size. | Large number of files that each are max. 10GB | ||||
DATA MANAGEMENT | ||||||
M | The digital archive will generate persistent, unique internal identifiers. | DOI | ||||
M | The digital archive will ensure that preservation description information (PDI) is persistently associated with the relevant content information. The relationship between a file and its metadata/documentation must be permanent. | |||||
M | The digital archive will support the PREMIS metadata schema and use it to store preservation metadata. | |||||
S | The digital archive will enable us to describe data at different levels of granularity – for example metadata may be attached to a collection, a group of files or an individual file. | |||||
M | The digital archive will accurately record and maintain relationships between different representations of a file (for example, from submitted originals to dissemination and preservation versions that will be created over time). | |||||
M | The digital archive will store technical metadata extracted from files (for example that which is created as part of the ingest process). | |||||
M | Fulfills The digital archive will fulfill Dublin Core metadata | |||||
M | Does the repository The digital archive will guarantee long-term preservation and integrity of the data | |||||
M | Is it The digital archive will be certified to the Trusted Repositories Audit and Certification standard | |||||
M | Access controlsThe digital archive will have access controls that can be used to restrict access to sensitive data if this is necessary | |||||
PRESERVATION PLANNING | ||||||
M | The digital archive will allow preservation plans (such as file migration/normalisation) to be enacted on individual or groups of files. | |||||
C | Automated checking of significant properties of files will be carried out post-migration to ensure these properties are adequately preserved (where appropriate tools exist). | |||||
M | The digital archive will record actions, migrations and administrative processes that occur whilst the digital objects are contained within the digital archive. | |||||
ADMINISTRATION | ||||||
M | The digital archive will allow for disposal of data where appropriate. | |||||
S | A record must be kept of data disposal including what was disposed of, when it was disposed of and reasons for disposal. | |||||
S | The digital archive will have reporting capabilities so statistics can be collated. For example it would be useful to be able to report on numbers of files, types of files, size of files, preservation actions carried out. | |||||
ARCHIVAL STORAGE | ||||||
M | The digital archive will actively monitor the integrity of digital objects on a regular and automated schedule with the use of checksums. | |||||
M | Where problems of data loss or corruption occur, The digital archive will have a reporting/notification system to prompt appropriate action. | |||||
S | The digital archive will be able to connect to, and support a range of storage systems | |||||
GENERAL | ||||||
S | The digital archive will be compliant with the Open Archival Information System (OAIS) reference model. | |||||
M | The digital archive will integrate with a range of repository or content management systems | |||||
S | The digital archive will integrate with our archival management systems. | |||||
S | The digital archive will have APIs or other services for integrating with other systems. | |||||
S | The digital archive will be able to incorporate new digital preservation tools (for migration, file validation, characterisation etc) as they become available. | |||||
M | The digital archive will include functionality for extracting and exporting the data and associated metadata in standards compliant formats. | |||||
S | The software or system chosen for the digital archive will be supported and technical help should be available. | |||||
S | The software or system chosen for the digital archive will be under active development. | |||||
S | A community of users will exist around the software or system to enable sharing of use cases, workflows and to promote developments in line with changes and innovations in the discipline of digital preservation. |
...