Collection Day card

Supplied collection dates can be used directly, or schedules can repeat weekly, fortnightly or every four weeks from an anchor week. Holiday changes are handled through explicit dates and exclusions. Recording a completion advances the stream, while missing or invalid schedules remain unknown. Across screens, the evening reminder follows the local clock.

Live card

This card is drawn in your browser by the same code the Players run, with sample data.

Category: Public information. Tags: Schedules, Lobbies and reception, Offices and workplaces, Schools and campuses.

Layouts

This fullscreen card fills the whole screen in landscape or portrait and is not placed as a corner, chip, or strip.

Layouts: full. Forms: landscape, portrait.

Card layouts, themes and publishing. Browse the cards.

Data and privacy

This card uses its configured properties and live card data.

Use site or neighbourhood labels; no personal addresses are needed.

Properties

For theme, background, accent and position, see Common properties.

Set static properties in params. Bind data to a project card data key for live values; that document holds only dynamic properties. Without a data key, put the complete configuration in params. Nested rows describe the contents of their parent property.

Static properties

Name	Type	Default	Values and limits
`setOutHour`	integer	`18`	minimum: `0`; maximum: `23`
`setOutMinute`	integer	`0`	minimum: `0`; maximum: `59`
`perPage`	integer	`4`	minimum: `2`; maximum: `6`
`pageSeconds`	integer	`12`	minimum: `8`; maximum: `120`

Dynamic properties

Name	Type	Default	Values and limits	Description
`title`	string	`"Collection day"`	maxLength: `100`
`location`	string	`""`	maxLength: `120`
`footnote`	string	`""`	maxLength: `240`
`updatedAt`	string	`""`	maxLength: `64`
`streams`	array	`[]`	maxItems: `12`
`streams[].id`	string		minLength: `1`; maxLength: `48`; Required
`streams[].name`	string		minLength: `1`; maxLength: `60`; Required
`streams[].tone`	string	`"cool"`	`"cool"`, `"success"`, `"warm"`, `"warning"`, `"text"`
`streams[].note`	string	`""`	maxLength: `180`
`streams[].dates`	array	`[]`	maxItems: `180`	Explicit collection dates override the weekly rule. Use these for holiday moves and irregular schedules.
`streams[].weekdays`	array	`[]`	maxItems: `7`	ISO weekdays, Monday1 through Sunday7. Used only when dates is empty.
`streams[].everyWeeks`	integer	`1`	minimum: `1`; maximum: `4`
`streams[].anchorDate`	string	`""`	maxLength: `10`	Any date in an active collection week, Monday-based. Required when everyWeeks exceeds1.
`streams[].excludeDates`	array	`[]`	maxItems: `120`
`streams[].collectedThrough`	string	`""`	maxLength: `10`	Explicit completion record: collections through this local date are already completed.

Canvas example

Add this item to a playlist page’s primitives. Publish the playlist and assign a screen.

{
  "id": "collection-day",
  "primitive": "card",
  "card": "collection-day",
  "major": 1,
  "params": {
    "theme": "neomustard"
  },
  "rect": {
    "x": 0,
    "y": 0,
    "width": 1920,
    "height": 1080
  },
  "layer": 0,
  "content_fit": "fill",
  "data": "example-key"
}

Write live data

The canvas example binds its data field to example-key. That value is a data key: a name this canvas item chooses, not the name of the card. Give each canvas item its own key when items should show different data, or share one key when they should show the same data. Keys are scoped to the project, follow the K/V key grammar, and cannot start with feed:.

Create this document before showing the card, then replace it to update the screen without republishing. Writes to a key that live canvas items bind are checked against each bound card’s dynamic properties. Use the same project as the playlist.

Save the document as card-data.json. The CLI reads the document itself, with no wrapper:

{
  "title": "Collection day",
  "location": {
    "name": "Vancouver",
    "latitude": 49.25,
    "longitude": -123.0
  },
  "footnote": "",
  "updatedAt": "",
  "streams": []
}

screenrig card-data put example-key --file card-data.json

Or call the API directly. The API wraps the same document in a document field. An agent token already names its project, so no project header is sent; if you send ScreenRig-Project, it must match the token’s project. Supply your API authorization through the environment; see API authentication.

curl --request PUT "https://api.screenrig.ai/api/card-data/example-key" \
  --header "Authorization: Bearer $SCREENRIG_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{"document":{"title":"Collection day","location":{"name":"Vancouver","latitude":49.25,"longitude":-123.0},"footnote":"","updatedAt":"","streams":[]}}'