How to Guide: Data Collection for Local Directgov Programme

• Local DirectGov    Programme
• Top 5 Benefits for Local    Authorites
• What Data is Needed for     Phase 2?
• How to Collect the data
• Manual Data Collection
• CSV Files (Spreadsheet)    Data Collection
• XML Data Collection
• Guidance on Selecting    and Entering URLs into    the esd-toolkit
• Sustaining the Links    with Local Directgov
• What Support will you    get?
• The Role of the    Portals/LGOL Consortiums
• Key Dates
• Metadata
• Overview of Technical    Approach for Local    DirectGov
• Using a CMS to Provide    the Required Data
• Sources of Information
• Appendix A. Local    DirectGov Projects
• Appendix B. FAQ
• Appendix C. Who's Who in    the Local DirectGov    Programme?
• Appendix D. Customer    Journey
• Appendix E. An    Introduction to    Metadata
• Appendix F. Controlled    Lists
• Appendix G. List of    Engagement Support    Assignments

USING A CMS TO PROVIDE THE REQUIRED DATA

As part of its national engagement strategy, LDG is working with CMS suppliers to develop the best way forward to support Local Authorities in their use of the LDG XML schema. This includes developing and maintaining a CMS Suppliers Forum, and working with the different CMS user groups to develop common practice and protocols.

We would encourage Local Authority Web Managers to speak to their CMS suppliers about how best to implement LDG within their authority. If an authority has a Content Management System in place, a schema has been developed as part of Local Directgov to allow Local Authorities to be able to populate esd-toolkit by exporting information from the CMS in a defined XML format which can then be uploaded to esd-toolkit. The XML structure is defined by a series of schema files, Version 1.0 of the schemas can be found at these addresses:

• http://www.esd.org.uk/standards/XmlSchemas/LocalDirectgov -v1.0.xsd.
• http://www.esd.org.uk/standards/XmlSchemas/WebPortal-v1.0.xsd.

The schemas define the structure of an XML ‘file’ (used in this document to mean any electronic source of XML data) containing information for a single public sector agency.

The XML file defines the services offered by the agency and associated guidance in the form of Frequently Asked Questions (FAQs).

Services are defined in a hierarchical structure going from broad service areas at the top of the hierarchy to more narrow services and, at the bottom (also known as ‘leaf’) layer, interactions supporting service delivery.

The number of levels in the hierarchy is not prescribed in order that the service data of most Local Authorities can readily be transformed into the Local Directgov format whether that information is held in a deep hierarchical structure or just as a flat list of services and associated interactions (or just interactions). Practically, a hierarchy (typically of about three levels) means that searches may result in broad service headings being found from where one may drill down to a specific service interaction. Such searches lead to only a manageable number of matching results and expose users (citizens, businesses, other agencies, etc) to information on related services about which they might not have known.

FAQ information is defined separately from services and cross-referenced with services.

Both services (including related interactions) and FAQs contain metadata that cross-references with national standard lists at www.esd.org.uk/standards. Some tagging against these lists is required and more tagging is supported.

Additional tagging against local vocabularies is supported. By extending the complex type ItemReferenceStructure, an agency can declare its own scheme names for metadata elements.

It is best to pass these schemas onto the person responsible for the content management system. When the schemas are used in conjunction with the content management system, the export will conform to a structure that can be understood by the esd-toolkit software. This export, in XML format, can then be uploaded to esd-toolkit, populating the access channel URLs that LDG will collect.

If you have any questions about how this relates to your own Local Authority CMS system, please contact a member of your Engagement team.