computer.localnetwork.epk.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, its key is the one the press kit will get. Photos it adds are blobs in the writer's repo until publishing copies them to the root's.

Repository @localnetwork.computer did:plc:d42l64gsczg6qh2vo243xv5l not from the namespace authority
Details · record, key tid
Kindrecord
Record keytid
Authorityepk.localnetwork.computer
Commit rev3n2kadcqrfi2b
Indexed

Record

record · key tid

Properties

base

ref

The published press kit (a computer.localnetwork.epk record) at the version this draft started from. Absent for a press kit that isn't published yet.

changes

requiredref

The fields this draft changes, with their new values. A field left out is unchanged; an empty string, list or object clears it.

Reference

createdAt

requiredstring · datetime

onBehalfOf

string · did

Set when the Local Network root account wrote this for a manager whose PDS can't write to spaces.

What each changed field held in the published press kit when the draft changed it; a changed field missing here was empty. Publishing compares these with the current values to find fields someone else published since. Absent for a press kit that isn't published yet.

Reference

updatedAt

requiredstring · datetime

#contentFields

object

Some fields of a press kit's computer.localnetwork.epk.content record.

Properties

bio

string
  • maxLength: 50000
  • maxGraphemes: 5000

mixes

array
  • maxLength: 12
itemsref

photos

array
  • maxLength: 20

quotes

array
  • maxLength: 10

techRider

string
  • maxLength: 20000
  • maxGraphemes: 2000

#fields

object

Some fields of a press kit: the public record's at the top level, the private part's under content.

Properties

bio

string
  • maxLength: 10000
  • maxGraphemes: 1000
Reference

headline

string
  • maxLength: 3000
  • maxGraphemes: 300

mixes

array
  • maxLength: 12
itemsref

photos

array
  • maxLength: 10

title

string
  • minLength: 1
  • maxLength: 1000
  • maxGraphemes: 100

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • computer.localnetwork.epk

    record not from the namespace authority

    An electronic press kit for a project, in the Local Network root account's repo. A project can have several, one per audience, and all its managers edit them through drafts (computer.localnetwork.epk.draft), which the root publishes. The root rewrites this record on every publish, so its CID identifies the published version. This record is the public part; the rest sits in the press kit's own space (computer.localnetwork.space.epk, with the same key), which people read once a manager grants them

  • computer.localnetwork.epk.content

    record not from the namespace authority

    The private part of a press kit, written by the Local Network root account into the press kit's space whenever a manager publishes it.

  • 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.

  • computer.localnetwork.epk.request

    record not from the namespace authority

    A request to see the private part of a press kit, written by the person asking into the project's computer.localnetwork.space.epkRequests space, which only the project's managers read.

  • An 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.