So Fedora may have gotten the best of me. I don't think that I want to pursue an open source solution me, by my lonesome, as my one mind blowing project. I really wanted to, in a way, to make myself feel smart -- Now I'm feeling like it would be an overwhelming decision. So... We may go with ContentDM for images.
My hesitations with ContentDM or any proprietary software:
1) Lack of ability to customize and to integrate into the library's website
2) Cost of updates / Inability to stay up with updates, if cost prohibitive
3) Creating a "cookie cutter" respository
I will be learning more about ContentDM next month at Palinet. My hypothesis is:
ContentDM will prove to be much more intuitive and easier to work with out of the box than an open source system. ContentDM will be less customizable and harder to integrate into the library's website, but may be worth the sacrifice, due to the lack of labor that the program will require to set up. ContentDM is making strides in abililty to handle text-based assets, but will continue to be outshined by DSpace or other institutional academic respositories.
I want to keep my hand in open source work to some degree so maybe we will look at implementing DSpace or EPrints for an academic respository of research and writing. The open source community is hard at work deploying cutting edge technologies and programming to make collections more accessible - I think it would be a good experience to have to do some of the original programming myself, and not rely completely on tech support and help lines to get things done...
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment