-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
24 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
# 3. Use the DSpace Submission Service (DSS) | ||
|
||
## Status | ||
|
||
Accepted | ||
|
||
## Context | ||
|
||
After completing the initial engineering plan for Wiley Deposits, it was | ||
discovered that ETD has a similar use case for depositing items into DSpace. | ||
DSpace submission message-oriented middleware was created (based partly on original work by Eric), taking into account | ||
architectural and use case input from the Wiley team. We want to minimize unnecessary duplicate functionality | ||
across applications and reuse middleware, in accordance with MIT Libraries architecture principles. Preliminary | ||
testing indicates that DSS is functional. | ||
|
||
## Decision | ||
|
||
We will use the DSpace Submission Service, instead of using the DSpace API directly. | ||
|
||
## Consequences | ||
|
||
* The Wiley codebase will be dependent on this service for timely and error-free ingests into DSpace. | ||
* The Wiley project will validate metadata (and PDFs) as DSS service contract may not do validation checks. | ||
* Features not provided by DSS (e.g., notifications) will still be implemented in AWD. |