Skip to content

Publication Checklist

Julia Flanders edited this page Jul 19, 2024 · 3 revisions

Process for publishing DHQ articles and issues

Publishing individual articles

When we publish individual articles, we are moving them from the internal preview space to the public preview space. This process involves the following :

  • Check every article for validity and fix all errors
  • Check every article's metadata: Author name, email address, bio; publication date; article ID
  • For each article being added to public preview, include a comment in the toc.xml file indicating the date when the file was added

Creating a new "preview" issue and promoting an entire issue to "current" status

When we publish a new issue, we create a new preview issue and also promote the previous "preview" issue to "current" status. This process involves the following steps:

For the new "preview" issue:

  • create a new <journal> element with an attribute preview="true"
  • add a comment at the start of the <journal> element indicating the date the issue went into public preview
  • validate the article, fix any errors, check the metadata for each article to be published, and make sure that the article's publication date and article ID have been added to the TEI header. Also check that the article type is correct in the metadata.
  • check the article type for each article (case study, review, etc.) and make sure it is being added to the correct section of the issue. (This information can be found in OJS in the Publication tab, in the "issue" subsection.)
  • move the relevant <item> elements from the internal preview area into the public preview area, and for each one, add a comment indicating the date the article was put into public preview

For the new "current" issue:

  • on the <journal> element, change preview="true" to current="true"
  • remove the current="true" value from the previous current issue
  • add a comment at the start of the <journal> element indicating the date the issue was published

Additional steps:

  • once the server has been updated, contact the Communication and Outreach team to let them know the new issue has been published
  • generate PDFs for each article in the new issue and upload them to the server (Julia does this)
  • contact the authors of the newly published articles