Pin Specification

Status

This table shows possible pin statuses. You can see what status can be updated Under Saraban and Physical columns shows what status is possible given current status, per user role are possible for each role.

Fields

• Status Pin status.
• Archived Default to false.

Notes

• Archived pins can be set by set Archived flag to true, not by updating status.

Status	Description	Saraban	Physical
Pending		Unassigned Assigned Processing Resolved Rejected Duplicated	n/a
Unassigned (Verified)		Assigned Processing Resolved Rejected Duplicated	n/a
Assigned		Unassigned Processing Resolved Rejected Duplicated	Unassigned Processing
Processing		Unassigned Assigned Resolved Rejected Duplicated	Unassigned Resolved
Resolved		Unassigned Assigned Processing Rejected Duplicated	n/a
Rejected		Unassigned Assigned Processing Resolved Duplicated	n/a
Duplicated		Unassigned Assigned Processing Resolved Rejected	n/a

Location

Pin location can be represented in various forms. Minimum requirement is GPS. Some may argue that GPS should be optional too because some client applications (e.g. web version of Facebook messenger) do not support sharing user's location. But for current specification, GPS is mandatory.

Fields

• GPS Location in lat/long.
• Place Name (optional) This can be derived from Facebook's place name.
• Location Description (optional) More details such as room number, floor, etc.