us.polhem.skywrite.draft
A Skywrite draft, in the account's us.polhem.skywrite.drafts space: a record that isn't published yet, or changes to one that is. The record key is derived from the collection and id, so every device writes a draft to the same record; read those fields rather than the key.
Details · record, key any
| Kind | record |
|---|---|
| Record key | any |
| Authority | skywrite.polhem.us |
| Commit rev | 3n2sy3ygkhb2b |
| Indexed |
Record
record · key anyProperties
The collection the draft's record is published to.
When the draft was started.
Names the draft in its collection: the published record's key for changes to it, or a TID made up for a new record.
rkey
stringFor a new record: the record key typed in so far, which may not be a valid key yet.
maxLength: 512
subject
refFor changes to a published record: the record, and the version the changes started from. A new record's draft has none.
When the draft was last saved, on any device.
The record as drafted. Files it uses are blobs this record references, which keeps them on the PDS.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
A personal space for an account's Skywrite drafts: unpublished records and unpublished changes to published ones, synced between the devices the account uses Skywrite on. Its authority is the account itself, and its key is always self.
-
us.off-the-clock.draft
recordAn unfinished post, event, listing or review, kept in the member's personal space until they post it (D43). The drafted record is carried as written so far and is validated only when it is posted.
-
id.skiddle.draft
recordA skiddle.id post that isn't published yet, kept apart from site.standard.document so readers don't list it. Anyone can read it on the PDS. Publishing turns it into a site.standard.document and deletes the draft.
-
One manager's unpublished changes to one press kit, in their repo in the project's backstage (computer.localnetwork.space.backstage). The record key is the press kit's: an existing one's, or for a new press kit, the key it will be published under, so a manager has at most one draft per press kit. A draft the Local Network root account writes on someone's behalf has a key of its own, since the root can hold several managers' drafts of one press kit; its base names the press kit, or for a new one,
-
net.wireservice.draft
recordAn unpublished or in-progress article, stored in the publication's private staff space and written by the publication's DID. On publish, the CMS writes a public site.standard.document; when space is set, it writes the full document into that space and a public net.wireservice.gatedContent stub instead.