Adding NOMAD .eln support to README.md #86
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SteffenBrinckmann
added a commit
to SteffenBrinckmann/TheELNFileFormat
that referenced
this pull request
Oct 5, 2024
This reverts commit 89a291e.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dear @NicolasCARPi and all the other contributors.
Since NOMAD does import .eln files and @amirgolp demonstrated this on the last elabFTW users meeting, I thought we should add NOMAD to the list of tools supporting the format. I only put input, since we only see NOMAD ad a consumer of .eln files and a potential data publishing platform for .eln file users. I think example does not apply, when you are importing files. Just listing an elabFTW file for example, seems wrong to me.