COPTR - User contributions [en-gb]

SoX (Sound eXchange)

2026-03-19T17:11:04Z

Carl: New SoX page

{{Infobox tool
|purpose=SoX (Sound eXchange) is a command-line, cross-platform audio processing utility.
|homepage=https://sourceforge.net/projects/sox/
|sourcecode=https://sourceforge.net/p/sox/code/
|license=GNU GPL v2 / GNU LGPL v2.1
|platforms=Linux, Windows, MacOS
|Wikidata ID=Q3487229
|function=File Format Migration, Redaction, Rendering
|content=Audio
}}
== Description ==
SoX is described as the Swiss army knife of audio utilities. It can read/write and migrate between many common audio formats. Note that MP3 is not directly supported due to patent concerns, but it can be added via LAME integration. SoX can also play, record and edit audio or be used as a digital audio processor, e.g. noise removal, applying impulse response filters.

== User Experiences ==


== Development Activity ==


{{Infobox tool details
|ohloh_id=https://openhub.net/p/sox
|mailing_lists=https://sourceforge.net/p/sox/mailman/
|releases_rss=https://sourceforge.net/p/sox/news/feed.rss
|issues_rss=https://sourceforge.net/p/sox/bugs/feed.rss
}}

ArchiFiltre

2025-08-20T15:33:17Z

Carl:

{{Infobox tool
|purpose=Overview of folder trees with fine diagrams
|homepage=https://archifiltre.fabrique.social.gouv.fr/
|license=Apache 2.0
|platforms=?
|function=File Management, Appraisal
|content=Database, Container, Binary Data, 3D, Audio, Document, Email, Ebook, Geospatial, Image, Research Data, Video, Web, Image, Software
}}
{{Infobox tool details}}
== Description ==
Archifiltre gives you orientation in deeply nested folder trees. It visualises folder contents in diagrams. It helps with cleaning up storage gone out of control. Further development is aimed at supporting archival processes like appraisal and transfer.

== User Experiences ==
* https://github.com/SocialGouv/archifiltre/wiki/Wiki-Archifiltre (French only)

== Development Activity ==

File:2023-06-06 Digital-archiving-workflow v0-8.png

2025-04-24T10:27:08Z

Carl: Version 0.8 of the digital archiving workflow at Archives & Special Collections, University of Glasgow.

== Summary ==
Version 0.8 of the digital archiving workflow at Archives & Special Collections, University of Glasgow.

File:PDF-hul-133 1.jpg

2025-04-24T10:21:16Z

Carl:

Workflow:Watch Folder Ingest

2025-03-28T15:56:06Z

Carl: 8 revisions imported

{{Infobox COW
|status=Production
|tools=Python, OVP, MAM, DAM, API, OTT
|input=Media assets and descriptive metadata in Watch Folder.
|output=Media assets and descriptive metadata in destination OVP.
|organisation=La Digitalizadora de la Memoria Colectiva
|organisationurl=https://ladigitalizadora.org/
}}
==Workflow Description==



<img src="https://media.licdn.com/dms/image/D4E12AQGakJHfY4Vmlw/article-inline_image-shrink_1500_2232/0/1712742432090?e=1718236800&v=beta&t=fv8JNxQgpGJ-Y343AGpNSKFJBCI8SdaYXqRC4VDum0U" alt="LinkedIn Image">

<br>

I want to monitor a local folder for new content. When a new file becomes available, the system will check if it's either an MP4 video file or an XML file. If it's an MP4 video, the system will then search for a corresponding XML file with the same name. Upon finding the XML file, it will extract metadata such as title, description, and tags. Subsequently, the system will upload the video file to an Online Video Platform (OVP) along with the extracted metadata. To prevent duplicates, before processing a new file pair (MP4 and XML), it will verify whether the pair has already been processed.

==Purpose, Context and Content==
Purpose: A watch folder serves as a designated directory that is monitored by a specific application or process. The primary purpose of a watch folder is to automate tasks based on the contents of that folder, facilitating Automated File Processing, Workflow Automation and Data Ingestion.

Context: In the context of digital content migration, this blueprint serves as a guide for facilitating bulk media and metadata ingests.

Github & Python Implementation Example: https://github.com/josev2046/WatchFolderAutomation

Workflow:Validation Error Analysis and Treatment for PDF-hul 133 Invalid date

2025-03-28T15:49:08Z

Carl: 6 revisions imported

{{Infobox COW
|status=Production
|tools=ExifTool, HxD, Pdfcpu, Qpdf, JHOVE, veraPDF Arlington Model Checker
|input=File with JHOVE validation error PDF-HUL-133 “Improperly formed date"
|output=Fixed file
|organisation=TIB
|organisationurl=https://wiki.tib.eu/confluence/display/lza/Digital+preservation+at+TIB
}}
==Workflow Description==

The workflow describes the analysis and the fix of a specific instance of a PDF-HUL-133 error.
It is a manual workflow. The methodology used here is that introduced in https://hdl.handle.net/2142/121092.

'''Validation Error'''

JHOVE v1.30.0RC1 PDF-hul v1.12.5 PDF-HUL-133 Improperly formed date. Well-formed, but not valid.

'''Cross-Check with other Tools'''

Cross-checked with:
pdfcpu v0.6.0dev relaxed mode - no error
pdfcpu v0.6.0dev strict mode - no error
qpdf v9.1.1 - no error
Arlington PDF Model checker by verapdf 1.26.0-RC1 Greenfield Parser:
Entry ModDate in DocInfo shall have type Date (1 occurance)
Entry CreationDate in DocInfo shall have type Date (1 occurance)
'''

'''Locate Error in Spec'''

ISO3200-2:2017 (PDF 2.0 Spec) lists the the Keys CreationDate and ModDate in the Document Info Dictionary as type Date.
Section 7.0.4 defines that a date shall be a text string containing no whitespace, of the form:
''(D:YYYYMMDDHHmmSSOHH'mm)
where:
YYYY shall be the year
MM shall be the month (01–12)
DD shall be the day (01–31)
HH shall be the hour (00–23)
mm shall be the minute (00–59)
SS shall be the second (00–59)
O shall be the relationship of local time to Universal Time (UT), and shall be denoted by one of the characters PLUS SIGN (U+002B) (+), HYPHEN-MINUS (U+002D) (-), or LATIN CAPITAL LETTER Z (U+005A) (Z) (see below)
HH followed by APOSTROPHE (U+0027) (') shall be the absolute value of the offset from UT in hours (00–23)
mm shall be the absolute value of the offset from UT in minutes (00–59)

The prefix D: shall be present, the year field (YYYY) shall be present and all other fields may be present but only if all of their preceding fields are also present. The APOSTROPHE following the hour offset field (HH) shall only be present if the HH field is present. The minute offset field (mm) shall only be present if the APOSTROPHE following the hour offset field (HH) is present. The default values for MM and DD shall be both 01; all other numerical fields shall default to zero values. A PLUS SIGN as the value of the O field signifies that local time is now and later than UT, a HYPHEN-MINUS signifies that local time is earlier than UT, and the LATIN CAPITAL LETTER Z signifies that local time is equal to UT. If no UT information is specified, the relationship of the specified time to UT shall be considered to be GMT. Regardless of whether the time zone is specified, the rest of the date shall be specified in local time.''

The specification further notes that ''versions up to and including 1.7 defined a date string to include a terminating apostrophe. PDF processors are recommended to accept date strings that still follow that convention''.

'''Locate Error in File
'''
Offset given by JHOVE can be navigated to using a hex editor such as HxD. The offset points to the Document Info Dictionary with /CreationDate (D:2018020915415409'00') and /ModDate(D:2018020915415409'00'). Mapping those dates to the notation given above it becomes clear that the O key which identifies the relation to UT is missing. Alternatively to looking for the dates in a hex editor, exiftool can be used to pull out all dates with:
exiftool -time:all -G -a -s file.pdf

''' Match?'''

Yes. Description in the spec and error in the file match. (D:2018020915415409'00') is missing the O key.

'''Fixable?'''

Yes. If other dates, e.g. in the XMP-section, are in the correct format, they can be used to determine the corect value for O. If not, the HH'MM' UT offset can be removed to form a valid date.

'''Fix'''

Option 1:
This option only works in the case of the missing O entry and the trailing apostrophe being present. In this case, the trailing apostrophe can be deleted and the O entry, if it can be determined from other dates, added to the value. This does not change the overall byte number of the date value and therefore has no impact on the PDF's internal structure.

Option 2:
The date can also be modified using exiftool. This will create an incremental update to the end of the file which can be rolled back with tools such as pdfressurect. Due to objects being added, the size of the file will change.
The exiftool command to e.g. update the dates above to include the O key + is:
exiftool -PDF:ModifyDate="2018:02:09 15:41:54+09:00" -PDF:CreateDate="2018:02:09 15:41:54+09:00" file.pdf
If you do not know the correct O key, you can also omit the offset with:
exiftool -PDF:ModifyDate="2018:02:09 15:41:54" -PDF:CreateDate="2018:02:09 15:41:54" file.pdf

'''Check'''

Re-validate file with Arlington PDF Model checker by veraPDF: Error messages are gone, no deviations found.
Re-validate file with JHOVE: Well-formed and valid with option 2. Well-formed but not valid with option 1, as JHOVE currently expects date in format pre-PDF2.0, i.e. without trailing apostrophe.

'''Success?'''

Yes.

[[File:PDF-hul-133_1.jpg|Workflow image]]<br>



==Purpose, Context and Content==

This workflow describes the analysis and treatment of JHOVE PDF-Hul error message PDF-HUL-133 Improperly formed date. It describes the process and results of a manual validation error analysis and treatment process.

==Evaluation/Review==

The workflow is effective and should be replicable for most improperly formed date related errors in PDFs. However, as an invalid date has little impact on the rendering behavior of the PDF file itself, institutions may decide to not fix the error.
Please note that most PDF Readers (e.g., Adobe Acrobat, Foxit) make use of XMP Metadata and not of Document Info Dictionary Metadata when they display Date Created and Last Modified Dates in a document's properties.

==Further Information==

Sling

2025-03-28T12:19:50Z

Carl: 2 revisions imported

{{Infobox tool
|purpose=Sling is a CLI tool that extracts data from a source storage/database and loads it in a target storage/database.
|homepage=https://slingdata.io/
|sourcecode=https://github.com/slingdata-io
|license=GNU GPL v3.0
|platforms=Windows, Mac, Linux
|function=Backup, File Format Migration, File Management
|content=Database
}}

== Description ==
Sling is a free CLI product which offers an easy solution to create and maintain small to medium volume data pipelines using the Extract & Load (EL) approach. It focuses on data movement between: Database to Database, File System to Database, Database to File System.

== User Experiences ==
[https://atwong.medium.com/streamlining-data-migration-why-sling-might-be-your-easiest-option-350aac05bfb8 Streamlining Data Migration: Why Sling Might Be Your Easiest Option]

=== Release Feed ===
Below the last 3 release feeds:
<rss max=3>https://github.com/slingdata-io/sling-cli/releases.atom</rss>

=== Activity Feed ===
Below the last 5 commits:
<rss max=5>https://github.com/slingdata-io/sling-cli/commits.atom</rss>

Puremagic

2025-03-28T12:18:44Z

Carl: 1 revision imported

{{Infobox tool
|purpose=Puremagic is a cross-platform pure python module that will identify a file based off it's magic numbers
|sourcecode=https://github.com/cdgriffith/puremagic
|license=MIT
|cost=Free
|function=File Format Identification
}}
{{Infobox tool details}}
== Description ==

It is designed to be minimalistic and inherently cross platform compatible. It is also designed to be a stand in for python-magic, it incorporates the functions from_file(filename[, mime]) and from_string(string[, mime]) however the magic_file() and magic_string() are more powerful and will also display confidence and duplicate matches.

It does NOT try to match files off non-magic string. In other words it will not search for a string within a certain window of bytes like others might.

Advantages over using a wrapper for 'file' or 'libmagic':

* Faster
* Lightweight
* Cross platform compatible
* No dependencies

Disadvantages:

* Does not have [https://github.com/cdgriffith/puremagic/blob/master/puremagic/magic_data.json as many] file types. ("Only" 1600 at the time of posting)
* No multilingual comments
* Duplications due to small or reused magic numbers

(Help fix the first two disadvantages by contributing!)

Premissh

2025-03-28T12:17:19Z

Carl: 6 revisions imported

{{Infobox tool
|purpose=Premissh is a simple prototype tool for automatically creating PREMIS XML from a file, using DROID, BASH and XSLT.
|homepage=https://github.com/bishbashbackup/premissh
|sourcecode=https://github.com/bishbashbackup/premissh
|license=BSD-3-Clause
|platforms=Linux
|formats_out=PREMIS (Preservation Metadata Implementation Strategies)
|function=Metadata Extraction, Metadata Processing
}}
{{Infobox tool details}}
== Description ==

Premissh was initially created by Alex Habgood in 2024, as a student project for the INST0045 Digital Curation module on the MA Archive and Records Management program at University College London.

== User Experiences ==

Mets-bag-checker

2025-03-28T12:15:14Z

Carl: 3 revisions imported

{{Infobox tool
|purpose=METS Bag checker is a simple python tool to check the validity of METS Information Packages (XML validity, completeness, Data Objects fixity, absence of unreferenced files).
|sourcecode=https://framagit.org/BCaron/mets-bag-checker
|license=GNU GPLv3
|language=python
|formats_in=METS (Metadata Encoding and Transmission Standard)
|function=Fixity, Validation
}}
{{Infobox tool details}}
== Description ==

METS Bag checker is a simple python tool to help METS implementers with little IT resources checking the validitiy of their Information Packages (below abbreviated as "IP(s)"). The term "bag" refers to the BagIt standard (RFC 8493), as this tool is based on some basic rules, similar to those defined by BagIt, in order to perform checks on IPs. Note that these conventions are not enforced by the METS standard itself but are of common usage in METS implementations:
* Manifest at the root Package (directory) level;
* Same manifest name in all Packages - or at least predictable, according to a given pattern -;
* Reference to all files contained in the Package by //mets:file elements;
* Reference to the Package files' via a relative path in the //mets:file/mets:FLocat/@xlink:href attribute;
* Use of //mets:file/@CHECKSUM and //mets:file/@CHECKSUMTYPE attributes to specify file checksum calculated with MD5, SHA-1, SHA-256, SHA-384 or SHA-512 algorithm.

Please note that this is a personal project by Bertrand Caron (Bibliothèque nationale de France).

Demystify

2025-03-28T12:12:32Z

Carl: 16 revisions imported

{{Infobox tool
|purpose=Format Identification Analysis and Reporting
|homepage=https://github.com/exponential-decay/demystify
|license=Open source (see URL above)
|platforms=sqlite + Python + text/html
|function=Metadata Extraction, Content Profiling, De-Duplication
}}
{{Infobox tool details}}
== Description ==

Now known as "Demystify" (formerly 'DROID Siegfried Sqlite Analysis Engine') with thanks to Joshua Ng for the suggestion to rename it. Demystify is an engine for the analysis of [https://github.com/digital-preservation/droid DROID] CSV export files, [https://github.com/richardlehane/siegfried Siegfried] YAML export files, and Siegfried 'DROID compatible' output. The tool has three purposes, break the exports into their components and store them within a table in a SQLite database; create additional columns to augment the output where useful; and query the SQLite database, outputting results in a readable form useful for analysis by researchers and archivists within digital preservation departments in memory institutions.

The tool provides archivist definitions for each of the sections output; these definitions are customizable. The tool also supports output of statistics about files that may require further triage or may not be appropriate for long-term preservation based on institutional rules, in the form of a blacklist. The tool also analyses file names and directory names for non-ascii characters, and also characteristics that may present problems cross-file-system based on known Microsoft rules: http://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx

The engine can be used to generate a list of file paths for files that may present digital preservation risks (Rogues) or files which on the surface i.e. via identification alone, look okay (Heroes) and these listings can be used in conjunction with [http://manpages.ubuntu.com/manpages/trusty/man1/rsync.1.html rsync] to isolate these sets from one-another to be more flexible to work with.

=== Demystify Lite ===

[https://ross-spencer.github.io/demystify-lite/ Demystify Lite] provides a Pyscript/WASM implementation of Demystify's features and runs completely browser side for users with DROID or Siegfried reports that they would like to see analyzed.

== User Experiences ==

*Blog entries from the tool author, Ross Spencer:
**'''[2014-06-03]''' [http://www.openplanetsfoundation.org/blogs/2014-06-03-analysis-engine-droid-csv-export Describing the creation and purpose of the tool.]
**'''[2015-08-25]''' [http://openpreservation.org/blog/2015/08/25/hero-or-villain-a-tool-to-create-a-digital-preservation-rogues-gallery/ Using the output of the tool to create a digital preservation rogues gallery.]
**'''[2016-05-23]''' [http://openpreservation.org/blog/2016/05/23/whats-in-a-namespace-the-marriage-of-droid-and-siegfried-analysis/ The integration of Siegfried output for consistent and repeatable reporting.]
**'''[2016-05-24]''' [http://openpreservation.org/blog/2016/05/24/while-were-on-the-subject-a-few-more-points-of-interest-about-the-siegfrieddroid-analysis-tool/ Creating a multi-lingual consistent, digital preservation dialect and exploring alternative methods of format identification using Siegfried's capabilities.]
**'''[2022-05-09]''' [https://journal.code4lib.org/articles/16351 Fractal in detail: What information is in a file format identification report?]

= Development Activity =

All development activity is visible on GitHub: http://github.com/ross-spencer/demystify/commits

=== Release Feed ===
Below the last 3 release feeds:
<rss max=3>https://github.com/exponential-decay/demystify/releases.atom</rss>

=== Activity Feed ===
Below the last 5 commits:
<rss max=5>https://github.com/exponential-decay/demystify/commits/main.atom</rss>

BorgFormat

2025-03-28T12:10:46Z

Carl: 5 revisions imported

{{Infobox tool
|purpose=A web application and service that combines multiple tools for format identification and validation.
|homepage=https://github.com/Landesarchiv-Thueringen/borg
|license=[https://www.gnu.org/licenses/gpl-3.0.en.html GPL v3]
|platforms=Linux, Web
|function=File Format Identification, Validation
|content=Document
}}
{{Infobox tool details
|releases_rss=https://github.com/Landesarchiv-Thueringen/borg/releases.atom
}}

== Description ==
BorgFormat combines format recognition and -validation using multiple third-party tools.
Results from different tools are combined with configurable weights to a simple result ("valid" / "invalid" / "no clear result").
It provides a standalone web application for manual file upload.
Alternatively, it can be embedded into other applications via REST API.

==== Supported Tools ====

* [https://digital-preservation.github.io/droid/ Droid]
* [https://tika.apache.org/ Tika]
* [https://jhove.openpreservation.org/ JHOVE]
* [https://verapdf.org/ verapdf]
* [https://odftoolkit.org/conformance/ODFValidator.html ODF Validator]
* [https://github.com/mikeebowen/OOXML-Validator OOXML Validator]

See [https://github.com/Landesarchiv-Thueringen/borg#integrierte-werkzeuge list of supported tools] for further / updated information.

==== Platform ====

BorgFormat runs on a Linux server and is delivered as a web application to be used on any platform.

==== Language ====

The application and documentation are currently only available in German.

==== Installation ====

BorgFormat is built and run using [https://docs.docker.com/compose/ Docker Compose]. See https://github.com/Landesarchiv-Thueringen/borg#installation.

==== Documentation ====

Documentation is available in German language on the [https://github.com/Landesarchiv-Thueringen/borg GitHub page].

== Development ==

BorgFormat is developed and maintained by the [https://landesarchiv.thueringen.de/ Landesarchiv Thüringen].

Bitflip

2025-03-28T12:09:30Z

Carl: 3 revisions imported

{{Infobox tool
|purpose=An interactive tool that can be used to demonstrate the effects of information decay ("bitrot") in digital files.
|homepage=https://github.com/aybabtme/bitflip
|sourcecode=https://github.com/aybabtme/bitflip
|license=MIT License
|cost=Free and Open Source (FOSS)
|platforms=Windows, Linux, MacOS, FreeBSD
|language=Golang
|function=Teaching, Research, Experimentation
}}

== Description ==


Bitflip is a tool designed to flip bits in digital files. It can provide a didactic reference for students of digital preservation to understand the effects of information decay ("bitrot") in digital files.

Its functionality similar to Manfred Thaller's [https://web.archive.org/web/20090323121026/http://hki.uni-koeln.de/material/shotGun/ Digital Preservation shotGun].

== User Experiences ==


* [https://www.youtube.com/watch?v=tdnyrk5m5vQ Example of an emulated video game glitched using Bitflip].

= Development Activity =

All development activity is visible on GitHub: http://github.com/aybabtme/bitflip/commits

=== Release Feed ===
Below the last 3 release feeds:
<rss max=3>https://github.com/aybabtme/bitflip/releases.atom</rss>

=== Activity Feed ===
Below the last 5 commits:
<rss max=5>https://github.com/aybabtme/bitflip/commits/master.atom</rss>

Sumfolder1

2025-03-28T12:05:37Z

Carl: 3 revisions imported

{{Infobox tool
|purpose=sumfolder1 is a utility for use within the archival and digital preservation community to generate checksums for file system directories, and to generate an overall "collection" checksum for a given set of files. The utility may be used in support of de-duplication at a directory/folder level.
|homepage=https://pypi.org/project/sumfolder1/
|sourcecode=https://github.com/ross-spencer/sumfolder1
|license=GPL-3.0
|cost=Free as in kittens (or a donation of 1 million dollars to an offshore account if you have the funding)
|platforms=Python 3
|function=Appraisal, De-Duplication, Fixity
}}
{{Infobox tool details}}
== Description ==


sumfolder1 uses a DROID CSV output to generate checksums for file system directories and to generate an overall "collection" checksum for a given set of files. It can be used for fixity and de-duplication at the folder level.

== User Experiences ==


**'''[2023-01-16]''' [https://openpreservation.org/blogs/what-is-the-checksum-of-a-directory/ What is the checksum of a directory? Using DROID reports and the concepts behind Merkle Trees to generate directory and collection checksums.]

= Development Activity =

All development activity is visible on GitHub: http://github.com/ross-spencer/sumfolder1/commits

=== Release Feed ===
Below the last 3 release feeds:
<rss max=3>https://github.com/ross-spencer/sumfolder1/releases.atom</rss>

=== Activity Feed ===
Below the last 5 commits:
<rss max=5>https://github.com/ross-spencer/sumfolder1/commits/main.atom</rss>

Lunas

2025-03-28T12:02:38Z

Carl: 2 revisions imported

{{Infobox tool
|purpose=A syncing cli tool that can handle more than two directories locally and remotely
|homepage=https://codeberg.org/cyber-luna/lunas
|sourcecode=https://codeberg.org/cyber-luna/lunas
|license=GNU GPL 3
|function=Storage, File Copy
}}
{{Infobox tool details}}
== Description ==
lunas is capable of syncing local to local, local to remote, remote to local and remote to remote at the same time with many input directories, with their file attributes if enabled and more. It syncs both ways, but it has src/dest options that can be assigned to individual input directories.

== User Experiences ==
* [https://lemmy.ml/post/14805950 hello! i made a versatile file syncing tool in C++ it's called lunas]

Library (xklb)

2025-03-28T12:02:38Z

Carl: 4 revisions imported

{{Infobox tool
|purpose=Media indexing multi-tool
|sourcecode=https://github.com/chapmanjacobd/library/
|license=BSD 3-Clause
|formats_out=DB
|function=File Management, Quality Assurance, Web Capture
}}
{{Infobox tool details}}
== Description ==


Web Capture subcommands:

* web-add: index open web directories using ffprobe and exifTool to fetch additional metadata from remote file headers (without downloading the full file) for later automated selective downloading.
* tube-add: index video site metadata via yt-dlp
* gallery-add: index image gallery site metadata via gallery-dl
* extract-links: extract links from within a webpage, even if the page uses ShadowDOM, postMessage, and nested frames
* links-add: build updatable link-scraping databases for paginated content

Local file management subcommands:

* fs-add: index local files with ffprobe, exifTool, and textract
* cluster-sort: sort lines of text by similarity (a common use for this is to identify similar file paths)
* merge-folders: merge file trees (similar to [https://github.com/chapmanjacobd/journal/blob/main/programming/linux/misconceptions.md#mv-src-vs-mv-src rclone move] but it will print detailed information about overwrites and trumps (future overwrites from multiple source folders) before moving anything)
* relmv: move but preserve parent folder information
* process-image: convert large images as scaled AVIF files as an alternative to file deletion
* process-ffmpeg: convert large video/audio files to AV1/Opus as an alternative to file deletion

Quality Assurance subcommands:

* media-check: check video and audio files for corruption by decoding small sections or the whole file

== User Experiences ==


- [https://old.reddit.com/r/opendirectories/comments/1adbv4b/i_made_a_little_cli_opendirectory_scanner_tool/ Introducing webadd to the /r/opendirectories community]

ArchiveBox

2025-03-28T12:00:37Z

Carl: 2 revisions imported

{{Infobox tool
|purpose=ArchiveBox is an open source tool that lets organizations & individuals archive both public & private web content while retaining control over their data.
|homepage=https://archivebox.io/
|sourcecode=https://github.com/ArchiveBox/ArchiveBox
|license=MIT License
|cost=Free
|platforms=Docker + Python
|language=English
|Wikidata ID=Q63097629
|formats_out=PDF, WARC, JSON
|function=Web Capture, Personal Archiving
}}
{{Infobox tool details}}
== Description ==


ArchiveBox is an open source tool that lets organizations & individuals archive both public & private web content while retaining control over their data. ArchiveBox was first released in 2017.

== User Experiences ==


**'''[2024-03-27]''' [https://demo.archivebox.io/public/ ArchiveBox Online Demo.]

== Development activity ==

=== Release Feed ===
Below the last 3 release feeds:
<rss max=3>https://github.com/ArchiveBox/ArchiveBox/releases.atom</rss>

=== Activity Feed ===
Below the last 5 commits:
<rss max=5>https://github.com/ArchiveBox/ArchiveBox/commits/main.atom</rss>

Archifiltre-Mails

2025-03-28T11:57:11Z

Carl: 1 revision imported

{{Infobox tool
|purpose=Archifiltre-Mails connects to email containers and visualizes their content, helping you in exploring and adding metadata.
|homepage=https://github.com/SocialGouv/archifiltre-mails/wiki/Wiki-Mails-par-Archifiltre
|sourcecode=https://github.com/SocialGouv/archifiltre-docs/wiki/Wiki-Archifiltre
|license=Version 2.0
|formats_in=PST
|function=Appraisal, Metadata Processing, Annotation, Data capture and Deposit, Transfer
|content=Email
}}
{{Infobox tool details}}
== Description ==
Mails is a product of the Archifiltre solution. Its purpose is to allow any holder of an Outlook messaging to be able to analyze it via the archive format Outlook PST. Archifiltre-Mails was born out of the need for apprehension of a messaging. Currently, there is no tool for understanding a messaging system. Until then, it is impossible to know the oldest e-mail, the most important recipient, the volume of attachments contained in the messaging system, etc.

ArchiFiltre

2025-03-28T11:49:09Z

Carl: 2 revisions imported