Skip to content
Interface to one museum's data in museum-digital. Conceptualized to be a basic alternative to museum apps.
JavaScript CSS PHP
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
static
.gitignore
LICENSE
README.org
config.json.sample
eventsCalendar.php
exhibitionCalendar.php
index.php
manifest.webmanifest
markers.json.sample
mdCalendar.js
mdInMuseum.js
sw.js

README.org

mdinmuseum: Displaying Data

mdinmuseum is a small web app for displaying one museum’s data from museum-digital. The basic idea is to provide smaller museums with an equivalent of an in-museum app with little additional work required. It is based on the public API of museum-digital.

While it is almost completely written in JavaScript, it requires a server running PHP for settings.

Features

  • An interface to the data of a single museum from museum-digitial.
  • Event and exhibition calendar
  • “Tour”: Opening object information based on markers (requires js-aruco)

Installation

To begin the installation, clone this repository and js-aruco (the tour feature can’t be disabled yet).

git clone https://github.com/jrenslin/mdinmuseum.git .
cd static
git clone https://github.com/jcmellado/js-aruco.git
cd ..

Next, the configuration-relevant files need to be created.

cp markers.json.sample markers.json && cp config.php.sample config.php

The source instance of museum-digital and the museum ID need to be entered in config.php. Using markers.json, aruco markers can be mapped to object IDs.

To-Do

  • Make it possible to toggle the tour feature using config.json.

Notes

Fonts and icons have been removed from the public repository.

Credits

You can’t perform that action at this time.