Another alternative: stick with CONTENTdm for metadata ingest and
admin but take charge of the front end by migrating it to Blacklight.
That is what we are doing here: http://lib-mdl-dev.oit.umn.edu (demo
/ prototype site). We plan on launching our MDL Blacklight instance
sometime this spring.
Everything we're doing is MIT:
I'm planning on pulling out a few more features from mdl_search
example app into the cdmbl gem to allow an even more "plug and play"
sort of experience. PRs and feedback are welcomed and appreciated.
On Wed, Oct 5, 2016 at 8:16 AM, Christopher H Day <[log in to unmask]> wrote:
> I wanted to solicit some feedback and advice from my code4lib colleagues
> about Digital Collections and Institutional Repository software solutions.
> For the past several years we have used a local installation of CONTENTdm
> as our digital repository [http://digital-libraries.saic.edu/]. Due to
> OCLC's recent announcement of a shift to a "hosted only" model for
> CONTENTdm, we are starting to research our options for change.
> We would like to be able to provide additional functionality for our
> library digital collections, and to provide our campus with a more
> versatile institutional repository.
> If your institution is using CONTENTdm Hosted, Islandora, Digital Commons,
> or other similar products, I'd love to get a feel for your experiences --
> especially about migrating to your current platform from an earlier
> product. If you have some time for a few brief questions by email please
> feel free to contact me off list.
> Thanks very much for your time.
> *Christopher Day *Digital Resources Librarian
> MacLean Visual Resources Center
> John M. Flaxman Library | The School of the Art Institute of Chicago
> 37 South Wabash, 6th FL, Chicago, IL 60603
> 312.899.5101 | [log in to unmask]
> http://libraryguides.saic.edu/vrc | https://digital-libraries.saic.edu
University of Minnesota Libraries