Working with Legacy Relational Data in A Graph-Based World

The Next Generation Linkage Management System (NGLMS) was designed around keeping all data in a graph database. However, this constraint, while easily achievable for greenfield projects and/or new data linkage units, may not be easily met where legacy data exists. Objectives and Approach The NGL...

Full description

Bibliographic Details
Main Author: James Farrow
Format: Article
Language:English
Published: Swansea University 2020-12-01
Series:International Journal of Population Data Science
Online Access:https://ijpds.org/article/view/1629
id doaj-ff4113a40a314c0bb1eb4188bb4db59d
record_format Article
spelling doaj-ff4113a40a314c0bb1eb4188bb4db59d2021-02-10T16:41:48ZengSwansea UniversityInternational Journal of Population Data Science2399-49082020-12-015510.23889/ijpds.v5i5.1629Working with Legacy Relational Data in A Graph-Based WorldJames Farrow0Farrow Norris Pty Ltd / SA.NT DataLink The Next Generation Linkage Management System (NGLMS) was designed around keeping all data in a graph database. However, this constraint, while easily achievable for greenfield projects and/or new data linkage units, may not be easily met where legacy data exists. Objectives and Approach The NGLMS was extended to encompassed system where data was held partially or even completely in a relational database. By grouping the data managed by the NGLMS into system metadata, record link data and record data and allowing system metadata and record data to be stored separately and independently in either a relational or a graph database, the NGLMS allows hybrid installations of mixed graph and relational data and, with some loss of functionality, purely relational installations. Results The functionality of the NGLMS was expanded to allow review of existing legacy data stored in a relational database system. Through minor changes to the server used by the NGLMS Clerical Review tool (NGLMS-CR) the review tools was able to present the same interface and allow the same integration as project stored completely within the graph database. Hybrid projects where link information was stored in a graph could be accommodated with no loss of functionality. Relational-only projects allowed clerical review of identified clusters in a manner identical to the graph-only NGLMS but involved some curtailment of the advanced clustering, time-slicing, compositional and concurrent functionality of the NGLMS due to the loss of the functionality provided by a graph database. They do provide an upgrade pathway to hybrid projects and then graph-only projects. Conclusion / Implications Allowing the NGLMS to be configured as a hybrid system enables a gradual adoption of the NGLMS toolset and software. • purely relational data still allows the use of the NGLMS-CR with customisable workpools and workflows • a hybrid relational/graph system where record data is still kept in a relational store but cluster and linkage information is kept in the graph store allows the use of legacy data without major disruption and provides a pathway to full adoption https://ijpds.org/article/view/1629
collection DOAJ
language English
format Article
sources DOAJ
author James Farrow
spellingShingle James Farrow
Working with Legacy Relational Data in A Graph-Based World
International Journal of Population Data Science
author_facet James Farrow
author_sort James Farrow
title Working with Legacy Relational Data in A Graph-Based World
title_short Working with Legacy Relational Data in A Graph-Based World
title_full Working with Legacy Relational Data in A Graph-Based World
title_fullStr Working with Legacy Relational Data in A Graph-Based World
title_full_unstemmed Working with Legacy Relational Data in A Graph-Based World
title_sort working with legacy relational data in a graph-based world
publisher Swansea University
series International Journal of Population Data Science
issn 2399-4908
publishDate 2020-12-01
description The Next Generation Linkage Management System (NGLMS) was designed around keeping all data in a graph database. However, this constraint, while easily achievable for greenfield projects and/or new data linkage units, may not be easily met where legacy data exists. Objectives and Approach The NGLMS was extended to encompassed system where data was held partially or even completely in a relational database. By grouping the data managed by the NGLMS into system metadata, record link data and record data and allowing system metadata and record data to be stored separately and independently in either a relational or a graph database, the NGLMS allows hybrid installations of mixed graph and relational data and, with some loss of functionality, purely relational installations. Results The functionality of the NGLMS was expanded to allow review of existing legacy data stored in a relational database system. Through minor changes to the server used by the NGLMS Clerical Review tool (NGLMS-CR) the review tools was able to present the same interface and allow the same integration as project stored completely within the graph database. Hybrid projects where link information was stored in a graph could be accommodated with no loss of functionality. Relational-only projects allowed clerical review of identified clusters in a manner identical to the graph-only NGLMS but involved some curtailment of the advanced clustering, time-slicing, compositional and concurrent functionality of the NGLMS due to the loss of the functionality provided by a graph database. They do provide an upgrade pathway to hybrid projects and then graph-only projects. Conclusion / Implications Allowing the NGLMS to be configured as a hybrid system enables a gradual adoption of the NGLMS toolset and software. • purely relational data still allows the use of the NGLMS-CR with customisable workpools and workflows • a hybrid relational/graph system where record data is still kept in a relational store but cluster and linkage information is kept in the graph store allows the use of legacy data without major disruption and provides a pathway to full adoption
url https://ijpds.org/article/view/1629
work_keys_str_mv AT jamesfarrow workingwithlegacyrelationaldatainagraphbasedworld
_version_ 1724275243986452480