MjolnirDocumentation
Databases guide current Reviewed 2026-09-17

Request a database

Before you request#

Check the shared repository first — what you need may already be there under a name you don't expect:

bash
ls /datasets/globe_databases

See Shared database repository for how it's organized.

How to request#

New databases and updates to an existing one are requested in Mjolnir Analytics, after signing in with your Mjolnir account:

Open database requests

Other questions about the repository go through the Support Center — see Getting help.

What to include#

To help the request get handled without a back-and-forth, include:

  • The database name, and a link to where it comes from
  • The version or release you need, if that matters for your work
  • Roughly how large it is, if you know
  • Why you need it — this sometimes reveals that something already in the repository covers it

Note Downloading and installing a shared database is centrally managed, not something you do yourself, and takes time depending on its size — there's no fixed turnaround.

Requesting an update#

If a database in the repository is out of date for your work, ask through the same route above rather than downloading your own copy. New versions are generally added as their own dated directory alongside the old one (see Shared database repository) rather than replacing it in place, so work that depends on a specific version keeps working after an update.

Licensing and restricted databases#

Some reference databases carry their own usage or redistribution terms from their original source, separate from anything Mjolnir controls. If you're not sure whether a database you want added has conditions attached, say so in your request rather than assuming.

Access for non-Mjolnir users#

If you're a Globe-affiliated user on another KU Research IT-hosted compute system rather than a Mjolnir user, request access to the shared repository with the Globe Database access request form — see Access for non-Mjolnir users.

What not to expect#

  • A guaranteed turnaround time
  • Automatic updates to a database once it's installed
  • Personal write access to the shared repository, even after a request is fulfilled