-
Notifications
You must be signed in to change notification settings - Fork 18
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
Admin API #553
Comments
do-not-edit-start-codetree-epic-issuesIssues in this epic:
do-not-edit-end-codetree-epic-issuesDepends on: #486 |
Depends on: #572 |
I get wrong ontology iris in the ProjectResponse. But when I want to use this IRI to get the ontology information (e.g. /allentities) I get the following response:
The ontology IRI in this project should be So, how should we fix this? |
The admin API uses internal IRIs (the ones used in the triplestore) rather than API v2's external IRIs. Not sure of the best way to deal with this. |
I'm sure @subotic has a solution. Otherwise I have to make two requests (and the ontology IRIs in project object are useless):
|
I see two possibilities:
What happens when we have It would be a small function in the GUI to transform an internal ontology IRI to an external V2 ontology IRI: replace |
That only works for project-specific ontologies. For a built-in Knora ontology, the external hostname is always Seems error-prone to have this knowledge in more than one place. I don’t see the harm in doing two requests as @kilchenmann said, especially since the GUI caches ontologies. |
Does it maybe make sense to return in the admin API both, the internal and external ontology IRIs? Or when requesting the project info, tell the API that you would like to have internal or external v2 /v3 /vx ontology IRIs. Anyhow, this will take a moment to implement. So the fastest way, for now, would be to make a second request, as @benjamingeer suggested. |
Either would be easy to do. To get an IRI in any schema you like, you just have to do something like |
The following list will provide an easier overview of what is implemented and what is still missing. Also, it provides the information if the feature is already available in
develop
or implemented in a PR (which would require using a specific branch).User
Projects
OntologyV1
andOntologyV2
objects for each project, keeping the admin API version independent.Groups
Keywords
Permissions
Lists
The text was updated successfully, but these errors were encountered: