AUCKLAND MUSEUM WEBSITE DOCUMENTATION

Hardware, Software, Web Infrastructure

In most cases, the Museum will provide the vendor with hardware, including screens so that testing can be performed on hardware that the experience will run on in the gallery. 

PCs

The majority of Auckland Museum touchscreen digital experiences run on either Brightsigns, Intel NUCs or Custom PCs (for high spec experiences). For NUC’s and PC’s only Windows 10 Professional is supported.

Sitekiosk

NUCs and PCs are set up running SiteKiosk security software (a kiosk browser software that safeguards public access to computers). SiteKiosk launches experiences with a built in Google Chromium (not Chrome).

Sitekiosk runs a security layer that disables keyboard input, restricts access to many applications for example cmd prompt, powershell or anything else that can be a security risk.  These restrictions only apply when running on autostart.  To mimic the gallery experience please test Sitekiosk in the following way:

  • Sitekiosk must run as the restricted sitekiosk user account with autostart enabled.
  • Sitekiosk base configuration must come from the Auckland Museum ICT team.
  • Sitekiosk security manager must not be changed or have any restrictions lifted.
  • Any application code or content that will be run must not reside in the userprofile.
  • It's preferable to run any web content from a html file as sitekiosk can auto restart its built in chrome browser if there was any kind of error a wrapped executable will simply crash and not recover.
  • If an application must run from an executable any arguments must be able to be passed to the executable directly or preferably simply referenced in a configuration file.  Running batch files will fail to execute on autostart as cmd.exe is blocked.

 

Software 

  • Any application that has a dependency to run - for example a background audio application or interface, web server, database etc should run as a system service.  The service should be set up to auto recover or restart.
  • Any application that is run from outside of sitekiosk (only possible for experiences that do not require input) should be set up to autorecover where possible.  Running from a batch file is possible.  Similar to sitekiosk it should run outside of the userprofile and if at all possible run as a service.
  • Software must be compatible with our security Layer; this will include Sitekiosk, ESET Antivirus (with our configuration applied).
  • Any errors should be logged to the Windows event log, ideally all error message windows will be suppressed as it's not ideal to show an error message in the gallery environment.
  • Software should be capable of working for weeks without intervention as part of our soak testing procedure.
  • Any proprietary software requiring licensing should be well documented, with maintenance contracts provided taking into consideration the intended lifespan of the gallery.
  • Technology and software chosen should not be deprecated or nearing EOL or support.
  • For more details on the particular applications of Brightsigns and Intel NUCs at Auckland Museum please contact the digital lead on your project.

Touchscreens

  • Multi-touch screens are specified by default.
  • Touchscreens 32” and above are an integrated overlay capacitive touch style over a commercial display.
  • Touchscreens are all USB interface.
  • All touchscreens we specify are capable of portrait and landscape orientation.

Headphones

The default headphones for experiences with closed audio are ‘MKII’ Armoured Cable Headphones – Standard / AutoPlay. These are two cup headphones. Several pre 2020 experiences have single cup headphones.

Web Infrastructure

It's preferable to use API’s, IAAS platforms that are stable, with a long life cycle and requiring few updates.  Platform providers such as GCP should be considered carefully as they have a tendency to deprecate products with short notice.  Interactions/experiences should be made with technology that will still be available in 10 years with minimal maintenance.

Any hosting requirements are done by the Museum or under the Museum’s IAAS environment – any Admin or root accounts must be provided hosting by the vendor is discouraged and would require consent from the Auckland Museum ICT Team.

Any logging data for online experiences should be centralised and accessible by the Museum’s Digital Experience and ICT staff.

It must be clear any confidential User Data that will be stored in a Database, it should take into account our Audience and comply with any privacy legislation depending on the target audience e.g. Australian Privacy Principles, GDPR

Security should always be a priority – budget constraints cannot be an excuse for lax security or implementations.  Any discovered security issues due to poor design or implementation will be considered work under warranty.