The eBookPDFStitcher application addresses the needs of the UVM library to combine multiple PDFs into a single file. The primary use case is to facilitate the creation of lendable digital copies of books for libraries. Publishers often release books with chapters in separate PDF documents, and this tool aims to provide an easy and cost-effective solution for combining them into a single PDF. The tool can also handle file inputs of types docx, xlsx, csv, pptx, png, jpeg, and jpg.
The project is currently locally hosted with Flask. The front-end provides the user with prompts to browse or drag/drop files onto the page and then displays the output in a scrollable window. The user can also delete pages and reorder files to their liking. Once the output is sufficient, they are able to download the file directly to their local machine.
We plan to host this application on a server so that it is accessible by not only UVM, but other universities to provide a free alternative to the Adobe paid software.
Clone the repository
git clone https://github.com/yourusername/yourproject.git
Navigate to the project directory
The testing_file directory contain sample pdfs for testing scripts
Install dependencies
You will need to install the following Python Packages
- PyPDF2
- fitz
- os
- shutil
- Flask
- Flask-Session
- cachelib
- uuid
- gotenberg-client
- pathlib
- Pillow
As well as Docker
Running the application
flask --app app.py run
or
python -m flask --app app.py run
You can add the --debug flag at the end of the command if you are actively working on the project, which will alow you to have your change carried over to the webpage when you save your work and reload the page
This project is for general use in stitching together sequencial PDFs while following the copyright for those documents.
There are several ways you can contribute to this project:
-
Bug Reports:
- If you find a bug or issue, please open a new issue with a detailed description.
- Include steps to reproduce the bug if possible.
- Mention the version of the project where the issue occurred.
-
Feature Requests:
- If you have a feature in mind that you'd like to see, open a new issue and describe the proposed feature.
- Include any relevant use cases or scenarios.
-
Pull Requests:
- Feel free to submit pull requests for bug fixes or new features.
- Before submitting, ensure your code follows the project's coding standards.
- Clearly describe the purpose of your pull request.
-
Documentation:
- Help improve the project's documentation.
- Fix typos, clarify explanations, or add missing information.
- Fork the project repository.
- Create a new branch for your contributions (
git checkout -b feature/your-feature). - Make your changes and commit them (
git commit -am 'Add some feature'). - Push to your branch (
git push origin feature/your-feature). - Open a pull request explaining your changes.
Please note that we have a Code of Conduct. By participating in this project, you agree to abide by its terms.
By contributing to this project, you agree that your contributions will be licensed under the MIT License.
This project would not be possible without the contributions of Tamunotonye Harry
Do the books tend to stick to a similar layout, or does it vary from one book to another? For instance, do they typically include elements like title pages and page numbers in consistent locations, or is it more diverse? Layouts vary some, but almost all books will have a title page and page numbers in consistent locations.
Do the dimensions of the pdfs often vary between chapters (so from a letter to a legal size) in a set of scans? All books are consistent chapter to chapter.
Is there a max number of individual PDF chapters for a given book the tool will need to handle and merge? Rare to see an academic book with more than 50 chapters