Zen

Source string Source string

303/10000 · 303

The string is read only.

English Actions
In this context, a user is a staff user who has some involvement with the License. They could be staff involved in negotiating or signing the license for example.
You can attach multiple users to a license.
In order to be attached to a license a staff user must have the :ref:`erm permission <permission-erm-label>` (or the :ref:`superlibrarian permission <permission-superlibrarian-label>`), otherwise they will not appear in the list when you try and select a user. This also keeps the list of patrons to a small, manageable, size by excluding your library patrons.
|licenseuser|
License documents
You can attach one or more documents to a license record. From here you can attach PDF copies of license or terms of use.
The physical location is where any paper version of the correspondence is held in the library and the URI provides a link to any online copy.
The file size of any uploaded documents for both licenses and agreements is limited to the value of the max_allowed_packet size in your MariaDB configuration file. If you exceed this size, you will get a file size warning. Speak to your system administrator to increase this value.
|ermfilesize|
Search and view a license record
|licensespage|
You will be presented with a list of existing licenses in the system ordered by the license name. You can use the table or column filters to search and filter data you are looking for (for example, all licenses with the Status: expired).
You can customize the columns of this table by clicking the 'Configure' button. It will take you to the Administration module and specifically to the 'table id: licenses' section of the :ref:`Table settings <column-settings-label>`.
Clicking on the name of the license will take you through to the full view.
|licensefullview|
The full view summarizes all the information you entered when you were creating the license. The vendor it is attached to (which is a hypertext link to the vendor record), the Status, Type, start and end dates, any users associated with the license and, importantly, the link to the license document(s).
eHoldings
Definition of terms:
**Resource**
A resource is an instance of a title. Consequently a resource would have a separate resource ID for each occurrence of the title in a package.
For example: Teise / Law belongs in
DOAJ
Criminal Justice Abstracts with Full Text
etc.
**Knowledge base (KB)**
A knowledge base is an extensive database maintained by a knowledge base supplier (for example, EBSCO) that contains information about electronic resources such as title lists and coverage dates, etc. Knowledge bases typically organize the resources provided by a content provider into collections or databases that reflect specific content provider offerings, for example packages of e-journals, e-books, or other materials.
**Providers**
The provider of the e-resource, for example, the vendor, consortia or publisher.
**Packages**
A collection of e-resource titles bundled together and distributed by a provider.
**Titles**

Loading…

User avatar None

Source string added

  1. koha-manual
  2. erm
  3. English
The full view summarizes all the information you entered when you were creating the license. The vendor it is attached to (which is a hypertext link to the vendor record), the Status, Type, start and end dates, any users associated with the license and, importantly, the link to the license document(s).
a year ago
Browse all string changes

Things to check

Unpluralised

The string is used as plural, but not using plural forms

Reset

Glossary

English English
No related strings found in the glossary.

String information

Flags
read-only
Source string location
../../source/erm.rst:346
String age
a year ago
Last updated
4 months ago
Source string age
a year ago
Translation file
string 92