Archive finished products to REAP
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 33
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Given that people are creating content for testing and further refinement before formal publishing, and that they do this regularly throughout the lifetime of their project, it would be good to provide a way to archive these "steps along the way" so that what they have done can be preserved. We already hold much of the meta-data required for a REAP submission package in PTXprint, and can already build an archive with presentation files and ALL supporting files (fonts, USFM data and even the macros themselves), so it seems to be an obvious step in the right direction to automate as much of this as possible, enabling them to be good stewards of their data AND more productive with their time.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by tracing how PTXprint builds archives and stores REAP submission metadata, including presentation, font, USFM, and macro files. Done should mean a defined way to preserve finished project states as a complete REAP-ready archive.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100