Stripping down Zenodo to build an Invenio repository – lessons learned

To build a university-wide research data repository, we evaluated different repository platforms and finally decided to go for an Invenio based repository – mainly for the user experience that is offered by zenodo.org. To implement a repository that offers a similar functionality and user experience like zenodo.org, we chose to take zenodo.org's code and tailor it to our needs, removing parts that we would not need or we could not use for different reasons. Since the zenodo source code was never meant to deliver a turnkey repository solution for everyone, but to provide the technical foundation for zenodo.org as a service, parts of the effort turned out to be more difficult than expected. An alternative approach would have been to take a barebones Invenio repository and try to rebuild zenodo.org's functionality on top of that. In our 24x7, we want to share the lessons we learned in the process and discuss which approach seems to be more fruitful