Others have shared some useful experiences, but I think you need to be
clearer about what you're looking for.
(a) is this primarily an internal-facing system or for broadcasting your
content to the world?
(b) are you expecting users to search and find content on the IR, or are
you using a discovery service for that kind of thing?
(c) is content going to be deposited manually into the IR or fed from some
(d) are you looking to do everything yourself on site? everything yourself
in the cloud? cloud hosted externally managed? or locally installed
(e) what kind of authentication system are you looking to connect to, if
any? (LDAP, Shibboleth federation, SAML, etc)
(f) what mix of content do you have? PDFs and word docs? Large scientific
datasets? 4K video streams? ...
(g) does 'publish to the web and push to archive.org' meet your archiving
needs or do you have more stringent requirements?
(h) do you need authority control?
...let us be heard from red core to black sky
On Tue, Mar 22, 2016 at 2:41 AM, Knight, Kathryn E. <[log in to unmask]>
> Hello all,
> My institution is working on a massive overhaul of our current
> institutional repository. At this point we're still deciding what to choose
> (DSpace, Invenio, etc.). Since I don't have much experience with IRs and so
> far all I can do in meetings is wave my arms and crow about metadata a
> bunch, I thought I'd appeal to the collective Code4Lib brain for some
> repository input. If you have an IR at your institution, what do you like
> about it? Hate? What about the end users? What is your submission process
> like? Anything you wish it could do that it doesn't? Etc.
> Please feel free to contact me off list with your thoughts, if you care to
> share-I'll keep all information confidential.
> Thanks so much,
> Kathryn Knight
> Metadata and Cataloging Librarian
> Oak Ridge National Laboratory Research Library