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.

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

e-Terminology: request possible collections and domain-ids #19

Open
pheyvaer opened this issue Jun 28, 2016 · 3 comments
Open

e-Terminology: request possible collections and domain-ids #19

pheyvaer opened this issue Jun 28, 2016 · 3 comments

Comments

@pheyvaer
Copy link
Contributor

So developers don't need to hard-code this.

@pheyvaer pheyvaer changed the title e-Terminology: request poosible collections and domain-ids e-Terminology: request possible collections and domain-ids Jun 28, 2016
@andish
Copy link
Contributor

andish commented Sep 22, 2016

Tilde endpoint now returns list of available collections in json format.
Curl:

curl -X GET -H "Authorization: Basic RlJFTUU6dXxGcjNtM19zJGN1ciQ="  "https://services.tilde.com/collections/terminology"

Optional query parameter (in order to retrieve private collections):

  • key

Optional query parameters for filtering (to return filtered list of collections):

  • sourceLang
  • targetLang
  • domain

Example of response:

{
  "collections": [
    {
      "id": 6681,
      "name": "EASTIN-CL Multilingual Ontology of Assistive Technology",
      "languages": [
        "da",
        "de",
        "en",
        "et",
        "it",
        "lt",
        "lv"
      ],
      "domains": [
        "TaaS-0200"
      ]
    },
 {
      "id": 6826,
      "name": "Foras na Gaeilge, Focal.ie",
      "languages": [
        "de",
        "el",
        "en",
        "es",
        "et",
        "eu",
        "fr",
        "hu",
        "la",
        "lt",
        "lv",
        "mt",
        "pl",
        "sk",
        "sl",
        "ga",
        "it",
        "ru",
        "cs",
        "ja",
        "nl",
        "da",
        "bg",
        "fi",
        "no",
        "pt",
        "ro",
        "sv"
      ],
      "domains": [
        "TaaS-0100",
        "TaaS-0300",
        "TaaS-1000",
        "TaaS-2000",
        "TaaS-2100",
        "TaaS-1500"
      ]
    }]
}

TO DO: include it in FREME server.

@jnehring
Copy link
Member

We can include this. @pheyvaer is this still a requirement?`

Do we actually need to provide this as a FREME endpoint? Users could call the service directly. This also applies to #18

@pheyvaer
Copy link
Contributor Author

No, not at the moment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants