Skip to main content
replaced http://academia.stackexchange.com/ with https://academia.stackexchange.com/
Source Link

arXiv is not only for preprints (actually, updating after publication is highly encouraged). So if you can self-archive*) and you have an intersection with an arXiv discipline, it is the best place to place it.

*) The only objection to post-publication is in case where you are not allowed to self-archive and don't wan't to mess with it.

For other disciplines, see Preprint services other than arXiv (for other fields)Preprint services other than arXiv (for other fields).

Or (maybe even better) just - putting them on GitHub repository. It is a stable service + makes it easy to upload work with source code (tex + figures) (much alike arXiv, but on GitHub it is more convenient). Just make sure to link the pdf file in the README.md and reference it properly (i.e. the full citation, the best with a DOI link) so to have its status clear.

arXiv is not only for preprints (actually, updating after publication is highly encouraged). So if you can self-archive*) and you have an intersection with an arXiv discipline, it is the best place to place it.

*) The only objection to post-publication is in case where you are not allowed to self-archive and don't wan't to mess with it.

For other disciplines, see Preprint services other than arXiv (for other fields).

Or (maybe even better) just - putting them on GitHub repository. It is a stable service + makes it easy to upload work with source code (tex + figures) (much alike arXiv, but on GitHub it is more convenient). Just make sure to link the pdf file in the README.md and reference it properly (i.e. the full citation, the best with a DOI link) so to have its status clear.

arXiv is not only for preprints (actually, updating after publication is highly encouraged). So if you can self-archive*) and you have an intersection with an arXiv discipline, it is the best place to place it.

*) The only objection to post-publication is in case where you are not allowed to self-archive and don't wan't to mess with it.

For other disciplines, see Preprint services other than arXiv (for other fields).

Or (maybe even better) just - putting them on GitHub repository. It is a stable service + makes it easy to upload work with source code (tex + figures) (much alike arXiv, but on GitHub it is more convenient). Just make sure to link the pdf file in the README.md and reference it properly (i.e. the full citation, the best with a DOI link) so to have its status clear.

added on referencing
Source Link
Piotr Migdal
  • 26.6k
  • 10
  • 74
  • 126

arXiv is not only for preprints (actually, updating after publication is highly encouraged). So if you can self-archive*) and you have an intersection with an arXiv discipline, it is the best place to place it.

*) The only objection to post-publication is in case where you are not allowed to self-archive and don't wan't to mess with it.

For other disciplines, see Preprint services other than arXiv (for other fields).

Or (maybe even better) just - putting them on GitHub repository. It is a stable service + makes it easy to upload work with source code (tex + figures) (much like onalike arXiv, but on GitHub it is more convenient). Just make sure to link the pdf file in the README.md and reference it properly (i.e. the full citation, the best with a DOI link) so to have its status clear.

arXiv is not only for preprints (actually, updating after publication is highly encouraged). So if you can self-archive*) and you have an intersection with an arXiv discipline, it is the best place to place it.

*) The only objection to post-publication is in case where you are not allowed to self-archive and don't wan't to mess with it.

For other disciplines, see Preprint services other than arXiv (for other fields).

Or (maybe even better) just - putting them on GitHub repository. It is a stable service + makes it easy to upload work with source code (tex + figures) (much like on arXiv). Just make sure to link the pdf file in the README.md.

arXiv is not only for preprints (actually, updating after publication is highly encouraged). So if you can self-archive*) and you have an intersection with an arXiv discipline, it is the best place to place it.

*) The only objection to post-publication is in case where you are not allowed to self-archive and don't wan't to mess with it.

For other disciplines, see Preprint services other than arXiv (for other fields).

Or (maybe even better) just - putting them on GitHub repository. It is a stable service + makes it easy to upload work with source code (tex + figures) (much alike arXiv, but on GitHub it is more convenient). Just make sure to link the pdf file in the README.md and reference it properly (i.e. the full citation, the best with a DOI link) so to have its status clear.

removed figshare part
Source Link
Piotr Migdal
  • 26.6k
  • 10
  • 74
  • 126

arXiv is not only for preprints (actually, updating after publication is highly encouraged). So if you can self-archive*) and you have an intersection with an arXiv discipline, it is the best place to place it.

*) The only objection to post-publication is in case where you are not allowed to self-archive and don't wan't to mess with it.

For other disciplines, see Preprint services other than arXiv (for other fields).

If there is not a particular repository for you discipline, uploading to Figshare may be a good option (however, then you get two DOIs).

Or (maybe even better) just - putting them on GitHub repository. It is a stable service + makes it easy to upload work with source code (tex + figures) (much like on arXiv). Just make sure to link the pdf file in the README.md.

arXiv is not only for preprints (actually, updating after publication is highly encouraged). So if you can self-archive*) and you have an intersection with an arXiv discipline, it is the best place to place it.

*) The only objection to post-publication is in case where you are not allowed to self-archive and don't wan't to mess with it.

For other disciplines, see Preprint services other than arXiv (for other fields).

If there is not a particular repository for you discipline, uploading to Figshare may be a good option (however, then you get two DOIs).

Or (maybe even better) just - putting them on GitHub repository. It is a stable service + makes it easy to upload work with source code (tex + figures) (much like on arXiv). Just make sure to link the pdf file in the README.md.

arXiv is not only for preprints (actually, updating after publication is highly encouraged). So if you can self-archive*) and you have an intersection with an arXiv discipline, it is the best place to place it.

*) The only objection to post-publication is in case where you are not allowed to self-archive and don't wan't to mess with it.

For other disciplines, see Preprint services other than arXiv (for other fields).

Or (maybe even better) just - putting them on GitHub repository. It is a stable service + makes it easy to upload work with source code (tex + figures) (much like on arXiv). Just make sure to link the pdf file in the README.md.

Source Link
Piotr Migdal
  • 26.6k
  • 10
  • 74
  • 126
Loading