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.

Sign up for GitHub

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

Jump to bottom

Add support for definition eg. as optional fields parameter in vocabulary specific search api #459

Closed
amiika opened this issue Feb 16, 2016 · 2 comments
Closed

Add support for definition eg. as optional fields parameter in vocabulary specific search api #459

amiika opened this issue Feb 16, 2016 · 2 comments
Labels
enhancement REST
Milestone
1.6

Comments

@amiika
Copy link

amiika commented Feb 16, 2016

Add skos:definition as supported fields parameter to //search API.

Currently any extra information (comment, definition eg.) needs to be queried with /data API, which means 1 /data call for each search result if you want to show the extra information along with the search results. Add support to comment & definition eg. or alternatively fields parameter could be extended to support any predicate that is encoded to field parameter as full uri.
@osma osma added this to the Next Tasks milestone Feb 16, 2016
@osma osma added the REST label Feb 16, 2016
@osma
Copy link
Member

osma commented Feb 16, 2016

Implementing this as fields=definition makes sense to me.

@osma
Copy link
Member

osma commented Apr 19, 2016

This was actually already implemented as part of #432 but the implementation seems to be buggy, it returns definition values as if they were URIs. Reported as #505

@osma osma modified the milestones: 1.6, Next Tasks Apr 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement REST
Projects
None yet
Milestone
1.6
Development

No branches or pull requests
2 participants
@osma @amiika