Omeka VS Kavita

Omeka

Omeka (https://omeka.org/) is OSS and has a REST API. Usually used by museums/libraries, but primary function is to upload and describe media files.

Adding new features to listmonk (mailing list / newsletter manager), preparing for its next release.

https://github.com/knadh/listmonk

Setting up and playing around with Omeka, a brilliant document publishing system, to help publish an archive of digitised physical books and documents.

https://omeka.org

If you Google "COVID-19 digital archive" you can also find a range of projects with different focuses. A benefit of technology is that now many organizations can create their own Omeka site and build a collection to document events in real time. However, I hope the post above demonstrates that while anyone can, any historian utilizing these various resources need to consider the practices undertaken to gather digital archives. We would never enter a physical archive and look at paper documents without questioning why those survive, what's missing, and thinking about voices specifically left out. A digital collection is the same, however they present an abundance of sources that can distract or distort- approaching the surviving records of the Salem Witch Trials is different from approaching a collection of 40,000 personal accounts. What voices might not volunteer a personal account to a website if it requires identifying information? How many images of people in masks at the grocery store do we need to deliberately save? These are not substantially different questions from what past historians and archivists thought about, but technology does reframe discussion. We'll see how many of these projects were developed with sustainability in mind.

Yes to this and other free, open source solutions such as Omeka.

I have not tried this yet but: https://wordpress.org/plugins/diviner-archive/ Or you might look into a non-Wordpress solution like Omeka https://omeka.org/

There are some great visual archives online that might serve as inspiration. Free tools to create them include Collection Builder, Omeka, and some other free, open source repository software. Most of their sites have links to projects that people have built using their tool, and I find them super inspiring to scroll through and get ideas for projects like yours.

A popular alternative is Omeka, which can't directly be used with WordPress but does have some workarounds to effectively show the digital collection in a frame. Search the Omeka forum for more info.

Omeka (https://omeka.org/)

Browse the Issue Tracker: Visit our bug tracker @ https://github.com/Kareadita/Kavita/issues to find a list of open issues tagged specifically for the Bug Bash. You'll find a variety of tasks, from beginner-friendly to advanced.

#! /bin/bash installFolder="/opt/Kavita" # defines the folder where Kavita is installed backupFolder="/opt/KavitaBackup" # defines the backup folder for kavita kavitaUser="kavita" # defines the kavita service user kavitaGroup="kavita" # defines the kavita service group architecture="kavita-linux-x64.tar.gz" # options are: # kavita-linux-x64.tar.gz # kavita-linux-arm.tar.gz # kavita-linux-arm64.tar.gz if [ ! -d $installFolder ] then echo "KAVITA FOLDER IS MISSING!!" exit 1 fi cd /tmp if [ -r $architecture ] then echo "Kavita already present - extracting now!" tar -xzf $architecture else echo "Downloading latest Kavita from GitHub" wget https://github.com/Kareadita/Kavita/releases/latest/download/$architecture echo "extracting now!" tar -xzf $architecture fi if [ ! -d Kavita ] then echo "Something went wrong downloading or extracting" exit 1 fi echo "Stopping Kavita service" systemctl stop kavita.service if [ -d $backupFolder ] then echo "Deleting old KavitaBackup" rm -r $backupFolder fi echo "Creating new Kavita backup" cp -r $installFolder/config $backupFolder echo "Deleting Kavita" rm -r $installFolder echo "Installing new Kavita" cp -r /tmp/Kavita $installFolder echo "Deleting default config" rm -r $installFolder/config echo "Moving old config into install folder" cp -r $backupFolder $installFolder/config echo "CHOWN Kavita folder to kavita user and group" chown -R $kavitaUser:$kavitaGroup $installFolder echo "Make Kavita executable" chmod +x $installFolder/Kavita echo "Launch Kavita" systemctl start kavita.service echo "Cleaning up downloaded files" rm -r Kavita rm $architecture echo "Update process finished :)"

--2023-09-19 18:28:27-- https://github.com/Kareadita/Kavita/releases/download/v0.7.1.4/kavita-linux-arm64.tar.gz

Hey, Kavita creator here and noticed you don't have any mentions of Kavita for epub readers. Kavita is not a Calibre replacement, but has a built-in epub/pdf reader along with some series-based organization.

https://www.kavitareader.com/

The full release can be found here.