-
1.
The System Overview
-
1.1
uniFi Server
The uniFi server has multiple functions:
- It holds all content created by authors or library staff.
- It holds all data about customers, applications and devices managed by Bibliotheca technicians and developers.
- It hosts the content management sites: uniFi admin (authors/library staff) and uniFi manager (Bibliotheca techs)
- It serves application content to all devices located in the Libraries via the API
-
1.1.1
Application
Today an application can be one of three different types: touchWall, infoWall or screenSaver.
An application can be regarded as a unique container of content with specific display settings, all compliant with the type of the application.
Applications are created in the uniFi manager, where they are mapped to a Customer and a Library (branch). Furthermore the application can be paired with a device - a piece of physical hardware (PC) located at the customer (or at bibliotheca for testing).
Applications that are not paired with a device are called virtual applications. These are mostly used for development and testing, but they are also handy for demonstrating anything from a single feature to a fullblown application to new customers, before they buy.
When an application has been created, the customer can see it in the Screens section of uniFi admin site, and they can now add content (themes, articles) to it, and change its design. If it is paired with a device which is connected to the internet, the admin user can moreover push the newest application content out on the physical screen of the device. More here.
-
1.1.2
Content
Content on the uniFi+ server refers to raw author created content such as articles and themes. A theme is basically a collection of articles, and each type of theme will display its articles in its own specialized way. Contents are created in the Admin site - a manual on Admin is found at the user-faced helpsite here: http://help.transformativelibrary.com/
-
1.2
Device
A device is a term that unifies a piece of hardware including its OS, the transformativeLibrary software installed, and the content used by the uniFi software. Basically it is a PC of any type or provider located at the Library. The installed software will fetch and show the attached content on the screen connected to the device.
-
1.2.1
Hardware
Hardware types supplied by bibliotheca:
- Intel NUC (touchWalls) https://www.intel.com/content/www/us/en/products/boards-kits/nuc.html
- Intel Stick PC (infoWalls) https://www.intel.com/content/www/us/en/products/boards-kits/compute-stick.html
Legacy hardware types we no longer supply:
- Intel BRIX (touchWalls and infoWalls) https://www.gigabyte.com/Mini-PcBarebone
Furthermore the screenSaver can be installed on any bibliotheca-provided kiosk.
Customers are allowed to provide their own hardware, as long as it meets the minimum requirements:
- Windows 7 or later installed
- i5 processor
- 8Gb RAM
- 20Gb free harddisk space (could be more, depending on how much media content the customer plans to display on the screen)
-
1.2.2
Software
On the device we install the software that does the following:
- Checking its device state from the cloud - is it paired with an application, and is thus allowed to start?
- Downloads the application content from uniFi Server. The content is physically stored in a folder on the device. This procedure ensures the content is available even in case of network issues.
- Displays the content interface on screen.
- By every restart of the software (usually every morning) it looks for content updates and downloads it to the content folder. If any "old" content is locally available this is shown until the new content has been fully downloaded and is ready to display.
- It is also at restart the software checks for any new software version available
- Continuously listening to commands given from uniFi Manager or Admin site (e.g. Update Content, or Restart Computer).
-
1.2.3
Application content
Content - downloaded to the device - is a combined bundle of application settings and design, and the content (themes, articles and media) attached to the given application on the uniFi server.
-
1.2.1
-
1.1