IIIF Bookshelf Webapp

This is a webapp for collecting IIIF representations of books. It is based on the functionality of the IIIF Presentation API for modelling books. You can add books to your bookshelf by loading the manifest.json of the book.

Development Quickstart using Docker Compose

Install Docker according to the official Docker documentation.

Add your user to docker group to run docker without sudo:

$ sudo groupadd docker
$ sudo gpasswd -a yourusername docker
$ sudo service docker restart

Install Docker Compose according to the official documentation.

To get the Bookshelf quickly up running, you can start all backend services using Docker Compose:

$ docker-compose build
$ docker-compose up -d

Then Solr and MongoDB are running in containers and everything is ready for running a local instance of IIIF Bookshelf Webapp (see below).

To start the IIIF Bookshelf Webapp, you have to run:

$ java -jar iiif-bookshelf-exec.jar

The Bookshelf is now running under http://localhost:8080/.

To stop the containers run

$ docker-compose stop

To delete the containers and all data:

$ docker-compose down

Requirements

Java 8: You will need the Java Runtime Environment (JRE) version 1.8 or higher. At a command line, check your Java version with "java -version".
MongoDB Version: 3.2.4+
Apache Solr Version: 5.4.1+

Mongo DB

Homepage: https://www.mongodb.com/
Version: 3.2.9

Installation

Download the binary files for the desired release of Mongo DB from official Mongo DB Downloads Page. To download the latest "Linux 64-bit legacy x64"-release through the shell:

$ cd ~/Downloads
$ curl -O https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-3.2.9.tgz

Extract the files from the downloaded archive:

$ cd ~/Downloads
$ tar xvfz mongodb-linux-x86_64-3.2.9.tgz

Copy the extracted archive to the target installation directory. Example:

$ sudo mkdir -p /opt
$ sudo mv mongodb-linux-x86_64-3.2.9/ /opt

Configuration

Ensure the location of the executables is in the PATH variable.

SuSE Linux:

$ sudo vi /etc/profile.d/mongodb.sh

# Add paths for mongo db
if [ -d /opt/mongodb-linux-x86_64-3.2.9/bin ]; then
    COUNT=`ls -1 /opt/mongodb-linux-x86_64-3.2.9/bin/ | wc -l`
    if [ $COUNT -gt 0 ]; then
        PATH="$PATH:/opt/mongodb-linux-x86_64-3.2.9/bin"
    fi
fi
export PATH=$PATH

$ sudo vi /etc/profile.d/mongodb.csh

# Add paths for mongo db
if ( -d /opt/mongodb-linux-x86_64-3.2.9/bin ) then
    set COUNT=`ls -1 /opt/mongodb-linux-x86_64-3.2.9/bin/ | wc -l`
    if ( $COUNT > 0 ) then
        setenv PATH "${PATH}:/opt/mongodb-linux-x86_64-3.2.9/bin"
    endif
endif

Ubuntu Linux:

$ sudo vi /etc/environment
...
PATH="/opt/mongodb-linux-x86_64-3.2.9/bin:$PATH"
...

Test it (after reboot or sourcing of file):

($ . /etc/environment)
$ mongod --version
db version v3.2.9
git version: 22ec9e93b40c85fc7cae7d56e7d6a02fd811088c
allocator: tcmalloc
modules: none
build environment:
    distarch: x86_64
    target_arch: x86_64

Usage

To run MongoDB, run the mongod process at the system prompt. If you do not use the default data directory (i.e., /data/db), specify the path of the data directory using the --dbpath option. Example:

$ sudo mkdir -p /local/mongodb/data
($ sudo chmod 777 /local/mongodb/data)
$ mongod --dbpath /local/mongodb/data
2016-09-01T12:58:32.531+0200 I CONTROL  [initandlisten] MongoDB starting : pid=18076 port=27017 dbpath=/local/mongodb/data 64-bit host=ralf-linux
2016-09-01T12:58:32.531+0200 I CONTROL  [initandlisten] db version v3.2.9
2016-09-01T12:58:32.531+0200 I CONTROL  [initandlisten] git version: 22ec9e93b40c85fc7cae7d56e7d6a02fd811088c
2016-09-01T12:58:32.531+0200 I CONTROL  [initandlisten] allocator: tcmalloc
2016-09-01T12:58:32.531+0200 I CONTROL  [initandlisten] modules: none
2016-09-01T12:58:32.531+0200 I CONTROL  [initandlisten] build environment:
2016-09-01T12:58:32.531+0200 I CONTROL  [initandlisten]     distarch: x86_64
2016-09-01T12:58:32.531+0200 I CONTROL  [initandlisten]     target_arch: x86_64
2016-09-01T12:58:32.531+0200 I CONTROL  [initandlisten] options: { storage: { dbPath: "/local/mongodb/data" } }
2016-09-01T12:58:32.573+0200 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=8G,session_max=20000,eviction=(threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),
2016-09-01T12:58:32.723+0200 I CONTROL  [initandlisten]
2016-09-01T12:58:32.723+0200 I CONTROL  [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/enabled is 'always'.
2016-09-01T12:58:32.723+0200 I CONTROL  [initandlisten] **        We suggest setting it to 'never'
2016-09-01T12:58:32.723+0200 I CONTROL  [initandlisten]
2016-09-01T12:58:32.723+0200 I CONTROL  [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/defrag is 'always'.
2016-09-01T12:58:32.723+0200 I CONTROL  [initandlisten] **        We suggest setting it to 'never'
2016-09-01T12:58:32.723+0200 I CONTROL  [initandlisten]
2016-09-01T12:58:32.724+0200 I FTDC     [initandlisten] Initializing full-time diagnostic data capture with directory '/local/mongodb/data/diagnostic.data'
2016-09-01T12:58:32.724+0200 I NETWORK  [HostnameCanonicalizationWorker] Starting hostname canonicalization worker
2016-09-01T12:58:32.761+0200 I NETWORK  [initandlisten] waiting for connections on port 27017

To shutdown mongod you have to specify the data directory, too (if you are not using the default directory):

$ mongod --dbpath /local/mongodb/data --shutdown
killing process with pid: 18076

If you specify the logpath option, then logging will direct to that log file instead of showing up on standard console:

$ mongod --dbpath /local/mongodb/data --logpath /var/log/mongodb.log

Apache Solr

Homepage: http://lucene.apache.org/solr/
Version: 5.4

Installation

Download and extract a Solr release:

$ cd /opt
$ sudo wget http://archive.apache.org/dist/lucene/solr/5.4.1/solr-5.4.1.tgz
$ sudo tar xvfz solr-5.4.1.tgz

Resulting Solr installation directory is /opt/solr-5.4.1.

Configuration

Set SOLR_JAVA_HOME

Set the path to the Java home that Solr should use (SOLR_JAVA_HOME variable):

SuSE Linux:

# vi /etc/profile.d/solr.sh

# /etc/profile.d/solr.sh
# Adds SOLR_JAVA_HOME for solr
export SOLR_JAVA_HOME="/opt/jdk1.8.0_60"

# vi /etc/profile.d/solr.csh

# /etc/profile.d/solr.csh
# Adds SOLR_JAVA_HOME for solr
setenv SOLR_JAVA_HOME="/opt/jdk1.8.0_60"

Ubuntu Linux:

# vi /etc/environment
...
SOLR_JAVA_HOME="/opt/jdk1.8.0_60"
...

Create core

In Solr, the term core is used to refer to a single index and associated transaction log and configuration files (including the solrconfig.xml and Schema files, among others). Your Solr installation can have multiple cores if needed, which allows you to index data with different structures in the same server, and maintain more control over how your data is presented to different audiences.

Help information for creating a core:

# cd /opt/solr-5.4.1
# bin/solr create_core -help

Usage: solr create_core [-c core] [-d confdir] [-p port]

  -c <core>     Name of core to create

  -d <confdir>  Configuration directory to copy when creating the new core, built-in options are:

      basic_configs: Minimal Solr configuration
      data_driven_schema_configs: Managed schema with field-guessing support enabled
      sample_techproducts_configs: Example configuration with many optional features enabled to
         demonstrate the full power of Solr

      If not specified, default is: data_driven_schema_configs

      Alternatively, you can pass the path to your own configuration directory instead of using
      one of the built-in configurations, such as: bin/solr create_core -c mycore -d /tmp/myconfig

  -p <port>     Port of a local Solr instance where you want to create the new core
                  If not specified, the script will search the local system for a running
                  Solr instance and will use the port of the first server it finds.

Note: The configuration directories (source of copy) are located in /opt/solr-5.4.1/server/solr/configsets/.

Creating a core needs a running solr server. As we want a custom location for data (e.g. /local/data-solr), we have to start the server with param -s, see help:

# cd /opt/solr-5.4.1
# bin/solr start -help

Usage: solr start [-f] [-c] [-h hostname] [-p port] [-d directory] [-z zkHost] [-m memory] [-e example] [-s solr.solr.home] [-a "additional-options"] [-V]

...
  -s <dir>      Sets the solr.solr.home system property; Solr will create core directories under
                  this directory. This allows you to run multiple Solr instances on the same host
                  while reusing the same server directory set using the -d parameter. If set, the
                  specified directory should contain a solr.xml file, unless solr.xml exists in ZooKeeper.
                  This parameter is ignored when running examples (-e), as the solr.solr.home depends
                  on which example is run. The default value is server/solr.
...

Start server with custom home directory "/local/data-solr":

# mkdir -p /local/data-solr
(# chmod 777 /local/data-solr)
$ /opt/solr-5.4.1/bin/solr start -s /local/data-solr

Solr home directory /local/data-solr must contain a solr.xml file!

Ok, copy the file "solr.xml" to the custom home directory:

# cp /opt/solr-5.4.1/server/solr/solr.xml /local/data-solr/

Start solr:

# cd /opt/solr-5.4.1/
# bin/solr start -s /local/data-solr
Waiting up to 30 seconds to see Solr running on port 8983 [/]  
Started Solr server on port 8983 (pid=7763). Happy searching!

Create a core named "bookshelf" for our bookshelf index, using a copy of "data_driven_schema_configs":

# cd /opt/solr-5.4.1
# bin/solr create_core -c bookshelf -d data_driven_schema_configs

Copying configuration to new core instance directory:
/local/data-solr/bookshelf

Creating new core 'bookshelf' using command:
http://localhost:8983/solr/admin/cores?action=CREATE&name=bookshelf&instanceDir=bookshelf

{
  "responseHeader":{
    "status":0,
    "QTime":1492},
  "core":"bookshelf"}

The new core has been created in directory "/local/data-solr/bookshelf".

Usage

To run the Solr server with the custom home directory:

$ cd /opt/solr-5.4.1
$ sudo bin/solr start -s /local/data-solr
Waiting up to 30 seconds to see Solr running on port 8983 [/]  
Started Solr server on port 8983 (pid=2771). Happy searching!

After 30 seconds check at http://localhost:8983/, whether the server has started. You can browse the Admin GUI under http://localhost:8983/solr/.

If you're not sure if Solr is running locally, you can use the status command:

$ bin/solr status

Found 1 Solr nodes:

Solr process 2771 running on port 8983
{
  "solr_home":"/local/data-solr",
  "version":"5.4.1 1725212 - jpountz - 2016-01-18 11:51:45",
  "startTime":"2016-06-06T08:13:25.42Z",
  "uptime":"0 days, 0 hours, 3 minutes, 15 seconds",
  "memory":"73.9 MB (%15.1) of 490.7 MB"}

Stopping Solr

$ cd /opt/solr-5.4.1
$ sudo ./bin/solr stop
Sending stop command to Solr running on port 8983 ... waiting 5 seconds to allow Jetty process 7763 to stop gracefully.

Bookshelf webapp

Installation

Build the webapp locally and copy it to the server:

$ cd <source_directory_bookshelf>
$ mvn clean install

Usage

To run iiif-bookshelf, run Mongo DB and Solr.

# mongod --dbpath /local/mongodb/data --logpath /var/log/mongodb.log &
# /opt/solr-5.4.1/bin/solr start -s /local/data-solr
# java -jar iiif-bookshelf-<version>-exec.jar

Open webapp in browser: http://localhost:8080/

To stop iiif-bookshelf stop the Spring Boot app and all servers:

# /opt/solr-5.4.1/bin/solr stop -s /local/data-solr
# mongod --dbpath /local/mongodb/data --shutdown

Accessing data from 'mongo' client:

$ mongo
> use iiif-bookshelf
switched to db iiif-bookshelf

Getting all data:

> db.getCollection('iiif-manifest-summaries').find()

Deleting all data (why do you want to do this?):

> db.getCollection('iiif-manifest-summaries').drop()
true

To enable annotations install and run SimpleAnnotationServer from https://github.com/glenrobson/SimpleAnnotationServer.

The server requires Java 1.7 and Maven installed. To install SimpleAnnotationServer run the following commands in Linux:

$ git clone https://github.com/glenrobson/SimpleAnnotationServer.git

$ cd SimpleAnnotationServer

$ mvn jetty:run

Check at http://localhost:8888/index.html whether the server has started. After that one can write annotations from IIIF Bookshelf Webapp.

FAQ

What library is used to shorten description text?

see https://github.com/viralpatel/jquery.shorten

de.digitalcollections:iiif-bookshelf-webapp
Release 4.0.0

Release 4.0.0

4.0.0

3.3.0

3.2.0

3.1.3

3.1.2

3.1.1

3.1.0

3.0.0

2.9.1

2.9.0

Documentation

IIIF Bookshelf Webapp

Development Quickstart using Docker Compose

Requirements

Mongo DB

Installation

Configuration

Usage

Apache Solr

Installation

Configuration

Set SOLR_JAVA_HOME

Create core

Usage

Bookshelf webapp

Installation

Usage

FAQ

What library is used to shorten description text?

Stats

Development practices

Releases

Contributors

de.digitalcollections:iiif-bookshelf-webapp Release 4.0.0

Release 4.0.0 Toggle Dropdown 4.0.0 3.3.0 3.2.0 3.1.3 3.1.2 3.1.1 3.1.0 3.0.0 2.9.1 2.9.0

Documentation

IIIF Bookshelf Webapp

Development Quickstart using Docker Compose

Requirements

Mongo DB

Installation

Configuration

Usage

Apache Solr

Installation

Configuration

Set SOLR_JAVA_HOME

Create core

Usage

Bookshelf webapp

Installation

Usage

FAQ

What library is used to shorten description text?

Stats

Development practices

Releases

Contributors

de.digitalcollections:iiif-bookshelf-webapp
Release 4.0.0

Release 4.0.0

4.0.0

3.3.0

3.2.0

3.1.3

3.1.2

3.1.1

3.1.0

3.0.0

2.9.1

2.9.0