Versions Compared

Old Version 3

changes.mady.by.user Unknown User (jamesenglish)

Saved on

compared with

New Version 4

changes.mady.by.user Unknown User (jamesenglish)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This should help you identify which problem applies to your book. (The known possible problems are listed immediately below.)

  • The book must have been imported correctly. It must have Identifier, an Edition, a LicensePool, and it must belong to a Work. Getting this right depends on the Monitor that imported the book in the first place.
  • The Work must be presentation-ready: it must have the minimal bibliographic information necessary to show to library patrons, and it must have gone through the classification process. Again, this is the responsibility of the importing Monitor.
  • The Work must have a cached OPDS entry. This is created as part of the task of making the Work presentation-ready, but it can be redone by running the bin/repair/work_opds script.
  • The LicensePool must be associated with at least one compatible DeliveryMechanism. If the book is not available in any particular format, or it's only available in formats that are not compatible with SimplyE, it will not show up in feeds. This, too, is the responsibility of the importing Monitor.
  • LicensePool.owned_licenses must be at least 1. If the library does not own any licenses for the book, it won't show up. If holds are disabled for the library, then LicensePool.available_licenses must also be at least 1.
  • The LicensePool must not be suppressed. Suppressing a LicensePool is a largely manual process done through the administrative interface.
  • The Work must be present in the materialized views, which are used to build the lanes. The materialized views are updated once a day, through the bin/refresh_materialized_viewsscript.
  • The CachedFeeds cache may contain an old version of a lane which was built before the book was imported, or before some other problem with the book was fixed. Since the materialized view is not being queried, this can make it look like a book is still not in the collection. By default, list-type feeds are cached for twenty minutes. Grouped feeds are cached forever, until they are replaced by running bin/cache_opds_blocks.
  • If a book shows up in list-type feeds but not in search results, it may not have been added to the ElasticSearch index. This can be repaired using the bin/repair/search_index script.

 

Panel
bgColor#fff
titleCommon Problems
  1. The book must have been imported correctly. It must have Identifier, an Edition, a LicensePool, and it must belong to a Work. Getting this right depends on the Monitor that imported the book in the first place.
  2. The Work must be presentation-ready: it must have the minimal bibliographic information necessary to show to library patrons, and it must have gone through the classification process. Again, this is the responsibility of the importing Monitor.
  3. The Work must have a cached OPDS entry. This is created as part of the task of making the Work presentation-ready, but it can be redone by running the bin/repair/work_opds script.
  4. The LicensePool must be associated with at least one compatible DeliveryMechanism. If the book is not available in any particular format, or it's only available in formats that are not compatible with SimplyE, it will not show up in feeds. This, too, is the responsibility of the importing Monitor.
  5. LicensePool.owned_licenses must be at least 1. If the library does not own any licenses for the book, it won't show up. If holds are disabled for the library, then LicensePool.available_licenses must also be at least 1.
  6. The LicensePool must not be suppressed. Suppressing a LicensePool is a largely manual process done through the administrative interface.
  7. The Work must be present in the materialized views, which are used to build the lanes. The materialized views are updated once a day, through the bin/refresh_materialized_viewsscript.
  8. The CachedFeeds cache may contain an old version of a lane which was built before the book was imported, or before some other problem with the book was fixed. Since the materialized view is not being queried, this can make it look like a book is still not in the collection. By default, list-type feeds are cached for twenty minutes. Grouped feeds are cached forever, until they are replaced by running bin/cache_opds_blocks.
  9. If a book shows up in list-type feeds but not in search results, it may not have been added to the ElasticSearch index. This can be repaired using the bin/repair/search_index script.

...