Implement location and archiving api
#496
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
(cherry picked from commit cd989e9)
(cherry picked from commit c5caa38)
(cherry picked from commit 9f367cd)
locations api - add username as parameter when creating a location history api - remove history_scl table - add location to data resource object archiving api - add archive resource history endpoint
minor changes: - don't delete archived resources when unassigning them from a location (in FS) - don't delete locations in FS - change assigned_resources Location attribute to only count distinct resources - return location id as location attribute in history resource search - change file structure in FS to use scl_resource id as folder name when archiving resource - fix unit tests
|
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.
No description provided.