> For the complete documentation index, see [llms.txt](https://iblpan.gitbook.io/craft-oa_training_materials_eng/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://iblpan.gitbook.io/craft-oa_training_materials_eng/four-pathways-based-on-proficiency-in-the-publishing-process/publisher-managing-dedicated-publishing-infrastructure.md).

# Publisher managing dedicated publishing infrastructure

<details>

<summary>Workflow Management</summary>

Efficient work organisation is the foundation of a successful team. In this section, we will demonstrate how automation, effective tools, and project management methods (Scrum, Kanban, Waterfall) can streamline every stage of the publishing process. These are practical tips designed to help you organise your workflow, reduce information overload, and focus on what truly matters.

[**GO TO SECTION**](/craft-oa_training_materials_eng/four-pathways-based-on-proficiency-in-the-publishing-process/publisher-managing-dedicated-publishing-infrastructure/workflow-management.md)

</details>

<details>

<summary>Data Management</summary>

Do you want to work faster and more confidently, without constantly searching for data or correcting mistakes? With well-organised, structured information, you’ll save time, achieve better order, and gain easier access to key content. In this section, you’ll discover tools and formats that will help you manage editorial data more effectively, from simple spreadsheets to exchange files and databases.

[**GO TO SECTION**](/craft-oa_training_materials_eng/four-pathways-based-on-proficiency-in-the-publishing-process/publisher-managing-dedicated-publishing-infrastructure/data-management.md)

</details>

<details>

<summary>Data Processing</summary>

Data processing is a key step in organizing information – it involves organizing files, cleaning up data, creating consistent metadata and preparing materials for further use. In this section, we present best practices, helpful tools, and show the potential of Python to automate repetitive tasks.

[GO TO SECTION](/craft-oa_training_materials_eng/four-pathways-based-on-proficiency-in-the-publishing-process/publisher-managing-dedicated-publishing-infrastructure/data-processing.md)

</details>

<details>

<summary>Publishing Software</summary>

Modern publishing software supports every stage of the publishing process – from accepting submissions, to reviewing, to publishing and archiving content. In this section we look at good practice when working with such software. In addition, we will consider moments when, however, publication software is not enough and the need to use additional solutions arises.

[**GO TO SECTION**](/craft-oa_training_materials_eng/four-pathways-based-on-proficiency-in-the-publishing-process/publisher-managing-dedicated-publishing-infrastructure/publishing-software.md)

</details>


---

# 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://iblpan.gitbook.io/craft-oa_training_materials_eng/four-pathways-based-on-proficiency-in-the-publishing-process/publisher-managing-dedicated-publishing-infrastructure.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.