Request: ReRepublisher on the cluster
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Scribe2 |
New
|
Undecided
|
danh |
Bug Description
Hi,
Just filing a formal request to put ReRepublisher on the cluster. This will make quality assurance corrections much less clunky.
Thanks to Jude's ReRepublisher, we at least have the ability to make these corrections (years ago, we use to gut and re-scan anything that had a quality issue). But this process is still a bit clunky:
1) Download the files to a Scribe computer using the rerepublisher script (which then processes the files to get them into a republishable state)
2) Open in Scribe to make your edits
3) Gut the version online, manually (including changing the repub_state)
4) Check in the edited version
5) Delete the backups from the Scribe's Desktop, manually
Just to get us thinking about ReRepublisher on the cluster, here's just one proposal for how it might work:
1) run a book_op from item manager which takes care of the necessary processing
2) create some dashboard where users can check to see which items are ready to be re-republished, they can launch that session from the dashboard. Perhaps us.archive.
3) republish the book in your browser and check in (checking in a book this way should initiate the gutting and changing of repub_state prior to submitting an archive.php task)
Changed in scribe2: | |
assignee: | nobody → danh (danh-archive) |