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

THE ROLE OF THE PORTALS / LGOL CONSORTIUMS

When a portal solution exists that can provide an upload of information to the esd-toolkit on behalf of its feeder authorities, then Local Directgov will work with the portal as the agent of the participating authorities. This assumes that this will be agreed by the members of the portal groups in advance of submission.

The esd-toolkit is to be enhanced to allow the portals to become “members” of esd-toolkit in order to load the data on behalf of the portal authorities.

The technical solution will be the same except that the portal will provide multiple streams of information indexed by each authority identifier.

Exception reports will then be sent to the portal web managers who will manage the correction and re-submission of information.

LGOL consortiums that have not yet developed, or do not intend to develop, a Local Authority portal, have a role to play in assisting and coordinating participating councils in the submission of data. County wide standards and use of common CMS systems will simplify submission for councils.