Library

Library holds written knowledge that isn’t tied to one workspace: your notebooks and your protocols, both personal ones and the ones shared with your institution. Open it from Knowledge → Library in the sidebar, then switch between Notebooks and Protocols at the top. Under Protocols, choose Personal or Shared.

Uploaded files, datasets and folders of evidence don’t live in Library. They belong to a workspace and are in Explorer.

How Library is organized

Each section has a tree on the left and an editor on the right. In the tree you can:

Create a New Folder or a new page or protocol.
Drag folders and items to reorganize them.
Right-click a folder or item to rename, duplicate or delete it.
Expand an item to see its saved revisions.

Pages and protocols are written in Markdown.

Notebooks

Notebooks are your own pages: lab notes, meeting notes, drafts. Only you see them. Create a page with New Page, give it a title, and write in the editor.

The editor has two ways to save:

Save keeps your working copy. Use it as often as you like; it replaces what was saved before.
Save as New Revision records a numbered version (Saved revision #3., for example) that stays as it is when you keep editing.

To look at an earlier version, expand the page in the tree and open a revision. Revisions open read-only. You can rename or delete a revision from its right-click menu.

Personal protocols

Personal protocols are written methods that only you can open. They work like notebook pages: Save keeps your working copy, Save as New Revision records a version, and earlier revisions open read-only from the tree.

Publish to Shared Library

To share a personal protocol with your institution, open it and choose Publish to Shared. In Publish to Shared Library, pick a mode:

Create new shared protocol, and choose the Destination folder in the shared tree (or Root).
Append revision to existing shared protocol, and pick the Existing shared protocol it updates.

Publishing copies what you last saved, so save your edits first. Your personal protocol stays yours and keeps changing independently of the shared copy.

Shared protocols

Shared protocols belong to your institution. Everyone in the institution can open them, create new ones, organize the shared tree and save new revisions.

Every save of a shared protocol is a revision: the editor offers Save as New Revision only, so earlier versions are always kept. Open an earlier revision from the tree to read it, then:

Restore This Revision saves its content as a new revision on top, so nothing in the history is lost.
Clone to Personal copies it into your personal protocols, where you can work on it privately.

Shared protocols can’t be deleted. A revision that is linked to a canvas node can’t be deleted either, so a node never loses the method it points to.

Protocols on canvas nodes

A canvas node shows protocols in its Protocol widget. Each link points at a fixed version, so editing the protocol in Library later doesn’t change what the node shows:

A Shared revision link points at one revision of a shared protocol. In a node’s editor, Add protocol searches the shared protocols and links the current revision of the one you pick.
A Personal snapshot link points at a snapshot of one of your personal protocols.

Snapshots

A snapshot is a frozen copy of a personal protocol’s title and content. Sauriq takes one when a personal protocol goes onto a canvas, through Quick build or Insert blueprint, so the canvas has a copy that doesn’t depend on your private Library. Sauriq reuses your latest snapshot of that protocol, or captures one if none exists. Later edits to the personal protocol don’t change an existing snapshot. To put an updated method on canvases, publish it to the Shared Library and link the shared revision.

Select a protocol link on a node to preview it. Open protocol opens shared revisions and snapshots you captured in Library. A snapshot’s separate Library page is read-only and is available only to the person who captured it; other collaborators can read it in the canvas preview.

Node blueprints

A node blueprint is a reusable set of canvas nodes and the links between them, built for one protocol: the steps of the method laid out as nodes, ready to place on any canvas. Blueprints open at /library/protocols/blueprints/….

To make one, open a personal or shared protocol and choose Node blueprints, then New blueprint. The blueprint builder shows the protocol’s text next to a small canvas:

Place nodes with Add node, the place-node tool or a right-click, and link them.
Select a node to set its Title, Type and Widgets in the inspector. Blueprints keep the structure only: values you’d fill in on a real canvas, such as dates, are reset when the blueprint is stamped.
Select Finalize when it’s ready. A finalized blueprint is read-only; select Reopen to change it again.

Blueprints of personal protocols are yours. A blueprint of a shared protocol can be edited by the person who created it and by institution owners and admins.

Insert a blueprint on a canvas

On a canvas you can edit, select Insert blueprint in the bottom toolbar. It lists the finalized blueprints you can use; choose one and Stamp onto canvas… adds its nodes and links to the canvas.

Activity nodes from the blueprint are linked to the blueprint’s protocol: a shared protocol links its current revision, and a personal protocol of yours links its snapshot. Someone stamping a blueprint of another person’s personal protocol gets the nodes without the protocol link.