Metadata Requirements

In addition to requiring a metadata file within the Submission Information Packages (SIPs), the National Library of Norway also requires a set of metadata submitted via the submission API. This ensures that a minimum level of metadata associated with the submitted representations is indexed and made searchable.

The metadata requirements are based on Dublin Core, an international ISO standard widely used in archives, libraries, and digital collections. Dublin Core was chosen because it is relatively easy to understand, simple to implement, and both flexible and extensible. To make the metadata more structured, the standard are supplemented with attributes.

Most metadata elements are optional, but it is strongly recommended to provide as complete metadata as possible. This enhances searchability and improves the long-term understanding and usability of the resources.

To make the deposited packages as self-contained as possible from a preservation perspective —and to ensure control over file formats, the metadata also will be included in an XML file attached to the Archival Information Package (AIP). XML is well-suited for long-term preservation: it is an open format, widely used, and a well-established standard for metadata exchange. Its text-based structure makes it readable by both machines and humans, which is a significant advantage for preservation purposes.


General Guidelines for the Use of Standards
Punctuation and character encoding for field input should follow UTF-8.
ISO 639-2 is used as the standard for specifying language when the lang attribute is applied.
ISO 8601-2 is used as the standard format for specifying dates and times.
ISO 3166-2 is used to specify country codes.



Metadataelements


1.
NameType
DescriptionType of resource/media type. The National Library uses its own controlled vocabulary for allowed media types.
The lang attribute SHOULD be used to specify the language code.
RequirementMUST
Cardinality1..1

Guidelines for Use:

  • Allowed types for describing the resource:

    Text: Book, Newspaper, Journal, Article, Pamphlet, Letter, Email, Manuscript, Music Manuscript, Sheet Music, Program Report, Program Statistics.

    Images: Image, Map, Poster, Postcard, Reference Material.

    Audio: Audiobook, Music, Radio.

    Moving images: Film, Television.

    It is possible to request the addition of new media types if needed.

  • Language code should be specified. ISO 639-2 is used as the standard for indicating language when the lang attribute is applied.

Example:

{
"type":{
  "value": "Image",
  "lang": "eng"
}
}

2.
NameIdentifier
DescriptionIdentifiers (identifier type + ID/value).
The type and value attributes MUST be used to define the identifier type.
The lang attribute SHOULD be used to specify the language code.
RequirementMUST
Cardinality1..n

Guidelines for Use:

  • Examples of identifiers may include URN, PID, URI to a record in a catalog or metadata system, document ID, issue ID, copy number, ISBN, ISSN, ISMN, ISNI, DOI, record label, etc.

  • The identifier type MUST be defined. The use of the type attribute should be meaningful to the submitter, reflect the metadata catalog or system, and be applied consistently (using a standardized format).

  • Language code should be specified. ISO 639-2 is used as the standard for indicating language when the lang attribute is applied.

Examples:

{
"identifier": [
  {
    "type": "URN",
    "value": "URN:NBN:no-nb_digifoto_20220311_00191_NB_PE_VM_M_05_09_01_036"
  },
  {
    "type": "image-id",
    "value": "NB_PE_VM_M_05_09_01_036",
    "lang": "eng"
  },
  {
    "type": "call-number",
    "value": "POEL00003975",
    "lang": "eng"
  }
]
}

3.
NameTitle
DescriptionName given to the resource. If a title is missing, the recommended practice is to assign the resource a “meaningful” title.
The lang attribute SHOULD be used to specify the language code.
RequirementMUST
Cardinality1..1

Guidelines for Use:

  • Some resources already have predefined titles, such as books, journals, articles, painted works, artistic photographs, etc. When a title is missing, the recommended practice is to assign the resource a “meaningful” title. By meaningful, means a title that facilitates recognition and identification of the resource—essentially, a name that makes sense to the submitter.

  • Language code should be specified. ISO 639-2 is used as the standard for indicating language when the lang attribute is applied.

Examples:

{
"title": {
  "value": "Ola and Kari on a fishing trip in Rondane",
  "lang": "eng"
}
}
{
"title": {
  "value": "Photographic negative from June 1972 [image 394]",
  "lang": "eng"
}
}
{
"title": {
  "value": "20131007.jpg"
}
}

4.
NameAlternative
DescriptionAlternative Title (original title, subtitle, etc.)
The type attribute MUST be used to specify the type of title.
The lang attribute SHOULD be used to specify the language code.
RequirementSHOULD
Cardinality0..n

Guidelines for Use:

  • To improve searchability by title, it is recommended to add an alternative title when the original title contains numbers and/or special characters, or when numbers are originally written out as words. Examples:
    title: 1-2-3 mathematics = alternative: one two three mathematics.
    title: Kari & Bjarne on a fishingtrip = alternative: Kari and Bjarne on a fishingtrip.
    title: Tousand mountain peaks = alternative: 1000 mountain peaks.

  • An explanation of the type of title provided is required. The use of the type attribute should be meaningful to the submitter, reflect the metadata catalog or system, and be applied consistently (using a standardized format).

  • Language code should be specified. ISO 639-2 is used as the standard for indicating language when the lang attribute is applied.

Example:

{
"alternative": [
  {
    "type": "original title",
    "value": "Ola and Kari on fishing trip in Rondane",
    "lang": "eng"
  }
]
}

5.
NameCreator
DescriptionName or entity appearing in a central role (e.g. author, composer, film director, photographer, etc.).
Therole attribute SHOULD be used to define the specific role.
The type attribute SHOULD be used to indicate the type of entity. Allowed types include: Person, Organization, Personal Name, Corporate Name, Meeting Name, Uniform Title.
The authority attribute SHOULD be used to specify the authority source.
The lang attribute SHOULD be used to specify the language code.
RequirementSHOULD
Cardinality0..n

Guidelines for use:

  • The use of an authority register is recommended whenever one is available, both for personal names and corporate entities. The specific authority register used must be identified. An example of such a register is the Shared Authority Register for Persons and Corporate Bodies.

  • The creator should also be identified using their full name (first name, last name/corporation). Birth and death years may be included in parentheses after the name. Examples: Nesbø, Jo (1960– ), Shakespeare, William (1564–1616).

  • It should be specified whether the name refers to a person or a corporation. This is handled in different ways across various metadata catalogs and authority registers. Currently, the following values are allowed to define the type of name or entity, though additional types may be added if needed: Person, Organization, Personal Name, Corporate Name, Meeting Name (e.g., conference), Uniform Title (e.g., treaty, contract).

  • The role of the person or organization should be specified. Examples of roles include: author, composer, film director, photographer, creator, etc.

  • The use of the role attribute should be meaningful for the data provider, reflect the metadata catalog or system being used, and follow consistent (standardized) formatting.

  • Language code should be specified. ISO 639-2 is used as the standard for indicating language when the lang attribute is applied.

Examples:

{
"creator": [
  {
    "name": "Marek, Václav (1908-1994)",
    "type": "Person",
    "role": "Photographer",
    "lang": "eng",
    "authority": {
      "source": "Felles autoritetsregister (BARE)",
      "code": "90169632",
      "uri": "https://bibsys-almaprimo.hosted.exlibrisgroup.com/permalink/f/nelpa2/AUTREG90169632"
    }
  }
]
}
{
  "creator": [
  {
    "name": "Shakespeare, William (1564-1616)",
    "type": "Person",
    "role": "author",
    "lang": "eng",
    "authority": {
      "source": "Felles autoritetsregister (BARE)",
      "code": "9016555",
      "uri": "https://bibsys-almaprimo.hosted.exlibrisgroup.com/permalink/f/nelpa2/AUTREG9016555"
    }
  }
]
}

6.
NameContributor
DescriptionNames appearing in a central role (e.g., illustrator, photographer, co-author).
The role attribute SHOULD be used to specify the person’s or organization’s role.
The type attribute SHOULD be used to indicate the type of authority. Allowed values include: Person, Organization, Personal Name, Corporate Name, Meeting Name, Uniform Title.
The lang attribute SHOULD be used to define the language code.
RequirementSHOULD
Cardinality0..n

Guidelines for Use:

  • The rules for filling in the Contributor field are the same as for the Creator field. Examples of contributor roles may include: contributor, depicted person, illustrator, model, editor, designer, etc.

  • Language code should be specified. ISO 639-2 is used as the standard for indicating language when the lang attribute is applied.

Examples:

{
  "contributor": [
  {
    "role": "depicted",
    "type": "Person",
    "name": "Nordmann, Ola",
    "lang": "eng"
  },
  {
    "role": "depicted",
    "name": "Nordmann, Kari",
    "lang": "eng"
  }
]
}
{"contributor": [
  {
    "role": "illustrator",
    "type": "Person",
    "name": "Solberg, Erna",
    "lang": "eng",
    "authority": {
      "source": "Kulturnav",
      "code": "e762d909-5cce-4d2b-892b-258272514fde",
      "uri": "https://kulturnav.org/e762d909-5cce-4d2b-892b-258272514fde"
    }
  }
]
}

7.
NamePublisher
DescriptionNames appearing in a central role (the organization or entity that has published the resource).
The type attribute SHOULD be used to define the type of authority. Allowed types include: Person, Organization, Personal Name, Corporate Name, Meeting Name, Uniform Title.
The lang attribute SHOULD be used to specify the language code.
RequirementSHOULD
Cardinality0..n

Guidelines for use:

  • It is recommended to use an authority register if one is available. The specific authority register used, as well as the type of authority, must be indicated. Allowed types include: Person, Organization, Personal Name, Corporate Name, Meeting Name (e.g., conference), Uniform Title (e.g., treaty, contract). When using an authority register, the publisher’s full name should also be provided. The place and/or year of publication can be added in parentheses after the name. Example: National Library (Oslo, 1984).

  • Language code should be specified. ISO 639-2 is used as the standard for indicating language when the lang attribute is applied.

Example:

{
  "publisher": [
  {
    "name": "National library of Norway (Oslo, 1984)",
    "type": "Organization",
    "lang": "eng",
    "authority": {
      "source": "Felles autoritetsregister (BARE)",
      "code": "90362181",
      "uri": "https://bibsys-almaprimo.hosted.exlibrisgroup.com/permalink/f/nelpa2/AUTREG90362181"
    }
  }
]
}

8.
NameSpatial
DescriptionNames of relevant geographic locations (place names). These may refer to geographic locations such as countries, regions or cities that are significant to the resource.
The type attribute SHOULD be used to specify what type of place is being referred to.
The lang attribute SHOULD be used to indicate the language code.
RequirementSHOULD
Cardinality0..n

Guidelines for use:

  • Use ISO 3166-2 for specifying countries. Country codes should be placed in parentheses after the country name (e.g., Norway (NO)).

  • It is recommended to use official place name services or registries for specifying Norwegian place names. One example is the Central Place Name Register (SSR) provided by the Norwegian Mapping Authority (Kartverket). The source registry must be specified.

  • When using authority registries to specify spatial information, the full form of the place name should also be included. If no registry is used, the location should preferably be written in the following format: country; region/county; municipality; place; street.

  • Coordinates may be provided using latitude and longitude. The format should be as follows: latitude=61.85401 longitude=9.80856.

  • Examples of type might include place of publication, recording location, setting, place of printing, place of birth, etc. The use of the type attribute should be meaningful for the data provider, reflect the metadata catalog or system, and follow a consistent and standardized format.

  • Language code should be specified. ISO 639-2 is used as the standard for indicating language when the lang attribute is applied.

Examples:

{
"spatial": [
  { 
    "name": "Norway (NO);Innlandet;Stor-Elvdal;Rondane gjestegård",
    "type": "Depicted location",
    "lang": "eng",
    "authority": {
      "source": "Kulturnav",
      "code": "1031636c-0717-4d12-8895-fb88a7d4e952",
      "uri": "http://kulturnav.org/1031636c-0717-4d12-8895-fb88a7d4e952"
    },    
    "coordinateReferenceSystem": "EPSG:4326",
    "latitude": 61.788453,
    "longitude": 10.224725
  },
  { 
    "name": "Norge (NO);Innlandet;Lillehammer;Lillehammer"
  }  
]
}

9.
NameDate
DescriptionRelevant dates for the resource (such as publication, copyright, creation, digitization, etc., including the type of date and the corresponding year or value).
The type attribute MUST be used to specify what kind of date it is reffered to.
The lang attribute SHOULD be used to indicate the language code.
RequirementSHOULD
Cardinality0..n

Guidelines for Use:

  • The type of date and the corresponding year or value must be specified. ISO 8601-2 is the standard to be used.

  • The use of the type attribute should be meaningful for the data provider, reflect the metadata catalog or system, and be applied consistently with a standardized format.

  • Language code should be specified. ISO 639-2 is used as the standard for indicating language when the lang attribute is applied.

Examples:

{
  "date": [
  {
    "type": "Content date",
    "value": "1938",
    "lang": "eng"
  },
  {
    "type": "Digitized",
    "value": "2022-03-05T14:28:12+02:00",
    "lang": "eng"
  },
  {
    "type": "Published",
    "value": "2022-03-12",
    "lang": "eng"
  }
]
}

10.
NameLanguage
DescriptionLanguages relevant to the resource.
The lang attribute MUST be used to specify the language code.
The type attribute MUST be used to define what the language represents (e.g., subtitles, spoken language, written language, etc.).
RequirementSHOULD
Cardinality0..n

Guidelines for Use:

  • ISO 639-2 is used as the standard for indicating language when the lang attribute is applied.

  • The type of language representation must be indicated. Examples of language types include subtitles, spoken language, written language, etc.

  • The use of the type attribute should be meaningful for the data provider, reflect the metadata catalog or system, and be applied consistently using a standardized format.

Examples:

{
  "language": [
  {
    "type": "subtitle",
    "value": "english",
    "lang": "eng"
  }
]
}
{
  "language": [
  {
    "type": "written language",
    "value": "french",
    "lang": "eng"
  }
]
}

11.
NameRelation
DescriptionA related resource in which the described resource is physically or logically included (e.g., title of the parent or related work, collection, series, or part).
Attributes for title + type OR id + type MUST be used.
TheURI attribute SHOULD be used.
The lang attribute SHOULD be used to specify the language code.
RequirementSHOULD
Cardinality0..n

Guidelines for use:

  • The use of attributes may vary, but the type attribute and EITHER title attribute OR id attribute are always required.

  • The title attribute specifies the title of the related resource.

  • The type attribute indicates the nature of the relationship between resources. It is recommended to use terms from Dublin Core (conformsTo, hasFormat, hasPart, hasVersion, isFormatOf, isPartOf, isReferencedBy, isReplacedBy, isRequiredBy, isVersionOf, references, replaces, requires). If other terms are used for the type attribute, they should be meaningful to the data provider, reflect the metadata catalog or system, and be applied consistently with a standardized format.

  • An example of using the id attribute is to reference a series record, work record, or other resources within the same series or work.

  • The URI attribute is used to provide a link to the related resource (such as a catalog record or webpage).

  • Language code should be specified. ISO 639-2 is used as the standard for indicating language when the lang attribute is applied.

Examples:

{
  "relation": [
  {
    "title": "Norway from end to end with Ola and Kari",
    "type": "IsPartOf",
    "id": "987654321",
    "URI": "https://www.nb.no/items/eb57e3c314894b0120cf631104065e74?page",
    "lang": "eng"
  }
]
}
{
  "relation": [
  {
    "title": "Chronicles of Narnia",
    "type": "IsPartOf",
    "lang": "eng"
  }
]
}
{
  "relation": [
  {
    "title": "20161203.jpg",
    "type": "hasPart",
    "URI": "https://www.nb.no/items/83af9a36b005c5737aa33d1fb64f429d?page"
  }
]
}

12.
NameProvenance
DescriptionInformation about any changes that may affect the authenticity, integrity, or interpretation of the resource (e.g., ownership, management, etc.).
The lang attribute SHOULD be used to spesify the language code.
RequirementSHOULD
Cardinality0..n

Guidelines for use:

  • Language code should be specified. ISO 639-2 is used as the standard for indicating language when the lang attribute is applied.

Example:

{
  "provenance": [
  {
    "value": "The collection was donated to the National Library by Václav Marek on May 12, 1979.",
    "lang": "eng"
  }
]
}

13.
NameSubject
DescriptionSubject terms related to the resource.
The lang attribute SHOULD be used to specify the language code.
RequirementMAY
Cardinality0..n

Guidelines for use:

  • This field is used to describe the content or subject matter of the resource. Examples include words or expressions that indicate the subject, theme, events, landmarks, buildings, or time periods relevant to the resource.

  • Dewey Decimal Classification (DDC) values are valid.

  • References to authority registers may be used where applicable. When using authority registers, subject terms must also be written out in full.

  • Language code should be specified. ISO 639-2 is used as the standard for indicating language when the lang attribute is applied.

Examples:

{
  "subject": [
  {
    "value": "rondane",
    "lang": "nor"
  },
  {
    "value": "fishingtrip",
    "lang": "eng"
  },
  {
    "value": "nature",
    "lang": "eng"
  }
]
}
{
  "subject": [
  { 
    "value": "natur",
    "lang": "nor",
    "authority": {
      "source": "Kulturnav",
      "code": "1031536c-0717-4d12-8895-fb88a7d4e952",
      "uri": "http://kulturnav.org/1031636c-0717-4d32-8895-fb88a7d4e952"
    }
  }
]
}

14.
NameDescription
DescriptionDescription of the resource. The description may include a summary, a table of contents, a graphical representation or any free-text information about the resource.
The lang attribute SHOULD be used to specify the language code.
RequirementMAY
Cardinality0..n

Guidelines for use:

  • Language code should be specified. ISO 639-2 is used as the standard for indicating language when the lang attribute is applied.

Example:

{
  "description": [
  {
    "value": "The image is part of the collection of Václav Marek, who followed Ola and Kari Nordmann on their journey across Norway. Václav Marek was an Englishman with a strong interest in Norway and its natural environment.",
    "lang": "eng"
  }
]
}


Example containing all the metadata elements:

{
  "objectId": "av_6e8bc430-9c3a11d9",
  "priority": 50,
  "metadata": {
    "type":{
      "value": "image",
      "lang": "eng"
    }
    "identifier": [
      {
        "type": "URN",
        "value": "URN:NBN:no-nb_digifoto_20220311_00191_NB_PE_VM_M_05_09_01_036"
      },
      {
        "type": "image-id",
        "value": "NB_PE_VM_M_05_09_01_036",
        "lang": "eng"
      },
      {
        "type": "call-number",
        "value": "POEL00003975",
        "lang": "eng"
      }
    ],
    "title": {
      "value": "Ola and Kari on a fishingtrip in Rondane",
      "lang": "eng"
    },
    "alternative": [
      {
        "type": "original title",
        "value": "Ola and Kari on fishing trip in Rondane",
        "lang": "eng"
      }
    ],
    "creator": [
      {
        "name": "Marek, Václav",
        "type": "Person",
        "role": "Photographer",
        "lang": "eng",
        "authority": {
          "source": "Felles autoritetsregister (BARE)",
          "code": "90362181",
          "uri": "https://bibsys-almaprimo.hosted.exlibrisgroup.com/permalink/f/nelpa2/AUTREG90362181"
        }
      }
    ],
    "contributor": [
      {
        "role": "depicted",
        "type": "Person",
        "name": "Nordmann, Ola",
        "lang": "eng"
      },
      {
        "role": "illustrator",
        "type": "Person",
        "name": "Solberg, Erna",
        "lang": "eng",
        "authority": {
          "source": "Kulturnav",
          "code": "e762d909-5cce-4d2b-892b-258272514fde",
          "uri": "https://kulturnav.org/e762d909-5cce-4d2b-892b-258272514fde"
        }
      }
    ],
    "publisher": [
      {
        "name": "National library of Norway",
        "type": "Organization",
        "lang": "eng",
        "authority": {
          "source": "Felles autoritetsregister (BARE)",
          "code": "90362181",
          "uri": "https://bibsys-almaprimo.hosted.exlibrisgroup.com/permalink/f/nelpa2/AUTREG90362181"
        }
      }
    ],
    "spatial": [
      { 
        "name": "Norge (NO);Innlandet;Stor-Elvdal;Rondane gjestegård",
        "type": "Avbildet sted",
         "lang": "nor",
        "authority": {
          "source": "Kulturnav",
          "code": "1031636c-0717-4d12-8895-fb88a7d4e952",
          "uri": "http://kulturnav.org/1031636c-0717-4d12-8895-fb88a7d4e952"
        },    
        "coordinateReferenceSystem": "EPSG:4326",
        "latitude": 61.788453,
        "longitude": 10.224725
      },
      { 
        "name": "Norge (NO);Innlandet;Lillehammer;Lillehammer"
      }  
    ],
    "date": [
      {
        "type": "Content date",
        "value": "1938", 
        "lang": "eng"
      },
      {
        "type": "digitized",
        "value": "2022-03-05T14:28:12+02:00",
        "lang": "eng"
      },
      {
        "type": "published",
        "value": "2022-03-12",
        "lang": "eng"
      }
    ],
    "language": [
      {
        "type": "subtext",
        "value": "english",
        "lang": "eng"
      }
    ],
    "relation": [
     {
    "title": "Norway from end to end with Ola and Kari",
    "type": "IsPartOf",
    "id": "987654321",
    "URI": "https://www.nb.no/items/eb57e3c314894b0120cf631104065e74?page",
    "lang": "eng"
  }
    ],
    "provenance": [
      {
        "value": "The collection was donated to the National Library by Václav Marek on May 12, 1979.",
        "lang": "eng"
      }
    ],
    "subject": [
      {
        "value": "rondane",
         "lang": "nor"
      },
      {
        "value": "fishingtrip",
        "lang": "eng"
      },
    { 
    "value": "nature",
    "lang": "eng",
    "authority": {
      "source": "Kulturnav",
      "code": "1031536c-0717-4d12-8895-fb88a7d4e952",
      "uri": "http://kulturnav.org/1031636c-0717-4d32-8895-fb88a7d4e952"
    }
  }
    ],
    "description": [
      {
        "value": "The image is part of the collection of Václav Marek, who followed Ola and Kari Nordmann on their journey across Norway. Václav Marek was an Englishman with a strong interest in Norway and its natural environment.",
        "lang": "eng"
      }
    ]
  }
}
Last updated on - Github commit history ↗