You can build a peachy document repository in Drupal. This will work fine if you have a small collection, say less than 10k items.
The issue is that it won’t scale. As a Drupal fanboy, I would love to see an all Drupal solution work, but, at least at this point, it doesn't.
We work with Islandora, which puts a Drupal front-end on Fedora. OOTB, Islandora is weighted towards the Fedora side, but the community has been working to move the balance to do more in Drupal. This will be easier once Islandora completes its move to Fedora 4.
FWIW, we offer Islandora in a hosted and fully supported service package that we call LibraryDAMS.
> On May 5, 2016, at 2: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.