Week of June 3
As I moved toward the later volumes, there was far less work to be done as I had cleaned up the template somewhere along the way, and most of the changes were made in one include file, one root level (issue) file and the index file.
Of course I will find bits and misses as I move back through for other fixes, but I’m confident that the “open current issue” button in the 43 issues now take readers to the new journal at the blackbird.vcu.edu URL, whereas before these links were throwing up a frustrating 404 page.
The idea, of course, is to bolster the throughput from legacy Blackbird content to the new journal.
I’m heading next to look at video for several issues that was on (at the encouragement of the tech powers that be at the time) the “Flash video server.” Fingers crossed that I have access at hand for all the video files that aren’t working without having to search through external drives.
These files will be uploaded the the blackbird-archive Kaltura account, embedded in the content page, and republished. After mending these non-working files, I will eventually also migrate all later media on the blackbird.vcu.edu Kaltura account to the blackbird-archive.vcu.edu Kaltura account a republish. (Whether new Blackbird chooses to publish any audio or video media on Kaltura or not, that account is tied to the new journals login and password, and the effort here is to consolidate all legacy materials under the blackbird-archive accounts for cleaner management.
I believe that all the deprecated Flash pages were repaired with Ruffle, but I will be auditing all that content. I know at least one Myron Helfgott piece was broken not because of Flash/Ruffle issues, but because of a missing image or broken path and a need to convert and republish the base audio.
Piece in question is v8n1’s “Tyranny of the Theoretical.” The first zoom interface works, the second does not, showing only a blank square; however, both run and work inside of Dreamweaver/Adobe setups when I click on the SWFs, so still need to troubleshoot where the glitch is; I mistakenly assumed an image path error, but now I think not.