Fixing Neo4j import issue with sources property being a dict#374
Open
Fixing Neo4j import issue with sources property being a dict#374
Conversation
…s with async ingest
…s with async ingest
This file contains hidden or 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
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.
@EvanDietzMorris This PR should fix the Neo4j import issue with sources property being a dict since I have successfully created a neo4j dump for the translator kg with this fix. It also fixes the issue with some unexpected formatting issues in the produced edges.jsonl file with publication property, e.g.,
\nand\tincluded in the PMID values plus multiple spaces betweenPMID:and the PubMed ID numbers, which will be better to be cleaned up in the upstream data ingest component.