diff --git a/.github/workflows/maven_unit_test.yml b/.github/workflows/maven_unit_test.yml
index 904e0e6c0a2..e2048f73431 100644
--- a/.github/workflows/maven_unit_test.yml
+++ b/.github/workflows/maven_unit_test.yml
@@ -4,9 +4,13 @@ on:
     push:
         paths:
             - "**.java"
+            - "pom.xml"
+            - "modules/**/pom.xml"
     pull_request:
         paths:
             - "**.java"
+            - "pom.xml"
+            - "modules/**/pom.xml"
 
 jobs:
     unittest:
diff --git a/doc/sphinx-guides/source/developers/dependencies.rst b/doc/sphinx-guides/source/developers/dependencies.rst
index 564d47c5972..65edfa3ffac 100644
--- a/doc/sphinx-guides/source/developers/dependencies.rst
+++ b/doc/sphinx-guides/source/developers/dependencies.rst
@@ -3,16 +3,24 @@ Dependency Management
 =====================
 
 .. contents:: |toctitle|
-	:local:
+    :local:
 
-The Dataverse Software is (currently) a Jakarta EE 8 based application, that uses a lot of additional libraries for special purposes.
-This includes features like support for SWORD-API, S3 storage and many others.
+Introduction
+------------
+
+As explained under :ref:`core-technologies`, the Dataverse Software is a Jakarta EE 8 based application that uses a lot of additional libraries for
+special purposes. This includes support for the SWORD API, S3 storage, and many other features.
+
+Besides the code that glues together individual pieces, any developer needs to describe dependencies used within the
+Maven-based build system. As is familiar to any Maven user, this happens inside the "Project Object Model" (POM) file, ``pom.xml``.
+
+Recursive and convergent dependency resolution makes dependency management with Maven quite easy, but sometimes, in
+projects with many complex dependencies like the Dataverse Software, you have to help Maven make the right choices.
+
+Maven can foster good development practices by enabling modulithic (modular monolithic) architecture: splitting
+functionalities into different Maven submodules while expressing dependencies between them. But there's more: the
+parent-child model allows you to create consistent dependency versioning (see below) within children.
 
-Besides the code that glues together the single pieces, any developer needs to describe used dependencies for the
-Maven-based build system. As is familiar to any Maven user, this happens inside the "Project Object Model" (POM) living in
-``pom.xml`` at the root of the project repository. Recursive and convergent dependency resolution makes dependency
-management with Maven very easy. But sometimes, in projects with many complex dependencies like the Dataverse Software, you have
-to help Maven make the right choices.
 
 Terms
 -----
@@ -23,7 +31,7 @@ As a developer, you should familiarize yourself with the following terms:
 - **Transitive dependencies**: things *others use* for things you use, pulled in recursively.
   See also: `Maven docs <https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Transitive_Dependencies>`_.
 
-.. graphviz::
+  .. graphviz::
 
     digraph {
         rankdir="LR";
@@ -44,6 +52,94 @@ As a developer, you should familiarize yourself with the following terms:
         yc -> dtz;
     }
 
+- **Project Object Model** (POM): the basic XML file unit to describe a Maven-based project.
+- **Bill Of Materials** (BOM): larger projects like Payara, Amazon SDK etc. provide lists of their direct dependencies.
+  This comes in handy when adding these dependencies (transitive for us) as direct dependencies, see below.
+
+  .. graphviz::
+
+    digraph {
+        rankdir="TD";
+        node [fontsize=10]
+        edge [fontsize=8]
+
+        msp [label="Maven Super POM"]
+        sp  [label="Your POM"]
+        bom [label="Some BOM"]
+        td  [label="Direct & Transitive\nDependency"]
+
+        msp -> sp [label="inherit", dir="back"];
+        bom -> sp [label="import", dir="back"];
+        bom -> td [label="depend on"];
+        sp -> td [label="depend on\n(same version)", constraint=false];
+    }
+
+- **Parent POM**, **Super POM**: any project may be a child of a parent.
+
+  Project silently inherit from a "super POM", which is the global Maven standard parent POM.
+  Children may also be aggregated by a parent (without them knowing) for convenient builds of larger projects.
+
+  .. graphviz::
+
+    digraph {
+        rankdir="TD";
+        node [fontsize=10]
+        edge [fontsize=8]
+
+        msp [label="Maven Super POM"]
+        ap  [label="Any POM"]
+        msp -> ap [label="inherit", dir="back"];
+
+        pp [label="Parent 1 POM"]
+        cp1 [label="Submodule 1 POM"]
+        cp2 [label="Submodule 2 POM"]
+
+        msp -> pp [label="inherit", dir="back", constraint=false];
+        pp -> cp1 [label="aggregate"];
+        pp -> cp2 [label="aggregate"];
+    }
+
+  Children may inherit dependencies, properties, settings, plugins etc. from the parent (making it possible to share
+  common ground). Both approaches may be combined. Children may import as many BOMs as they want, but can have only a
+  single parent to inherit from at a time.
+
+  .. graphviz::
+
+    digraph {
+        rankdir="TD";
+        node [fontsize=10]
+        edge [fontsize=8]
+
+        msp [label="Maven Super POM"]
+        pp  [label="Parent POM"]
+        cp1 [label="Submodule 1 POM"]
+        cp2 [label="Submodule 2 POM"]
+
+        msp -> pp [label="inherit", dir="back", constraint=false];
+        pp -> cp1 [label="aggregate"];
+        pp -> cp2 [label="aggregate"];
+        cp1 -> pp [label="inherit"];
+        cp2 -> pp [label="inherit"];
+
+        d [label="Dependency"]
+        pp -> d [label="depends on"]
+        cp1 -> d [label="inherit:\ndepends on", style=dashed];
+        cp2 -> d [label="inherit:\ndepends on", style=dashed];
+    }
+
+- **Modules**: when using parents and children, these are called "modules" officially, each having their own POM.
+
+  Using modules allows bundling different aspects of (Dataverse) software in their own domains, with their own
+  behavior, dependencies etc. Parent modules allow for sharing of common settings, properties, dependencies and more.
+  Submodules may also be used as parent modules for a lower level of submodules.
+
+  Maven modules within the same software project may also depend on each other, allowing to create complex structures
+  of packages and projects. Each module may be released on their own (e. g. on Maven Central) and other projects may
+  rely on and reuse them. This is especially useful for parent POMs: they may be reused as BOMs or to share a standard
+  between independent software projects.
+
+  Maven modules should not be confused with the `Java Platform Module System (JPMS) <https://en.wikipedia.org/wiki/Java_Platform_Module_System>`_ introduced in Java 9 under Project Jigsaw.
+
 Direct dependencies
 -------------------
 
@@ -62,24 +158,34 @@ Within the POM, any direct dependencies reside within the ``<dependencies>`` tag
 
 
 Anytime you add a ``<dependency>``, Maven will try to fetch it from defined/configured repositories and use it
-within the build lifecycle. You have to define a ``<version>``, but ``<scope>`` is optional for ``compile``.
-(See `Maven docs: Dep. Scope <https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope>`_)
+within the build lifecycle. You have to define a ``<version>`` (note exception below), but ``<scope>`` is optional for
+``compile``. (See `Maven docs: Dep. Scope <https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope>`_)
 
-
-During fetching, Maven will analyse all transitive dependencies (see graph above) and, if necessary, fetch those, too.
+During fetching, Maven will analyze all transitive dependencies (see graph above) and, if necessary, fetch those too.
 Everything downloaded once is cached locally by default, so nothing needs to be fetched again and again, as long as the
 dependency definition does not change.
 
 **Rules to follow:**
 
 1. You should only use direct dependencies for **things you are actually using** in your code.
-2. **Clean up** direct dependencies no longer in use. It will bloat the deployment package otherwise!
-3. Care about the **scope**. Do not include "testing only" dependencies in the package - it will hurt you in IDEs and bloat things. [#f1]_
-4. Avoid using different dependencies for the **same purpose**, e. g. different JSON parsing libraries.
-5. Refactor your code to **use Jakarta EE** standards as much as possible.
-6. When you rely on big SDKs or similar big cool stuff, try to **include the smallest portion possible**. Complete SDK
+2. When declaring a direct dependency with its **version** managed by ``<dependencyManagement>``, a BOM or parent POM, you
+   may not provide one unless you want to explicitly override!
+3. **Clean up** direct dependencies no longer in use. It will bloat the deployment package otherwise!
+4. Care about the **scope** [#f1]_:
+
+   * Do not include "testing only" dependencies in the final package - it will hurt you in IDEs and bloat things.
+     There is scope ``test`` for this!
+   * Make sure to use the ``runtime`` scope when you need to ensure a library is present on our classpath at runtime.
+     An example is the SLF4J JUL bridge: we want to route logs from SLF4J into ``java.util.logging``, so it needs to be
+     present on the classpath, although we aren't using SLF4J unlike, some of our dependencies.
+   * Some dependencies might be ``provided`` by the runtime environment. Good example: everything from Jakarta EE!
+     We use the Payara BOM to ensure using the same version during development and runtime.
+
+5. Avoid using different dependencies for the **same purpose**, e. g. different JSON parsing libraries.
+6. Refactor your code to **use Jakarta EE** standards as much as possible.
+7. When you rely on big SDKs or similar big cool stuff, try to **include the smallest portion possible**. Complete SDK
    bundles are typically heavyweight and most of the time unnecessary.
-7. **Don't include transitive dependencies.** [#f2]_
+8. **Don't include transitive dependencies.** [#f2]_
 
    * Exception: if you are relying on it in your code (see *Z* in the graph above), you must declare it. See below
      for proper handling in these (rare) cases.
@@ -92,8 +198,8 @@ Maven is comfortable for developers; it handles recursive resolution, downloadin
 However, as life is a box of chocolates, you might find yourself in *version conflict hell* sooner than later without even
 knowing, but experiencing unintended side effects.
 
-When you look at the graph above, imagine *B* and *TB* rely on different *versions* of *TC*. How does Maven decide
-which version it will include? Easy: the dependent version of the nearest version wins:
+When you look at the topmost graph above, imagine *B* and *TB* rely on different *versions* of *TC*. How does Maven
+decide which version it will include? Easy: the version of the dependency nearest to our project ("Your Code)" wins. The following graph gives an example:
 
 .. graphviz::
 
@@ -110,19 +216,19 @@ which version it will include? Easy: the dependent version of the nearest versio
         yc -> dtz2;
     }
 
-In this case, version "2.0" will be included. If you know something about semantic versioning, a red alert should ring in your mind right now.
-How do we know that *B* is compatible with *Z v2.0* when depending on *Z v1.0*?
+In this case, version "2.0" will be included. If you know something about semantic versioning, a red alert should ring
+in your mind right now. How do we know that *B* is compatible with *Z v2.0* when depending on *Z v1.0*?
 
 Another scenario getting us in trouble: indirect use of transitive dependencies. Imagine the following: we rely on *Z*
-in our code, but do not include a direct dependency for it within the POM. Now *B* is updated and removed its dependency
-on *Z*. You definitely don't want to head down that road.
+in our code, but do not include a direct dependency for it within the POM. Now assume *B* is updated and removed its 
+dependency on *Z*. You definitely don't want to head down that road.
 
 **Follow the rules to be safe:**
 
-1. Do **not use transitive deps implicit**: add a direct dependency for transitive deps you re-use in your code.
-2. On every build check that no implicit usage was added by accident.
+1. Do **not use transitive deps implicitly**: add a direct dependency for transitive deps you re-use in your code.
+2. On every build, check that no implicit usage was added by accident.
 3. **Explicitly declare versions** of transitive dependencies in use by multiple direct dependencies.
-4. On every build check that there are no convergence problems hiding in the shadows.
+4. On every build, check that there are no convergence problems hiding in the shadows.
 5. **Do special tests** on every build to verify these explicit combinations work.
 
 Managing transitive dependencies in ``pom.xml``
@@ -130,15 +236,24 @@ Managing transitive dependencies in ``pom.xml``
 
 Maven can manage versions of transitive dependencies in four ways:
 
-1. Make a transitive-only dependency not used in your code a direct one and add a ``<version>`` tag.
-   Typically a bad idea, don't do that.
-2. Use ``<optional>`` or ``<exclusion>`` tags on direct dependencies that request the transitive dependency.
-   *Last resort*, you really should avoid this. Not explained or used here.
-   `See Maven docs <https://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html>`_.
-3. Explicitly declare the transitive dependency in ``<dependencyManagement>`` and add a ``<version>`` tag.
-4. For more complex transitive dependencies, reuse a "Bill of Materials" (BOM) within ``<dependencyManagement>``
-   and add a ``<version>`` tag. Many bigger and standard use projects provide those, making the POM much less bloated
-   compared to adding every bit yourself.
+.. list-table::
+    :align: left
+    :stub-columns: 1
+    :widths: 12 40 40
+
+    * - Safe Good Practice
+      - (1) Explicitly declare the transitive dependency in ``<dependencyManagement>`` with a ``<version>`` tag.
+      - (2) For more complex transitive dependencies, reuse a "Bill of Materials" (BOM) within ``<dependencyManagement>``.
+            Many bigger projects provide them, making the POM much less bloated compared to adding every bit yourself.
+    * - Better Avoid or Don't
+      - (3) Use ``<optional>`` or ``<exclusion>`` tags on direct dependencies that request the transitive dependency.
+            *Last resort*, you really should avoid this. Not explained or used here, but sometimes unavoidable.
+            `See Maven docs <https://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html>`_.
+      - (4) Make a transitive-only dependency not used in your code a direct one and add a ``<version>`` tag.
+            Typically a bad idea; don't do that.
+
+**Note:** when the same transitive dependency is used in multiple Maven modules of a software project, it might be added
+to a common ``<dependencyManagement>`` section of an inherited parent POM instead. (Overrides are still possible.)
 
 A reduced example, only showing bits relevant to the above cases and usage of an explicit transitive dep directly:
 
@@ -214,12 +329,12 @@ Helpful tools
 
 Maven provides some plugins that are of great help to detect possible conflicts and implicit usage.
 
-For *implicit usage detection*, use `mvn dependency:analyze`. Examine the output with great care. Sometimes you will
+For *implicit usage detection*, use ``mvn dependency:analyze``. Examine the output with great care. Sometimes you will
 see implicit usages that do no harm, especially if you are using bigger SDKs having some kind of `core` package.
 This will also report on any direct dependency which is not in use and can be removed from the POM. Again, do this with
 great caution and double check.
 
-If you want to see the dependencies both direct and transitive in a *dependency tree format*, use `mvn dependency:tree`.
+If you want to see the dependencies both direct and transitive in a *dependency tree format*, use ``mvn dependency:tree``.
 
 This will however not help you with detecting possible version conflicts. For this you need to use the `Enforcer Plugin
 <https://maven.apache.org/enforcer/maven-enforcer-plugin/index.html>`_ with its built in `dependency convergence rule
@@ -228,7 +343,7 @@ This will however not help you with detecting possible version conflicts. For th
 Repositories
 ------------
 
-Maven receives all dependencies from *repositories*. Those can be public like `Maven Central <https://search.maven.org/>`_
+Maven receives all dependencies from *repositories*. These can be public like `Maven Central <https://search.maven.org/>`_
 and others, but you can also use a private repository on premises or in the cloud. Last but not least, you can use
 local repositories, which can live next to your application code (see ``local_lib`` dir within the Dataverse Software codebase).
 
@@ -262,6 +377,73 @@ Typically you will skip the addition of the central repository, but adding it to
 dependencies are first looked up there (which in theory can speed up downloads). You should keep in mind that repositories
 are used in the order they appear.
 
+
+Dataverse Parent POM
+--------------------
+
+Within ``modules/dataverse-parent`` you will find the parent POM for the Dataverse codebase. It serves different
+purposes:
+
+1. Provide the common version number for a Dataverse release (may be overriden where necessary).
+2. Provide common metadata necessary for releasing modules to repositories like Maven Central.
+3. Declare aggregated submodules via ``<modules>``.
+4. Collate common BOMs and transitive dependencies within ``<dependencyManagement>``.
+   (Remember: a direct dependency declaration may omit the version element when defined in that area!)
+5. Collect common ``<properties>`` regarding the Maven project (encoding, ...), dependency versions, target Java version, etc.
+6. Gather common ``<repositories>`` and ``<pluginRepositories>`` - no need to repeat those in submodules.
+7. Make submodules use current Maven plugin release versions via ``<pluginManagement>``.
+
+As of this writing (2022-02-10), our parent module looks like this:
+
+.. graphviz::
+
+  digraph {
+    rankdir="TD";
+    node [fontsize=10]
+    edge [fontsize=8]
+
+    dvp [label="Dataverse Parent"]
+    dvw [label="Submodule:\nDataverse WAR"]
+    zip [label="Submodule:\nZipdownloader JAR"]
+
+    dvw -> dvp [label="inherit"];
+    dvp -> dvw [label="aggregate"];
+    zip -> dvp [label="inherit"];
+    dvp -> zip [label="aggregate"];
+
+    pay [label="Payara BOM"]
+    aws [label="AWS SDK BOM"]
+    ggl [label="Googe Cloud BOM"]
+    tc  [label="Testcontainers BOM"]
+    td  [label="Multiple (transitive) dependencies\n(PSQL, Logging, Apache Commons, ...)"]
+
+    dvp -> td [label="manage"];
+
+    pay -> dvp [label="import", dir="back"];
+    aws -> dvp [label="import", dir="back"];
+    ggl -> dvp [label="import", dir="back"];
+    tc -> dvp  [label="import", dir="back"];
+
+  }
+
+The codebase is structured like this:
+
+.. code-block::
+
+    <project root>              # Dataverse WAR Module
+    ├── pom.xml                 # (POM file of WAR module)
+    ├── modules                 #
+    │   └── dataverse-parent    # Dataverse Parent Module
+    │       └── pom.xml         # (POM file of Parent Module)
+    └── scripts                 #
+        └── zipdownload         # Zipdownloader JAR Module
+            └── pom.xml         # (POM file of Zipdownloader Module)
+
+- Any developer cloning the project and running ``mvn`` within the project root will interact with the Dataverse WAR
+  module, which is the same behavior since Dataverse 4.0 has been released.
+- Running ``mvn`` targets within the parent module will execute all aggregated submodules in one go.
+
+
 ----
 
 .. rubric:: Footnotes
diff --git a/doc/sphinx-guides/source/developers/intro.rst b/doc/sphinx-guides/source/developers/intro.rst
index 8fc0c679a8b..c8da72da8b5 100755
--- a/doc/sphinx-guides/source/developers/intro.rst
+++ b/doc/sphinx-guides/source/developers/intro.rst
@@ -21,6 +21,8 @@ Getting Help
 
 If you have any questions at all, please reach out to other developers via the channels listed in https://github.com/IQSS/dataverse/blob/develop/CONTRIBUTING.md such as http://chat.dataverse.org, the `dataverse-dev <https://groups.google.com/forum/#!forum/dataverse-dev>`_ mailing list, `community calls <https://dataverse.org/community-calls>`_, or support@dataverse.org.
 
+.. _core-technologies:
+
 Core Technologies
 -----------------
 
diff --git a/doc/sphinx-guides/source/developers/making-releases.rst b/doc/sphinx-guides/source/developers/making-releases.rst
index cbd88b1a357..064ed6f1b78 100755
--- a/doc/sphinx-guides/source/developers/making-releases.rst
+++ b/doc/sphinx-guides/source/developers/making-releases.rst
@@ -22,7 +22,7 @@ Make the following changes in the release branch:
 
 Increment the version number to the milestone (e.g. 4.6.2) in the following two files:
 
-- pom.xml
+- modules/dataverse-parent/pom.xml -> ``<properties>`` -> ``<revision>``
 - doc/sphinx-guides/source/conf.py (two places)
 
 Add the version being released to the lists in the following two files:
@@ -31,6 +31,7 @@ Add the version being released to the lists in the following two files:
 - scripts/database/releases.txt
 
 Here's an example commit where three of the four files above were updated at once: https://github.com/IQSS/dataverse/commit/99e23f96ec362ac2f524cb5cd80ca375fa13f196
+(Note: the version has been moved to a property in parent module since this commit was created.)
 
 2. Check in the Changes Above...
 ================================
diff --git a/doc/sphinx-guides/source/installation/advanced.rst b/doc/sphinx-guides/source/installation/advanced.rst
index 2bb592dc837..4f06ed37d01 100644
--- a/doc/sphinx-guides/source/installation/advanced.rst
+++ b/doc/sphinx-guides/source/installation/advanced.rst
@@ -72,43 +72,44 @@ Once a standardized version of you Custom Terms are registered as a license, an
 Optional Components
 -------------------
 
+.. _zipdownloader:
+
 Standalone "Zipper" Service Tool
 ++++++++++++++++++++++++++++++++
 
-As of Dataverse Software 5.0 we offer an experimental optimization for the multi-file, download-as-zip functionality. If this option
-(``:CustomZipDownloadServiceUrl``) is enabled, instead of enforcing
-the size limit on multi-file zipped downloads (as normally specified
-by the option ``:ZipDownloadLimit``), we attempt to serve all the
-files that the user requested (that they are authorized to download),
-but the request is redirected to a standalone zipper service running
-as a cgi-bin executable under Apache. Thus moving these potentially
-long-running jobs completely outside the Application Server (Payara);
-and preventing worker threads from becoming locked serving them. Since
-zipping is also a CPU-intensive task, it is possible to have this
-service running on a different host system, freeing the cycles on the
-main Application Server. (The system running the service needs to have
-access to the database as well as to the storage filesystem, and/or S3
-bucket).
-
-Please consult the scripts/zipdownload/README.md in the Dataverse Software 5.0+ source tree for more information. 
-
-To install: You can follow the instructions in the file above to build
-``ZipDownloadService-v1.0.0.jar``. It will also be available, pre-built as part of the Dataverse Software 5.0 release on GitHub. Copy it, together with the shell
-script scripts/zipdownload/cgi-bin/zipdownload to the cgi-bin
-directory of the chosen Apache server (/var/www/cgi-bin standard). 
-
-Make sure the shell script (zipdownload) is executable, and edit it to configure the
-database access credentials. Do note that the executable does not need
-access to the entire Dataverse installation database. A security-conscious admin
-can create a dedicated database user with access to just one table:
-``CUSTOMZIPSERVICEREQUEST``.
-
-You may need to make extra Apache configuration changes to make sure /cgi-bin/zipdownload is accessible from the outside.
-For example, if this is the same Apache that's in front of your Dataverse installation Payara instance, you will need to add another pass through statement to your configuration:
+As of Dataverse Software 5.0 we offer an **experimental** optimization for the multi-file, download-as-zip functionality.
+If this option (``:CustomZipDownloadServiceUrl``) is enabled, instead of enforcing the size limit on multi-file zipped
+downloads (as normally specified by the option ``:ZipDownloadLimit``), we attempt to serve all the files that the user
+requested (that they are authorized to download), but the request is redirected to a standalone zipper service running
+as a cgi-bin executable under Apache. This moves these potentially long-running jobs completely outside the Application Server (Payara), and prevents worker threads from becoming locked serving them. Since zipping is also a CPU-intensive task, it is possible to have
+this service running on a different host system, freeing the cycles on the main Application Server. (The system running
+the service needs to have access to the database as well as to the storage filesystem, and/or S3 bucket).
+
+Please consult the `README at scripts/zipdownload <https://github.com/IQSS/dataverse/tree/master/scripts/zipdownload>`_
+in the Dataverse Software 5.0+ source tree for more information.
+
+To install:
+
+1. Follow the instructions in the file above to build ``zipdownloader-0.0.1.jar``. Please note that the package name and
+   the version were changed as of the release 5.10, as part of an overall cleanup and reorganization of the project 
+   tree. In the releases 5.0-5.9 it existed under the name ``ZipDownloadService-v1.0.0``. (A pre-built jar file was
+   distributed under that name as part of the 5.0 release on GitHub. Aside from the name change, there have been no 
+   changes in the functionality of the tool). 
+2. Copy it, together with the shell script :download:`cgi-bin/zipdownload <../../../../scripts/zipdownload/cgi-bin/zipdownload>`
+   to the ``cgi-bin`` directory of the chosen Apache server (``/var/www/cgi-bin`` standard).
+3. Make sure the shell script (``zipdownload``) is executable, and edit it to configure the database access credentials.
+   Do note that the executable does not need access to the entire Dataverse installation database. A security-conscious
+   admin can create a dedicated database user with access to just one table: ``CUSTOMZIPSERVICEREQUEST``.
+
+You may need to make extra Apache configuration changes to make sure ``/cgi-bin/zipdownload`` is accessible from the outside.
+For example, if this is the same Apache that's in front of your Dataverse installation Payara instance, you will need to
+add another pass through statement to your configuration:
 
 ``ProxyPassMatch ^/cgi-bin/zipdownload !``
 
-Test this by accessing it directly at ``<SERVER URL>/cgi-bin/download``. You should get a ``404 No such download job!``. If instead you are getting an "internal server error", this may be an SELinux issue; try ``setenforce Permissive``. If you are getting a generic Dataverse collection "not found" page, review the ``ProxyPassMatch`` rule you have added. 
+Test this by accessing it directly at ``<SERVER URL>/cgi-bin/download``. You should get a ``404 No such download job!``.
+If instead you are getting an "internal server error", this may be an SELinux issue; try ``setenforce Permissive``.
+If you are getting a generic Dataverse collection "not found" page, review the ``ProxyPassMatch`` rule you have added.
 
 To activate in your Dataverse installation::
 
diff --git a/doc/sphinx-guides/source/installation/config.rst b/doc/sphinx-guides/source/installation/config.rst
index 9b5c3a3eb68..008661fe262 100644
--- a/doc/sphinx-guides/source/installation/config.rst
+++ b/doc/sphinx-guides/source/installation/config.rst
@@ -2380,7 +2380,10 @@ If you don’t want date facets to be sorted chronologically, set:
 :CustomZipDownloadServiceUrl
 ++++++++++++++++++++++++++++
 
-The location of the "Standalone Zipper" service. If this option is specified, the Dataverse installation will be redirecing bulk/mutli-file zip download requests to that location, instead of serving them internally. See the "Advanced" section of the Installation guide for information on how to install the external zipper. (This is still an experimental feature, as of Dataverse Software 5.0).
+The location of the "Standalone Zipper" service. If this option is specified, the Dataverse installation will be
+redirecing bulk/multi-file zip download requests to that location, instead of serving them internally.
+See :ref:`zipdownloader` of the Advanced Installation guide for information on how to install the external zipper.
+(This is still an **experimental** feature, as of Dataverse Software 5.0).
 
 To enable redirects to the zipper installed on the same server as the main Dataverse Software application: 
 
@@ -2388,7 +2391,7 @@ To enable redirects to the zipper installed on the same server as the main Datav
 
 To enable redirects to the zipper on a different server: 
 
-``curl -X PUT -d 'https://zipper.example.edu/cgi-bin/zipdownload' http://localhost:8080/api/admin/settings/:CustomZipDownloadServiceUrl`` 
+``curl -X PUT -d 'https://zipper.example.edu/cgi-bin/zipdownload' http://localhost:8080/api/admin/settings/:CustomZipDownloadServiceUrl``
 
 :ArchiverClassName
 ++++++++++++++++++
diff --git a/modules/dataverse-parent/pom.xml b/modules/dataverse-parent/pom.xml
new file mode 100644
index 00000000000..f20dd34f5f6
--- /dev/null
+++ b/modules/dataverse-parent/pom.xml
@@ -0,0 +1,318 @@
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd;">
+    <modelVersion>4.0.0</modelVersion>
+ 
+    <groupId>edu.harvard.iq</groupId>
+    <artifactId>dataverse-parent</artifactId>
+    <version>${revision}</version>
+    <packaging>pom</packaging>
+ 
+    <name>dataverse-parent</name>
+    <url>https://dataverse.org</url>
+    
+    <modules>
+        <module>../../pom.xml</module>
+        <module>../../scripts/zipdownload</module>
+    </modules>
+    
+    <!-- Transitive dependencies, bigger library "bill of materials" (BOM) and
+         versions of dependencies used both directly and transitive are managed here. -->
+    <dependencyManagement>
+        <dependencies>
+            
+            <!-- MAJOR SYSTEM COMPONENTS, BOMs -->
+            
+            <dependency>
+                <groupId>fish.payara.api</groupId>
+                <artifactId>payara-bom</artifactId>
+                <version>${payara.version}</version>
+                <type>pom</type>
+                <scope>import</scope>
+            </dependency>
+            <dependency>
+                <groupId>com.amazonaws</groupId>
+                <artifactId>aws-java-sdk-bom</artifactId>
+                <version>${aws.version}</version>
+                <type>pom</type>
+                <scope>import</scope>
+            </dependency>
+            <dependency>
+                <groupId>com.google.cloud</groupId>
+                <artifactId>google-cloud-bom</artifactId>
+                <version>${google.cloud.version}</version>
+                <type>pom</type>
+                <scope>import</scope>
+            </dependency>
+            
+            <!-- BASIC LIBRARIES / LOGGING / ... -->
+    
+            <dependency>
+                <groupId>org.postgresql</groupId>
+                <artifactId>postgresql</artifactId>
+                <version>${postgresql.version}</version>
+            </dependency>
+            <dependency>
+                <groupId>commons-logging</groupId>
+                <artifactId>commons-logging</artifactId>
+                <version>${commons.logging.version}</version>
+            </dependency>
+            <dependency>
+                <groupId>org.apache.commons</groupId>
+                <artifactId>commons-lang3</artifactId>
+                <version>${commons.lang3.version}</version>
+            </dependency>
+            <!-- Dependency of SolrJ, DuraCloud & used by ourselves -->
+            <dependency>
+                <groupId>org.apache.httpcomponents</groupId>
+                <artifactId>httpclient</artifactId>
+                <version>${apache.httpcomponents.client.version}</version>
+            </dependency>
+            <!-- Dependency of SolrJ, Tika, RestAssured, DuraCloud - added here for convergence reasons -->
+            <dependency>
+                <groupId>org.apache.httpcomponents</groupId>
+                <artifactId>httpmime</artifactId>
+                <version>${apache.httpcomponents.client.version}</version>
+            </dependency>
+            <!-- Dependency of SolrJ, DuraCloud Store Client & used in our codebase -->
+            <dependency>
+                <groupId>org.apache.httpcomponents</groupId>
+                <artifactId>httpcore</artifactId>
+                <version>${apache.httpcomponents.core.version}</version>
+            </dependency>
+            
+            <!-- Dependency of Tika, Sword2-server, JOSS (Swift), DuraCloud, Lyncode XOAI -->
+            <dependency>
+                <groupId>commons-io</groupId>
+                <artifactId>commons-io</artifactId>
+                <version>${commons.io.version}</version>
+            </dependency>
+            <!-- Dependency of Sword2-server, Apache POI and in our own codebase -->
+            <dependency>
+                <groupId>org.apache.commons</groupId>
+                <artifactId>commons-compress</artifactId>
+                <version>${commons.compress.version}</version>
+            </dependency>
+            
+            <!-- Dependency of A LOT of libraries. Ensuring convergence here. -->
+            <dependency>
+                <groupId>org.slf4j</groupId>
+                <artifactId>slf4j-api</artifactId>
+                <version>${slf4j.version}</version>
+            </dependency>
+            <dependency>
+                <groupId>org.slf4j</groupId>
+                <artifactId>slf4j-jdk14</artifactId>
+                <version>${slf4j.version}</version>
+            </dependency>
+            <dependency>
+                <groupId>org.slf4j</groupId>
+                <artifactId>jcl-over-slf4j</artifactId>
+                <version>${slf4j.version}</version>
+            </dependency>
+            <dependency>
+                <groupId>org.slf4j</groupId>
+                <artifactId>jul-to-slf4j</artifactId>
+                <version>${slf4j.version}</version>
+            </dependency>
+            
+            <!-- TESTING DEPENDENCIES -->
+            
+            <dependency>
+                <groupId>org.testcontainers</groupId>
+                <artifactId>testcontainers-bom</artifactId>
+                <version>${testcontainers.version}</version>
+                <scope>import</scope>
+                <type>pom</type>
+            </dependency>
+        </dependencies>
+    </dependencyManagement>
+ 
+    <properties>
+        <!-- This is a special Maven property name, do not change! -->
+        <revision>5.9</revision>
+    
+        <target.java.version>11</target.java.version>
+        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
+        <additionalparam>-Xdoclint:none</additionalparam>
+        <!-- Needed to avoid IDEA IDE compilation failures. See commits in GH #5059 -->
+        <compilerArgument></compilerArgument>
+        <project.timezone>UTC</project.timezone>
+        <project.language>en</project.language>
+        <project.region>US</project.region>
+        <!--
+            Moving this from plugin config to global config, because of GH-5122.
+            This seems to play well with NetBeans 8.2, IDEA 2018.1 and mvn including compatibility with JaCoCo.
+        -->
+        <argLine>-Duser.timezone=${project.timezone} -Dfile.encoding=${project.build.sourceEncoding} -Duser.language=${project.language} -Duser.region=${project.region}</argLine>
+    
+        <!-- Major system components and dependencies -->
+        <payara.version>5.2021.5</payara.version>
+        <postgresql.version>42.3.3</postgresql.version>
+        <solr.version>8.8.1</solr.version>
+        <aws.version>1.11.762</aws.version>
+        <google.cloud.version>0.157.0</google.cloud.version>
+    
+        <!-- Basic libs, logging -->
+        <jakartaee-api.version>8.0.0</jakartaee-api.version>
+        <slf4j.version>1.7.35</slf4j.version>
+        <commons.io.version>2.11.0</commons.io.version>
+        <commons.logging.version>1.2</commons.logging.version>
+        <commons.lang3.version>3.12.0</commons.lang3.version>
+        <commons.compress.version>1.21</commons.compress.version>
+        <apache.httpcomponents.client.version>4.5.13</apache.httpcomponents.client.version>
+        <apache.httpcomponents.core.version>4.4.14</apache.httpcomponents.core.version>
+    
+        <!-- Testing dependencies -->
+        <testcontainers.version>1.15.0</testcontainers.version>
+        <microbean-mpconfig.version>0.4.1</microbean-mpconfig.version>
+    
+        <junit.version>4.13.1</junit.version>
+        <junit.jupiter.version>5.7.0</junit.jupiter.version>
+        <junit.vintage.version>${junit.jupiter.version}</junit.vintage.version>
+        <mockito.version>2.28.2</mockito.version>
+        
+        <checkstyle.version>9.3</checkstyle.version>
+        
+        <!-- Official Maven Plugins -->
+        <maven-compiler-plugin.version>3.8.1</maven-compiler-plugin.version>
+        <maven-jar-plugin.version>3.2.2</maven-jar-plugin.version>
+        <maven-war-plugin.version>3.3.2</maven-war-plugin.version>
+        <maven-dependency-plugin.version>3.2.0</maven-dependency-plugin.version>
+        <maven-surefire-plugin.version>3.0.0-M5</maven-surefire-plugin.version>
+        <maven-failsafe-plugin.version>3.0.0-M5</maven-failsafe-plugin.version>
+        <maven-assembly-plugin.version>3.3.0</maven-assembly-plugin.version>
+        <maven-checkstyle-plugin.version>3.1.2</maven-checkstyle-plugin.version>
+    </properties>
+    
+    <pluginRepositories>
+        <pluginRepository>
+            <id>central</id>
+            <name>Central Repository</name>
+            <url>https://repo.maven.apache.org/maven2</url>
+            <layout>default</layout>
+            <snapshots>
+                <enabled>false</enabled>
+            </snapshots>
+            <releases>
+                <updatePolicy>never</updatePolicy>
+            </releases>
+        </pluginRepository>
+    </pluginRepositories>
+    
+    <build>
+        <pluginManagement>
+            <plugins>
+                <plugin>
+                    <groupId>org.apache.maven.plugins</groupId>
+                    <artifactId>maven-compiler-plugin</artifactId>
+                    <version>${maven-compiler-plugin.version}</version>
+                </plugin>
+                <plugin>
+                    <groupId>org.apache.maven.plugins</groupId>
+                    <artifactId>maven-jar-plugin</artifactId>
+                    <version>${maven-jar-plugin.version}</version>
+                </plugin>
+                <plugin>
+                    <groupId>org.apache.maven.plugins</groupId>
+                    <artifactId>maven-war-plugin</artifactId>
+                    <version>${maven-war-plugin.version}</version>
+                </plugin>
+                <plugin>
+                    <groupId>org.apache.maven.plugins</groupId>
+                    <artifactId>maven-dependency-plugin</artifactId>
+                    <version>${maven-dependency-plugin.version}</version>
+                </plugin>
+                <plugin>
+                    <groupId>org.apache.maven.plugins</groupId>
+                    <artifactId>maven-surefire-plugin</artifactId>
+                    <version>${maven-surefire-plugin.version}</version>
+                </plugin>
+                <plugin>
+                    <groupId>org.apache.maven.plugins</groupId>
+                    <artifactId>maven-failsafe-plugin</artifactId>
+                    <version>${maven-failsafe-plugin.version}</version>
+                </plugin>
+                <plugin>
+                    <groupId>org.apache.maven.plugins</groupId>
+                    <artifactId>maven-checkstyle-plugin</artifactId>
+                    <version>${maven-checkstyle-plugin.version}</version>
+                    <dependencies>
+                        <dependency>
+                            <groupId>com.puppycrawl.tools</groupId>
+                            <artifactId>checkstyle</artifactId>
+                            <version>${checkstyle.version}</version>
+                        </dependency>
+                    </dependencies>
+                </plugin>
+            </plugins>
+        </pluginManagement>
+    </build>
+    
+    <!--Maven checks for dependencies from these repos in the order shown in the pom.xml
+        This isn't well documented and seems to change between maven versions -MAD 4.9.4 -->
+    <repositories>
+        <repository>
+            <id>payara-nexus-artifacts</id>
+            <name>Payara Nexus Artifacts</name>
+            <url>https://nexus.payara.fish/repository/payara-artifacts</url>
+            <releases>
+                <enabled>true</enabled>
+            </releases>
+            <snapshots>
+                <enabled>false</enabled>
+            </snapshots>
+        </repository>
+        <!-- This repository is about to being phased out. See https://github.com/payara/Payara_PatchedProjects/issues/366 -->
+        <repository>
+            <id>payara-patched-externals</id>
+            <name>Payara Patched Externals</name>
+            <url>https://raw.github.com/payara/Payara_PatchedProjects/master</url>
+            <releases>
+                <enabled>true</enabled>
+            </releases>
+            <snapshots>
+                <enabled>false</enabled>
+            </snapshots>
+        </repository>
+        <repository>
+            <id>central-repo</id>
+            <name>Central Repository</name>
+            <url>https://repo1.maven.org/maven2</url>
+            <layout>default</layout>
+        </repository>
+        <repository>
+            <id>prime-repo</id>
+            <name>PrimeFaces Maven Repository</name>
+            <url>https://repository.primefaces.org</url>
+            <layout>default</layout>
+        </repository>
+        <repository>
+            <id>dataone.org</id>
+            <url>https://maven.dataone.org</url>
+            <releases>
+                <enabled>true</enabled>
+            </releases>
+            <snapshots>
+                <enabled>true</enabled>
+            </snapshots>
+        </repository>
+        <repository>
+            <id>dvn.private</id>
+            <name>Local repository for hosting jars not available from network repositories.</name>
+            <url>file://${project.basedir}/local_lib</url>
+        </repository>
+        <!-- Uncomment when using snapshot releases from Maven Central
+        <repository>
+            <id>oss-sonatype</id>
+            <name>oss-sonatype</name>
+            <url>
+                https://s01.oss.sonatype.org/content/repositories/snapshots/
+            </url>
+            <snapshots>
+                <enabled>true</enabled>
+            </snapshots>
+        </repository>
+        -->
+    </repositories>
+    
+</project>
\ No newline at end of file
diff --git a/pom.xml b/pom.xml
index dc3a0111bf5..7663bb3e6e6 100644
--- a/pom.xml
+++ b/pom.xml
@@ -1,207 +1,36 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="https://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd;">
     <modelVersion>4.0.0</modelVersion>
+    
+    <parent>
+        <groupId>edu.harvard.iq</groupId>
+        <artifactId>dataverse-parent</artifactId>
+        <version>${revision}</version>
+        <relativePath>modules/dataverse-parent</relativePath>
+    </parent>
+    
     <!--
     If you are doing more than bumping the version number, please read
     doc/sphinx-guides/source/developers/dependencies.rst
     -->
-    <groupId>edu.harvard.iq</groupId>
     <artifactId>dataverse</artifactId>
-    <version>5.9</version>
     <packaging>war</packaging>
     <name>dataverse</name>
     <properties>
-        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
-        <additionalparam>-Xdoclint:none</additionalparam>
-        <!-- Needed to avoid IDEA IDE compilation failures. See commits in GH #5059 -->
-        <compilerArgument></compilerArgument>
-        <project.timezone>UTC</project.timezone>
-        <project.language>en</project.language>
-        <project.region>US</project.region>
-        <!--
-            Moving this from plugin config to global config, because of GH-5122.
-            This seems to play well with NetBeans 8.2, IDEA 2018.1 and mvn including compatibility with JaCoCo.
-        -->
-        <argLine>-Duser.timezone=${project.timezone} -Dfile.encoding=${project.build.sourceEncoding} -Duser.language=${project.language} -Duser.region=${project.region}</argLine>
         <skipUnitTests>false</skipUnitTests>
-    
-        <target.java.version>11</target.java.version>
-        <jakartaee-api.version>8.0.0</jakartaee-api.version>
-        <payara.version>5.2021.5</payara.version>
-        <postgresql.version>42.3.3</postgresql.version>
-        <aws.version>1.11.762</aws.version>
-        <slf4j.version>1.7.35</slf4j.version>
         <reload4j.version>1.2.18.4</reload4j.version>
-        <commons.io.version>2.11.0</commons.io.version>
-        <commons.logging.version>1.2</commons.logging.version>
-        <commons.lang3.version>3.12.0</commons.lang3.version>
-        <apache.httpcomponents.client.version>4.5.13</apache.httpcomponents.client.version>
-        <apache.httpcomponents.core.version>4.4.14</apache.httpcomponents.core.version>
-        <google.cloud.version>0.157.0</google.cloud.version>
-        <junit.version>4.13.1</junit.version>
-        <junit.jupiter.version>5.7.0</junit.jupiter.version>
-        <junit.vintage.version>${junit.jupiter.version}</junit.vintage.version>
-        <testcontainers.version>1.15.0</testcontainers.version>
-        <microbean-mpconfig.version>0.4.1</microbean-mpconfig.version>
-        <mockito.version>2.28.2</mockito.version>
         <flyway.version>5.2.4</flyway.version>
         <jhove.version>1.20.1</jhove.version>
         <jacoco.version>0.8.7</jacoco.version>
     </properties>
-    <pluginRepositories>
-        <pluginRepository>
-            <id>central</id>
-            <name>Central Repository</name>
-            <url>https://repo.maven.apache.org/maven2</url>
-            <layout>default</layout>
-            <snapshots>
-                <enabled>false</enabled>
-            </snapshots>
-            <releases>
-                <updatePolicy>never</updatePolicy>
-            </releases>
-        </pluginRepository>
-    </pluginRepositories>
-    <!--Maven checks for dependencies from these repos in the order shown in the pom.xml
-        This isn't well documented and seems to change between maven versions -MAD 4.9.4 -->
-    <repositories>
-        <repository>
-            <id>payara-nexus-artifacts</id>
-            <name>Payara Nexus Artifacts</name>
-            <url>https://nexus.payara.fish/repository/payara-artifacts</url>
-            <releases>
-                <enabled>true</enabled>
-            </releases>
-            <snapshots>
-                <enabled>false</enabled>
-            </snapshots>
-        </repository>
-        <!-- This repository is about to being phased out. See https://github.com/payara/Payara_PatchedProjects/issues/366 -->
-        <repository>
-            <id>payara-patched-externals</id>
-            <name>Payara Patched Externals</name>
-            <url>https://raw.github.com/payara/Payara_PatchedProjects/master</url>
-            <releases>
-                <enabled>true</enabled>
-            </releases>
-            <snapshots>
-                <enabled>false</enabled>
-            </snapshots>
-        </repository>
-        <repository>
-            <id>central-repo</id>
-            <name>Central Repository</name>
-            <url>https://repo1.maven.org/maven2</url>
-            <layout>default</layout>
-        </repository>
-        <repository>
-            <id>prime-repo</id>
-            <name>PrimeFaces Maven Repository</name>
-            <url>https://repository.primefaces.org</url>
-            <layout>default</layout>
-        </repository>
-        <repository>
-            <id>dataone.org</id>
-            <url>https://maven.dataone.org</url>
-            <releases>
-                <enabled>true</enabled>
-            </releases>
-            <snapshots>
-                <enabled>true</enabled>
-            </snapshots>
-        </repository>
-        <repository>
-            <id>dvn.private</id>
-            <name>Local repository for hosting jars not available from network repositories.</name>
-            <url>file://${project.basedir}/local_lib</url>
-        </repository>
-        <!-- Uncomment when using snapshot releases from Maven Central
-        <repository>
-            <id>oss-sonatype</id>
-            <name>oss-sonatype</name>
-            <url>
-                https://s01.oss.sonatype.org/content/repositories/snapshots/
-            </url>
-            <snapshots>
-                <enabled>true</enabled>
-            </snapshots>
-        </repository>
-        -->
-    </repositories>
-    <!-- Transitive dependencies, bigger library "bill of materials" (BOM) and
-         versions of dependencies used both directly and transitive are managed here. -->
+    
+    <!-- Versions of dependencies used both directly and transitive are managed here.
+         REMEMBER: only manage things here that are going to be used ONLY for this module.
+                   Anything else should go into the parent POM!
+    -->
     <dependencyManagement>
         <dependencies>
-            <dependency>
-                <groupId>fish.payara.api</groupId>
-                <artifactId>payara-bom</artifactId>
-                <version>${payara.version}</version>
-                <type>pom</type>
-                <scope>import</scope>
-            </dependency>
-            <dependency>
-                <groupId>com.amazonaws</groupId>
-                <artifactId>aws-java-sdk-bom</artifactId>
-                <version>${aws.version}</version>
-                <type>pom</type>
-                <scope>import</scope>
-            </dependency>
-            <dependency>
-                <groupId>commons-logging</groupId>
-                <artifactId>commons-logging</artifactId>
-                <version>${commons.logging.version}</version>
-            </dependency>
-            <dependency>
-                <groupId>org.apache.commons</groupId>
-                <artifactId>commons-lang3</artifactId>
-                <version>${commons.lang3.version}</version>
-            </dependency>
-            <!-- Dependency of SolrJ, DuraCloud & used by ourselves -->
-            <dependency>
-                <groupId>org.apache.httpcomponents</groupId>
-                <artifactId>httpclient</artifactId>
-                <version>${apache.httpcomponents.client.version}</version>
-            </dependency>
-            <!-- Dependency of SolrJ, Tika, RestAssured, DuraCloud - added here for convergence reasons -->
-            <dependency>
-                <groupId>org.apache.httpcomponents</groupId>
-                <artifactId>httpmime</artifactId>
-                <version>${apache.httpcomponents.client.version}</version>
-            </dependency>
-            <!-- Dependency of SolrJ, DuraCloud Store Client & used in our codebase -->
-            <dependency>
-                <groupId>org.apache.httpcomponents</groupId>
-                <artifactId>httpcore</artifactId>
-                <version>${apache.httpcomponents.core.version}</version>
-            </dependency>
-            <dependency>
-              <groupId>com.google.cloud</groupId>
-              <artifactId>google-cloud-bom</artifactId>
-              <version>${google.cloud.version}</version>
-              <type>pom</type>
-              <scope>import</scope>
-            </dependency>
-            <dependency>
-                <groupId>org.testcontainers</groupId>
-                <artifactId>testcontainers-bom</artifactId>
-                <version>${testcontainers.version}</version>
-                <scope>import</scope>
-                <type>pom</type>
-            </dependency>
-            
-            <!-- Dependency of Tika, Sword2-server, JOSS (Swift), DuraCloud, Lyncode XOAI -->
-            <dependency>
-                <groupId>commons-io</groupId>
-                <artifactId>commons-io</artifactId>
-                <version>${commons.io.version}</version>
-            </dependency>
-            <!-- Dependency of Sword2-server, Apache POI and in our own codebase -->
-            <dependency>
-                <groupId>org.apache.commons</groupId>
-                <artifactId>commons-compress</artifactId>
-                <version>1.21</version>
-            </dependency>
-            
             <!-- Dependency of sword2-server and used in our codebase -->
             <dependency>
                 <groupId>org.apache.abdera</groupId>
@@ -213,29 +42,6 @@
                 <artifactId>abdera-i18n</artifactId>
                 <version>1.1.3</version>
             </dependency>
-    
-            <!-- Dependency of A LOT of libraries. Ensuring convergence here. -->
-            <dependency>
-                <groupId>org.slf4j</groupId>
-                <artifactId>slf4j-api</artifactId>
-                <version>${slf4j.version}</version>
-            </dependency>
-            <dependency>
-                <groupId>org.slf4j</groupId>
-                <artifactId>slf4j-jdk14</artifactId>
-                <version>${slf4j.version}</version>
-            </dependency>
-            <dependency>
-                <groupId>org.slf4j</groupId>
-                <artifactId>jcl-over-slf4j</artifactId>
-                <version>${slf4j.version}</version>
-            </dependency>
-            <dependency>
-                <groupId>org.slf4j</groupId>
-                <artifactId>jul-to-slf4j</artifactId>
-                <version>${slf4j.version}</version>
-            </dependency>
-            
         </dependencies>
     </dependencyManagement>
     <!-- Declare any DIRECT dependencies here.
@@ -251,9 +57,10 @@
         <dependency>
             <groupId>org.slf4j</groupId>
             <artifactId>slf4j-jdk14</artifactId>
+            <scope>runtime</scope>
         </dependency>
         
-	<dependency>
+	    <dependency>
             <groupId>org.passay</groupId>
             <artifactId>passay</artifactId>
             <version>1.6.0</version>
@@ -338,7 +145,6 @@
         <dependency>
             <groupId>org.postgresql</groupId>
             <artifactId>postgresql</artifactId>
-            <version>${postgresql.version}</version>
         </dependency>
         <dependency>
             <groupId>org.flywaydb</groupId>
@@ -407,12 +213,12 @@
         <dependency>
             <groupId>commons-io</groupId>
             <artifactId>commons-io</artifactId>
-            <!-- no version here as managed in <dependencyManagement> above for convergence! -->
+            <!-- no version here as managed in <dependencyManagement> of parent for convergence! -->
         </dependency>
         <dependency>
             <groupId>org.apache.commons</groupId>
             <artifactId>commons-lang3</artifactId>
-            <!-- no version here as managed in <dependencyManagement> above for convergence! -->
+            <!-- no version here as managed in <dependencyManagement> of parent for convergence! -->
         </dependency>
         <!-- Some utils from commons.lang have been moved to commons-text (especially escapeHtml()) -->
         <dependency>
@@ -612,6 +418,7 @@
             <groupId>ch.qos.reload4j</groupId>
             <artifactId>reload4j</artifactId>
             <version>${reload4j.version}</version>
+            <scope>runtime</scope>
         </dependency>
         <!-- Added for AutoService -->
         <dependency>
@@ -693,6 +500,7 @@
         <dependency>
           <groupId>com.google.cloud</groupId>
           <artifactId>google-cloud-storage</artifactId>
+          <!-- no version here as managed in <dependencyManagement> of parent for convergence! -->
         </dependency>
         
         
@@ -828,7 +636,6 @@
             <plugin>
                 <groupId>org.apache.maven.plugins</groupId>
                 <artifactId>maven-compiler-plugin</artifactId>
-                <version>3.8.1</version>
                 <configuration>
                     <release>${target.java.version}</release>
                     <!-- for use with `mvn -DcompilerArgument=-Xlint:unchecked compile` -->
@@ -838,7 +645,6 @@
             <plugin>
                 <groupId>org.apache.maven.plugins</groupId>
                 <artifactId>maven-jar-plugin</artifactId>
-                <version>2.3</version>
                 <configuration>
                     <archive>
                         <manifest>
@@ -851,7 +657,6 @@
             <plugin>
                 <groupId>org.apache.maven.plugins</groupId>
                 <artifactId>maven-war-plugin</artifactId>
-                <version>2.3</version>
                 <configuration>
                     <attachClasses>true</attachClasses>
                     <failOnMissingWebXml>false</failOnMissingWebXml>
@@ -863,11 +668,6 @@
                     </archive>
                 </configuration>
             </plugin>
-            <plugin>
-                <groupId>org.apache.maven.plugins</groupId>
-                <artifactId>maven-dependency-plugin</artifactId>
-                <version>3.2.0</version>
-            </plugin>
             <plugin>
                 <groupId>de.qaware.maven</groupId>
                 <artifactId>go-offline-maven-plugin</artifactId>
@@ -914,10 +714,10 @@
                 </dependencies>
             </plugin>
             <plugin>
-                <!-- https://stackoverflow.com/questions/46177921/how-to-run-unit-tests-in-excludedgroups-in-maven -->
+                <groupId>org.apache.maven.plugins</groupId>
                 <artifactId>maven-surefire-plugin</artifactId>
-                <version>3.0.0-M5</version>
                 <configuration>
+                    <!-- https://stackoverflow.com/questions/46177921/how-to-run-unit-tests-in-excludedgroups-in-maven -->
                     <!-- testsToExclude come from the profile-->
                     <excludedGroups>${testsToExclude}</excludedGroups>
                     <skip>${skipUnitTests}</skip>
@@ -926,19 +726,11 @@
             <plugin>
                 <groupId>org.apache.maven.plugins</groupId>
                 <artifactId>maven-checkstyle-plugin</artifactId>
-                <version>3.1.2</version>
                 <configuration>
                     <configLocation>checkstyle.xml</configLocation>
                     <encoding>UTF-8</encoding>
                     <consoleOutput>true</consoleOutput>
                 </configuration>
-                <dependencies>
-                    <dependency>
-                        <groupId>com.puppycrawl.tools</groupId>
-                        <artifactId>checkstyle</artifactId>
-                        <version>8.42</version>
-                    </dependency>
-                </dependencies>
             </plugin>
         </plugins>
     </build>
@@ -969,7 +761,7 @@
                     <plugin>
                         <groupId>org.apache.maven.plugins</groupId>
                         <artifactId>maven-failsafe-plugin</artifactId>
-                        <version>2.22.2</version>
+                        <version>${maven-failsafe-plugin.version}</version>
                         <configuration>
                             <groups>testcontainers</groups>
                             <systemPropertyVariables>
diff --git a/scripts/zipdownload/cgi-bin/zipdownload b/scripts/zipdownload/cgi-bin/zipdownload
index c2a9db8ca9b..ff9d6a53a24 100644
--- a/scripts/zipdownload/cgi-bin/zipdownload
+++ b/scripts/zipdownload/cgi-bin/zipdownload
@@ -8,4 +8,4 @@ PGUSER="dvnapp";    export PGUSER
 PGDB="dvndb"; 	    export PGDB
 PGPW="xxxxx"; 	    export PGPW
 
-java -Ddb.serverName=$PGHOST -Ddb.portNumber=$PGPORT -Ddb.user=$PGUSER -Ddb.databaseName=$PGDB -Ddb.password=$PGPW -jar ZipDownloadService-v1.0.0.jar
\ No newline at end of file
+java -Ddb.serverName=$PGHOST -Ddb.portNumber=$PGPORT -Ddb.user=$PGUSER -Ddb.databaseName=$PGDB -Ddb.password=$PGPW -jar zipdownloader-0.0.1.jar
\ No newline at end of file
diff --git a/scripts/zipdownload/pom.xml b/scripts/zipdownload/pom.xml
index 256062a46e2..efd028c1089 100644
--- a/scripts/zipdownload/pom.xml
+++ b/scripts/zipdownload/pom.xml
@@ -2,51 +2,25 @@
 <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
     <modelVersion>4.0.0</modelVersion>
-    <groupId>ZipDownloadService</groupId>
-    <artifactId>ZipDownloadService</artifactId>
-    <version>1.0.0</version>
+    
+    <parent>
+        <groupId>edu.harvard.iq</groupId>
+        <artifactId>dataverse-parent</artifactId>
+        <version>${revision}</version>
+        <relativePath>../../modules/dataverse-parent</relativePath>
+    </parent>
+    
+    <artifactId>zipdownloader</artifactId>
+    <version>0.0.1</version>
+    <packaging>jar</packaging>
+    
     <properties>
-        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
     </properties>
-    <pluginRepositories>
-        <pluginRepository>
-            <id>central</id>
-            <name>Central Repository</name>
-            <url>https://repo.maven.apache.org/maven2</url>
-            <layout>default</layout>
-            <snapshots>
-                <enabled>false</enabled>
-            </snapshots>
-            <releases>
-                <updatePolicy>never</updatePolicy>
-            </releases>
-        </pluginRepository>
-    </pluginRepositories>
-    <repositories>
-        <repository>
-            <id>central-repo</id>
-            <name>Central Repository</name>
-            <url>https://repo1.maven.org/maven2</url>
-            <layout>default</layout>
-        </repository>
-    </repositories>
-    <dependencyManagement>
-        <dependencies>
-            <dependency>
-                <groupId>com.amazonaws</groupId>
-                <artifactId>aws-java-sdk-bom</artifactId>
-                <version>1.11.790</version>
-                <type>pom</type>
-                <scope>import</scope>
-            </dependency>
-        </dependencies>
-    </dependencyManagement>
+    
     <dependencies>
-        <!-- https://mvnrepository.com/artifact/org.postgresql/postgresql -->
         <dependency>
             <groupId>org.postgresql</groupId>
             <artifactId>postgresql</artifactId>
-            <version>42.2.2</version>
         </dependency>
         <dependency>
             <groupId>com.amazonaws</groupId>
@@ -58,28 +32,27 @@
         <plugins>
             <plugin>
                 <artifactId>maven-compiler-plugin</artifactId>
-                <version>3.1</version>
                 <configuration>
-                    <source>1.8</source>
-                    <target>1.8</target>
+                    <release>${target.java.version}</release>
                 </configuration>
             </plugin>
             <plugin>
-                <groupId>org.apache.maven.plugins</groupId>
-                <artifactId>maven-assembly-plugin</artifactId>
-                <version>2.4</version>
-                <configuration>
-                    <archive>
-                        <manifest>
-                            <mainClass>edu.harvard.iq.dataverse.custom.service.download.ZipDownloadService</mainClass>
-                        </manifest>
-                    </archive>
-                    <descriptorRefs>
-                        <descriptorRef>jar-with-dependencies</descriptorRef>
-                    </descriptorRefs>
-                    <finalName>${project.artifactId}-v${project.version}</finalName>
-                    <appendAssemblyId>false</appendAssemblyId>
-                </configuration>
+                <groupId>org.springframework.boot</groupId>
+                <artifactId>spring-boot-maven-plugin</artifactId>
+                <version>2.6.3</version>
+                <executions>
+                    <execution>
+                        <goals>
+                            <goal>repackage</goal>
+                        </goals>
+                        <configuration>
+                            <!--<classifier>spring-boot</classifier>-->
+                            <mainClass>
+                                edu.harvard.iq.dataverse.custom.service.download.ZipDownloadService
+                            </mainClass>
+                        </configuration>
+                    </execution>
+                </executions>
             </plugin>
         </plugins>
     </build>
diff --git a/scripts/zipdownload/src/main/java/edu/harvard/iq/dataverse/custom/service/download/ZipDownloadService.java b/scripts/zipdownload/src/main/java/edu/harvard/iq/dataverse/custom/service/download/ZipDownloadService.java
index 4b66ee770d5..db7eb7b8428 100644
--- a/scripts/zipdownload/src/main/java/edu/harvard/iq/dataverse/custom/service/download/ZipDownloadService.java
+++ b/scripts/zipdownload/src/main/java/edu/harvard/iq/dataverse/custom/service/download/ZipDownloadService.java
@@ -148,9 +148,9 @@ public void processFiles() {
             String zipEntryName = checkZipEntryName(fileName, fileNamesList);
             // this may not be needed anymore - some extra sanitizing of the file 
             // name we used to have to do - since all the values in a current Dataverse 
-            // database may already be santized enough. 
-	    // (Edit: Yes, we still need this - there are still datasets with multiple 
-	    // files with duplicate names; this method takes care of that)
+            // database may already be santized enough.
+            // (Edit: Yes, we still need this - there are still datasets with multiple
+            // files with duplicate names; this method takes care of that)
             if (inputStream != null && this.zipOutputStream != null) {
                 
                 ZipEntry entry = new ZipEntry(zipEntryName);