Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,110 of 9,110 pages
About the help in other languages
All help pages

Library site checklist

One checklist for a library, archive or catalog site on Exponential - scope and planning, the record model, subject headings, search, files and licenses, exports and feeds, accessibility, launch, and the monthly routine…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/businesses/libraries/library-site-checklist.md

On this page

Library site checklist

This page is for the project lead of a library, archive or catalog site. It gathers the checks of this section in the order of a project, so you can copy it into your tracker and tick it off. Every item links to the page that explains it; nothing here is new.

Contents

  1. Planning
  2. Record model
  3. Subject headings
  4. Records in
  5. Search
  6. Files and digital collections
  7. Exports and feeds
  8. Accessibility and readers
  9. Launch
  10. Every month
  11. Every year

Planning

From Catalog planning:

  • To do: Scope written: what is in the site, and which system stays master for holdings and loans.
  • To do: It is understood that there is no MARC, Z39.50 or circulation support (Libraries and catalogs).
  • To do: Expected record numbers now and in three years.
  • To do: Record types listed; audiences and their tasks listed.
  • To do: Who catalogs, who approves, who owns the vocabulary.
  • To do: Languages of description decided.
  • To do: Measures for the monthly review chosen.

Record model

From Modeling catalog records:

  • To do: One class per record type; containers for collections and series.
  • To do: Fields with value datatypes for everything sorted, filtered or browsed (ezdate, ezselection, relations, tags).
  • To do: Identifiers such as the ISBN in their own fields, not translatable.
  • To do: Creators as Person or Organization objects, related with ezobjectrelationlist.
  • To do: Required, searchable and translatable set on purpose.
  • To do: Object name and URL alias patterns give readable names.
  • To do: Classes built on a development copy and moved as a package.

Subject headings

From Tagging and subject headings:

  • To do: Tag tree built: top terms, narrower terms, synonyms; shallow where possible.
  • To do: How related terms are handled is decided (they are not a built-in tag relation).
  • To do: Subjects field closed; a separate open keywords field only if wanted.
  • To do: Visitors have tags/read and tags/view; catalogers add only below their tags.
  • To do: Subject pages have a scope note.
  • To do: Tags translated for each language of description.

Records in

  • To do: Route decided: typed, script import, REST, RSS import or Writer import (Catalog planning).
  • To do: Imports use remote ids so they can run again without duplicates (Creating and updating content in code).
  • To do: A sample of real records reviewed by catalogers before the full import.
  • To do: Old collections published before feeds are announced.

From Catalog search:

  • To do: Searchable fields reviewed; index rebuilt after every large import.
  • To do: Results template shows counts, paging and what to try when nothing is found.
  • To do: Advanced search offered if readers need class or date filters.
  • To do: Text extraction programs installed if file contents must be found; scans made searchable before upload.
  • To do: Search statistics decided with the data protection contact.
  • To do: A dated decision on Solr (ezfind).

Files and digital collections

From Files and digital collections:

  • To do: Open, member and staff material separated by sections; downloads tested logged out.
  • To do: No direct links into var/.../storage/.
  • To do: Download links show format and size.
  • To do: Default license set for the installation and per record class; per-item licenses where they differ.
  • To do: Upload limits and disk space planned with the host.
  • To do: Visitor upload forms use enhancedezbinaryfile with a sensible MaxFiles and spam protection.

Exports and feeds

From PDF and print exports and Feeds for new acquisitions:

  • To do: Stored PDF exports hold only public material; restricted lists generated on the fly.
  • To do: A TrueType font configured if titles use non-Latin scripts.
  • To do: A named person regenerates stored exports.
  • To do: Feeds for new records active, one source per record class, links to the public site.
  • To do: Autodiscovery links in the pagelayout; /rss/feed/ not blocked in robots.txt.
  • To do: A recurring newsletter of new acquisitions, if planned, set up with consent (Newsletters).

Accessibility and readers

Launch

Every month

  • To do: Search phrases with no results reviewed; synonyms or records added.
  • To do: Content checks run: unreferenced files, broken relations, missing files (Content checks).
  • To do: Feeds opened in a feed reader; stored PDFs regenerated where needed.
  • To do: Roles reviewed for staff and volunteers who changed (Access reviews).

Every year

  • To do: Vocabulary reviewed: headings without records, headings with very many.
  • To do: Record classes reviewed against what catalogers actually fill in.
  • To do: The Solr decision reviewed against the catalog's size.
  • To do: Licenses of digital items reviewed with the rights holders.

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x