KBART introduction

The abbreviation KBART stands for “Knowledge Base And Related Tools”.

Goals

  • NISO “Best Practice” for the
    • Transmission of title lists of e-resources offered by a provider in a package.
    • Transmission of inventory information / holdings data from a provider for knowledge bases of link resolvers, ERM systems or discovery interfaces.
    • Data exchange: “KBART is on data exchange among and between knowledge bases”
  • Improvement of data quality exchanged between providers and knowledge bases.
  • Complement of existing metadata formats like ONIX-SOH.

Links

File format

File name

{ProviderName}_{Region/Consortia}_{PackageName}_{YYYY-MM-DD}.txt
  • ProviderName: Short name of the provider, e.g. Herdt, Springer, Emerald.
  • Region/Consortia: Geltungsbereich des Pakets
    • Region: If the package is only offered in one country or other regionally definable area, the country or region should be noted here. Example: Springer_Asia-Pacific_Medicine_2013-01-28.txt.
    • Consortia: If the package is tailored for a consortia, that should be noted here. Example: IOP_NESLi2_Option1-2011_2012-05-31.txt.
    • If the package is available worldwide “Global” should be added to the file name. Example: TaylorandFrancis_Global_AllTitles_2012-08-30.txt.
  • PackageName: Name for the package.
      • Unique name of the package or provider unique short name of the package.
      • For package with all titles of a provider add “AllTitles” or “AllJournals”. Example:

    TaylorandFrancis_Global_AllTitles_2012-08-30.txt.

  • YYYY-MM-DD: date of the KBART file in ISO-8601 format

File Content

  • Tab as separator
  • UTF-8 encoded
  • Date information according to ISO 8601
  • No empty line between header and content
  • Titles should be sorted alphabetically
  • A title should be listed multiple times if there is a “coverage gap” of at least 12 months

KBART fields

Field NameDescriptionSerial/Monograph
publication_titlePublication title for serial or monograph. Conference proceedings series titles should be entered as serial titles, while volume titles should be entered as monograph titles.S/M
print_identifierPrint-format identifier. ISSN for serials, ISBN for monographs, etc. Conference proceedings may have serial ISSNs while each proceeding volume may have its own ISBN.S/M
online_identifierOnline identifier. eISSN for serials, eISBN for monographs, etc. Conference proceedings may have serial eISSNs while each proceeding volume many have its own eISBN.S/M
date_first_issue_onlineDate of first serial issue available online. Applicable only to serials.S
num_first_vol_onlineNumber of first volume available online. Applicable only to serials.S
num_first_issue_onlineNumber of first issue available online. Applicable only to serials.S
date_last_issue_onlineDate of last issue available online. Leave blank if coverage is to the present. Applicable only to serials.S
num_last_vol_onlineNumber of last volume available online. Leave blank if coverage is to the present. Applicable only to serials.S
num_last_issue_onlineNumber of last issue available online. Leave blank if coverage is to the present. Applicable only to serials.S
title_urlTitle-level URL. Applicable to both serials and monograph. For conference proceedings, the title_url for the proceedings series and the title_url for each volume should be different.S/M
first_authorFirst author. Applicable only to monograph.M
title_idTitle identifier. Applicable to both serials and monographs. For conference proceedings, the title_id for the conference proceedings series and the title_id for each proceeding volume should be different.S/M
embargo_infoEmbargo information. Describes any limitations on when resources become available online.S/M
coverage_depthCoverage depth. For example, abstracts or full text.S/M
notesNotesFree-text field to describe the specifics of the coverage policy.S/M
publisher_namePublisher name. Not to be confused with third-party platform hosting name.S/M
publication_typeSerial or monograph. Use “serial” for journals and conference proceeding series. Use “monograph” for e-books and conference proceeding volumes.S/M
date_monograph_published_printDate the monograph is first published in print.M
date_monograph_published_onlineDate the monograph is first published online.M
monograph_volumeNumber of volume for monograph. Applicable to e-books and conference proceedings. For proceedings, use the volume within the conference proceedings series.M
monograph_editionEdition of the monograph.M
first_editorFirst editor, Applicable to monographs, i.e., e-books or conference proceedings volumes.M
parent_publication_title_idTitle identifier of the parent publication. For a conference proceeding volume, the parent_publication_title_id is the title_id of the conference proceedings series. 
preceding_publication_title_idTitle identifier of any preceding publication title. Applicable to serials and conference proceedings series.S
access_typeAccess type. „F“ (Free) or „P“ (Paid).S/M

Proprietary GOKB fields

Field NameDescriptionSerial/Monograph
zdb_idTitle ID from ZDB journal databaseS
last_changedDate of last change.S/M
access_start_dateDate when the title was added the package. Date of earliest possible access via package license.S/M
access_end_dateDate when title removed from the package. Date of last possible access via package license.S/M
mediumDetailed media type of the publication.S/M
doi_identifierDOI identifierM
ezb_idTitle ID from EZB journal databaseS
monograph_parent_collection_titleExtension for series titlesS/M
subject_areaSubject classes. DDC or choose other via namespaces.S/M