computer.localnetwork.epk.content

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.

Repository @localnetwork.computer did:plc:d42l64gsczg6qh2vo243xv5l not from the namespace authority
Details · record, key literal:self
Kindrecord
Record keyliteral:self
Authorityepk.localnetwork.computer
Commit rev3n2kadbyaai2b
Indexed

Record

record · key literal:self

Properties

bio

string

The full bio.

  • maxLength: 50000
  • maxGraphemes: 5000

mixes

array

Mixes only people with access can play, like unreleased promos.

  • maxLength: 12
itemsref

photos

array
  • maxLength: 20

quotes

array
  • maxLength: 10

techRider

string
  • maxLength: 20000
  • maxGraphemes: 2000

updatedAt

requiredstring · datetime

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

    record not from the namespace authority

    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,

  • computer.localnetwork.epk.defs

    not from the namespace authority

    Who can ask to see the private part of a press kit, and whether they get it straight away. Each audience is auto (approved at once), review (a manager decides) or none (can't ask). Someone in several audiences gets the most open of their answers. Managers can always add people directly.

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