Pre-Installed repositories versus self built

Not sure how this got past me but I just realized I failed to discuss the possibility of downloading a pre-installed VM (Virtual Machine) versus building your own. Well better late than never...

I believe having both options is actually beneficial if you plant to first build a repository, configure it and get to know it and then perhaps either have it packaged for a new installation. Alternatively, if you have already built a prior version, but just need a quick, stand-alone system you could download a prebuilt one to avoid the needless downtime you would incur.

A pre-configured system (hopefully built to your needs) is helpful and provides rapid deployment of resources. For example, if you have an event or exhibit rapidly approaching and not much time to create a whole new web presentation unloading a boxed repository, like Omeka, will get you up an running within a couple of days. This system should have everything you need to either promote or enhance and the usability and discoverability of your digital objects.

On the other hand, learning how databases work and the various tools within your repository will ultimately provide greater functionality and a base understanding of what's going on behind the scenes. Why is this important? Long term maintenance, sustainability, and trouble shooting. Should something go wrong you'll have a much better understanding of where the problems could lie and how to get your system back up and running. You'll have a better opportunity to build your own tools and hook into your repository to connect to other services. Building for the "ground up" also provides the developer with more opportunities for modulatory construction.

My current technical skills are rudimentary at best as far as network administration and database development. I require a lot of instruction and reminders to achieve a fully functional repository up and running so I certainly see the advantage of having an out-of-box solution. In my case having one to create an initial web presence and making content discoverable is very advantageous but I would also want to then build that same repository from scratch and then replace the "out-of-box" with a customized and more functional system when it is available and then employ the OAI Object Reuse and Exchange protocol to seamlessly migrate the content to the new system.