🎁 Implement Bulkrax location input #991
Merged
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 commit makes it so we can use Bulkrax to import locations into the based_near property. It also will work for invalid locations.
laritakr
force-pushed
the
i964-location-name-field-through-bulkrax
branch
from
f1499c9 to
992603b
Compare
orangewolf
approved these changes
Mar 8, 2024
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.
Story
This commit makes it so we can use Bulkrax to import locations into the based_near property. It also will work for invalid locations.
Ref:
Expected Behavior Before Changes
Bulkrax does not handle location/based_near fields correctly
Expected Behavior After Changes
Bulkrax should now handle location/based_near fields correctly, it will either take a string like
"San Diego, California, United States"or a URI like"https://sws.geonames.org/5391811/"