Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

General formatting

Package names in GOKb should have the following general format:
{ContentProvider}:{Package name}

Whenever possible, the package name should be the name that the content provider gives to the package at the source.

If the content provider does not assign a name or uses a name that is too vague to be useful, you will need to construct a name yourself. You will want to consider including the following elements:

Subject (not repeatable) could be any phrase describing a package’s topical content/scoping. These are important to distinguish packages from providers that sell their titles in subject packages and whose lists may otherwise have the same name. The subject may be part or all of the package name.

Package scope (not repeatable) refers to the coverage of the package. The most common scope terms used in package names will be "front file" and "back file." You may also use the scope term "all titles" to refer to a package that contains a provider's complete holdings.

Scope (repeatable) could be a Year or string with scoping meaning, e.g., “title list,” “catalog,” “master list,” “backfile list,” etc. It is noted that Ref Data values encode what we care about controlling here, i.e. valid date and scope (extent). If there is a year, it should appear as the last scope statement. The year should define the content of the package as it was sold during a particular year (NOT the year the package file was created).

Examples

Elsevier:Freedom Collection

JSTOR:Arts and Sciences I

Sage:Premier 2010

Taylor & Francis:Environmental Science Backfile

Sage:A to Z List

 

 

  • No labels