You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
curl --request PUT "https://korap.ids-mannheim.de/api/v1.0/vc/~owid/test" --header "Authorization: Bearer XXX" --header "Content-Type: application/json" --data "{"type": "PRIVATE", "corpusQuery": "corpusSigle=GOE & creationDate since 1820"}"
Please replace the following information
User: owid
Virtual-Corpus-Name: test
Bearer Token: XXX
Get this error:
{
"errors": [
[
2010,
"Unauthorized operation for user: MAIL",
"MAIL"
]
]
}
Problem: MAIL is the e-mail of user owid (I have replaced this info here with MAIL). I would expect the username here, not the email address. That's creepy. The problem: I need to specify the email for both creating and retrieving sub-corpus information.
As mentioned in #566, I do not have access to this info.
Thanks for reporting the bug. That is really bad. The virtual corpus services have not been integrated in the Web-UI thus not tested very often. It used to show only username. This must have been caused by the synchronization of username and emails.
I tried this: https://github.com/KorAP/Kustvakt/wiki/Service:-Virtual-Corpus-Creation
Example:
curl --request PUT "https://korap.ids-mannheim.de/api/v1.0/vc/~owid/test" --header "Authorization: Bearer XXX" --header "Content-Type: application/json" --data "{"type": "PRIVATE", "corpusQuery": "corpusSigle=GOE & creationDate since 1820"}"
Please replace the following information
Get this error:
{
"errors": [
[
2010,
"Unauthorized operation for user: MAIL",
"MAIL"
]
]
}
Problem: MAIL is the e-mail of user owid (I have replaced this info here with MAIL). I would expect the username here, not the email address. That's creepy. The problem: I need to specify the email for both creating and retrieving sub-corpus information.
As mentioned in #566, I do not have access to this info.
I see two solutions here:
The text was updated successfully, but these errors were encountered: