Please type one or more space separated search terms



Search terms mode
 
 
Search terms matching
 
 
Search field filters

Search exclusively in these fields





clear all search field filters
 
Facet filters

Status

  (236)
  (2847)
  (80)

Concept Schemes

  (1)
  (4)
  (4)
  (15)
  (4)
  (25)
  (1520)
  (399)
  (1)
  (210)
  (115)
  (95)
  (98)
  (10)
  (0)
  (0)
  (0)
  (4)
  (0)
  (0)
  (875)

Collections

  (21)
  (16)
  (84)
  (135)
  (10)
  (245)
  (85)
  (30)
  (20)
  (3)
  (35)
  (46)
  (19)
  (91)
  (14)
  (62)
  (106)
  (13)
  (222)
  (78)
  (64)
  (80)
  (11)
  (30)
  (42)
  (79)
  (31)
  (54)
  (9)
  (78)
  (10)
  (22)
  (57)
  (32)
  (135)
  (119)
  (17)
  (7)
  (24)
  (16)
  (10)
  (5)
  (175)
  (160)
  (16)
  (3)
  (71)
  (7)
  (85)
  (27)
  (54)

Tenant's Collections

  (3163)
  
  

Tenants

  (3163)
  (97)
  (1189)
 
clear all facets

back

Field Value
classConcept
statuscandidate
prefLabel@enkeyValuePair
definition@enIndication of an entity consisting of a pair with a key and a value to specify a property. (source: NaLiDa)
notationkeyValuePair
example@enlength=182, transcription-convention=HIAT, segmented=false, etc. (source: NaLiDa)
scopeNote@enEspecially in legacy data there are data categories that are idiosyncratic. To allow for these to be included, key-value pairs can be used. Note that key-value-pairs may contain both key and value as separate structures or as a string consisting of both parts. While the description elements are free text elements, keys are more formal notations that can also be exploited by search engines. The name of a key-value-pair can be stored as an attribute of a keyValuePair element. (source: NaLiDa)
changeNoteThis concept is based on the ISOcat data category: http://www.isocat.org/datcat/DC-3898
inSchemeMetadata
deleted---
toBeChecked---
urihttp://hdl.handle.net/11459/CCR_C-3898_7ebbc25a-ee14-171c-3b58-f00b81d8d0d8
licenseCreative Commons Attribution (CC BY) (use the uri above for the attribution)

back