Feature/person, event, OU dynapi crud #3908
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ching resource from graph.
…rsulja/VIVO into feature/person-dynapi-crud
…er unwrapping for same entity.
…e. Added missing fields to person position creation.
…ome bugs and naming errors in person and OU n3 files.
This was
linked to
issues
Sep 26, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
VIVO GitHub issues
3873, 3874, 3875
What does this pull request do?
Added basic CRUD procedures for Person, Organisation Unit and Event entities.
What's new?
Addition of required .n3 files containing implementation of basic CRUD operations on before mentioned entities.
How should this be tested?
You can test this using VIVI's built-in Swagger docs or use a client mocking software such as Postman or cURL.
Postman collection is avaliable here.
Interested parties
@chenejac @litvinovg @brianjlowe @milospp