Overview
Library
Browse, edit metadata, set access, and remove library files.
Review
Review staged uploads: approve, return, or discard.
Upload
Add new audio files to the library.
Users
Create accounts; manage roles and passwords.
Verify & Prune
in progress
Scan for dangling records and prune them.
Duplicates
Review same-audio recordings with more than one rendition.
Recordings
Curate recordings: renditions and appearances, merge, move, delete.
Data sources
scanning
Import external folders in place via symlinks; no copying.
Network
Friend other madshare nodes: exchange node cards, manage peers.
Upgrades
Better renditions of what you already have, found on the madnetwork.
Cache
What the swarm fetched from other nodes — review it, free the disk.
Swarm
Traffic per file, in and out — and this node’s rate limits.
Trash
Restore or permanently delete trashed files.
Settings
License-based auto-publish policy.
Storage
{{/* Populated by dashboard.js from GET /api/admin/storage. Hidden until the fetch succeeds (an admin lacking file.delete simply never sees it). The per-category bar segments and detail rows (audio, images, …future video) are inserted by JS before #storageBarOther / #storageTotalRow. The meter block is disk-only; an object-store backend (future S3) reports no fixed capacity, so the meter is replaced by the "no fixed capacity" note and only the per-category breakdown + backend/location remain. */}}— free of —
Object storage — no fixed capacity.
-
{{/* per-category rows inserted here by JS, before the total row */}}
{{/* The two figures are measured differently and can disagree in a way
that looks wrong but is not: "Madshare total" is logical bytes
(SUM of sizes), "Disk used" is what the filesystem has allocated,
so on a compressing or sparse filesystem the total can read LARGER
than the disk usage. The title= says so rather than leaving a
reader to assume a bug. */}}
- Madshare total
- —
- External (linked)
- —
- Disk used
- —
- Backend
- —
- Location
- —