Repository Management

Overview #

Repositories in DnXT Reviewer define where your eCTD dossier files are stored. Before you can import or upload dossiers, you must configure at least one repository that points to a file storage location. Reviewer supports two repository types: Filesystem (for network shares and local paths) and Veeva (for Veeva Vault cloud document management). This guide covers how to add, edit, delete, and manage repositories in DnXT Reviewer.

Accessing Repository Management #

Click Repository in the left sidebar to open the Repository Management screen. The main area displays a table of all configured repositories with their names, types, paths, and status.

Repository Table #

The repository table shows the following columns:

Toolbar Actions #

• Add — Opens the Add Repository form
• Delete — Removes the selected repository (with restrictions, see below)
• Export — Exports the repository list as a CSV file
• Refresh — Reloads the repository table from the server

Adding a Filesystem Repository #

A Filesystem repository connects Reviewer to a directory on the server’s file system or a mounted network share.

Step-by-Step #

1. Click the Add button in the toolbar.
2. The Add Repository form appears.
3. Select Filesystem from the Type dropdown.
4. Enter a Name for the repository (e.g., “Default”, “eCTD Production Share”).
5. Enter the Path to the directory where your eCTD dossiers are stored. This must be a path accessible by the Reviewer server.
   • Example (Linux/Mac): /mnt/ectd-share/regulatory
   • Example (Windows): \\server\ectd-share\regulatory
6. Click Save to create the repository.

Adding a Veeva Repository #

A Veeva repository connects Reviewer to a Veeva Vault instance, allowing you to browse and import eCTD content stored in Veeva’s cloud document management system.

Step-by-Step #

1. Click the Add button in the toolbar.
2. Select Veeva from the Type dropdown.
3. The form updates to show Veeva-specific fields:

4. Optionally check Save Credentials to store your Veeva username and password on the server. When saved, future imports will authenticate automatically without requiring you to re-enter credentials.
5. Click Save to create the repository.

Filesystem vs. Veeva: Comparison #

Editing a Repository #

To edit an existing repository:

1. Select the repository row in the table.
2. Click the Edit button (or double-click the row).
3. Modify the fields as needed (name, path, Veeva URL, credentials).
4. Click Save to apply changes.

Deleting a Repository #

To delete a repository:

1. Select the repository row in the table.
2. Click the Delete button in the toolbar.
3. A confirmation dialog appears.

Delete Restrictions #

A repository cannot be deleted if it has applications (dossiers) registered from it. This safeguard prevents accidentally orphaning imported dossiers. If you need to delete a repository that has associated applications:

1. Navigate to Dossier Library.
2. Delete all dossiers that were imported from this repository.
3. Return to Repository and delete the now-empty repository.

Exporting Repository Information #

Click the Export button in the toolbar to download the repository list as a CSV file. This export includes the repository name, type, path/URL, status, and application count. This is useful for documentation, audits, and configuration tracking.

Best Practices #

• Use descriptive names — Name your repositories clearly (e.g., “US NDA Production Share” rather than “Repo 1”) to help team members identify the correct repository during imports.
• Separate by purpose — Consider creating separate repositories for different regions, teams, or project phases (e.g., “US eCTD Archive”, “EU Active Submissions”).
• Verify paths before saving — Test that the file path is accessible from the Reviewer server before adding the repository. Incorrect paths will result in empty folder browsers during import.
• Review Veeva credentials periodically — If you use the Save Credentials option with Veeva, update the stored credentials when your Veeva Vault password changes.
• Limit repository count — While there is no hard limit, keeping the number of repositories manageable makes the import workflow smoother for all users.

Frequently Asked Questions #

Can I have multiple repositories pointing to the same path? #

Yes, but this is generally not recommended as it can lead to confusion and duplicate imports. Use a single repository for each unique storage location.

Do I need a repository for ZIP and Folder uploads? #

Yes. When you upload a ZIP or folder, you must first select a target repository. The uploaded content is extracted into that repository’s storage location.

What happens if the network path becomes unavailable? #

If the file system path is temporarily unavailable (e.g., a network share goes offline), the repository will still appear in the list but the folder browser will show an error when you try to browse it. Already-imported dossiers remain accessible in the Dossier Library since their metadata is stored in Reviewer’s database.

Can I share a repository across multiple Reviewer instances? #

Yes, if multiple Reviewer instances point to the same file system path, they can each import from that shared location. However, each instance maintains its own import state and metadata independently.

How do I set up a repository for a cloud file share? #

For cloud deployments (Azure, AWS), the file share must be mounted to the Reviewer server’s file system. Once mounted, use the mount path as the Filesystem repository path. Consult your DnXT Administrator or infrastructure team for mount configuration.

Related Articles #

• Importing Dossiers — Using repositories to import dossiers
• ZIP and Folder Uploads — Uploading content to repositories
• Getting Started with Reviewer — First-time setup including repository configuration