Category I | Category II | |||
|---|---|---|---|---|
Price
| Initial subscription price
| TBD | TBD | |
Free storage size limit | TBD | TBD | ||
Price per GB above this limit | TBD | TBD | ||
Price per year | TBD | TBD | ||
Size limit
| Default uploaded file size limit | 512MB | 10MB | |
File size limit on request | ∞ | ∞ | ||
Number of files that can be stored | ∞ | ∞ | ||
Total allowed storage capacity | ∞ | ∞ | ||
Data types |
| All formats are allowed | All formats are allowed | |
Research restrictions
| Allowed researchers (Accept material from) | At first only researchers associated with SB | At first only researchers associated with SB | |
Material not allowed | Material that breaks danish law | Material that breaks danish law | ||
Research
| Phase | Primarily long term preservation and presentation of the content | Primarily long term preservation and presentation of the content | |
Disciplinary | Any | Any | ||
Access to data
| Open data | ✓ | ✓ | |
Embargoed data | ✓ | ÷ (open issue on GitHub) | ||
Closed data | ✓ | ✓ | ||
Tracking users and statistics | ✓ | ✓ | ||
Restricted Access | ✓ | ✓ | ||
Data security
| Multiple redundant copies | TBD | TBD | |
How protected are the data? | TBD | TBD | ||
Location |
| State and University Library | State and University Library | |
Accept material from |
| At first only researchers associated with SB | At first only researchers associated with SB | |
| Ownership |
| The individual researcher or his/her institution. | The individual researcher or his/her institution | |
Ability to have versions |
| ✓(requires extension) | ✓ | |
Safety |
| ? | ? | |
Sustainability
| What is the plan in case the service gets terminated? | Help to find other repositories | Help to find other repositories | |
What funding is there | Funded by DEFF | Funded by DEFF | ||
How high is the risk of the service getting terminated | Medium | Medium | ||
Data
| Withdrawal | ✓ | ✓ | |
Revocation of DOIs | ÷ | ÷ | ||
Encryption | ÷ | ÷ | ||
Virus check | Not as default but can be done by implementing an extension | ÷ | ||
Storage of sensitive data | ✓ | ✓ | ||
Policy/law
| Access | At first only researchers associated with State and University Library | At first only researchers associated with State and University Library | |
Mandate | Institutional | Institutional | ||
Preservation
| Retention period | Minimum 10 years | Minimum 10 years | |
Functional preservation | ÷ | ÷ | ||
File preservation | ✓ | ÷ | ||
Fixity and authenticity | ✓ | ÷ | ||
Curation | ✓ | ÷ | ||
Metadata
| Access and reuse | All metadata are exported via OAI-PMH and can be harvested. | There is an OAI-PMH extension | |
License | Each submission has a license | Each submission has a license | ||
INGEST M – must S – should C – could |
Requirement. These user stories are borrowed from the SB repository evaluation. |
| ||
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). | ✓ | ÷ | |
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). | ✓ | Using an extension | |
S | The digital archive will be able to validate files (where appropriate tools exist). | ✓ | Using an extension | |
S | The digital archive will support automated extraction of metadata from files. | ÷ | ÷ | |
S | The digital archive will virus check files on ingest. | Using an extension | ÷ | |
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. | ✓ | ✓ | |
DATA MANAGEMENT |
| |||
M | The digital archive will generate persistent, unique internal identifiers. | ✓ | Using an extension | |
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. | ✓ | uses DCAT - Data Catalog Vocabulary - an RDF vocabulary - maybe with an extension? | |
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 | ✓ | Yes, when an extension is applied | |
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/normalization) 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 | ✓ (difficult, though) | ÷ (requires code change) | |
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 | ✓ (difficult, though) | ÷ | |
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, characterization 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. | ✓ | det tror jeg altså godt det kan... | |
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. | ✓ | ✓ | |
Priority M – must S – should | Description. These user stories were selected as the most important ones for a research data repository. We would like to add user stories for researchers and data re-users. |
DSpace |
CKAN |
|---|---|---|---|
| S | As web and external user I will be able to harvest objects that have changed since last harvest (including deleted objects), so I can maintain a synchronized copy or index of the repository. | It is not possible to register changes - it is only possible to harvest single elements | It is not possible to register changes - it is only possible to harvest single elements |
| M | As DCM I will be able to see the checksum of the individual file in the repository so I at any point in time can make a manual checksum check. | ✓ | ÷ (GitHub issue) |
| S | As DCM I will be able to ensure that the collections objects are validated/characterized so we are certain that the formats are correct. | ✓ | ✓ (with plugin) |
| M | As DCM I will have a system, that supports persistent IDs so I for eternity can reference the object with the same ID. | ✓ | ✓ (with plugin) |
| M | As internal user of the system I would like to have different user roles, so we can limit who will be able to edit and who will be able to change the configuration of the system. | ✓ | ✓ |
| S | As metadata person I will be able to mass edit metadata for instance across a collection, so I do not have to open and update every single object. | ✓ | ÷ |
| S | As metadata person I will be able to add extra metadata to all files in a collection at the same time, so the collection get enriched. | ✓ | ÷ |
| S | As metadata person I will be able to change metadata field X for all files in collection Y at once, so the collection gets updated uniformly correct | ✓ | ÷ |
| M | As collection owner I will be able to use the normal metadata protocols and standards, so as few metadata as possible has to be adapted to new standards | ✓ | ✓ (with plugin) |
| M | As collection owner I will have different models for metadata for different objects and collections, so there is much flexibility when a choice has to be made between different metadata models and protocols. | ✓ | ÷ |
| M | As metadata person I will be able to add fields in the metadata protocol, so I can expand the description of the objects if new information come. | ✓ | ÷ |
| M | As DCM I will be able to see an overview of file formats in the collections, so I can see if there are formats, that have to be migrated | ÷ | ÷ |
| M | As DCM/collection owner I will be able to maintain provenance of collections and objects, so I can ensure the different objects history of digital maintenance and end users. | Possible but requires extension | ✓ |
As developer and maintainer of metadata I will be able to find history and old versions of metadata so I can troubleshoot and correct errors as well as evaluate the correctness and integrity of data. | Possible but requires extension | ✓ | |
| S | As DCM I will be able to do virus check as part of ingesting so I can have a clean collection and furthermore give a report of which infections that occurred. | Possible but requires extension | ÷ |
| S | As collection owner and system developer I will be able to authenticate the users by existing user registration registers for instance WAYF, AD, NemID so both we and the users does not have to administer a user register separately. | ✓ | ÷ |
| M | As system operator I will be able to perform backup of the running system, so I can have a continuous and consistent backup | ✓ | ✓ |
| M | As system operator I will be able to replicate central parts of the repository so it is not necessary to have the system being down during the frequent upgrades. | ✓ | ÷ |
| S | As user I will be able to ingest many large files | ✓ | ✓ |
| M | As a lawyer or metadata specialist I will be able to proviso a number of files, so they in the future cannot be seen by users that are not allowed to see them. | ✓ | ✓ |
| M | As a lawyer I will be able to handle rights of objects, so I can control the different user's access. | ✓ | ✓ |
| M | As a lawyer I can define the role of the end user, so I can handle large user groups access | ✓ | ✓ |
| M | As a lawyer I need that legal facts are registered on the object and can be brought in play in a license system, so we can be sure that we only allow access to those that legally should have access. | ÷ | ÷ |
| M | As a lawyer I will be able to tie legal facts/metadata to the objects, so we ensure that we know these metadata, when we use the objects. | ✓ | ÷ |
| M | As a lawyer I may tie different information about the relation to the collection to the object, so I can find specific relations to collections since the right of use often are tied to that. | ✓ | ÷ |
| M | As collection owner I will ensure, that my users get access to the parts of the collection that they may access, so we give access to as much as possible without having legal problems. | ✓ | ✓ |