Editor guide

What to do first

You do not need to act on anything your first day. Open the editor dashboard and read through what is waiting: the tab badges show a live count for each queue, so you can see the shape of the workload before touching anything.

A reasonable first session is to read a few items in the Submission queue and the Feedback queue, without approving or closing anything, and ask Christina about any judgment call you are not sure of. Once one or two of those feel familiar, start clearing the easy ones: an obvious typo fix, a feedback note that is already resolved, a submission with clean licensing and nothing to question.

Where the queues are

Everything routes through the editor dashboard at /commons/admin/ (also reachable as /admin/). It has six tabs plus a separate feedback page:

• Submission queue: proposed records waiting for an editor. Check the license and provenance, confirm the attestation, and verify the license at the source before publishing any hosted CC0 or public-domain copy.
• Peer review: assign a willing reviewer by specialization, read their decision, set the peer-reviewed badge on accept.
• Moderation: pending comments and use notes. Nothing here is destructive; a hidden item can be approved later.
• Authorship claims: a member claiming an original record that was added before they joined.
• Flagged: flagged community discussions and replies.
• Edit records: a search-and-fix form on the dashboard itself, for quick changes to a record's title, summary, description, link, license, or status.
• Feedback (/commons/admin/feedback/): screenshots and notes people send from anywhere on the site, filterable open or closed.

How editing works today

There are three separate ways to edit content on BLOOM right now, and they are not one unified tool. Consolidating them is planned, but has not happened yet. Knowing which one to reach for saves you the "which Edit button" question:

1. Edit page: the floating button on Home, About, and a community page's banner. Use this for page copy: headings, section text, the site-wide banner message.
2. A record's own edit panel: opens from the record's own page. Use this when you are already looking at one record and want to change its title, summary, license, status, or taxonomy. It also handles the owner-vs-editor split: an owner can publish directly, an editor working on someone else's record submits it for review instead.
3. Edit records (dashboard tab): a search box on the dashboard itself. Use this when you know the title and want a fast fix without leaving the dashboard, for the same fields as the record's own panel.

Options 2 and 3 write to the same fields on the same record. If you and another editor might both be looking at the same record, prefer finishing one save before starting the next, rather than having both open at once. The later save wins, and the earlier one is not recoverable through either tool.

What is safe, what is dangerous

SafeFixing typos, editing summaries and descriptions, editing page copy, approving or hiding a moderation item, closing a feedback note once you have addressed it, reassigning a peer reviewer. None of these are destructive, and page-copy edits now keep a one-step undo (see below).

Needs careDelete and Archive on a record are owner-only (an editor working on someone else's record cannot reach them). Delete has a real confirm dialog and means it: "This permanently removes the record. This cannot be undone." Treat that literally: there is no undo behind it.

Leaving a note for the next editor

There is no shift log or handoff notebook built into BLOOM yet. If you want to leave a note for whoever edits next (or for Christina), the closest tool today is the feedback widget: write yourself a note there. It lands in the same open/closed queue every editor can see, even though it was not built for this exactly. Keep it short, and mark it closed once it has been read so it does not sit in the open count forever. A proper handoff log is on the list to build.