You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Discussion on Slack suggests this should point to...
list the ORDA repo for it first
then Beton
then over/under?
Whilst ORDA (the University of Sheffield self-hosted figshare instance) has been used in the past and is still available it may not allow DOIs for specific versions to be easily (i.e. automatically) generated. This is perhaps possible with Zenodo though, see #1019 for further details.
Regardless the documentation in the following (at least, perhaps more under docs/) need updating to reflect the current released version
README.md
CITATION.cff - will require a DOI for released versions to be available and long term this becomes a chicken and egg problem as each new release, which will trigger a Zenodo (or otherwise) DOI will then require this file to be updated. Perhaps there is a GitHub Action that could be crafted to do this and make a PR to update the file automatically (although perhaps extending the Zenodo update action linked from DOI for versioned releases #1019 would be more appropriate, thus making it available to others).
The text was updated successfully, but these errors were encountered:
Currently the lined paper under Publications in the README.md points to TopoStats – A program for automated tracing of biomolecules from AFM images.
Discussion on Slack suggests this should point to...
Whilst ORDA (the University of Sheffield self-hosted figshare instance) has been used in the past and is still available it may not allow DOIs for specific versions to be easily (i.e. automatically) generated. This is perhaps possible with Zenodo though, see #1019 for further details.
Regardless the documentation in the following (at least, perhaps more under
docs/
) need updating to reflect the current released versionREADME.md
CITATION.cff
- will require a DOI for released versions to be available and long term this becomes a chicken and egg problem as each new release, which will trigger a Zenodo (or otherwise) DOI will then require this file to be updated. Perhaps there is a GitHub Action that could be crafted to do this and make a PR to update the file automatically (although perhaps extending the Zenodo update action linked from DOI for versioned releases #1019 would be more appropriate, thus making it available to others).The text was updated successfully, but these errors were encountered: