Category I | Category II | |||
|---|---|---|---|---|
Price | Initial subscription price
| ? | ? | |
| Free storage size limit | ? | ? | |
| Price per GB above this limit | ? | ? | |
| Price per year | ? | ? | |
Size limit | Default uploaded file size limit | 512MB | 1GB | |
| File size limit on request | ∞ | ? | |
| Number of files that can be stored | ∞ | ? | |
| Total allowed storage capacity | ∞ | ? | |
Data types |
| All formats are allowed | Png, jpg, gif, csv, xls, json, jsonp, pdf, x-pdf, acrobat, vnd.pdf | |
Research restrictions | Allowed researchers | Anyone | ? | |
| Material not allowed | Material breaking danish law | ? | |
Research | Phase | Any | ? | |
| Disciplinary | Any | ? | |
Access to data | Open data | Yes | Yes | |
| Embargoed data | Yes | ? | |
| Closed data | Yes | ? | |
| Tracking users and statistics | ? | ? | |
| Restricted Access | ? | ? | |
Data security | Multiple redundant copies | ? | ? | |
| How protected are the data? | ? | ? | |
Location |
| Denmark | Denmark | |
Accept material from |
| Researchers that for the moment are associated with SB | Researchers associated with SB | |
Ownership |
| ? | ? | |
Ability to have versions |
| Yes | Yes | |
Safety |
| ? | ? | |
Sustainability | What is the plan in case the service gets terminated? | Help to find other repositories | ? | |
| What funding is there | Funded by Statsbiblioteket | ? | |
| How high is the risk of the service getting terminated | Medium | ? | |
Data | Withdrawal | Deleted data can be permanently deleted | Deleted data can still be accessed by explicit URL, but will not be easy to find otherwise | |
| Revocation of DOIs | ? DOI is possible via extension | ? DOI is possible via extension | |
| Encryption | No | ? | |
| Virus check | Not as default but can be done by implementing an extension | ? | |
| Storage of sensitive data | Yes | Data can be selected to be viewable to only a number of people, so data are secure | |
Policy/law | Access | ? | ? | |
| Mandate | Institutional | Institutional | |
Preservation | Retention period | Minimum 10 years | Minimum 10 years | |
| Functional preservation | No, so the institution has to | ? | |
| File preservation | Yes | ? | |
| Fixity and authenticity | Yes | ? | |
| Curation | ? | ? | |
Metadata | Access and reuse | All metadata are exported via OAI-PMH and can be harvested. | There is an OAI-PMH extension | |
| License | ? | ? | |
INGEST M – must S – should C – could |
Requirement |
| ||
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 | There is an extension to facilitate 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. | Yes |
| |
|
| |||
M | The digital archive will generate persistent, unique internal identifiers. | DOI | There is an extension to facilitate 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 | Yes | Yes, when an extension is applied | |
M | The digital archive will guarantee long-term preservation and integrity of the data | Yes | ? | |
M | The digital archive willbe 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 | Yes | ? | |
|
| |||
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. | ? | ? | |
|
| |||
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. | ? | ? | |
|
| |||
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 |
|
| |
|
| |||
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. |
|
| |
Priority M – must S – should |
Description |
Epic Link |
CKAN |
DSpace |
|---|---|---|---|---|
| M | 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 syncronised copy or index of the repository.
| Formidling - Eksport af metadata | Det er muligt, man kan, men jeg tror det ikke. Man kan dog høste enkelte elementer. | |
| 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.
| Bevar.handl. - Integeritetstjek | ✓ | |
| 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. | Bevar.handl. - Validering, karakterisering mv. | ✓ | |
| M | As DCM I will have a system, that supports persistent IDs so I for eternity can reference the object with the same ID.
| Persistente ID’er (PID) / ID | ✓ | |
| M | As internal user of the system I would like to have different user roles, so we can limit who will be able edit and who will be able to change the configuration of the system. | Adgang - Roller, rettigheder og licenser | ✓ | |
| M | 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.
| Metadataber. - manuel | ✓ | |
| M | 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. | Metadataber. - manuel | ✓ | |
| M | 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 | Metadataber. - manuel | ✓ | |
| 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 | Datamodeller | ✓ | |
| 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. | Datamodeller | ✓ | |
| 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.
| Datamodeller | ✓ | |
| 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 | Brugergrænseflade | ÷ | |
| 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. | Tracking - Proveniens | Muligt, men kræver dog extension | |
| M | 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. | Tracking - Versionering | Muligt, men kræver dog extension | |
| S | Som DCM vil jeg som en del af karakterisering kunne udføre virustjek, sådan at jeg kan rense for vira eller dokumentere infektionsgraden. | Ingest - Virus | Muligt, men kræver dog extension | |
| S | Som samlingsejer og systemudvikler vil jeg kunne autentificere mine brugere ved hjælp af eksisterende brugerregistre, f.eks. WAYF, AD, NemID, sådan at vi og brugerne ikke skal administrere et separat brugerregister. | Systemintegration | ✓ | |
| M | Som driftsansvarlig vil jeg kunne udføre backup på det kørende system, sådan at jeg kan have kontinuert og konsistent backup. | Systemkrav - Drift | ✓ | |
| M | Som driftsansvarlig vil jeg kunne replikere centrale dele af systemet (metadata-storage?) så det ikke er nødvendigt at have nedetid ved (de jævnlige) opgraderinger der kommer. | Systemkrav - Performance | Muligt, men kræver konfigruationsændring | |
| S | Som bruger vil jeg kunne ingeste mange store filer | Ingest – Manuelt | ✓ | |
| M | Som jurist eller metadataspecialist vil jeg kunne klausulere en række filer, sådan at de efterfølgende ikke vises til brugere der ikke må se dem. | Adgang - Klausulering | Muligt, men forudsætter, at filerne er private. | |
| M | Som jurist vil jeg kunne håndtere rettigheder for objekter, sådan at jeg kan styre brugers adgang. | Adgang - Roller, rettigheder og licenser | Muligt, men kræver, at objekterne er private. | |
| M | Som jurist vil jeg kunne definere slutbrugerroller, sådan at jeg kan håndtere store brugergruppers adgang. | Adgang - Roller, rettigheder og licenser | ✓ | |
| M | Som juristvil jeg kunne slå op, hvilke aftaler, licenser og lovgivning, en samling er underlagt, sådan at jeg til enhver tid kan se, om vi har fået tilknyttet de korrekte rettigheder til den enkelte samling. | Adgang - Roller, rettigheder og licenser | ÷ | |
| M | Som jurist har jeg brug for at juridiske fakta registreret på objektet kan bringes i spil i forhold til et licenssystem, så vi er sikre på kun at give adgang til det, vi har ret til at give adgang til. | Metadataber. - manuel | ÷ | |
| M | Som jurist vil jeg kunne knytte juridiske faktaoplysninger/metadata (herunder afdækning af ophav/klarering) tæt til objekterne, så vi sikrer, at vi kender disse metadata, når vi bruger objekterne. | Metadataber. - manuel | ✓ | |
| M | Som jurist har jeg brug for at knytte oplysninger om værkstype (tilhørsforhold til samling) til objekter, så jeg kan fremsøge specifikke værkstyper, da brugsretten ofte knyttes til en værkstype. | Metadataber. - manuel | ✓ | |
| M | Som samlingsejer vil jeg sikre, at mine brugere får adgang til de dele af samlinger, vi har lov til at give brugeren adgang til, sådan at vi giver adgang til mest muligt uden at få juridiske problemer. | Adgang - Roller, rettigheder og licenser | ✓ |