Objects/closures for storing movie information
You're using the "module" pattern, which works well for many use cases. Your code for this pattern is correct as it stands. The best pattern to use is more about how you are planning to use it.

Some different patterns and why they might be better depending on your use case:


This module pattern is a little difficult if you ever needed to create two movie lists on the same page. A different pattern would be the constructor pattern. This would allow you to easily initialize a new list on the same page.
One potential issue with this pattern is there is a lot of private variables. While this is sometimes good design, when you want to unit test this code, it might be faster to have these private variables available, so you can manipulate them for the test. You can do this with the revealing module pattern, or the constructor pattern which will expose them.