<h1 id="2024-03-07">2024-03-07<a aria-hidden="true" class="anchor-heading icon-link" href="#2024-03-07"></a></h1>
<h1 id="this-is-luca-cappellettis-dbgi-daily-open-notebook">This is Luca Cappelletti's DBGI daily open-notebook.<a aria-hidden="true" class="anchor-heading icon-link" href="#this-is-luca-cappellettis-dbgi-daily-open-notebook"></a></h1>
<p>Today is 2024.03.07</p>
<h2 id="todo-today">Todo today<a aria-hidden="true" class="anchor-heading icon-link" href="#todo-today"></a></h2>
<ul>
<li>Extend the <a href="https://github.com/LucaCappelletti94/actix_yew_websockets">Actix/Yew/WebSocket example</a> to also include Diesel and Postgres, using pg_notify to notify the frontend of changes in the database.</li>
<li>Clean a bit more the code so to make it more reusable with less duplication.</li>
<li>Add housekeeping routines for websocket, such as ping/pong and reconnection.</li>
</ul>
<h2 id="doing">Doing<a aria-hidden="true" class="anchor-heading icon-link" href="#doing"></a></h2>
<h2 id="paused">Paused<a aria-hidden="true" class="anchor-heading icon-link" href="#paused"></a></h2>
<h2 id="done">Done<a aria-hidden="true" class="anchor-heading icon-link" href="#done"></a></h2>
<ul>
<li>Cleaned up as much as possible the WebSocket code, but yew makes it really hard to simplify it further.</li>
<li>Extended the example to include Diesel and Postgres, using pg_notify to notify the frontend of changes in the database.</li>
<li>Discovered that Diesel does not support pg_notify out of the box, so I will have to implement it myself. I have found examples using the Postgres drivers <a href="https://github.dev/KenMan79/graph-node/blob/671d885ea4376dad95e93a31278b08fae2acd0a2/store/postgres/src/chain_head_listener.rs">here</a>. Alternatively here they do a similar thing with <a href="https://github.com/sfackler/rust-postgres/blob/3e4be865318ddd4a6b4493d689703db32ca3d184/tokio-postgres/tests/test/main.rs#L615-L648">tokio</a>. I have asked informations on the Diesel forum, we will see if they have a better solution.</li>
</ul>
<h2 id="notes">Notes<a aria-hidden="true" class="anchor-heading icon-link" href="#notes"></a></h2>
<ul>
<li>Found an example that (defines a pg_notify function for Diesel)[https://github.com/KenMan79/graph-node/blob/671d885ea4376dad95e93a31278b08fae2acd0a2/store/postgres/src/functions.rs#L10]</li>
<li>Found an example that <a href="https://github.com/KenMan79/graph-node/blob/671d885ea4376dad95e93a31278b08fae2acd0a2/store/postgres/src/chain_head_listener.rs#L100">uses pg_notify with Diesel</a></li>
</ul>

This is Luca Cappelletti's DBGI daily open-notebook.

2024-03-07


# Overview

The Digital Botanical Gardens Initiative (DBGI, www.dbgi.org) ambitions to explore innovative solutions for the collection, management and sharing of digital information acquired on living botanical collections. A particular focus will be placed on the large scale characterization of the chemodiversity of living plants collections through mass spectrometric approaches. The acquired data will be structured, organized and connected with relevant metadata through [semantic web](https://en.wikipedia.org/wiki/Semantic_Web) technology. The gathered knowledge will then inform ecosystem functioning research and orient [biodiversity conservation](https://en.wikipedia.org/wiki/Conservation_biology) projects. The DBGI initially aims to take advantage of the readily available living collections of Swiss botanical gardens to establish robust and scalable biodiversity digitisation workflows. The ultimate goal is to apply these approaches in the field and at the global scale in wildlife ecosystems. 

# Main goals

The DBGI main goals are briefly summarized below :

![](/assets/images/2022-06-18-17-13-23.png){max-width: 400px, display: block, margin: 0 auto}

# An Open Science project


## Working with the workshop doors open

![](/assets/images/2022-06-18-17-47-56.png){max-width: 400px}

A way of working briefly described by Andy Matuschak here https://notes.andymatuschak.org/z21cgR9K3UcQ5a7yPsj2RUim3oM2TzdBByZu. 


## Open Notebook Science

If we apply this "working with the workshop doors open" idea to a scientific research endeavor we understand it as respecting the core concepts of Open Science. These is more precisely the principle of Open Notebook Science https://en.wikipedia.org/wiki/Open-notebook_science

For the projects of the DBGI we will follow such an Open Notebook Science approach in order to share early ideas and results but also the less shiny parts of the research projects. 

You can follow the DBGI related Open Notebooks here [[open-notebook]].

Expect to find strange ideas, badly formulated text and poorly written code. However if you have time and interest you should be able to participate at each step of the process. Hopefully this will lead to enhanced collaboration and participation. Maybe yes, maybe not. Let's make it a methodological experiment !

Each pages of this website are written in markdown and hosted on Github. You can edit them by clicking on the "Click here to edit this page on Github !" link at the bottom of the page. See down there 👇

If you are willing to participate the the DBGI Dendron notes have a look at the [[welcome]] section to get you started !


## What's new ?!

This web site might not necessarily seem to be change since the last time you came to visit.

If something moved recently you should be able to track this over there https://github.com/digital-botanical-gardens-initiative/dendron-dbgi/commits/main