smithsonian/edan-schemas

JSON schemas for EDAN

edan-schemas's Issues

3D content types- consistency

After issue #6

Discuss w/team- consistency with other definitions and content types

Update schemas as necessary

Outside of this repo:
Update existing records to conform
Modify 3DSI modules to use new schemas
Re-validate records

Test validating JSON that references definitions that live outside the schema file being used.

Note tool/s that work for referenced schema files/schemas.

Create schemas for 3D content types

3D content types:
3d_article
3d_model
3d_snapshot
3d_tour

Determine the domain/root path for schema URNs/IDs

We need a base path for our URNs/IDs, it should be a "safe" namespace that wouldn't collide with a potential EDAN application or API. One option would be /schemastore or maybe something like /STUFF where STUFF is something awesome.

http://edan.si.edu/STUFF/schemas

See:
http://some.site.somewhere/entry-schema#
http://json-schema.org/latest/json-schema-core.html#rfc.section.8.2

Review efs - update references.

in online_media, where we currently have this:
"$ref": "media-element.json#/edanMediaElement"

we should instead have this:
"$ref": "media-element.json#/definitions/edanMediaElement"

and in something like si-unit, we are re-using our "efs" like this:
"$ref": "field-object.json#/fieldObject"
but it should be like:
"$ref": "definitions/field-object.json#/definitions/fieldObject"

Rename /atoms to /definitions

See this example below. We should relabel /atoms to /definitions to avoid overlap with "atom" in the context of atomic content in the EDAN repo.

http://json-schema.org/example2.html

{
    "id": "http://some.site.somewhere/entry-schema#",
    "$schema": "http://json-schema.org/draft-04/schema#",
    "description": "schema for an fstab entry",
    "type": "object",
    "required": [ "storage" ],
    "properties": {
        "storage": {
            "type": "object",
            "oneOf": [
                { "$ref": "#/definitions/diskDevice" },
                { "$ref": "#/definitions/diskUUID" },
                { "$ref": "#/definitions/nfs" },
                { "$ref": "#/definitions/tmpfs" }
            ]
        }
    },
    "definitions": {
        "diskDevice": {},
        "diskUUID": {},
        "nfs": {},
        "tmpfs": {}
    }
}

Change "si-unit" to si_unit

JSON file, and content within EDAN <- careful, need to work with si.edu on templates.

Also: "unit" records should supersede si-unit data eventually- again, requires collaboration with si.edu team.

Move miss records into subdirectory

There are a few types:

• sound_assets.json
• attract_loop_video.json
• attract_loop.json
• cortina_files.json
• cortina_section.json
• gallery_description.json
• miss_component.json
• miss_interactive.json

Schemas need better definitions

should we allow users to input undisclosed fields into their content?

Validate existing 3D records

After issue #5:

Validate existing data conforms

(need to check w/PD) Delete test recs (QUOTIENTPROD)

Verify eresource.json and ecr.json

Can these be merged? What records are using eresource.json? I think it's the "original" type LASSB defined but was renamed to ecr.json by OCIO.