Collections & Tags
Add optional project groups and cross-cutting labels without making organization a prerequisite for capture.
Collections and tags remain optional ways to organize bookmarks. Arivu does not require either before capture, and Library adds broader filters across all supported knowledge types.
Collections
A collection is a named group of bookmarks. Collections can be nested into an owner-scoped tree, and a bookmark can belong to more than one collection. Deletion is non-recursive: move or delete child collections before deleting a parent. Deleting a leaf removes its memberships, never its bookmarks.
The browser extension can place a new bookmark into one of your existing collections during capture.
Tags
Tags are cross-cutting labels. Add them manually or review suggestions produced by local or optional provider-backed enrichment. Tag aliases help consolidate alternate spellings or names.
Each user controls AI tagging in Settings Automation: turn it off, restrict suggestions to existing vocabulary, or allow new generated tags. An instance-wide provider does not override that personal policy.
Tags are useful for search and filtering, but they are not the only relationship model. Explicit links, backlinks, sources, entities, concepts, and optional semantic similarity can connect material without assigning the same tag.
Library First
Library can filter by type, topic, source, workflow stage, date, and connection state. Begin by capturing freely, then add a collection or tag only when it improves retrieval.
API Routes
| Method | Endpoint | Purpose |
|---|---|---|
GET |
/api/collections |
List collections |
POST |
/api/collections |
Create a collection |
POST |
/api/collections/{id}/add |
Add a bookmark to a collection |
GET |
/api/tags |
List tags |
POST |
/api/tags/aliases |
Create a tag alias |