Skip to end of metadata
Go to start of metadata
NumberAS A <type of user>I WANT TO <perform some task> SO THAT I CAN <achieve some goal>Satisfied by
1Repository Managerselect a subset of my data corpussend it to a DDP for preservationSelection occurs in the Hyrax interface. Deposit is result of APIs outlined in specs. 
2Repository Managerselect all of my data, including all versionssend it to a DDP for preservationSelection occurs in the Hyrax interface. Deposit is result of APIs outlined in specs. Versioning needs more clarity in Gateway API.
3Repository ManagerSend data to multiple DDPsuse multiple DDPsMultiple Gateways and Bridges would be configured to satisfy this. 
4Repository Managerquery the repository to find out the total number of files and bits selected before authorizing transfer to a DDPinform the Budget Manager before transferring to a DDP.Workflow in Hyrax.
5Repository Managertransfer all of my new data on a schedule (nightly, weekly, monthly)know all new data is sent to a DDP within a specified timeframeWorkflow in Hyrax.
6Repository Managerbe able to configure the repository to send changes as they happento minimize the amount of time between when changes happen in my local system and when they are preserved in a DDP.Workflow in Hyrax.
7Repository Managerconfigure my workflows to define what metadata flags result in objects being sent to a particular DDPso that replication to a DDP can be automated.Workflow in Hyrax.
8Repository Managerknow the status of my data (ie, processing/completed/error) for the ingest process into a DDPreact to errors as neededGateway can query Bridge for deposit status. 
9Repository Managerknow what DDP locations my data was replicated tomake sure the data is in diverse locationsReturned in audit information. 
10Repository Manager and Archivist/Curatorbe able to determine which data has been sent to a DDP and when it was sentverify that it's being preserved, have a record of what was sent for future repo managersBridge can query for a list of deposits and return to Gateway.
11Archivist/Curatorknow if the current version of a digital object is in my DDPmake policy decisions about its preservation statusBridge can query and return to Gateway. 
12Repository Manager or Archivist/Curatormonitor audit events performed by the DDPverify the audit events performed by the DDPReturned in audit information.
13Archivist/Curatorrequest a checksum from the DDPcompare it to my local repo checksum infoReturned in audit information.
14Repository Managerrestore a specific object/work from a DDPrestore a corrupted object/work in my repository systemRetrieve in Gateway spec, Restore in Bridge spec.
15Repository Managerrestore all works preserved in a DDP for a given repository systemrestore a repository after a system failureRestore in Bridge spec.
16Archivist/Curatorrequest restoration of a specific version of an object from a DDPrevert unwanted changes to the objectRetrieve in Gateway spec, Restore in Bridge spec.
17Archivist/Curatorrecord the restoration of a work or filehave an audit trail of what has happened to the work or fileAudit in Bridge spec. Requires additional scoping in the UI.
18Repository Managerrequest removal of a file, in compliance with my removal policy, from a work in the repository and in the DDPcomply with a legal requirement.Delete in Bridge spec, Purge in Gateways spec. Workflow restrictions/permissions should also be in place to prevent accidents or malicious actions.
19Repository Managerrequest complete removal of all versions of a work from the repository and all DDP backups, in compliance with my removal policycomply with a legal requirementDelete in Bridge spec, Purge in Gateways spec. Workflow restrictions/permissions should also be in place to prevent accidents or malicious actions.
20Repository Managerrequest complete removal of all my institution's data from a DDP, in compliance with my removal policycancel my contract with that particular DDPPossible through Purge/delete requests. May be best handled outside of system through policy. 
21Archivist/Curatorupdate the metadata or file(s) for objects/works that have been ingested into the DDPmake sure the latest version of metadata is preserved in the DDP
22Archivist/Curatorretain prior states of an object/work and its files once they have been versionedwe can revert to a prior version if neededVersioning in this system is additive; DDPs should be expected to keep all versions of an object. 
23Budget Managerknow how much data I have (broken down by different aggregations, like admin sets or collections) in one or more DDPscalculate how much it costs to preserve my content which enables me to better understand the costs of digital preservation and demonstrate this to stakeholders and administrators.Hyrax interface/workflow requirement. 
  • No labels