DATALAD-EXPORT-ARCHIVE-ORA(1)

✨ datalad export-archive-ora — like, the manual page 💅

okay so bestie, welcome to datalad export-archive-ora(1), a General Commands Manual situation, and honestly? it's giving "pack up all your annex objects and ship them to ORA" energy. no cap. let's get into it 🎀

---

🌸 NAME 🌸

datalad export-archive-ora — export an archive of a local annex object store for the ORA remote. literally what it says on the tin, and it slays at it 💖

---

🦋 SYNOPSIS 🦋

datalad export-archive-ora [-h] [-d DATASET] [--for LABEL] [--annex-
       wanted FILTERS] [--from FROM [FROM ...]] [--missing-
       content {error|continue|ignore}] [--version] TARGET ...

---

✨ DESCRIPTION ✨

okay so here's the vibe: the keys chillin' in your local annex object store get reorganized into a temporary directory — and no, it's not copying anything, it uses links so there's zero storage duplication. iconic behavior honestly 🫶 then that whole alternative object store gets moved into a 7zip archive, and that archive is suitable for use in an ORA remote dataset store. so fancy.

and here's the part where it all comes together — placing such an archive into:

<dataset location>/archives/archive.7z

Enables the ORA special remote to locate and retrieve all keys contained in the archive. main character energy fr fr 🔥

---

💅 OPTIONS 💅

• TARGET — if it's an existing directory, an archive.7z is placed into it. otherwise this is the path to the target archive. lowkey does two jobs. Constraints: value must be a string or value must be NONE
• list of options for 7z to replace the default -mx0 to generate an uncompressed archive. (yes, no compression — that's the default and we're telling you how to override it 🎀)
• -h, --help, --help-np — show this help message. and --help-np forcefully disables the use of a pager for displaying the help message, so if your pager was about to jump-scare you, it won't 🙈
• -d DATASET, --dataset DATASET — specify the dataset to process. if no dataset is given, an attempt is made to identify the dataset based on the current working directory. it'll try to figure it out, bestie, but like… be nice and just tell it. Constraints: Value must be a Dataset or a valid identifier of a Dataset (e.g. a path) or value must be NONE
• --for LABEL — name of the target sibling; wanted/preferred settings will be used to filter the files added to the archives. Constraints: value must be a string or value must be NONE
• --annex-wanted FILTERS — git-annex-preferred-content expression for git-annex find to filter files. Should start with 'or' or 'and' when used in combination with --for. iykyk 🌈
• --from FROM [FROM ...] — one or multiple tree-ish from which to select files. bring your faves ✨
• --missing-content {error|continue|ignore} — okay so by default, any discovered file with missing content will result in an error and the export is aborted 😭. Setting this to 'continue' will issue warnings instead of failing on error. The value 'ignore' will only inform about problem at the 'debug' log level. The latter two can be helpful when generating a TAR archive from a dataset where some file content is not available locally. Constraints: value must be one of ('error', 'continue', 'ignore') [Default: 'error']

⚠️ real talk: the default is 'error' and it aborts the whole export. if your content is missing and you want it to not throw a fit, you've gotta say so.

• --version — show the module and its version which provides the command. periodt 👑

---

👑 AUTHORS 👑

datalad is developed by The DataLad Team and Contributors <team@datalad.org>. iconic. no notes 💜

---

and that's the tea, bestie 🍓 this was datalad export-archive-ora version 1.1.5, dated 2025-06-15 — go forth and archive, you absolute legend 🌟💅