Fix remote digital objects import error via csv #1558
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
|
This change makes the --link-source option work. |
willian95cs
changed the title
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.
When importing digital objects via command line (csv) after importing the records, you get the error "Could not read the file" due to checking the path to the local directory. However, remote digital objects have no local path.
Fixes the bug by commenting out these validations and replacing importFromFile with importFromURI when creating digital objects so we can import to remote digital objects.
Allows the sending of local and remote digital objects in the same csv, validating the URI by the presence of the host. If the host does not exist, import the object with the local path.