Collections

A collection is a folder in the tree: a library holds collections and snippets, and so does each collection.

Requires: a curator or an admin. For an assembler, the write commands in the menu are off, reading Only curators or admins can write to the library.; for a paused member they read This account is paused, so it cannot write to libraries. Reading, assembling and exporting still work. Either way the database refuses the write.

1. Right-click a library or collection row, or press its ⋯, and pick New collection.
2. Type a name in the New collection in <row> dialog and press Create collection.
3. Put snippets in it with a snippet's Move to…, pick the collection in the dialog, then press Move to <destination>.

The menu on a collection

In the tree, a row's right-click and its ⋯ render one list. A collection row's has six items: New snippet, New collection, Insert all, Rename, Move to…, Archive.

How deep collections go

A collection at the top of a library is depth 0, and the deepest one allowed is depth 4: five levels under the library. On a collection at depth 4, New collection is off, reading Nesting is limited to five levels., and creating one deeper is refused with the same sentence.

Moving and renaming

A collection's Move to… lists its library's top level and its other collections; Already here. marks the current parent, Inside the collection being moved. marks its own subtree, and a destination that would push the subtree past the cap repeats Nesting is limited to five levels. — all off.

Neither moving nor renaming touches identity. A snippet's address is /w/<workspace>/library/<uuid>/<title-in-the-url>, and the last part is never read, so a link survives both.

Archiving a collection

Archive removes the collection from the tree without archiving its contents. Its child collections and snippets — including colleagues' unshared snippets — move up to the collection's parent (or the library's top level when the collection sat at depth 0) in the same write.