> For the complete documentation index, see [llms.txt](https://bcds.gitbook.io/using-open-journal-systems-best-practices-and-tool/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bcds.gitbook.io/using-open-journal-systems-best-practices-and-tool/open-journal-systems-tools-for-success/organizing-your-issues.md).

# Organizing your Issues

Managing online versions of your journal is not necessarily as intuitive as organizing print copies: these articles are not bound and covered, and without a cohesive strategy for organizing your content into separate articles and issues, it could be difficult for a reader to navigate your website. These are a few key tools to use to help organize your online Journal Issues.

### Creating New Issues

Creating a New Issue can help to organize articles before you publish them. By assigning articles to an issue, make them accessible to your readers, and provide a cohesive issue.&#x20;

To create a New Issue, navigate to the "Issues" pane in the sidebar and select "Future Issues" you will then see an option for "Create Issue."

{% embed url="<https://www.loom.com/share/96c20f60d78a4cf1acbbdd0186a6a4cd?sid=ce5dd00e-c3f7-4acb-9c1a-60963449ddba>" %}

### Assigning Articles to Issues

Without an Issue, readers cannot view your articles. You can publish articles immediately in an Issue that is already published, a "Back Issue." Or you can assign you published articles to a "Future Issue" which can collect articles and then be published all at once.

To assign your article to an issue, find the article in the "Submissions" dashboard. Once you have found the proper submission, navigate to the "Production" stage and select "Schedule for Production."

{% embed url="<https://www.loom.com/share/b0b23fe85b914326b7e7dd3916d88404?sid=62a7869e-01c3-4a31-87ad-59325b0875bd>" %}

### Assigning Page Numbers to Articles

In the same window where you select the issue, you can assign page numbers to you article within your issue.&#x20;

<figure><img src="/files/-MhPt0RDmRrV8QnbNpz2" alt="Open Journal Systems dialogue screen with boxes for publication date and licensure information"><figcaption></figcaption></figure>

These page numbers appear on the right side of the article on your journals page:

<figure><img src="/files/-MhPxHWZ27TxfDFexZVb" alt="Example articles on Open Journal Systems with page numbers listed in right hand column"><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://bcds.gitbook.io/using-open-journal-systems-best-practices-and-tool/open-journal-systems-tools-for-success/organizing-your-issues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
