Feature request: Check before reprocessing

Bug #778594 reported by Venus I Jones
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Scribe2
New
Undecided
danh

Bug Description

reprocessing should be feasible before the gui allow it.

Revision history for this message
danh (danh-archive) wrote :

some checks might be (for example):

(a) that there is not already a copy of the item in the republish directory
(b) that the item is not egregiously malformed (so it should at least have a scandata and jpgs)

The checks have to be very simple and fast to perform, so that the gui is capable of them without interfering with its responsiveness.

But both the checks above would be (they just involve looking at the filesystem).

Changed in scribe2:
assignee: nobody → danh (danh-archive)
Revision history for this message
paul.n (paul-n) wrote :

If there are duplicate ids, we want to block people from proceeding unless they adress the duplicate items. Here's what I think that entails:

Everything is blocked except 1) the ability to peek and an item (for investigation) 2) deletion.

Here's one idea on how this would work --

   * The republisher links would be a different color (perhaps red)
   * Clicking the republisher link would give the user the dupe-item prompt, asking them to investigate and fix
   * Likewise, "reprocess" wouldn't work
   * Peek, however, should work. This allows people to assess which copy they'd like to keep

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.