they would try again in a few weeks. Since the preconditions we were told about for the software and applications on the server were incorrect, and solving the issues we ran into were out of our control, we decided to use a new platform called DSpace in place of Zenodo. In addition to pivoting to DSpace, we also decided to install Zenodo locally and we will work on the local DSpace installation on the side. Appendix 3.3 DSpace Installation Before starting the DSpace installation, we acquired root access to the server to avoid permission errors similar to those which we encountered during the Zenodo installation. The following week during spring break, we spent time doing individual research on DSpace and the various applications that would be needed for the installation. When spring break ended, we began the installation of DSpace, however we ran into an issue with DSpace installation regarding the PostgreSQL that it uses as its database. We had a meeting on March 16 with Professor Yang regarding this issue and came to the conclusion that PostgreSQL was installed by the IT staff at LSU via Docker. As a result, the DSpace installation is having trouble locating PostgreSQL inside its Docker container. After doing some research, we were able to find a solution for this: when performing PostgreSQL commands on the command line, we must include two additional parameters. One of the parameters is the port number that PostgreSQL uses and the second is localhost. After solving this issue, however, we ran into an issue with connecting DSpace to a servlet engine. We attempted to use Jetty as our servlet engine because it was already on the server, but we were having issues getting that to work. After talking to the LSU IT staff, they recommended we download and install Tomcat for the servlet engine. We plan to perform this installation and will verify that Tomcat can work as the DSpace servlet engine. Appendix 3.4 Implementation Timeline Figure 43. Gantt chart representing our current timeline progress. Appendix 3.5 Metadata Specifications Our client also asked us to look ahead in our project and to begin formatting the
they would try again in a few weeks. Since the preconditions we were told about for the software and applications on the server were incorrect, and solving the issues we ran into were out of our control, we decided to use a new platform called DSpace in place of Zenodo. In addition to pivoting to DSpace, we also decided to install Zenodo locally and we will work on the local DSpace installation on the side. Appendix 3.3 DSpace Installation Before starting the DSpace installation, we acquired root access to the server to avoid permission errors similar to those which we encountered during the Zenodo installation. The following week during spring break, we spent time doing individual research on DSpace and the various applications that would be needed for the installation. When spring break ended, we began the installation of DSpace, however we ran into an issue with DSpace installation regarding the PostgreSQL that it uses as its database. We had a meeting on March 16 with Professor Yang regarding this issue and came to the conclusion that PostgreSQL was installed by the IT staff at LSU via Docker. As a result, the DSpace installation is having trouble locating PostgreSQL inside its Docker container. After doing some research, we were able to find a solution for this: when performing PostgreSQL commands on the command line, we must include two additional parameters. One of the parameters is the port number that PostgreSQL uses and the second is localhost. After solving this issue, however, we ran into an issue with connecting DSpace to a servlet engine. We attempted to use Jetty as our servlet engine because it was already on the server, but we were having issues getting that to work. After talking to the LSU IT staff, they recommended we download and install Tomcat for the servlet engine. We plan to perform this installation and will verify that Tomcat can work as the DSpace servlet engine. Appendix 3.4 Implementation Timeline Figure 43. Gantt chart representing our current timeline progress. Appendix 3.5 Metadata Specifications Our client also asked us to look ahead in our project and to begin formatting the