At FSU we are using Islandora for both our Digital Collections and the Research 
Repository (http://diginole.fsu.edu).  We rely on the consortial office, FLVC, 
to host.  We work closely with their tech team and can develop features 
ourselves.  I've copied Bryan Brown and Favenzio Calvo, our two developers, in 
case you have questions.

We migrated material from Digitool and Digital Commons.

Feel free to ask us questions.

Jean

Jean Phillips
Assoc. Dean, Technology & Digital Scholarship
Florida State University Libraries
[email protected]<mailto:[email protected]>

________________________________
From: Code for Libraries <[email protected]> on behalf of Habing, Thomas 
<[email protected]>
Sent: Wednesday, October 5, 2016 3:56:53 PM
To: [email protected]
Subject: Re: [CODE4LIB] CONTENTdm And Alternatives

Hi all,

The system at the UIUC Library that you would want to look at is this: 
https://digital.library.illinois.edu/

Think of it as a public-facing front-end to the Medusa preservation archive.  
The data from our local CONTENTdm collections are already in the Medusa 
preservation archive, and soon they will all also be available through the 
public web interface; currently only a subset are.  After this we will be 
retiring our on-premises CONTENTdm.

Also of interest might be our nascent data repository, Illinois Data Bank, 
https://databank.illinois.edu/.   It too makes use of the Medusa preservation 
system and infrastructure.

Pretty much all digital data managed by the UIUC Library are in Medusa or will 
be.   This is currently around 26 million files in about 1000 collections or 83 
TB of content, replicated at two data centers on campus and backed up to Amazon 
Glacier.

The digital library access system also uses our homegrown IIIF image server, 
https://medusa-project.github.io/cantaloupe/.   The Cantaloupe IIIF server is 
really the only open source part that is packaged, documented, and could be 
easily deployed or reused.  However, for the  adventurous, all (or most?) of 
our code for all of the above systems is available on GitHub, 
https://github.com/medusa-project/.

Most of this was developed by the UIUC Library IT, Scholarly Communication & 
Repository Services (SCARS) team.

Kind regards,
Tom Habing

-----Original Message-----
From: Code for Libraries [mailto:[email protected]] On Behalf Of McAulay, 
Lisa
Sent: Wednesday, October 05, 2016 1:54 PM
To: [email protected]
Subject: Re: [CODE4LIB] CONTENTdm And Alternatives

This is pretty interesting — is Medusa a home-grown solution? I can’t find 
information about who made it on the FAQ.




On October 5, 2016 at 11:40:29 AM, Dubnicek, Ryan C 
([email protected]<mailto:[email protected]>) wrote:

This isn¹t quite my area, but thought I¹d chime in to say that the U.
Illinois Library is piloting a few collections in Medusa (more details on this 
here: https://medusa.library.illinois.edu/) as a potential replacement for 
CONTENTdm.

Best,

‹Ryan


Ryan Dubnicek
Project Coordinator
HathiTrust Research Center
Visiting Research Services Specialist
School of Information Sciences
University of Illinois at Urbana-Champaign
209 LIS Building, MC-493
501 E. Daniel Street | Champaign, IL 61820 [email protected]
217-244-7260







On 10/5/16, 1:30 PM, "Code for Libraries on behalf of Diaz, Noel A"
<[email protected] on behalf of [email protected]> wrote:

>We at Purdue Libraries are on the same boat. Already talked with OCLC
>about hosted solution, but we are really now thinking of and looking
>into a better local alternative. We don't plan to make any moves any
>time soon so would be very interested in hearing what others are
>doing/planning.
>
>-- Noel
>
>‹
> Noel Díaz
> Instruction & Research Services Administrator  Information Technology
>Department  Purdue University Libraries
> E-Mail: [email protected]
>
>On 10/5/16, 9:16 AM, "Code for Libraries on behalf of Christopher H Day"
><[email protected] on behalf of [email protected]> 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.
>
>
>
>Chris
>
>--
>
>
>*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 | [email protected]
>http://libraryguides.saic.edu/vrc | https://digital-libraries.saic.edu
>
>

Reply via email to