Determine If All 186 Masterfile deletes were valid #142
Comments
|
As a FYI, these 76 masterfile ids represent while Johnny Cash lost files They are present on Avalon 4, but not on AWS. So these pids can be remigrated when do our final check. Good news is this means there aren't split media objects or random unattached masterfiles running around 6 probably I will look into the other 110 and see how many need to be remigrated. |
|
Okay @mbklein Looks like 156 of the 186 need to come across. My methodology was to pull up the masterfile on 4 and see if it had:
If it had both, flag it as something that needs to be remigrated. The pid list is: |
|
We also need to do media objects |
|
@mbklein media object ids (and all masterfiles and derivatives, they've been totally cleared out of AWS Avalon) ["numedia:9916", |
|
@carrickr Corresponding migrated ids of those media objects: ["2f75r8519", |
|
For some reason, I had to manually find and reattach two master files to one large (177 section) media object. There were also 3 strays that thought they belonged to that object – and they probably did, but were removed in 4 – that I had to get rid of. This may be the case with the other objects I migrated tonight. Several of them thought they had the wrong number of master files, but I forced them to complete with what they had. So the above 27 items will need to be hand-checked against legacy. Please emphasize to everyone not to panic if there are small discrepancies. The master files are there; they just need to be found and wired up. This 177-section item was a pain, but it's also a good sign that it was doable. |
|
Don’t Panic… And make sure you keep your towel, man.
… On Jun 17, 2017, at 12:51 AM, Michael B. Klein ***@***.***> wrote:
For some reason, I had to manually find and reattach two master files to one large (177 section) media object. There were also 3 strays that thought they belonged to that object – and they probably did, but were removed in 4 – that I had to get rid of. This may be the case with the other objects I migrated tonight. Several of them thought they had the wrong number of master files, but I forced them to complete with what they had. So the above 27 items will need to be hand-checked against legacy.
Please emphasize to everyone not to panic if there are small discrepancies. The master files are there; they just need to be found and wired up. This 177-section item was a pain, but it's also a good sign that it was doable.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#142 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AElKnlkngjA9XBz9S44AfBXsPKbxzwqnks5sE2lEgaJpZM4N7QyF>.
|
|
Migration has run, since there are just 27 media objects I'll check them by hand with regard to section count and spot check individual master files for streaming |
|
This is done, everything migrated, just HLS splits and attachments left. |
|
@carrickr want me to close this or leave it open/in review? |
|
@carrickr This is closed, correct? reopen if not |
We have 186 masterfiles in Avalon 4 that did not make it to Avalon 6. At least some of these are probably valid deletes and shouldn't have been migrated (old testing data that was never cleaned up, etc). However mbk and I have concerns that 186 seems rather high.
The master files are:
The text was updated successfully, but these errors were encountered: