Community Meeting II, 4:00 p.m. CEST, 16 May 2024

[ELN-uzun]

Dear eLabFTW Users,

following the success of the first Community Meeting, we're thrilled to invite you to our second session, scheduled for May 16, 2024, at 4:00 p.m. (UTC +2). This bi-monthly webinar series continues to provide a valuable platform for collaboration and knowledge sharing within the eLabFTW community.

In this session, we will offer users the opportunity to present their work with eLabFTW in three talks - each 15 minutes. We invite you to participate and also want to give you the opportunity to present your work. Simply leave a comment and we will get back to you. In the coming weeks, the exact talks will then be added here:

1. Niels Cautaerts - (Using eLabFTW as a flexible data entry system #4857 (reply in thread))
2. Manuel Lera Ramirez - eLabFTW as a source for plasmids manulera/ShareYourCloning#8
3. Nicolas CARPI - Add ed25519 signature and action requests #5027

The last 15 minutes of the session will be open to your thoughts, feedback, and questions.

Save the date and join us for another interactive session where we'll continue to shape the future of eLabFTW together!

Zoom-Link for this meeting: https://zoom.us/j/94038650576?pwd=MGJEeFdKYjVzTU1wYlhGMFYrbjBqZz09

Best regards,
Hüseyin Uzun

[NicolasCARPi]

[Andrew-Porter1]

Fab, really enjoyed the first meeting and found it very useful. The topics for the talks this time are very relevant to our current early testing of ELabFTW, too.

[cknuepfer]

Is it really 4 p.m. CET (UTC+1)? Or European summer time CEST (UTC+2)?

[ELN-uzun]

It's UTC +2. I'll add it to the original post

[NicolasCARPi]

Two days!

[NicolasCARPi]

Meeting starts in 40 minutes!

[Aveyron-RetD]

oh !! :-( it was full could not connect to it. Maybe they need to be turned into livestreams...

[NicolasCARPi]

@Aveyron-RetD you should connect now, we're at 98 !! And yes, next one will have bigger limit!

[Aveyron-RetD]

yeah managed after multiple retry !! thanks for the talk !!

[NicolasCARPi]

AI Summary

Quick recap

The team discussed secure user authentication methods and potential improvements to the user experience for accessing an archive. They also delved into technical aspects such as timestamps, signatures, and the management of metadata fields, with a focus on the challenges of updating old items and preventing dangling links. Lastly, they explored the development of an exclusive edit mode for experiments and the storage of data and metadata, agreeing to continue discussions on Github and be informed about the next community meeting.
Next steps

Timm will explore a user-friendly way to achieve the discussed security feature of encrypting and signing emails for file access, potentially using the local mail user client.

Cautaern will consider implementing a feature to archive deleted items instead of allowing them to be deleted, to prevent loss of data and maintain data integrity.

Andreas will explore the possibility of locking signed documents to prevent unauthorized changes, as suggested by Nicolas, to enhance the security and trustworthiness of the system.
Summary

Secure Authentication and Technical Discussions

Nicolas and Timm debated on secure user authentication methods for accessing an archive, with Timm advocating for a user-friendly email-based approach while Nicolas voiced concerns about the trustworthiness of system administrators. Meanwhile, Hüseyin led discussions on various technical topics such as timestamps, signatures, and the upcoming project's release date. Cautaern clarified that no constraint is enforced when deleting an entity indicated by a metadata field, but a dangling pointer could result. Lastly, Josh proposed a potential solution to prevent dangling links upon item deletion.

Metadata Management and Resource Blocking

Josh inquired about the management and versioning of metadata fields, with Cautaern explaining their current manual process involving a git repository and a yaml file. Cautaern also highlighted the challenge of updating old items when templates are updated. Josh expressed interest in this solution for his own team's challenges. Andreas asked about the possibility of blocking resource entries post-signing for security and presentation purposes. Nicolas suggested a user experience improvement involving a lock option after signing, which Andreas found convincing for demonstrating to authorities.

Time of Signature, Last Change, and Storage

Nicolas and Hüseyin discussed the comparison of the time of signature and the last change recorded on experiments, with Marcel adding that an exclusive edit mode is being developed to prevent unauthorized changes. Christophe asked about the storage and metadata of data, to which Nicolas clarified that they use databases and that the specifics of their approach would be detailed in their documentation. The team agreed to continue discussions on Github and to be informed about the next community meeting.

[NicolasCARPi]

Thanks everyone for joining and for questions, remarks and feedback!

[alexander-haller]

while Nicolas voiced concerns about the trustworthiness of system administrators

🤣

[Andrew-Porter1]

[like] Andrew Porter reacted to your message:

…

________________________________ From: Nicolas CARPi ***@***.***> Sent: Thursday, May 16, 2024 3:19:18 PM To: elabftw/elabftw ***@***.***> Cc: Andrew Porter ***@***.***>; Comment ***@***.***> Subject: Re: [elabftw/elabftw] Community Meeting II, 4:00 p.m. CEST, 16 May 2024 (Discussion #4988) Thanks everyone for joining and for questions, remarks and feedback! — Reply to this email directly, view it on GitHub [github.com]<https://urldefense.com/v3/__https://github.com/elabftw/elabftw/discussions/4988*discussioncomment-9459619__;Iw!!PDiH4ENfjr2_Jw!HwMqEpgJwswjhV3KwNhp6VrK8SO_mgYmKYJl16Nx9Bj4aBgs0AInKhPnHcNW1OHjrqY9UlyiaNmGGoddsd_c8ZyunkBxzacDk_rGkbs$>, or unsubscribe [github.com]<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/BBLGV4NJXSFSXZTSN6DFB53ZCTE7NAVCNFSM6AAAAABEWOOWNWVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TINJZGYYTS__;!!PDiH4ENfjr2_Jw!HwMqEpgJwswjhV3KwNhp6VrK8SO_mgYmKYJl16Nx9Bj4aBgs0AInKhPnHcNW1OHjrqY9UlyiaNmGGoddsd_c8ZyunkBxzacDZdpbY4o$>. You are receiving this because you commented.Message ID: ***@***.***>