IPSV in Local Government Content Management
As the world moves towards the idea of 'Web 2.0' - where information is freely distributed in a wide variety of formats and 'social-computing' methods are used to breed content, ideas, news and rich media, the underlying principle is the adoption of common standards.
The idea that information can be shared and re-distributed, indexed and searched easily is vital to ensure an open and interoperable approach to publishing.
The Integrated Public Sector Vocabulary (IPSV) is an 'encoding scheme' for populating the e-Government Metadata Standard (e-GMS) subject element of metadata. The IPSV was developed with the backing of the Department for Communities and Local Government (DCLG - formerly the Office of the Deputy Prime Minister) and the e-Government Unit (e-GU) of the Cabinet Office.
What is the IPSV used for?
The aim of using the IPSV is to make it easier for people to find what they want on networks or systems such as the internet or internal document management systems. It can also be used as a tool for helping systems to share data i.e. interoperate. IPSV provides terms to use when tagging an electronic resource, to describe what it is about.
Jadu and the IPSV
Jadu develop content management systems that deploy IPSV as the standard underlying taxonomy. Two of the main reasons are:
- As a leading provider to government, Jadu CMS is intended to enable UK government organisations to implement a Commercial, Off-The-Shelf (COTS) content management system that provides full compliance to mandated government standards.
- Because Jadu's underpinning 'semantic-web' strategy is "to make content accessible to humans and machines". The IPSV standards category list enables public content to be indexed and categorised in a standardised way - providing a standard indexing system as well as a more interoperable approach to publishing content on any device or platform.
Support is limited to ensure councils can migrate to IPSV. Some content management system (CMS) providers are exploiting councils by charging additional fees for helping them comply.
IPSV either means infrastructure changes to the content management system, or bolting on third party classification systems, which few councils can afford. Changes of this type should rest with the CMS provider and not with the council.
"Any responsible content management system provider to local government should automatically upgrade their customers' IPSV requirements to show their support to councils, who have had a lot of expenditure on IT over the past few years already," explains Suraj Kika, CEO at Jadu.
"The drive for efficiency savings in local government is in full swing and many authorities are asking questions about IPSV's return on investment, because they are having to pay so heavily to comply."Jadu successfully upgraded all its Jadu CMS local authority content management systems to be fully IPSV compliant in just two months, all without any extra expenditure or effort from its customers.