Category I | Category II | ||
|---|---|---|---|
Price | Initial subscription price
| 0
|
|
| Free storage size limit | 10GB | ||
Price per GB above this limit | 10kr | ||
Price per year | GB/yearly 5kr | ||
Size limit | Default uploaded file size limit | 10GB |
|
File size limit on request | 10GB | ||
Number of files that can be stored | No limit | ||
Total allowed storage capacity | No limit | ||
Data types |
| All. SPSS-filer format are, though, changed from SAW/POR to TAB. | Text, which get photographed and saved as TIFF files |
Research restrictions | Allowed researchers | All Danish researchers | Danish researchers. The material has to have substantial relevance for the danish state |
Material not allowed | Material that are not important for the Danish society | ||
| Research | Phase | All phases Both the managing active data phase and the data repositories phase have focus, but the recommended preservation time period is 5-10 years | Long-term preservation |
| Disciplinary | ? |
|
Access to data | Open data | Yes |
|
| Embargoed data | Yes | ||
| Closed data | Yes | ||
Tracking users and statistics | ? | ||
Restricted Access | Metadata can always be seen by anybody, but users may restrict access to the actual data. | ||
Data security | Multiple redundant copies |
| |
How protected are the data? | |||
| Location |
| Denmark | Denmark |
Accept material from | Danish researchers | Danish researchers | |
| Ownership | it offers distributed ownership for data authors through virtual web archives named "dataverses." | ||
Ability to have versions | ? | ||
Safety |
| ||
Sustainability | What is the plan in case the service gets terminated? | ? |
|
What funding is there | Funded by the danish state | ||
How high is the risk of the service getting terminated | High risk till more researchers use it | No risk | |
Data | Withdrawal | ? | |
Revocation of DOIs | ? | ||
| Encryption | Yes |
|
Virus check | |||
| Storage of sensitive data | Data can be selected to be viewable to only a number of people, so data are secure |
|
Policy/law | Access | Open for danish researcher | Open for danish researcher |
| Mandate | Institutional | Government | |
| Preservation | Retention period | 5-10 years if enough researchers use it | The TIFF-files will be retained for at least 20 years |
Functional preservation | Yes | ||
File preservation | |||
Fixity and authenticity | |||
Logical preservation | No | ||
| Curation | ? | Yes | |
Metadata | Access and reuse | Each dataset gets a DOI that ensures future harvesting |
|
License | |||
Digital preservation requirement
| |||
INGEST
M – must
S – should
C – could | Requirement | KB | Rigsarkivet |
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). | ||
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). | ||
S | The digital archive will support automated extraction of metadata from files. | ||
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. 2GB | |
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 | The digital archive will fulfill Dublin Core metadata | ||
| M | The digital archive will guarantee long-term preservation and integrity of the data | ||
| M | The digital archive will be certified to the Trusted Repositories Audit and Certification standard | ||
| M | The 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. | Yes | |
S | The digital archive will be able to incorporate new digital preservation tools (for migration, file validation, characterisation etc) as they become available. | No | |
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. | ||
General
Content
Integrations