Table of Contents

Introduction

Overview of the Dataset Structure

This dataset is part of the digital "Corpus of Stamp Seals of the Southern Levant" hosted on cssl.levantineseals.org and published by the SNFS Sinergia Project: Stamp Seals of the Southern Levant. The dataset is provided in JSON format, structured into two main sections: metaData and records. Below is an explanation of these key sections:

1. metaData

The metaData section contains information about the dataset itself. This includes details such as its creation, licensing, and the latest version.

2. records

The records section (Array) consists of an array of individual entries, each representing a specific stamp seal in the dataset. These records contain all relevant details about the stamp seals, such as:

This structure ensures that essential metadata is separated from the actual dataset records, making the dataset more flexible and readable while providing a comprehensive view of each entry.

JSON Structure of Each Record

Each record in the JSON structure is divided into the following main sections:

A Remark on Unique Identifiers and the primaryKey Field

In the JSON structure, many elements include a field called primaryKey, which is a universally unique identifier (UUID). A UUID is a 128-bit value used to uniquely identify information in computer systems. In this context, the primaryKey serves as a globally unique reference for each object within the dataset, ensuring that every element (such as a building, period, or institution) can be individually referenced, tracked, and connected without ambiguity.

Important Note on the remarks Key (in case remarks is an Object)

The remarks key is normally a structured object that contains rich, hypertext-like content with references to various entities, such as gods, kings, items, publications, locations, symbols, and groups. The remarks key allows for encoding complex relationships between these entities, which are reflected in the textEncoded field, while providing a more readable form in the textPrint field. References are "translated" from codes in the textEncoded field to detailed entries in the references object.

remarks Object Structure

Each remarks object includes the following fields:

Key Fields in the remarks Object

1. primaryKey

The primaryKey field is a UUID that uniquely identifies the remarks entry. This key ensures that each set of remarks can be distinctly referenced and connected to other objects in the dataset.

2. references

The references field contains various arrays of referenced entities. These entities are linked to the codes found in the textEncoded field. Each array corresponds to a specific type of reference, such as gods, items, kings, etc. If there are no references of a certain type, the corresponding array will be empty.

3. textEncoded

The textEncoded field contains the hypertext version of the remarks, where entities are referenced using codes in double square brackets ([[ ]]). These codes refer to entries in the references object, allowing for complex relationships between the text and the referenced entities.

Examples of encoded references:

Example of encoded text:

4. textPrint

The textPrint field provides a human-readable version of the remarks, where references are replaced by their names, identifiers, or short bibliographic notes.

Example of printed text:

Detailed Key Sections of the data Key Explanation

bibliography Object

collection Object

context Object

dating Object

Contains various dating information related to the item, including dynastic, relative, and royal dating systems, as well as any remarks or summaries.

iconography Object

Contains details about the iconographic analysis of the item, including comparanda, descriptions, discussions, and taxonomic classifications. It is structured as follows:

Structure of Keysections

comparanda Object

description Object

discussion Object

taxa Array

manufacture Object

The manufacture section (Object) contains detailed information about the manufacturing techniques, coating, engraving, group attributions, perforations, and additional remarks related to the object.

object Object

The object key contains detailed information about the condition, measurements, mountings, physical properties, and typology of the object.

Detailed Key Sections of the media key

The media key contains an array (Array) of media objects associated with a record. Each media object provides detailed information regarding the attributes, file properties, copyright information, and other metadata related to a media file (such as an image, video, or other digital media). Below is a breakdown of the key sections within each media object.
This structure is repeated for each media item in the media array.

Media Object Structure

Each media object consists of several key parts (this structure is repeated for each media item in the media array):

Key Sections and Descriptions

1. attributes Object

This section contains metadata related to the media file's upload, modification, and unique identification.

2. copyrights Array

Contains information about the copyright holders for the media file.

3. creators Array

Contains information about the individuals or organizations who created the media file.

4. file Object

Describes the media file's format, name, and file path.

5. license Object

Provides details about the license under which the media is shared.

6. originators Array

Contains information about any originators of the media file's content, such as people manufacturing a modern impression that was then photographed by someone else (i.e. the creator of the media file). This array can be empty if no originator information is available.

7. properties Object

Describes the technical properties of the media, such as its dimensions, resolution, and type.

Detailed Key Sections of the metadata Key Explanation

The metadata key contains important information about the record itself, including details on the creators, creation and modification dates, unique identifiers, and other relevant metadata fields. This section provides an overview of the key components within the metadata object.

Metadata Object Structure

Each metadata object includes the following key parts:

Key Sections and Descriptions

1. creators Array

The creators array contains information about the individuals or organizations responsible for creating the record. Each element in the array represents a contributor and includes their attributes, role, and personal details.

2. dateCreated String

The dateCreated field records the date when the record was originally created in the system. This is typically formatted as a string in the YYYY-MM-DD format (e.g., "2024-05-31").

3. doi String

The doi field contains the Digital Object Identifier (DOI) for the record, which is a standardized identifier used to permanently reference the object. If no DOI is available, this field can be left as an empty string (e.g., "").

4. identifier String

The identifier field provides a unique label or name for the record. This could be a title, catalog number, or another system-specific identifier (e.g., "Lachish 945").

5. lastUpdated String

The lastUpdated field stores the date when the record was last modified, allowing for version control and tracking of changes. This field is typically formatted as a string in the YYYY-MM-DD format (e.g., "2024-10-21").

6. primaryKey String

The primaryKey field contains a universally unique identifier (UUID) for the record, ensuring that each record is distinct and can be referenced unambiguously. This key is essential for cross-referencing and database management (e.g., "CA7848CB-D2A4-4AA0-9DB2-CC8FC0F2CAD2").


Stefan Münger, 20/10/2024