To be clear, Hydra-in-a-box is in the planning stage at this point, and has not AFAIK, begun development. While planning to offer a much friendlier install than earlier incarnations of Hydra, is still a Fedora-based solution, and won’t come with a Fedora-expert-in-the-box. It will address metadata management issues, but exactly how that will happen is not yet defined.

The good news is that both Islandora, the tool I work with, and Hydra will be moving to Fedora 4, and that will make them both easier to use in many respects. In fact, they should become interoperable.

Thanks,

Cary




> On May 5, 2016, at 2:38 PM, Kerchner, Daniel <[log in to unmask]> wrote:
> 
> Although you might not have the level of technical expertise required to
> support Fedora-based applications in their current incarnations, you might
> want to keep an eye on progress on the Hydra-In-A-Box project.
> Hydra-In-A-Box is meant to provide the benefits of Hydra but would actually
> be easy to install (i.e. not requiring a software developer on staff)
> and/or can be used as a hosted solution.  I think a major driver is to
> provide a solution that is just as much an option for "small, scrappy
> institutions" :)
> 
> http://hydrainabox.projecthydra.org/
> 
> - Dan
> 
> 
> 
> 
> 
> 
> 
> *Dan KerchnerSenior Software Developer, Scholarly Technology GroupThe
> George Washington University LibrariesGelman Library2130 H Street,
> NWWashington, DC [log in to unmask] <[log in to unmask]>*
> 
> 
> On Thu, May 5, 2016 at 5:15 PM, Kelsey Williamson <
> [log in to unmask]> wrote:
> 
>> Hi code4lib,
>> I was hoping to get some input on this. My small, scrappy institution is
>> considering using drupal as a repository, primarily via the Biblio module.
>> 
>> Obviously this is not ideal, but for reasons I won't get into, our tech
>> environment won't support ePrints or dspace, and hosted services are not an
>> option either. We do not really have the level of technical expertise
>> required to support any fedora-based applications, and cannot hire any
>> additional support. There's a chance existing staff could stretch to get
>> there, but it would not be a pretty process.
>> 
>> With all that said, do any red flags come to mind? I looked through both
>> code4lib and drupal4lib listserv archives and poked around google, but
>> didn't find much evidence of anyone else using drupal in this way. Seems
>> suspicious. While my gut tells me it's a bad idea (metadata! standards!
>> preservation!), I'm having trouble articulating this to my group in a way
>> that sticks, because using Biblio would be easy. I would appreciate hearing
>> any other thoughts or opinions on this.
>> 
>> Thanks!
>> Kelsey
>>