Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Interact with ORA Hyrax via Sword2 #18

Open
tomwrobel opened this issue Apr 8, 2019 · 0 comments
Open

Interact with ORA Hyrax via Sword2 #18

tomwrobel opened this issue Apr 8, 2019 · 0 comments
Labels
AS import/export process Feature is required by a Import/Export process AS repository manager Feature is required by a repository manager AS Sword2/OCFL connector Feature is required by a Sword2/OCFL connector DP Solution SHOULD Digital preservation solution SHOULD MoSCoW requirement Non-OCFL feature A feature that is not within the scope of the OCFL spec

Comments

@tomwrobel
Copy link
Collaborator

tomwrobel commented Apr 8, 2019 •
edited
Loading

As a repository manager, I would like the ORA OCFL client to interact with Hyrax via the Sword2 interface created for Symplectic Elements Repotool 2 so that I can re-use existing tested code for crosswalking metadata and ingesting objects

AS an import/export process I want to be able to migrate objects between Hyrax and OCFL by using the Sword2 interface so that I can use existing code wherever possible.

AS a Sword2 OCFL connector I want to read an object (metadata and binary files) from the OCFL layer so I can restore it into Hyrax

AS a Sword2 OCFL connector I want to add a binary file and its metadata to an object in order to back it up to the OCFL layer

AS a Sword2 OCFL connector I want to save an entire object in order to back it up to the OCFL layer

AS a Sword2 OCFL connector I want to save a new version of an object in order to back it up to the OCFL layer

DP Solution: SHOULD interface with the Hyrax system via its SWORD2 endpoint
@tomwrobel tomwrobel added AS repository manager Feature is required by a repository manager Non-OCFL feature A feature that is not within the scope of the OCFL spec DP Solution SHOULD Digital preservation solution SHOULD MoSCoW requirement labels Apr 8, 2019
@tomwrobel tomwrobel added the AS import/export process Feature is required by a Import/Export process label Apr 10, 2019
@tomwrobel tomwrobel added AS Sword2 OCFL connector AS Sword2/OCFL connector Feature is required by a Sword2/OCFL connector and removed AS Sword2 OCFL connector labels Apr 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
AS import/export process Feature is required by a Import/Export process AS repository manager Feature is required by a repository manager AS Sword2/OCFL connector Feature is required by a Sword2/OCFL connector DP Solution SHOULD Digital preservation solution SHOULD MoSCoW requirement Non-OCFL feature A feature that is not within the scope of the OCFL spec
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tomwrobel