Home

#DRS Project Planning

##Objective

The University Library, with the support of Information Services, is pleased to offer this service to members of the Northeastern Community. The DRS is a secure environment where you can store, manage, and access your digital research, pedagogical, departmental, and administrative materials.

The DRS provides Northeastern faculty and departments with a set of tools that support:

• Submission - placing your materials into the repository is fast and simple
• Creating Collections - you can create as many collections as you need
• Access Control - you control who may discover and/or use your content
• Content Aggregation - create customized groups of content for use in your instruction and research
• Permanence and Preservation your content is part of a university wide digital storage and preservation environment and will receive a permanent URL

##Application Requirements

Functional Requirements

• Application must allow users to browse repository items by collection.
• Application must allow authorized users to contribute repository items, metadata and access arguments.
• Application must allow authorized users to organize repository content into collections.
• Application must allow users to be organized into groups for access, for example accessing material for a class.
• Application is required to manage access policies by groups.
• Application must integrate with the campus Single Sign-On system, Shibboleth.
• Application must validate and create the objects for Fedora’s ingestion.
• Application must allow authenticated users to manage custom sets of repository objects in the interface.
• Application must allow for users to select sub-item streams to be able to download and must allow an intuitive interface.

Non-Functional Requirements

• Application must be rapidly developed.
• Approved by campus Marketing and Communications and other stakeholders.
• Scalable and maintainable with limited resources.
• Prevent copyrighted material from being too publicly accessible.
• Developers must provide adequate documentation.
• Application must strive for responsive web design to allow access on all devices.
• Application must follow accessible best practices.

Use Cases

Actor

Simple use case examples

• Search items
• View items
• Manage users roles
• Manage Items
• Organize Items into collection items
• Manage access to items/collections by user roles.
• Download sets of items
• Authenticated users create own collections

Conceptual Object Model

• User
• Roles
• OrganicGroups
• Search
• RepositoryItem
• Collection
• UserSet
• FavoriteSet
• DownloadSet

Service Providers

Creating Service Descriptions

$result = $app['guzzle']['my_client']->getCommand('foo');
$result = $foo->execute();

Fedora Methods

SERVICE DESCRIPTION

--sdef:core--

getDC getMODS getCRUD getRELS-EXT getTREE-UP getTREE-DOWN getMEMBER-QUERY getMEDIA-QUERY getHIGHRES getFITS