How to install iGotchaSignage

• Get the zip file
  • Right-click ⇒ properties and check unlock ¹⁾
• Extract all content into a folder, usually Documents
• Make a shortcut of iGotchaSignageManager.exe to the desktop
• In Windows menu type run
• In the run window type shell:startup ²⁾
• Make a copy of the link in that folder
• Run the application
• Double click the iGotcha logo
• Enter the iGotcha Server address
  • Usually http://igotchasignage.prod.i-gotcha.com
• Enter your player ID
• Wait for content to load

• Get a FAT32 formatted SD card ( 32 Gb )
• Copy the BrightSign Firmware file on it On the NAS
• On Signage CMS, go to the settings of the player you want to set up
• Enter the Serial number of the player in the field Brightsign serial
• Set the Memory threshold override to 500Megs
• Set the Override os type to BrightSign
• Save and return to the settings tab
• Under Override os type, select the latest version of the software
• Save again

Bitbucket: Link

Written on August 16th, 2019

Lamar version: 5.0.6 iGotcha Signage version: 2.14.0.5

Update: iGS v. 2.14.0.5 resolves issue with Advanced Installer not updating the registry key to show the latest version of Lamar application on CMS.

Also, if you come across a computer that has Lamar v.3.x.x or v.4.x.x installed, then you need to uninstall the application first before you can install version 5.x.x. N.B. Lamar CMS is more reliable than iGS CMS with respect to showing Lamar version.

Note: This steps below show you how to prepare a new build for upgrading the kiosks Refer to this path in iGotcha Drive if you need to know how to set up Advanced Installer: /iGotcha Drive/Client Documentation/Lamar Transit Advertising/Update Process.docx 1. Run command to change application version: yarn run version –new-version XXXXX 2. Run command: yarn run package 3. Go to Advanced Installer on Quy's computer: Lammar_NEW_July23.aip 4. In “Product Information” section, under Product Details: change the version number in the “Version” field 5. In “Files and Folders” section, make sure that the Application Folder is directed to where the lamar build is located in the computer. At this time of writing the documentation, it's located in this path: D:\\Players\lammar\release\win-unpacked 6. In “Builds” section, under Output, change the name of the build in “MSI name” field, e.g. lamar 5.0.6 7. Click to save 8. Make a new build. The new .msi file is saved in this path: D:\\Downloads\Setup Files folder 9. Upload the msi file to AWS. Save it in this folder: “NewAdvanceInstaller” 10. Don't forget to make this file public. Once you've done that, then copy the Object URL of the msi file 11. Go back to Advanced Installer. Open another file: update_NEW_July23.aip 12. In “Updates” section, under Installer Download, paste the Object URL (from AWS) in Main URL field 13. In “Updates” section, under Update Installer, make sure that the “File path” is directed to the new msi file 14. In “Updates” section, under Update Installer, make sure that the Product version field is updated 15. Click to save 16. Click to build 17. It will create a text file for you, titled “update.txt” in Setup File folder. Upload that to AWS 18. Once it's been uploaded to AWS, then make this file public

Credentials: Please see a PM or scrum master Type of reports: Pages report and Sessions report Duration: The client usually would ask for the reports once a month. And that the Pages and Sessions data should be split into 4 reports (one for each week). In that case, there should be 8 reports total (4 for Pages reports and 4 for Sessions reports) Final format of the report: Not specified by the client. You could export the reports to Google Sheets and email the client links to these sheets. Where to generate reports on Google Analytics: Go to Customization tab –> Navigate to Custom Reports –> Click on Players Report –> Here you would find data for Sessions and Pages N.B. Previous reports are saved in Google Sheets in case you need an idea of what the reports should look like

Api keys - we use 2 APIs that require APIs key - Google Map API and Darksky (to get temperature) found here: https://bitbucket.org/igotchamedia/lammar/src/master/src/index.html

These Apis key are used in main process and are also store in config.js (see this link: https://bitbucket.org/igotchamedia/lammar/src/master/electron-resource/config.js)

Google Map API: use to render google map Use to search place (https://bitbucket.org/igotchamedia/lammar/src/master/electron-resource/google-place-search.js) Darksky Api: Used to fetch weather in Vancouver (https://bitbucket.org/igotchamedia/lammar/src/master/electron-resource/weather-service.js)