Help:Story proposals for agents - Revision history

Admin: Import story-proposal wiki content from git

2026-10-08T15:28:56Z

Import story-proposal wiki content from git

← Older revision		Revision as of 15:28, 8 October 2026
Line 12:		Line 12:
	== Unactioned proposals (primary queue) ==		== Unactioned proposals (primary queue) ==

	~~Treat~~ '''Open''' and '''In review''' as unactioned. Ignore '''Published''' and '''~~Declined~~''' ~~unless doing housekeeping~~.		'''Status values:'''
			* '''Open''' / '''In review''' — not yet a wiki story; poll these for writing work.
			* '''wiki''' — story exists on this wiki; not yet published to [https://bseatimes.com/ BSea Times]. Set '''Published link''' to the wiki article. Poll <code>Status='wiki'</code> for BSea Times publishing.
			* '''Published''' — live on BSea Times (use '''Published link''' for that URL or page).
			* '''Declined''' — rejected; ignore unless housekeeping.

			For new wiki stories, treat '''Open''' and '''In review''' as unactioned. Ignore '''Published''', '''Declined''', and '''wiki''' in that queue.

	=== Cargo API (recommended) ===		=== Cargo API (recommended) ===
Line 47:		Line 53:

	* Set <code>\|Status=In review</code> when work starts.		* Set <code>\|Status=In review</code> when work starts.
	* Set <code>\|Status=Published</code> and <code>\|Published_link=...</code> when the ~~article exists~~.		* Set <code>\|Status=wiki</code> and <code>\|Published_link=...</code> to the wiki story page when the article is on this wiki.
			* Set <code>\|Status=Published</code> and update <code>\|Published_link=...</code> when the story is on BSea Times.
	* Set <code>\|Status=Declined</code> with a note in <code>\|Internal_notes=...</code> if rejecting.		* Set <code>\|Status=Declined</code> with a note in <code>\|Internal_notes=...</code> if rejecting.

			=== BSea Times queue (wiki status) ===

			<pre>
			action=cargoquery
			&format=json
			&tables=Story_proposals
			&fields=About,Story_URLs,Story_date,Submitted_by,Submitted_at,Status,Published_link,Internal_notes
			&where=Status='wiki'
			&order_by=Submitted at DESC
			&limit=50
			</pre>

	Example summary: <code>Agent: mark proposal published</code>		Example summary: <code>Agent: mark proposal published</code>

Admin: Import story-proposal wiki content from git

2026-10-08T13:02:18Z

Import story-proposal wiki content from git

← Older revision		Revision as of 13:02, 8 October 2026
Line 22:		Line 22:
	&format=json		&format=json
	&tables=Story_proposals		&tables=Story_proposals
	&fields=_pageName,~~Story URLs~~,About,~~Story date~~,~~Submitted by~~,~~Submitted at~~,Status,~~Published link~~,~~Internal notes~~		&fields=_pageName,Story_URLs,About,Story_date,Submitted_by,Submitted_at,Status,Published_link,Internal_notes
	&where=Status='Open' OR Status='In review'		&where=Status='Open' OR Status='In review'
	&order_by=Submitted at DESC		&order_by=Submitted at DESC
Line 47:		Line 47:

	* Set <code>\|Status=In review</code> when work starts.		* Set <code>\|Status=In review</code> when work starts.
	* Set <code>\|Status=Published</code> and <code>\|~~Published link~~=...</code> when the article exists.		* Set <code>\|Status=Published</code> and <code>\|Published_link=...</code> when the article exists.
	* Set <code>\|Status=Declined</code> with a note in <code>\|~~Internal notes~~=...</code> if rejecting.		* Set <code>\|Status=Declined</code> with a note in <code>\|Internal_notes=...</code> if rejecting.

	Example summary: <code>Agent: mark proposal published</code>		Example summary: <code>Agent: mark proposal published</code>

Admin: Import story-proposal wiki content from git

2026-10-08T12:59:59Z

Import story-proposal wiki content from git

New page

This page documents how the Brightlingsea wiki '''agent''' (bot account in the <code>bot</code> group) should find and update story proposals.

== Permissions ==

The bot account must be in the <code>bot</code> group and use a [[Special:BotPasswords|bot password]] with at least:

* <code>highwrite</code> (or equivalent edit rights)
* <code>editprotected</code> if proposals are protected later

Site config grants bots <code>editrestrictedfields</code> and <code>runcargoqueries</code> so the bot can change '''Status''', '''Published link''', and '''Internal notes''' on the form, and query Cargo over the API.

== Unactioned proposals (primary queue) ==

Treat '''Open''' and '''In review''' as unactioned. Ignore '''Published''' and '''Declined''' unless doing housekeeping.

=== Cargo API (recommended) ===

Base URL: <code>https://brightlingsea.localwiki.org.uk/api.php</code>

<pre>
action=cargoquery
&format=json
&tables=Story_proposals
&fields=_pageName,Story URLs,About,Story date,Submitted by,Submitted at,Status,Published link,Internal notes
&where=Status='Open' OR Status='In review'
&order_by=Submitted at DESC
&limit=50
</pre>

Authenticate with bot password via HTTP Basic Auth or <code>lgname</code>/<code>lgpassword</code> login + token for edits.

=== MediaWiki allpages (fallback) ===

<pre>
action=query
&format=json
&list=allpages
&apprefix=Submit a story proposal/
&aplimit=50
</pre>

Then load each page and parse template parameters, or filter client-side by Status.

== Updating status ==

Prefer '''Edit with form''' semantics via the Page Forms API where available; otherwise edit the wikitext on the proposal page:

* Set <code>|Status=In review</code> when work starts.
* Set <code>|Status=Published</code> and <code>|Published link=...</code> when the article exists.
* Set <code>|Status=Declined</code> with a note in <code>|Internal notes=...</code> if rejecting.

Example summary: <code>Agent: mark proposal published</code>

== Human editors ==

Users in the <code>editor</code> group also have <code>editrestrictedfields</code> for manual overrides; day-to-day status changes are expected from the agent.

[[Category:Brightlingsea Local Wiki]]