FAQ – Frequently Asked Questions
Using the GOKB
Go to the URL of the GOKB (or test system) auf. Click on the person icon in the top right corner and choose between Login or Register.
Detailed information can be found in our Documentation.
On the login screen, click Forgot password. Enter your username. You will then receive an email with a link to reset your password.
If you have any problems, please send an e-mail to: support@gokb.org.
Under Dokumentation you will find instructions and tips on how to use the GOKB.
We also offer training on request. Please contact info@gokb.org.
You can always contact us by email at support@gokb.de or info@gokb.org.
SAGE maintains its data in the GOKB. There is interest in adding other providers. The community makes the contact and the GOKB team takes over the discussions. We are currently in dialogue with other providers.
If you are uploading more than 10,000 titles, please let us know so we can coordinate server usage. Please contact support@gokb.org.
The GOKB UUID is a unique internal identifier for a component (package, provider, reference title, package title, review request, etc.). The UUID can be used to create a stable URI (‘Cool URI’). This serves as a permanent backlink to the GOKB dataset and can therefore be delivered via the interfaces.
We are working with the EZB so that the national journal licences maintained there, including all updates, are transferred to the GOKB. The EZB will remain the source system for these licences. It is important that the packages in the EZB are approved by the package maintainers there.
The Access Start Date describes the date when the title was added to the package and licence holders were given access to that title. The Access End Date describes when a title was removed from the package.
Coverage, on the other hand, relates directly to the title and provides information such as the publication period of journals and the type of coverage (full text, abstracts, etc.).
Packages
If you find a duplicate in the GOKB, please contact support@gokb.org.
Please contact the registered curatory group with your enquiry. If no curatory group is registered, please contact support@gokb.org.
ZDB-Sigel can be entered when creating packages.
Last list verification is related to the list status. The date is updated whenever the list status is changed from in process to Checked. This is only possible when the verification requests have been completed.
Last updated shows when the package was last modified (package details, title, etc.). The date is relevant for third party systems to receive updates from the GOKB.
Yes, package titles can be archived. If this data is maintained appropriately, a package status for a specific date can be viewed in the Access tab. The data is also set automatically when titles are removed from or added to the KBART list during a package update.
DDCs at title level and package level are not interdependent. There is no automatic inheritance because the package DDC may not match all titles.
Individual subscriptions to journals are part of individual agreements with providers. For these cases, local packages can be created in the GOKB. See our Documentation for more information. ERM systems often offer the possibility to manage individual subscriptions.
The List Status controls the release of packages between the GOKB and FOLIO. A newly created package is automatically given the List Status In progress. This must be changed to Checked once the package has been processed. Please note that the List Status can only be changed after the review requests have been processed. The List Status Checked is mandatory for packages to be uploaded to FOLIO.
The Editing Status is for information only. The default status is In Progress. The status settings can be used for internal workflows.
Both statuses can be filtered.
If the status of a title in the GOKB is set to retired or deleted, this change will be passed on to FOLIO. We therefore advise against manual status changes for global packages. In the case of automatic and manual updates, the status of the titles is automatically adjusted when changes are made.
If you select this field, the contents of the package will not be completely updated, but only the titles from the KBART file will be added. Make sure that the structure of the list is the same, including the same namespace under title_id.
Curatorship
An institution (usually a library, less often a consortium administration or a commercial provider) that is responsible for the maintenance, correctness and up-to-dateness of packages in the GOKB. The curatorship of GOKB components can be transferred after consultation with the GOKB team. All GOKB users are organised into curatory groups.
You can choose a curator group when you register. If your institution is not yet in the GOKB, please contact support@gokb.org.
In addition to packages that you create, you can also become a curator for ‘orphaned’ packages (packages without a curatory group) and packages that are no longer being kept up to date.
To do this, write to the curatory group listed for that package, or send an email to support@gokb.org.
Please contact support@gokb.org so that we can clarify the next steps.
We recommend that you contact the consortium office and inform them that the packages are required in the GOKB. However, you can also import the package into the GOKB yourself. It is always possible to change the curatory group (from the institution to the consortium office).
Please send an email to support@gokb.org. We will look into the case.
Content providers & platforms
In this case, please contact support@gokb.org.
This will vary from case to case. In such cases, please contact info@gokb.org.
The IP addresses are 193.174.240.28 for the GOKB and 193.174.240.29 for the test system.
There are different provider namespaces to avoid mismatches via the title_id. Different providers internally identify their titles independently – some with numbers, some with letters, some with combinations of numbers and letters.
For example, it is possible for two providers to use the same number internally for completely different titles. To avoid suggesting a false match in the GOKB, they must be recorded in different namespaces, e.g. Cambridge University Press and Springer.
KBART
This tool allows you to validate KBART files and display errors independently of the import process. The KBART Validator can also be used without logging in.
The strict mode checks the KBART files to be validated according to the NISO standard. In non-strict mode, values automatically interpolated by the GOKB are also accepted.
In this case, ask your provider directly for data in KBART format. You can also contact major publishers (such as Springer, Emerald, etc.) who already use KBART as standard.
This could be because another package is being uploaded at the same time. Please wait a moment and check the progress again. If the problem persists, please contact support@gokb.org.
Please do not re-import the KBART file!
Review requests
Review requests can only be viewed with a login! They are displayed on the dashboard, under review requests, and in the package and reference title details.
Review requests for reference titles without a curatory group can be edited by all users.
See our Documentation for more information.