set scandate to date of republishing in new workflow
Bug #702681 reported by
danh
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Scribe2 |
New
|
Undecided
|
danh | ||
Bug Description
Per both Paul and Jude, we should be using the date of republishing as the scandate, at least in the new workflow.
The change of date could be done as part of the checkin process (where we have a chance to edit the scandata).
| Changed in scribe2: | |
| assignee: | nobody → danh (danh-archive) |
Revision history for this message
| Celeste Compton (celeste-h) wrote | #1 |
To post a comment you must log in.
Prior to pushing code throughout the Princeton center, the scandate associated with an item reflected the date it was "checked-in" following republishing. Now, it seems the scandate is the date the book was shot at the scribe, regardless of when it was actually republished. This is presenting a problem for monitoring the progress of our fold-out operators since blanks for folio items are often shot long before they make it to the republishing stage.