S
Simpleasyty
Help Center — Import a JSON or YAML schema package
GETTING STARTED
IntroductionQuick start
CREATE A SCHEMA
Create a schema from a templateCreate a schema from scratch
SCHEMA TEMPLATES
Security Risk RegisterISO 27001 Document ControlSOC 2 Evidence RegisterPolicy ManagementThird-Party RiskData ClassificationApplication PortfolioControlled DocumentArchitecture Decision RecordInformation Asset RegisterBusiness Continuity RegisterGDPR Processing Activity
IMPORT
Import a JSON or YAML schema packageImport Page Properties
FIELD TYPES
Schema field typesText fieldsNumber fieldsYes / No fieldsSingle choice fieldsDate / Time fieldsEmail fieldsURL fieldsConfluence reference fieldsList fieldsField group fields
MANAGE SCHEMAS
Manage schemasIndexed fields and filtersSchema permissions
CAPTURE DATA ON PAGES
Capture metadata on a pageCapture, validate and repair metadata
CREATE REPORTS
Build a Metadata ReportConfigure report filters and viewer controls
STORAGE & PRIVACY
Data residencyStorage in ForgeRetention and deletion
COMPLIANCE
Compliance workflowsMetadata, history and revisions
ADMINISTRATION & TROUBLESHOOTING
Import and exportSchema reconciliation and processesSecurity, storage and limitsTroubleshoot schemas, filters and reports

IMPORT

Import a JSON or YAML schema package

Create schemas from an exported Simple Metadata package.

Before you begin

Check these requirements before following the steps below.

  • A Simple Metadata package file in .json, .yaml or .yml format.
  1. 1

    Open Import

    In Simple Metadata, open Schemas and select Import. Choose Schema package as the source.

  2. 2

    Choose and check the file

    Download the example JSON if you need a valid starting file. Upload your JSON or YAML package, then review the preview of schemas to create and any names that will be changed to avoid a conflict.

  3. 3

    Import the schemas

    Select Import, then review the created schemas and their access rules before using them on pages.

  4. 4

    What the file import includes

    This workflow imports schema definitions only. Page metadata and history in the package are skipped; no page values or capture macros are created.