Replicating functionality from / deprecating scaife-cts.perseus.org #590
Comments
|
This is a great summary! One thing that seems missing for our use case is that we'd like to get a list of all the citable locations in a text. In the old API, the capabilities told us how many levels of citation there were (e.g., book.line vs. book.chapter.section) and then we could call GetValidReff with the "level" argument, e.g.: but the equivalent JSON call seems to only give us the top level of books: Is there some way to get a list of all sections with the JSON API? This is especially helpful for poetry, so that we can just get each line separately and not have to split the cards up ourselves. |
|
@dasmiq I had tried to reply here yesterday, but it looks like it didn't go through...sorry! You're correct that the current endpoints only support the "top level". The GraphQL API we're working on will support multiple levels, but in the interim, I'll backport I'll work to get things deployed to a dev instance next week and will bump this issue when that has been completed. |
Backport of GetValidReff from scaife-cts-api. Refs #590
|
@dasmiq: The new endpoint is available for preview here: It should work just as the old I will get it "promoted" to scaife.perseus.org early next week. |
|
Fantastic! Thanks very much, Jake. Have a great weekend!
…On Fri, Jun 23, 2023 at 6:21 PM Jacob Wegner ***@***.***> wrote:
@dasmiq <https://github.com/dasmiq>: The new endpoint is available for
preview here:
https://scaife-dev.perseus.org/library/urn:cts:greekLit:tlg0081.tlg001.perseus-grc2/cts-api-xml/reffs/?level=1
https://scaife-dev.perseus.org/library/urn:cts:greekLit:tlg0081.tlg001.perseus-grc2:1/cts-api-xml/reffs/?level=1
It should work just as the old GetValidReff request on
scaife-cts.perseus.org.
I will get it "promoted" to scaife.perseus.org early next week.
—
Reply to this email directly, view it on GitHub
<#590 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALL6MP4K26PK4LYO66AF5DXMYJGFANCNFSM6AAAAAAZQPQS7I>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
The new endpoints have been promoted to scaife.perseus.org:
I've documented some of what I wrote in an email to you last week over in Infrastructure Architecture I'm going to work on winding down scaife-cts.perseus.org soon; please let me know if the new endpoints are working for you or if there is anything that would be helpful to have ported over. Thanks! |
|
I've just deployed a redirect from I'll work on a public deprecation notice / plan for |
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!The text was updated successfully, but these errors were encountered: