DP-009

Publication Venue Selection

Selecting a publication venue requires balancing scholarly fit, audience, requirements, reputation, timing and practical constraints. Characterise the manuscript first, then discover and compare plausible venues against explicit criteria. Verify current scope, submission rules, fees and other consequential details from authoritative sources near the point of decision. Ranking tools and GenAI may broaden the shortlist and explain trade offs, but the author selects the venue and records the rationale rather than treating a generated recommendation as authoritative.

Source manuscript

When this helps

Editorial synthesis grounded in the source pattern. A manuscript or publication proposal is sufficiently developed to compare plausible venues and plan a submission.

Academics often complete a manuscript yet encounter difficulty determining an appropriate publication venue. This requires balancing scope, audience, prestige, alignment and likelihood of acceptance, while manual approaches such as memory, colleague advice or browsing journal lists are slow and incomplete.

Pattern response

Editorial synthesis grounded in the source response. Frame venue selection as a transparent comparison between the manuscript and plausible publication contexts. Characterise the contribution, methods and audience; discover and rank candidates against explicit criteria; then verify current scope, requirements, fees and constraints from authoritative sources. The author selects the venue and records the rationale rather than treating a generated ranking as authoritative.

  • An evidence-backed shortlist of publication venues with transparent criteria and trade-offs.
  • Verified current scope, requirements and practical constraints for leading options.
  • An author-owned venue decision and recorded rationale.

Workflow at a glance

DP-009 | Publication Venue Portrait workflow diagram for Finding Where to Publish DP-009 | Publication Venue
Canonical workflow · DP-009Publication Venue Selection
  1. 01

    Characterise the manuscript

    An accountable academic initiates, interprets, or approves this stage; automation remains bounded by the listed modules.

    MOD-003 · MOD-001 · MOD-015
  2. 02

    Discover candidate venues

    An accountable academic initiates, interprets, or approves this stage; automation remains bounded by the listed modules.

    MOD-025 · MOD-023
  3. 03

    Match and rank

    An accountable academic initiates, interprets, or approves this stage; automation remains bounded by the listed modules.

    MOD-026 · MOD-020
  4. 04

    Verify scope and requirements

    An accountable academic initiates, interprets, or approves this stage; automation remains bounded by the listed modules.

    MOD-013 · MOD-042
  5. 05

    Select and plan submission

    An accountable academic initiates, interprets, or approves this stage; automation remains bounded by the listed modules.

    MOD-044 · MOD-032

Human checkpoints

People define purpose and boundaries, supply or authorise source material, inspect intermediate representations, resolve ambiguity, approve consequential outputs, correct errors, and remain accountable for scholarly, pedagogical, legal, or organisational decisions. A generated recommendation or draft is not an approval decision.

Risks and misuse

Source-stated improvement concerns

  • Integrate real time calls for papers into recommendation systems to improve timeliness and relevance.
  • Develop improved filtering mechanisms for open access requirements, ethical publishing standards and region specific constraints.
  • Provide case studies demonstrating how manuscripts evolve in response to venue alignment.
  • Enhance interoperability between AI tools and existing research workflows to reduce duplication and manual verification.

Inferred workflow risks

  • Inferred: duplicate ingestion.
  • Inferred: unsupported formats.
  • Inferred: lost provenance.
  • Inferred: partial imports.
  • Inferred: unstated constraints.
  • Inferred: scope drift.
  • Inferred: ambiguous success conditions.
  • Inferred: stereotyping.

Use this pattern

Begin with the recurring problem and the authorised inputs. Follow the workflow in order, keep intermediate outputs inspectable and retain the named human decisions.

  • Minimum viable implementation: a documented human procedure using the ordered modules: Source and Record Ingestion → Workflow Briefing and Context Definition → Audience Analysis → Scholarly Search → Keyword and Metadata Search → Recommendation and Ranking → Constraint Checking → Source Linking and Citation Grounding → Output Quality Evaluation → Human Review and Approval → Task and Milestone Planning.
  • Robust implementation: add explicit schemas, source identifiers, access controls, logging, exception queues, independent evaluation, backups, and named approval owners.
  • Low-code implementation: use forms and a workflow orchestrator to connect bounded services, with approval gates before external communication or state changes.
  • Local or privacy-preserving implementation: keep sensitive artefacts in controlled storage and prefer local extraction, transcription, search, or model execution where capability and governance permit.
  • Speculative implementation: more autonomous coordination may be explored only with constrained tools, stop conditions, audit logs, and human authority; it is not implied by the source pattern.

Reusable modules

View in Atlas →

Technical and provenance detail

Data and information flow

Inputs may include files, records, messages, source metadata, request, context, constraints, audience evidence, communication purpose, research query, date and field constraints, query, indexed records, filters, candidate set, selection criteria, user history, candidate output, constraint set, claim or output, source corpus, location identifiers, output, criteria, source evidence, candidate output or action, evidence, review criteria, goal, available capacity. The stage sequence transforms, analyses, enriches, retrieves, generates, coordinates, stores, or outputs information according to each linked module contract. Outputs may include ingested source set, ingestion log, approved workflow brief, audience profile, design implications, candidate works, bibliographic metadata, search log, ranked matching records, match metadata, ranked candidates, reasons, uncertainty, pass/fail findings, exceptions, unresolved constraints, grounded output, source links, support status, evaluation findings, score or decision, required revisions, approval decision, corrections, rationale, escalation, task plan, milestones, dependency map. Source identity, permission state, uncertainty, retention, and human decisions should travel with records rather than being discarded between stages.

Source provenance

  • Pattern ID: DP-009
  • Original title: Pattern 12: Finding Where to Publish
  • Source location: SRC-001:P0206–P0230; page number unknown.
  • Source status: explicit.
  • Extraction notes: Canonical ID follows manuscript order. Legacy numbers are not used as publication identifiers; any numbered source heading is retained only for provenance and source fidelity.
  • Editorial interventions: The public title, summary, context, response and intended outcomes are concise editorial syntheses grounded in the source pattern. Original source prose is preserved below; workflows and modules remain separated and provenance-labelled.

Open questions

  • Which elements of this pattern require empirical or practice-based evaluation in the intended setting?
  • Which implementation examples remain current, authorised and proportionate to the setting at the time of use?