| core_schema | ||
| doc/user_guide | ||
| examples | ||
| ext | ||
| rockspecs | ||
| src | ||
| templates | ||
| test | ||
| .busted | ||
| .gitignore | ||
| .gitmodules | ||
| CODE_OF_CONDUCT | ||
| LICENSE | ||
| pocket_archive-scm-1.rockspec | ||
| README.md | ||
| run_tests.lua | ||
| scratch.lua | ||
Pocket Archive
The idea
Stick it in your pocket and carry it around. Install it on a cloud server. Install it on a Raspberry Pi. Browse it offline. Browse it online. Duplicate it, share it, harvest it and aggregate it. Feed it non-GMO spreadsheets regularly and it will thrive.
A more sensical description
Pocket Archive is a digital archival system and static site generator for small- to medium-(?) sized archives. It is designed to function in environments with unreliable connectivity and requires very low technical and human resources to set up, run, and use.
Pocket Archive fulfills the following business functions:
- Storage and management of files and metadata-only resources
- Management of descriptive, administrative, and technical metadata
- Static site generation (presentation)
Some interesting features it currently provides:
- Bulk content creation and updates are done by pushing spreadsheets (CSV) and data packages to a drop box
- Highly customizable content model with user-definable relationships between resources
- Able to run a presentation site and search form a thumb drive, without an Internet connection
- Fully implementing Linked Data under the hood, hiding its ugly parts from the end user
In spite of its design simplicity, Pocket Archive strives to be flexible. It is based on Volksdata, a very compact Linked Data store and manipulation library. There is no restriction to the types and schema of metadata allowed, or the file types supported. A file-based configuration allows to set up content types and validation rules, or to have (almost) no rules at all.
Pocket Archive is designed to reinvent as little as possible and to use
standard tools found in open source operating systems to provide a full
management and preservation environment. It creates and updates resources using
spreadsheets instead of running a web user interface; it writes all contents to
disk and metadata in an embedded database that can be archived, replicated,
backed up, and restored with reliable UNIX tools such as tar, rsync, etc.
Documentation
The full user documentation sources are in the user guide folder and published at https://pkar-doc.bmll.cc
API documentation is in progress.