I just returned from seeing “Star Wars: Rogue One” and thought it was a fun exploration of the challenges of finding, retrieving, and transferring mission critical content (in this case, plans for the Death Star showing a critical vulnerability).
Before I begin, let me give this
*** Spoiler alert! ***
The core of the story, from an enterprise content management (ECM) point of view, is that our hero – Jyn Erso – is told there is a piece of content that would help her team make better decisions (regarding a certain upcoming attack). Jyn, eager to help her team, heads off to get it.
It seems the Empire uses siloed, decentralized ECM systems and this particular document (some sort of CAD file) is stored in Scarif at headquarters. Arriving in Scarif, Jyn has trouble locating the file because it has been given an intentionally obscure filename and lacks metadata. There doesn’t seem to be any full-text search capability either (e.g., “search: death star vulnerability”), compounding the problem. Luckily Jyn figures out the filename and goes to the storage array to remove the file.
But a content manager’s job is never easy or done. The file needs to be sent to her team, but it turns out the wifi is down. Jyn has to re-aim the antenna. Once it connects, she has to use a form of managed file transfer (MFT) to get the file to her team.
Success! When the Empire’s CSO – Orson Krennic – realizes the file has been transferred he is enraged that unauthorized personnel were able to access the file despite not appearing on the access control list (ACL). But Jyn’s team is overjoyed at the successful file transfer.
My verdict? Star Wars: Rogue One is the most exciting ECM movie in a long time. It does a great job of illustrating the thrill and challenge of being a content manager and should inspire new generations to enter the exciting field of knowledge management.
Also, the difficulty involved in finding, retrieving, and transferring the file will no doubt educate IT leaders of the dangers of siloed ECM systems, the importance of proper file naming and taxonomy, and the criticality of maintaining proper security and access control for mission critical content. I’m sure this was the intent of director Gareth Edwards and the screenwriters.
Why only 3 stars? While many ECM tasks were accurately portrayed (or exaggerated as Hollywood tends to do), some were wildly inaccurate. For example, Bodhi (one of Jyn’s staff) has to use a massive cable to manually connect the repository to the antenna. Or, worse, Jyn has to physically find the file, which takes the form of a box. I’m hoping that a society that can build star ships that warp around the galaxy and death stars wouldn’t require unplugging files like they are lego bricks.
But that’s being picky. It’s not too often Hollywood will spend $200 million on a movie about file retrieval, so I encourage everyone to see it. May the Files be with you!
[Seriously, Star Wars: Rogue One is a fun popcorn movie. I saw it in 3D, which I highly recommend. I do believe that movies can offer a great way to view the application, use, and abuse of technology from a different lens, although this review was more humorous. “Lives of Others”, for example, is a more serious view into privacy and information management and taxonomy, and a powerful and meaningful movie as well. If you enjoyed this review, check out “‘Her’ – A Tech Movie Review” as well.]
View Free, Relevant Gartner Research
Gartner's research helps you cut through the complexity and deliver the knowledge you need to make the right decisions quickly, and with confidence.Read Free Gartner Research
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.