21

Hello all and welcome to the first DeepLynx newsletter! This newsletter is designed to keep you up to date with the current development status of the DeepLynx data warehouse. While it doesn’t look like much yet, we hope that this newsletter will improve as we put out each issue, and that by reading it you’ll feel like you’re a part of the DeepLynx ecosystem and team.

Let’s jump right in!

Query Builder and Query Visualization Last week we released a prototype query building and data visualization tool for the DeepLynx web app. This allows users to quickly query DeepLynx and then visualize those results in a graph-like format. Please note that this tool is still being actively developed, so please don’t hesitate to reach out with any comments or concerns. As we continue to rebuild the query layer this tool will change and improve. You can find this tool under the left hand sidebar – Data -> Data Query.

We are currently working on ways to select multiple nodes in the graph display and connect them, as well as a 3D viewer tool for certain files attached to the nodes/edges in the return value.

Natrium and VTR Issue Boards In an effort to maintain transparency we have created individual tracking boards for both the Natrium and VTR projects inside the Gitlab repository. This allows users to quickly view the tickets most relevant to their project, their priority, and track what’s being actively worked on. Planning sessions are held every one to two weeks to reprioritize and review work completed so expect these boards to change frequently.

Natrium - https://gitlab.software.inl.gov/b650/Deep-Lynx/-/boards/33 VTR - https://gitlab.software.inl.gov/b650/Deep-Lynx/-/boards/34

Documentation Documentation will be a large focus of the team for the next few weeks. As we prepare to stand an instance of DeepLynx up for the Natrium team we want to insure that their ability to use and understand DeepLynx is not hindered by lack of documentation. Efforts will be directed mainly towards the Gitlab wiki – but plans have been made to also include a “landing page” of sorts on the DICE website. If you have written any documentation that contains information on how to work with DeepLynx, or how your integration functions alongside DeepLynx, we ask that you please send it to us so that we can include it.

Database Overhaul We are currently hard at work at overhauling the underlying database schema and interaction for DeepLynx. Included in this email is a slide deck of a presentation given on the overhaul, why it’s necessary, and what exactly is going to be changed. Please note that this is a breaking change for all local development instances of DeepLynx. Instructions will be published on how to migrate from your version of DeepLynx to the new release when it is finished. Also note that none of the HTTP endpoints are changing and that any exported Type Mapping/Transformations will still function as expected – so external integrations should not be affected by these changes.

That’s all we have for this newsletter. As always, please feel free to reach out with any comments or concerns you might have and please submit any issues you have via Gitlab or by sending an email to [email protected]