Number | AS A <type of user> | I WANT TO <perform some task> | SO THAT I CAN <achieve some goal> | Satisfied by |
---|
1 | Repository Manager | select a subset of my data corpus | send it to a DDP for preservation | Selection occurs in the Hyrax interface. Deposit is result of APIs outlined in specs. |
2 | Repository Manager | select all of my data, including all versions | send it to a DDP for preservation | Selection occurs in the Hyrax interface. Deposit is result of APIs outlined in specs. Versioning needs more clarity in Gateway API. |
3 | Repository Manager | Send data to multiple DDPs | use multiple DDPs | Multiple Gateways and Bridges would be configured to satisfy this. |
4 | Repository Manager | query the repository to find out the total number of files and bits selected before authorizing transfer to a DDP | inform the Budget Manager before transferring to a DDP. | Workflow in Hyrax. |
5 | Repository Manager | transfer all of my new data on a schedule (nightly, weekly, monthly) | know all new data is sent to a DDP within a specified timeframe | Workflow in Hyrax. |
6 | Repository Manager | be able to configure the repository to send changes as they happen | to minimize the amount of time between when changes happen in my local system and when they are preserved in a DDP. | Workflow in Hyrax. |
7 | Repository Manager | configure my workflows to define what metadata flags result in objects being sent to a particular DDP | so that replication to a DDP can be automated. | Workflow in Hyrax. |
8 | Repository Manager | know the status of my data (ie, processing/completed/error) for the ingest process into a DDP | react to errors as needed | Gateway can query Bridge for deposit status. |
9 | Repository Manager | know what DDP locations my data was replicated to | make sure the data is in diverse locations | Returned in audit information. |
10 | Repository Manager and Archivist/Curator | be able to determine which data has been sent to a DDP and when it was sent | verify that it's being preserved, have a record of what was sent for future repo managers | Bridge can query for a list of deposits and return to Gateway. |
11 | Archivist/Curator | know if the current version of a digital object is in my DDP | make policy decisions about its preservation status | Bridge can query and return to Gateway. |
12 | Repository Manager or Archivist/Curator | monitor audit events performed by the DDP | verify the audit events performed by the DDP | Returned in audit information. |
13 | Archivist/Curator | request a checksum from the DDP | compare it to my local repo checksum info | Returned in audit information. |
14 | Repository Manager | restore a specific object/work from a DDP | restore a corrupted object/work in my repository system | Retrieve in Gateway spec, Restore in Bridge spec. |
15 | Repository Manager | restore all works preserved in a DDP for a given repository system | restore a repository after a system failure | Restore in Bridge spec. |
16 | Archivist/Curator | request restoration of a specific version of an object from a DDP | revert unwanted changes to the object | Retrieve in Gateway spec, Restore in Bridge spec. |
17 | Archivist/Curator | record the restoration of a work or file | have an audit trail of what has happened to the work or file | Audit in Bridge spec. Requires additional scoping in the UI. |
18 | Repository Manager | request removal of a file, in compliance with my removal policy, from a work in the repository and in the DDP | comply 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. |
19 | Repository Manager | request complete removal of all versions of a work from the repository and all DDP backups, in compliance with my removal policy | comply 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. |
20 | Repository Manager | request complete removal of all my institution's data from a DDP, in compliance with my removal policy | cancel my contract with that particular DDP | Possible through Purge/delete requests. May be best handled outside of system through policy. |
21 | Archivist/Curator | update the metadata or file(s) for objects/works that have been ingested into the DDP | make sure the latest version of metadata is preserved in the DDP |
|
22 | Archivist/Curator | retain prior states of an object/work and its files once they have been versioned | we can revert to a prior version if needed | Versioning in this system is additive; DDPs should be expected to keep all versions of an object. |
23 | Budget Manager | know how much data I have (broken down by different aggregations, like admin sets or collections) in one or more DDPs | calculate 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. |