Common Alert Protocol (CAP) - A frequently supported feature by many digital signage solutions allowing an alert message to be quickly pushed to digital signs, ‘overriding’ the existing layout content.
It is common to run into requests for this relatively frequently, especially from Universities, Health Care, or Government organizations requiring the solution to be tied into some sort of unified alerting system, (but increasingly from private companies as well). The lack of this functionality tends to make Xibo less attractive to customers looking for this built-in functionality in their RFPs, and digital signs are the obvious destination where alerting systems would want to push these emergency messages. CAP seems like the most universally established standard for this functionality.
For the dev team to fill in:
The current status and the username of the:
A broad description of the changes required.
Which parts of Xibo are effected
DB Schema Changes
Any necessary DB Schema Changes
This is an interesting request - almost all of the hard work for this is done already (push messaging, layout overrides, etc) and in use via API integrations with other commercial alerting systems.
I’m not clear on how the CAP feed arrives at the CMS though - is it designed to be pushed or pulled?
That’s a good question. I’m guessing it’s pulled. I know it’s an XML based technology, and I am aware of some resources that may clarify that, however:
Here’s the Wikipedia link: https://en.wikipedia.org/wiki/Common_Alerting_Protocol
Here’s the link to the OASIS CAP 1.2 specification: http://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.html
And here’s a link to an existing PHP library for handling CAP on Git: https://github.com/AT-backbone/Cap-PHP-library
I imagine these might help?
After poking around a bit more, it looks like some implementations allow for push and pull sources, although I’m not sure what the mechanism behind this is, (https://www.weather.gov/documentation/services-web-alerts lists both push and pull sources for CAP content).
Hope this helps. But we are currently using a paid for digital display software that is able to switch to the alerts automatically. Most of the work is done by the emergency software, it creates a rss\xml. Through the CMS I was able to have the players parse the xml for a trigger word to either turn the emergency template on or off. Due to the high cost we are looking for an alternative.
No it isn’t; unfortunately it is one of those features that is requested occasionally, but never as much as other things. Its been raised again as something we should think about for 4.1 or 4.2.
Understood. This may not be true in other countries, but here in the U.S., if you don’t support this, you’re automatically disqualified from most K12 and college/university campuses. They wouldn’t request as a feature because Xibo wouldn’t be far enough along in the process for someone to even entertain Xibo as a contender to begin with.
That’s an interesting insight, thank you. I’ll make a note of that against our log of the feature request so we can give it the proper weight.