...

• Description the journal project proposed

• Who will be the journal manager?

• Who is the library/publisher contact? 

• Continuity plan

  • [Suggestion: Create a journal email via campus IT that can be accessed by subsequent journal managers. This also prevents old emails remaining in the system. ]

Section III: Responsibilities of the Library or Publisher

...

• Editorial overview and creation of an editorial board

• Filling out journal information on the website. 

  • [COAPI or COPE information can go here. ]

• Staffing

• Copyediting/typesetting

• Peer review workflows and policy (single blind, double blind, open) 

• Website customization (refer to the TDL OJS Service Policy (link) to see limits on customization available). 

• Copyright policy and Creative Commons license assignment 

  • SPARC offers guidance on Publishing Program Policies:

    • Examples for Submission and Content Policy are included

    • Examples for Access and Preservation Policy are also included

• Migration. OJS does come with import tools and a Quick Submit plugin that can help Journal Teams move issue and article archives from a previous journal system into a new TDL-hosted journal. TDL cannot provide support for this migration during the initial journal setup. 

• Awareness of plans for indexing and listing the journal. For example, DOAJ or SCOPUS inclusion will have certain requirements that the editor will want to have in mind very early.

• Maintaining user accounts

  • Deleting old user accounts periodically (recommended once per year). 

  • Using a journal email address for workflow and continuity. 

  • Reporting any suspicious user registration behavior to TDL Help Desk or Library contact. 

...