Title (goal) | Content model |
---|---|
Primary Actor | Developers, repository managers |
Scope | |
Level | Repository Goal |
Story | As developers of PASS, which interacts with Fedora-backed JHU Institutional repository, we need to be informed of content required to make a "deposit", and how to organize that content, so that we can update PASS to send acceptable manuscript or data packages, and we can validate that has received what it needs. -- use cases for first class content modeling as part of Fedora 6 |
Title (goal) | IIIF integration |
---|---|
Primary Actor | Repository manager |
Scope | |
Level | |
Story |
As a repository manager, I need the repository I use to be integratable with iiif viewer in a bidirectional way:
|
Title (goal) | Deposit & status |
---|---|
Primary Actor | Submission system for documents and data |
Scope | |
Level | |
Story | As a submission system which interacts with Fedora-backed JHU institutional repository, PASS needs to be able to send manuscripts along with associated metadata to the repository and receive confirmation of a successful deposit. |
Title (goal) | Data deposit either by value or by reference |
---|---|
Primary Actor | Submission system for documents and data |
Scope | |
Level | |
Story | As a submission system which interacts with Fedora-backed JHU institution repository, PASS needs to be able to send data packages to the repository. The data packages would contain the data files, associated metadata files. Sizes are currently unknown. There are 3 scenarios regarding file size:
|
Title (goal) | Persistent IDs for deposited content |
---|---|
Primary Actor | Submission system for documents and data |
Scope | |
Level | |
Story |
|
Title (goal) | Migration requirements |
---|---|
Primary Actor | Developers for an application using Fedora 4 as a backend |
Scope | |
Level | |
Story | The migration from 4/5 to 6 needs to preserve resource URIs. For example, if an application deposits submissions into /fcrepo/rest/jhu/submissions using Fedora 4, the application can continue, unchanged, depositing into /fcrepo/rest/jhu/submissions in Fedora 6. |
Title (goal) | Relationship modeling and representation |
---|---|
Primary Actor | Repository manager |
Scope | |
Level | |
Story |
|
Title (goal) | Access control |
---|---|
Primary Actor | Repository manager |
Scope | |
Level | |
Story | As a repository manager, I need the repository I use to support for restricted access to data (e.g., institution only). Access to data should be controllable by roles or groups. |
Title (goal) | Access control |
---|---|
Primary Actor | Repository manager |
Scope | |
Level | |
Story | As an administrator, I want to restrict access to high-resolution digital assets but store them in the digital asset delivery platform and make them available by request so that I can ensure that high-resolution digital assets are used in accordance with applicable policies. |
Title (goal) | Access control & integration with Digital asset delivery platform |
---|---|
Primary Actor | Repository manager |
Scope | |
Level | |
Story | As an administrator, I want to provide access to restricted digital assets through the digital asset delivery platform so that end users who are permitted to access these digital assets do not need to be provided copies outside of the digital asset delivery platform to fulfill their research need.[3] |
Title (goal) | Bulk ingest |
---|---|
Primary Actor | Data Wrangler |
Scope | |
Level | |
Story | As an administrator, I want to bulk ingest digital assets and associated metadata into the digital asset delivery system, and have the digital asset delivery system associate the assets to their corresponding metadata, so that I can efficiently provide end-users with access to digital assets. |
Title (goal) | Small updates |
---|---|
Primary Actor | Data Wrangler |
Scope | |
Level | |
Story | As an administrator, I want to ingest and replace individual digital assets so that I can make small edits to a digital collection.
|
Title (goal) | Audit & reporting |
---|---|
Primary Actor | Repository manager |
Scope | |
Level | |
Story | As an administrator, I want to gather relevant statistics on use of digital assets so that I can understand what collections are used, how they are used, who is using them, and other information relevant to inform service priorities. |
Title (goal) | Integration with library applications |
---|---|
Primary Actor | Repository admin |
Scope | |
Level | |
Story | As an administrator, I want the digital asset delivery platform to integrate with other platforms for managing and providing access to library resources (such as the catalog and ArchivesSpace) so that the end user has a more seamless user experience and so that administrators can more efficiently manage and provide access to digital assets. |