Get and check KBART files
Package and title data are imported into GOKB from KBART files.
KBART is a NISO standard for representing titles in a package of e-resources. A corresponding example KBART file, which also contains GOKB-relevant extensions of the standard as well as explanations of the individual KBART fields, can be found here: KBART introduction.
Validation of the KBART file
Make sure that the KBART file is correct, i.e.
- KBART files must comply with the KBART standard:
- The field names and contents must comply with the KBART standard or the enhanced GOKB format. A list of all fields can be found here.
- All column headers must exist – even if a column has no values.
- The character encoding must be UTF-8.
- Tab as separator.
- Preferably alphabetical order of the titles.
- The file must contain all current titles of the package offered by the provider, i.e.
- The title scope and content must correspond to the negotiated package.
- The access URLs for individual titles must be correct. They must also be universally valid URLs, not institution-specific URLs like proxy URLs.
- Each resource must be tagged with identifiers.
- For serial publications like journals, the coverage information (years) must be correct. For example, if only volumes from 1996 onward are offered in a package, this must be reflected in the appropriate columns of the KBART list.
Mandatory fields for serials (e-journals, serials)
Element | KBART field | Mandatory/Optional | Notes |
---|---|---|---|
Publication type | publication_type | Mandatory | Essential for distinction of E-Book and E-Journal |
Publication title | publication_title | Mandatory | |
ZDB identifier | zdb_id | Optional* | At least one identifier must be provided |
Electronic ISSN | online_identifier | Optional* | At least one identifier must be provided |
Print ISSN | print_identifier | Optional* | At least one identifier must be provided |
Proprietary identifier used by the content provider | title_id | Optional* | At least one identifier must be provided |
Coverage start | date_first_issue_online | Mandatory | |
num_first_vol_online | Optional | ||
num_first_issue_online | Optional | ||
Coverage end | date_last_issue_online | Optional | |
num_last_vol_online | Optional | ||
num_last_issue_online | Optional | ||
Coverage depth (fulltext, abstracts) | coverage_depth | Mandatory | |
Title level URL | title_url | Mandatory | |
Media type | medium | Optional |
Mandatory fields for monographs (e-books, audio and video streams)
Element | KBART field | Mandatory/Optional | Notes |
---|---|---|---|
Publication type | publication_type | Mandatory | Essential for distinction of E-Book and E-Journal |
Publication title | publication_title | Mandatory | |
Electronic ISBN | online_identifier | Optional* | At least one identifier must be provided |
Digital Object Identifier (DOI) | doi_identifier | Optional* | At least one identifier must be provided |
Proprietary identifier | title_id | Optional* | At least one identifier must be provided |
Print ISBN | print_identifier | Optional | |
Date when monograph was published online | date_monograph_published_online | Mandatory | |
Volume number | monograph_volume | Optional | |
Edition number | monograph_edition | Optional | |
Series statement for a series title | monograph_parent_collection_title | Optional | |
Author | first_author | Optional | |
Editor | first_editor | Optional | |
Title level URL | title_url | Mandatory | |
Media type (journal, book, database) | medium | Fakultativ |
GOKB supports the enhancement of KBART with some proprietary fields:
- For serial publications, the ZDB id can be added to the field
zdb_id
. - Dates when a title is added or removed for a package can be added to
access_start_date
andaccess_end_date
fields. These dates are useful for obtaining the historical status of a package at a particular time. - For series of monographs the series statement can be added to :
monograph_parent_collection_title
. - Use field
medium
for different media type.
Notes
- Make sure to import generic title lists into GOKB for each package. Special, locally tailored packages (e.g. different access URL via proxy) from these generic packages, should only be used in local ERM systems.
- For journal lists, make sure that each title has either a ZDB id, an e-ISSNs, or at least a corresponding print ISSN.
- All titles, especially from e-book packages, should have an internal, provider specific title ID (
title_id
), as other identifiers such as ISBNs are often ambiguous.