Skip to content
This repository has been archived by the owner on May 11, 2022. It is now read-only.

SuriService - migrate to dor-services-app after hydra-etd stops using it #708

Open
ndushay opened this issue Jun 10, 2020 · 1 comment
Open

SuriService - migrate to dor-services-app after hydra-etd stops using it #708

ndushay opened this issue Jun 10, 2020 · 1 comment

Comments

@ndushay
Copy link
Contributor

ndushay commented Jun 10, 2020 •
edited
Loading

Once hydra_etd app no longer uses SuriService directly (see sul-dlss/hydra_etd/issues/351) for object registration, the SuriService will be is used by dor-services-app only.

Since consumer code should live in the consumer app.
@jcoyne
Copy link
Contributor

jcoyne commented Jun 10, 2020

Yes!

@ndushay ndushay changed the title SuriService - migrate to dor-services-app after hydra-etd stops using it? SuriService - migrate to dor-services-app after hydra-etd stops using it Jun 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jcoyne @ndushay