new: resource_collection_name, migrate_edges_to_attributes(), uri_map_collection_name
#34
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.
Test with:
3 Changes:
Introduces
resource_collection_nameto therdf_to_arangodb_by_pgt()method which proposes to replace some of the ArangoDB Collection Mapping Process with a simpler approach: store all RDF Resources in one ArangoDB Collection. This can be beneficial for those wanting to benefit from having a simpler ArangoDB Graph to manage.Introduces
migrate_edges_to_attributes()as a general PGT method. Similar tomigrate_unknown_resources(), this function can be called after invokingrdf_to_arangodb_by_pgt()to transform Edges into Document Properties. For example, this method can be used to **convert alltypeedges into a_typeproperty on each document`.Refactor
iri_collection_nametouri_map_collection_name: Due to risk of confusion betweeniri_collection_nameandresource_collection_name, this parameter has been renamed touri_map_collection_name. Functionality remains the same.Example usage