Spam detection software, running on the system "avery.infomotions.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see eric_morgan_at_infomotions.com for details. Content preview: California State University system is moving from Dspace to Hydra (Fedora-based) early next year. At least a few of us in the consortium are thinking of moving our local CONTENTdm to the hydra as well. [...] Content analysis details: (0.6 points, -1.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 3.0 SINGLE_HEADER_3K A single header contains 3K-4K characters -0.0 SPF_PASS SPF: sender matches SPF record -0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail domains are different -0.0 SPF_HELO_PASS SPF: HELO matches SPF record 0.0 T_HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail domains are different -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
attached mail follows:
California State University system is moving from Dspace to Hydra (Fedora-based) early next year. At least a few of us in the consortium are thinking of moving our local CONTENTdm to the hydra as well. --- Bin Zhang Digital Information Services Librarian Library Systems & IT Services, University Library California State University, Sacramento 2000 State University Drive East, Sacramento, CA 95819-6039 (916) 278-5664 (O); (916) 278-3891 (F) bzhang AT csus DOT edu > -----Original Message----- > From: Code for Libraries [mailto:CODE4LIB_at_LISTS.CLIR.ORG] On Behalf Of > Phillips, Jean > Sent: Wednesday, October 05, 2016 1:05 PM > To: CODE4LIB_at_LISTS.CLIR.ORG > Subject: Re: [CODE4LIB] CONTENTdm And Alternatives > > 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 Jsphillips2_at_fsu.edu<mailto:Jsphillips2_at_fsu.edu> > > ________________________________ > From: Code for Libraries <CODE4LIB_at_LISTS.CLIR.ORG> on behalf of Habing, > Thomas <thabing_at_ILLINOIS.EDU> > Sent: Wednesday, October 5, 2016 3:56:53 PM > To: CODE4LIB_at_LISTS.CLIR.ORG > 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:CODE4LIB_at_LISTS.CLIR.ORG] On Behalf Of > McAulay, Lisa > Sent: Wednesday, October 05, 2016 1:54 PM > To: CODE4LIB_at_LISTS.CLIR.ORG > 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 > (rdubnic2_at_illinois.edu<mailto:rdubnic2_at_illinois.edu>) 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 rdubnic2_at_illinois.edu > 217-244-7260 > > > > > > > > On 10/5/16, 1:30 PM, "Code for Libraries on behalf of Diaz, Noel A" > <CODE4LIB_at_LISTS.CLIR.ORG on behalf of noel_at_PURDUE.EDU> 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: noel_at_purdue.edu > > > >On 10/5/16, 9:16 AM, "Code for Libraries on behalf of Christopher H Day" > ><CODE4LIB_at_LISTS.CLIR.ORG on behalf of cday2_at_SAIC.EDU> 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 | cday2_at_saic.edu > >http://libraryguides.saic.edu/vrc | https://digital-libraries.saic.edu > > > >Received on Wed Oct 05 2016 - 16:26:49 EDT