Supported library types

For a compatibility list, see http://en.opacapp.net/compatibility/

Bibliotheca

Implementation for Bibliotheca Web Opacs, originally developed by BOND, now owned by OCLC. Known to work well with Web Opac versions from 2.6, maybe older, to 2.8

Technical difficulties

• Everything is session-based, direct hyperlinks are possible to hardly anything
• We only get to now the book's unique IDs from a HTML comment on the search result pages
• In every city, the amount and order of table columns of 3 tables is different

Additional data needed in JSON file

Example file:

{
    "api": "bibliotheca", 
    "city": "Mannheim", 
    "data": {
        "accounttable": {
            "author": 1, 
            "barcode": 0, 
            "homebranch": 5, 
            "lendingbranch": 6, 
            "prolongurl": 7, 
            "returndate": 3, 
            "status": 4, 
            "title": 2
        }, 
        "baseurl": "http://katalog.mannheim.de/wopac", 
        "copiestable": {
            "barcode": 0, 
            "branch": 1, 
            "department": 2, 
            "location": 3, 
            "reservations": 6, 
            "returndate": 5, 
            "status": 4
        }, 
        "information": "/../read/info.html", 
        "mediatypes": {
            "MDVD.gif": "DVD", 
            "cdkl.gif": "LP_RECORD", 
            "cdromkl.gif": "CD_SOFTWARE", 
            "ekl.gif": "EBOOK", 
            "mBuchSsich.gif": "BOOK", 
            "mBuecherS.gif": "PACKAGE", 
            "mCasetteS.gif": "AUDIO_CASSETTE", 
            "mFilmS.gif": "MOVIE", 
            "mMusikCDS.gif": "CD_MUSIC", 
            "mNoten1S.gif": "SCORE_MUSIC", 
            "mZtgS.gif": "NEWSPAPER", 
            "mhoerbuchS.gif": "AUDIOBOOK", 
            "spielekl.gif": "BOARDGAME", 
            "tafelkl.jpg": "SCHOOL_VERSION"
        }, 
        "reservationtable": {
            "author": 0, 
            "availability": -1, 
            "branch": 3, 
            "cancelurl": 5, 
            "expirationdate": 2, 
            "title": 1
        }
    }, 
    "geo": [
        49.4874592, 
        8.466039499999999
    ], 
    "group": "Baden-W\u00fcrttemberg", 
    "support": "Katalogsuche und Konto", 
    "title": "Stadtbibliothek"
}

The three extra arrays in data are due to the fact that in each city the order of columns in tables like the table of existing copies of a book is different. The three arrays specify those orders. The mapping is as follows:

• copiestable (Table of existing copies of a search result - mapping from content to column index)
• accounttable (Table of borrowed books)
• reservationtable (Table of reserved books)
• mediatypes (optional): A mapping of image file names to de.geeksfactory.opacclient.objects.SearchResult.MediaType constants
• db (optional): Database name (used for Web-Opac installations which have multiple databases)

A copiestable array like [0, 2, -1, …] would mean: "Column 0 contains the barcode, Column 2 contains the point of presence, there is no column containing the department, …"

SISIS SunRise

This software for example is in use in Bonn.

Technical difficulties

• Everything is session-based, direct hyperlinks are possible to hardly anything
• We only get to now the book's unique IDs in some installations which have a extension called BibTip and reveals the IDs in some div to be used by BibTip's javascript. The ID is also hidden in some reservation links.

Zones 2.2

This software is in use in Hamburg and Koeln and does not require special data in the configuration.

aDIS/BMS

This software does not require one special parameter in the configuration, data.startparams.

BiBer Bibdia

Starting with Offenburg, @ruediger-w implemented support for some of the BiBer library systems. Configuration is similar to Bibliotheca. More information will follow.

OCLC PICA

Starting with UB Kiel, @johan12345 implemented support for PICA library systems.

PICA Libraries need the following data in their JSON file:

"data": {
        "accountSupported": true, 
        "baseurl": "http://kiopc4.ub.uni-kiel.de:8080/", 
        "db": "1", 
        "httpsbaseurl": "https://lhopc4.ub.uni-kiel.de/", 
        "customssl": true, 
        "information": "http://www.ub.uni-kiel.de/"
    }, 

• accountSupported: (Optional) Boolean value that determines if the library supports accounts. Libraries like Uni Kiel are supported, where the URL of the login form contains USERINFO_LOGIN. UB Weimar, for example, isn't supported (its URL contains LBS_WEB/login.htm), but if we have a test account, we could probably add support for that, too.
• baseurl: The base URL of the catalogue
• db: The DB number of the OPAC. Sometimes, there are multiple OPACs on the same server, with different DB numbers. You can see the number in the URL (for example .../DB=2/...)
• httpsbaseurl: (Optional) When the catalogue has https access, you should specify this URL so that a secure connection is used.
• customssl: (Optional) Some libraries need their SSL certificates added to the ssl_trust_store.bks file. If you did this, set this boolean value to true.
• information: URL with information about the library

Fleischmann iOPAC

Starting with Stadtbücherei Schleswig, @johan12345 implemented support for Fleischmann iOPAC library systems.

iOPAC Libraries need the following data in their JSON file:

"data": {
        "baseurl": "http://176.94.16.49", 
        "information": "http://stadtbuecherei-schleswig.de/", 
        "maxprolongcount": 1
    }, 

• baseurl: The base URL of the catalogue
• information: URL with information about the library
• maxprolongcount: (Optional) Because iOPAC libraries do not show if a book is prolongable in their account interface (only the number of prolongings), this is an artificial boundary. If this is not set, the prolonging button will be available every time and give an error message if the book is not prolongable any more.

Technical difficulties

• It isn't visible if a book is prolongable or not (see above)
• When more than 200 results are found, the real result count is only shown on the next page. Currently, we show "200 results" on the first page and then update the result count when the second page was loaded.

WebOPAC.net

Starting with Gemeindebibliothek Nürensdorf, @johan12345 implemented support for WebOPAC.net library systems. The current version 2.2.70 of the OPAC is supported. WebOPAC.net was really simple to implement and runs extremely fast because it provides a JSON interface that the mobile version uses.

WebOPAC.net libraries currently don't need any additional info in the JSON file, only the baseurl (for example http://www.winmedio.net/nuerensdorf) and the information URL.