Versions Compared

Key

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

...

  • Division: Putting the fiction and nonfiction books in separate sections instead of mixing them together.
  • Pagination: Putting 50,000 books on 100 small pages, rather than all on one huge page.

OPDS as user interface

When the SimplyE mobile app is pointed at an OPDS server, the links between OPDS feeds determine the graphical user interface shown to SimplyE, just as the links between HTML pages become the user interface of a website. There are two main features of OPDS which elevate it past just a big scrolling list of books:

...

(Note that the SimplyE mobile app doesn't actually support navigation feeds yet. Grouped feeds offer a nicer version of the same functionality, but it's more work on your end.)
If your OPDS feed is intended for distributing books through other institutions, rather than for direct consumption by the SimplyE App, you should probably just create a simple paginated list of books with the newest books at the top.

Static generation

In most cases, it's preferable to generate your OPDS feeds statically ahead of time. As your collection becomes more complicated, it may be more practical to generate OPDS feeds as needed and cache them.

Info
titleCommon Issues
  • Metadata does not specify the works language - a book that has no language will be imported but it will never be shown to any particular patron, since there's no situation where we believe the language is compatible with the patron's language settings
  • Metadata does not specify nonfiction.
  • Metadata does not specif audience
  • Classifications not included in OPDS Feed see below

Classifications

The Classification the CM can use to organize and process works into the catalog.

The following should be brought in if used for classifying works or used when constructing OPDS feeds intended to be used in SimplyE.

...