Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-8588

Create DOIs for DMTN-006 and DMTN-021

    XMLWordPrintable

Details

    Description

      PUB-39 requires DOIs for DMTN-006 and DMTN-021. For now, these DOIs are prepared manually since we haven't engineering a technote release process yet.

      Attachments

        Activity

          DOI for DMTN-006 is http://dx.doi.org/10.5281/zenodo.192828 (also needed to configure LSST the Docs deployment).

          DOI for DMTN-021 is http://dx.doi.org/10.5281/zenodo.192833 (this also required significant effort to fix reStructuredText issues in the original document before releasing the artifact to Zenodo).

          jsick Jonathan Sick added a comment - DOI for DMTN-006 is http://dx.doi.org/10.5281/zenodo.192828 (also needed to configure LSST the Docs deployment). DOI for DMTN-021 is http://dx.doi.org/10.5281/zenodo.192833 (this also required significant effort to fix reStructuredText issues in the original document before releasing the artifact to Zenodo).

          Procedure is roughly:

          • Start a deposition on Zenodo and reserve a DOI. The 'journal' is "LSST DM Technical Notes" (could be standardized later).
          • Create a v1-prerelease branch in the Git repo.
          • Add DOI to metadata.yaml
          • Add DOI to README.rst (as a badge)
          • Add DOI text to top of index.rst
          • Push branch to ensure it builds
          • Create a 'v1' tag and push to GitHub
          • Viewing the v1 build on LSST the Docs, create a PDF of the technote using the browser
          • Build the technote locally and copy the local repo and delete the .git and _build/doctree directories
          • tarball the technote repository
          • Upload the PDF and tarball to Zenodo
          • Submit the Zenodo deposition
          jsick Jonathan Sick added a comment - Procedure is roughly: Start a deposition on Zenodo and reserve a DOI. The 'journal' is "LSST DM Technical Notes" (could be standardized later). Create a v1-prerelease branch in the Git repo. Add DOI to metadata.yaml Add DOI to README.rst (as a badge) Add DOI text to top of index.rst Push branch to ensure it builds Create a 'v1' tag and push to GitHub Viewing the v1 build on LSST the Docs, create a PDF of the technote using the browser Build the technote locally and copy the local repo and delete the .git and _build/doctree directories tarball the technote repository Upload the PDF and tarball to Zenodo Submit the Zenodo deposition

          People

            jsick Jonathan Sick
            jsick Jonathan Sick
            Jonathan Sick
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Jenkins

                No builds found.