The Workforce Information Database (WID) is a prescribed structure for state LMI offices to use to maintain data resources in a predictable format. The structure contains both “Core” tables – required to be kept current by the grant – and “Non-Core” tables – defined in the structure but populated at state discretion. Only Occupational License data gets submitted externally in the WID structure. The WID standard is used in many places to help provide resources for states – it’s a data format output from various BLS programs and provides a scope for contractors offering data management and visualization services to state Labor Market Information offices. Because it’s common between states, it also provides opportunities for states to share technical tools and experience that can be more easily adapted for another state’s data environment.
The WID standard has been long established and is a core part of the IT infrastructure for many LMI offices. As technologies change and time passes, there have been a few features that are awkward, depending on the scope and extent of the data maintained by a state. Specifically, the many new versions of NAICS and MSA definitions make it difficult to sort and filter on comparable descriptors in a time series. The table and field names (set based on the character limits common in database platforms at the time) often seem cryptic and confusing to new hires. WID 3.0 addresses these problems but implementing it may require more significant state effort than past structure changes.
Because of the more substantial lift, there is an open comment period until April 21, 2023. At that time, all feedback received will be evaluated and a recommendation for adoption or not will be sent to ETA to be included as a requirement in future years, at the earliest in 2024.
Proposed WID 3.0 Structure Document
- Should the proposed WID 3.0 be implemented?
- Does the WID 3.0 structure meet your needs?
- What is likely to be the largest obstacle to adoption in your state?
- What is the biggest advantage?
- Are there any improvements that were not included that should be?
- Do you have any other comments?
Send feedback to email@example.com