{'fraction_non_alphanumeric': 0.027777777777777776, 'fraction_numerical': 0.005341880341880342, 'mean_word_length': 4.8930817610062896, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Representing history in graph-oriented NoSQL databases: A versioning system

Graph databases are taking more and more importance, especially for social networking. For instance, organizations can implement graph databases to represent and query data such as Person1 is CEO of Organization1. NoSQL graph databases (e.g., Neo4j) have been designed to deal with such data. However, managing history is not yet possible in an easy manner while being critical in many applications. Tracking changes is indeed one of the main functionalities in databases (especially Relational BD) and should not be forsaken in NoSQL graph DB. For instance, queries like “list all the people who have been CEO of Organization1” or “list all the functions People1 has been taken in his career” are important. In this paper, we thus propose a novel representation of historical graph data and tools to implement it as a plug-in of existing NoSQL graph systems.