The changes provided by #566 (deployed in the v2022-08-30-001 release have allowed us to remove the dependency on scaife-viewer/scaife-cts-api (powering scaife-cts.perseus.org.
I now realize that there have been other users of scaife-cts.perseus.org that were not aware of the changes in v2022-08-30-001 release or that content is no longer being updated there.
This issue serves to do a few things:
As part of development of Beyond Translation, there will also be a GraphQL API that should be able to replicate the functionality from scaife-cts.perseus.org.
Current APIs on scaife.perseus.org
(also formatted as a list)
Please leave a comment on this issue if there is a desire to have a particular scaife-cts-api endpoint ported over "verbatim", and we'll see what we can do to accomodate!
The changes provided by #566 (deployed in the v2022-08-30-001 release have allowed us to remove the dependency on scaife-viewer/scaife-cts-api (powering scaife-cts.perseus.org.
I now realize that there have been other users of scaife-cts.perseus.org that were not aware of the changes in v2022-08-30-001 release or that content is no longer being updated there.
This issue serves to do a few things:
As part of development of Beyond Translation, there will also be a GraphQL API that should be able to replicate the functionality from scaife-cts.perseus.org.
Current APIs on scaife.perseus.org
(also formatted as a list)
.first_passage)Please leave a comment on this issue if there is a desire to have a particular
scaife-cts-apiendpoint ported over "verbatim", and we'll see what we can do to accomodate!