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

Multiple top concepts / dct:subject of concept schemes #663

Merged
merged 5 commits into from
Dec 11, 2017

Conversation

tfrancart
Copy link
Contributor

@tfrancart tfrancart commented Nov 22, 2017

fix #636

of Concept schemes.
2. Ability to fetch and return multiple concept schemes for which a
concept is a top concept in the parent hierarchy (new 'tops' key in the
JSON-LD result)
@osma
Copy link
Member

osma commented Nov 23, 2017

Thanks for the PR. Looks much cleaner than the previous one :)

@osma osma requested a review from henriyli November 23, 2017 14:20
@tfrancart
Copy link
Contributor Author

Just a gentle reminder on this PR. @henriyli were you able to review it ?
(I am asking because I have at least one other PR depending on this one to propose to handle hierarchy properly on the javascript side)
Thanks

@osma osma merged commit 7b235c5 into NatLibFi:master Dec 11, 2017
@osma
Copy link
Member

osma commented Dec 11, 2017

We reviewed this together with @henriyli and decided to merge it, looks good although we don't need this functionality in our own vocabularies

@tfrancart
Copy link
Contributor Author

Thanks - yes, it should be harmless for data that don't use this structure.

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

Successfully merging this pull request may close these issues.

Make top ConceptSchemes in REST API an Array and not a single value
2 participants