search

elifesciences / elife-vendor-workflow-config

capturing requriemtns and niggles for setting up the elife production workflow
0 stars 1 forks source link

Changes to archive need co-ordination with any "corrections" and resupplies #116

Open Melissa37 opened 9 years ago

Melissa37 commented 9 years ago

New issue to think about: When we move from TNQ, we do the PMC deliveries. That means when EXeter supply a corrected VoR file, they will deliver direct to HW with no indication in file naming, and deliver to the AWS bucket with a new r number. How does Graham’s system know to pick up this new version for the archive for PPP going live? Archive renamer to look in the ExeterPremedia AWS bucket and pick up most recent version.

gnott commented 9 years ago

If Exeter is to correct a VoR file from before the switch, I suggest they add "r2" to the file name on the new file naming zip file.

We can either update the archive renamer to pickup the "r1" from the old bucket and then look for any "r2" in the new bucket. It can set the "v1", "v2", "v3" names appropriate to any PoA versions and all the VoR versions.

Melissa37 commented 9 years ago

The workflow is set up so they will load the latest version into their bucket on AWS using r numbers anyway, and our system is to ignore that. That's because there could be revisions to this stage before reaching hosting and just part of the production process. Therefore, we cannot rely on the r numbers. I suspect we'll maybe need to do a manual work around while we are still with HW but switched to ExeterPremedia? Looking at the stats, this happens about

Q3 2015 data: Number of articles published 230 Number of revised files post VoR publication 27 About 12% of content. We're still discussing in the planning team which, if any, of these will get a new VoR version on the site (for instance XML changes will not warrant a new version). Once that is decided, it will hopefully be easier to work out what to do here.

However, this issue just relates to the archive and ensuring when we go live it is run with the exact final XML that is on the HW site.

Hope that makes sense?

gnott commented 9 years ago

In the final run of the archive renaming, if we take the latest VoR version from the Exeter bucket in place of the VoR from the elife-articles bucket then it should work by producing one VoR version only. That sounds like the simplest plan and is probably a good option.

Melissa37 commented 9 years ago

Sounds good to me, thank you for simplifying it!