To maintain quality and version control, the following steps will be used to make additions to a WebResource.

Draft final deliverable stage

• • The PI submits the draft final deliverable abstracts in Microsoft Word. For updated abstracts, the previously edited text is used as the base.
  • The SPO checks that, for any updated abstracts, the PI has used the previously edited version as a base (i.e., edits in the Word files for the previous version, except for possible minor changes made after the initial edit, are in the DFD).
  • The SPO will share this version with the panel to provide their comments and feedback.

Final deliverable stage

• • When submitting the final deliverable, the PI will also submit PDFs of the rulings for editorial reference. The PI provides a list of all abstracts indicating which are new cases and which are new rulings on old cases.
  • The SPO double-checks that, for any updated abstracts, the PI has used the previously edited version as a base (i.e., edits in the Word files for the previous version, except for possible minor changes made after the initial edit, are in the final deliverable).

Publication production stage

• • After the editor has reviewed the abstracts and incorporated the author’s responses to queries, the editor will send the edited Word files to the PI and the SPO so that the SPO will have them on hand for subsequent versions.
  • The PI uploads the text of the edited Word files and PDFs of the rulings into WordPress, creating new pages for any updated rulings. Old pages are not unpublished (i.e., marked private). Users can distinguish between old pages and updates by the name and date of each ruling, which appear on the search page.
  • Publications staff checks that, for any updated cases, the PI has used the previously edited version as a base.