Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  

Priority

M – must

S – should



 

Description



 

Epic Link

 

DSpace

 

 

 

CKAN

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 synchronized copy or index of the repository.

 Metadata export

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.

 

Integrity check

 

÷

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.

Validation, characterization etc

 

÷?

M

As DCM I will have a system, that supports persistent IDs so I for eternity can reference the object with the same ID.

 

Persistent IDs (PID) / 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.

Roles, rights and license regarding access

 

 
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.

 Manual metadata

 

÷?

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.

Manual metadata 

÷?

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

Manual metadata

 

÷?

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

Data models
(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.

Data models 

÷?

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.

 

Data models

 

÷?

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

UI

÷

÷

 

?

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.

Provenance

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.

VersionsPossible 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.

VirusPossible 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.

System integration

 
M

As system operator I will be able to perform backup of the running system, so I can have a continuous and consistent backup

Operation

 
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.

Performance

 
 

As user I will be able to ingest many large files

Manual ingest

 
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.

Clauses

 

 
M

As a lawyer I will be able to handle rights of objects, so I can control the different user's access.

 

Roles, rights and license regarding access

 
M

As a lawyer I can define the role of the end user, so I can handle large user groups access

 

Roles, rights and license regarding 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.

Manual metadata

÷

 
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.

Manual metadata 
M

Ad 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.

Manual metadata 
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.

Roles, rights and license regarding access