Home > Metadata Policy

Metadata Policy

 

  1. Title

 

Dublin Core Definition: A name given to the resource

Dublin Core Comment: Typically, a Title will be a name by which the resource is formally known

Mandatory: Yes

Repeatable: No

Local Comments:

  • Title of temple images should be the name of the temple, or the part of that.
  • Title of design images should be “design type of the temple”

Input Guidelines:

  • Capitalize initial of the first word and every proper noun (e.g. name of temple)

  1. Subject

Dublin Core Definition: The topic of the resource

Dublin Core Comment: Typically, the subject will be represented using keywords, key phrases, or classification codes. Recommended best practice is to use a controlled vocabulary

Mandatory: Yes

Repeatable: Yes

Local Comments:

  • Briefly mention the nature of the item

Input Guidelines:

  • Use semicolon to split elements when necessary

  1. Description

Dublin Core Definition: An account of the resource

Dublin Core Comment: Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource

Mandatory: Yes

Repeatable: No

Local Comments:

  • For the images of physical object, the description should be towards the physical object, instead of the still image
  • For the design images of temples, describe the content of the image

  1. Creator

Dublin Core Definition: An entity primarily responsible for making the resource

Dublin Core Comment: Examples of a Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity

Mandatory: Yes

Repeatable: Yes

Input Guidelines:

  • Capitalize all initials of names

  1. Source

Dublin Core Definition: A related resource from which the described resource is derived

Dublin Core Comment: The described resource may be derived from the related resource in whole or in part. Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system

Mandatory: Yes

Repeatable: No

Local Comments:

  • Describe the content of the image

  1. Date

Dublin Core Definition: A point or period of time associated with an event in the lifecycle of the resource

Dublin Core Comment:Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF]

Mandatory: Yes

Repeatable: Yes

Local Comments:

  • Date of temple images should be the construction and/or rebuilding time of the temple
  • Date of design images should be the drawing date of the image

Input Guidelines:

  • Specify the date with constructed, rebuilt and/or drew

  1. Relation

Dublin Core Definition: A related resource

Dublin Core Comment: Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system

Mandatory: No

Repeatable: No

Local Comments:

  • For the items of partial component of temples, describe the relationship of it with overall appearance

  1. Format

Dublin Core Definition: The file format, physical medium, or dimensions of the resource

Dublin Core Comment: Examples of dimensions include size and duration. Recommended best practice is to use a controlled vocabulary such as the list of Internet Media Types [MIME]

Mandatory: Yes

Repeatable: Yes

Local Comments:

  • The measurement of the temple hall will be the area, if possible
  • The measurement of the drawings/models will be the dimensions

Input Guidelines:

  • Use centimeter for the standard length unit
  • Use centimeter square for area

  1. Language

Dublin Core Definition: A language of the resource

Dublin Core Comment: Recommended best practice is to use a controlled vocabulary such as RFC 4646 [RFC4646]

Mandatory: No

Repeatable: Yes

Local Comments:

  • The main language that is presented in the resources, excluding numbers

Input Guidelines:

  • For resources in Chinese, use “Chi”
  • For resources in English, use “Eng”
  • For resources in Thai, use “Tha”
  • For resources in Japanese, use “Jap”

  1. Type

Dublin Core Definition: The nature genre of the resource

Dublin Core Comment: Recommended best practice is to use a controlled vocabulary such as the DCMI Type Vocabulary [DCMITYPE]. To describe the file format, physical medium, or dimensions of the resource, use the Format element

Mandatory: Yes

Repeatable: No

Local Comments:

  • The original medium of the resource

Input Guidelines:

  • For the main hall and components, use “Physical object”
  • For drawings and models, use “Still image”

  1. Identifier

Dublin Core Definition: An unambiguous reference to the resource within a given context

Dublin Core Comment: Recommended best practice is to identify the resource by means of a string conforming to a formal identification system

Mandatory: Yes

Repeatable: No

Input Guidelines:

  • Use the name of the person who inputs the particular resources

  1. Coverage

Dublin Core Definition: The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant

Dublin Core Comment: Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates. Temporal topic may be a named period, date, or date range. A jurisdiction may be a named administrative entity or a geographic place to which the resource applies. Recommended best practice is to use a controlled vocabulary such as the Thesaurus of Geographic Names [TGN]. Where appropriate, named places or time periods can be used in preference to numeric identifiers such as sets of coordinates or date ranges

Mandatory: No

Repeatable: Yes

Local Comments:

  • A brief geographic information of the resources, may include the physical location, date or period of construction/renovation/expansion, or the relationship with the physical surrounding